What you signed on day one, and what it asks of you
You signed the ORIGIN Culture and Code of Conduct on your first day, and most people never open it again. This section takes it apart in the order it will reach you. Act 01 Section 02 teaches the six values; this is the mechanics.
What you signed
The Code is version 4.0, dated March 2026, and confidential. It covers all four contract types with some sections switched off for some of them, so find your own type in the applicability matrix at the front before assuming a rule applies to you. It is also scored, out of 150 points, weighted heaviest on values and culture.
Source: Register tab 13 rows 2, 3 and 4
How ORIGIN communicates, and where a decision becomes real
Asana is the single source of truth. If it is not in Asana, it does not exist.
- Asana holds the work: tasks, status, deadlines, approvals, links. Discussion about a task happens in that task, as comments.
- WhatsApp is conversation, not documentation. Email is everything external: client communication and client files. There are no internal emails at ORIGIN.
- Meetings run on Teams and every one is recorded with Loom Notetaker, the only approved tool, link on the task.
- Files are linked in Asana from OneDrive or SharePoint, and client files never go out over WhatsApp.
- In your core overlap hours, set by your Team Lead or Line Manager: WhatsApp within 60 minutes, Asana within 2 hours, email within 4 hours.
THE 24 HOUR RULE
A decision made on a call or in WhatsApp goes into the Asana task as a comment within 24 hours, and so do meeting action items. Until it is in Asana, it has not happened.
Source: Register tab 8 rows 9 to 12; tab 3 rows 4, 5, 9, 11
Asana standards
- Every task has a named owner, a due date and a project, and the owner updates status daily. Not the manager.
- Use an @mention when you need someone to review or act. Without it they are not notified, and you have not asked.
- If your line manager asks you on a call to change a task, you update Asana. Not them.
Source: The Code, Asana Standards
Your time and deadlines
Weekly timesheets are mandatory for FTE, Part-Time and Hourly; Project-Based is exempt. Time is allocated per client and project, submitted at the end of the business week, Thursday, or Wednesday if Thursday is an off day, and your line manager must approve it. They must be at least 80 percent accurate, so log daily. ORIGIN also tracks hours in HubStaff.
Source: Register tab 8 row 13; tab 3 row 19
A deadline can be moved. Missing one in silence cannot be. To move one you tell your line manager at least 24 hours before it falls due, they approve the change on Asana with a comment on the new due date, and both of you acknowledge it. Without that, missed deadlines escalate over a rolling three month period: verbal warning in Asana, written warning in your file, then termination. The Code calls this non-negotiable, and a small task counts the same as a large one.
Source: Register tab 13 row 5
THE BREACH IS THE SILENCE
The Code says plainly that flagging a risk early is ownership, not failure. The breach is not the slip.
Money and credentials
- Expenses apply to FTE and Part-Time, and nothing is reimbursed without pre-approval and a receipt. Raise a subtask in your Asana Expenses project with the expense, amount and purpose, assigned to your line manager.
- Spend only after they approve, upload the receipt within 48 hours, then tag the Head of Finance. Reimbursement follows within 30 days. A verbal approval is not one.
- Passwords, API keys, payment methods and client credentials are never shared over WhatsApp, email, Asana comments, screenshots or any unencrypted channel.
- Share every credential you create only with the company admin, for the company password manager. Payment credentials go through that manager or the Head of Finance secure channel, and client payment data never sits on a personal device.
Source: Register tab 13 rows 11 and 13
What is confidential, and who owns the work
- Client information, business strategy, internal process and financial data are confidential, and that survives your employment.
- Work you create with ORIGIN tools, time or resources belongs to ORIGIN, and client deliverables are ORIGIN property until the MSA transfers them.
- ORIGIN and client data live on approved tools only, with OneDrive and SharePoint the file standard. No personal devices, cloud or email. 2FA is mandatory.
- On exit, every file leaves your devices within 48 hours, confirmed in writing, and you may not do business with an ORIGIN client for 3 years.
- Any side business, freelancing or advisory role needs written CEO approval. No FTE freelances independently; opportunities come to ORIGIN, which routes or approves them.
Source: Register tab 13 rows 8 and 12
A referral bonus exists when you bring work in. It is capped, case by case, never automatic, and the figure is read from register tab 13 row 10 and tab 4 row 26 when applied.
Source: Register tab 13 row 10; tab 4 row 26
Naming a client, and naming a file
This is where a new hire does damage fastest, usually with good intentions, in a post or a deck.
| The rule | What it means for you |
|---|---|
| ORIGIN is always uppercase | Never Origin, never origin. Everything else is sentence case, never Title Case or all capitals. |
| Only cleared names go public | Only the 34 names cleared on 17 July 2026, listed in the profile fact base, may appear in public marketing. A prospect or pipeline name is never proof. |
| Three names sit behind the white label wall | EY, Talemia and SDL are never named in public facing content, whatever else is cleared. |
| Every file carries the naming standard | CLIENT NAME - DOCUMENT TITLE - INITIALS - DDMMYYYY - VERSION, ORIGIN as the client name internally. Initials and date lock at creation; later editors move the version. |
| No commercial rate travels in your writing | Margins, floors and multipliers are read from register tab 4 rows 7 and 9 when needed. The one figure you may state plainly is VAT at 15 percent in KSA. |
Source: Register tab 6 rows 2, 3, 18, 19, 20; tab 8 rows 15, 18; tab 4 rows 5, 7, 9
Townhalls, and when the Code is broken
Townhalls are mandatory for FTE and Part-Time, encouraged for Hourly and Project-Based, and non-negotiable when you are asked in person. Absence without prior approval is a breach. Cameras stay on in every meeting.
Source: Register tab 13 row 14; tab 8 row 11
The disciplinary path has three steps: a documented verbal warning, a written warning in your file, then termination. Some things skip it and mean immediate dismissal: breach of client confidentiality, theft or fraud, violence, gaslighting, gossiping, an undisclosed side business.
You also have a right of reply. A warning you believe is wrong goes to the Conflict Resolution Assembly: your line manager, the HR in charge and one core team member. File in writing with HR within 48 hours of notice. The panel decides unanimously within 7 business days, or the CEO rules. One dispute per quarter, and immediate termination offences are not disputable.
Source: Register tab 13 rows 6 and 7
THE LINE THAT MATTERS
The Code is signed, not read. Your signature is already on file, and from your first week you are measured against every rule in it whether or not anyone walked you through it.