Standard Operating Procedures

The reality

A founder runs a 38 person MEP contracting firm in Abu Dhabi. AED 14M (USD 3.8M) last year, three active sites, a senior project manager who has been with the business for nine years. The senior PM knows every client preference, supplier quirk, and shortcut for getting municipality approvals on time. None of it is written down.

Last year the senior PM went on medical leave for six weeks. Within ten days, two projects missed submission deadlines. A junior engineer sent an incorrect BOQ (bill of quantities, the line-by-line list of materials and labour priced into a construction or fitout project) to a client because nobody had told him about the internal review step. The founder spent his evenings on WhatsApp putting out fires the senior PM would have caught at 8am. The cost of the six weeks of chaos was roughly AED 180,000 (USD 49,000) in rework and penalties. The cost of writing five SOPs after the senior PM came back was two afternoons.

Read this if

• A senior team member is the only person who knows how a critical process actually works
• A new hire takes three months to handle a deliverable independently because nobody documented how
• The same kind of mistake recurs at the same step every quarter
• Quality varies depending on which team member runs the project
• The founder fields the same operational questions on WhatsApp every evening
• An auditor or new enterprise client asking how the work flows would receive a different answer from each team member

What dysfunction costs

When the method lives only in one or two heads, the business is a few absences away from a quarter of pain.

Continuity cost. When the senior person is on leave, on a flight, or moves to a competitor, the team rebuilds the work from memory and pays for the gaps over the next two quarters. The cost rarely shows as one line item. It shows as a missed deadline, a rework charge, a client query that took six emails to answer, and the founder back in operational detail. Single-point dependence is covered in Depth Before Width.

Compliance cost. In regulated work (Emiratisation reviews, MOHRE audits, ISO certifications, regulator inspections), the absence of written method is the absence of proof. A role that exists in someone's head looks the same on paper as a role that does not exist at all.

What success looks like

When SOPs are a discipline:

• The top five revenue or compliance tasks each have a one-page SOP with a named owner
• A new hire can read the SOP and run the task at 70 percent quality on day one
• The team members who do the work wrote the first draft of the SOPs for their roles
• SOPs include a screen recording or photo sequence where language or detail makes pure text harder to follow
• Each SOP has a quarterly review date, and at least one has been updated based on team feedback in the last quarter
• An auditor or new enterprise client could be shown the SOP without a week of preparation

The framework

SOPs run as four layers. Skip a layer and the document collects dust.

Layer 1: Pick the right tasks

Not every task needs an SOP. The 70 percent rule decides what does. If a task happens at least 70 percent the same way each time, it earns documentation. A client proposal has a standard structure, standard pricing logic, and standard approval steps. A negotiation with a difficult landlord on a unique lease term is mostly judgment, and judgment cannot be written down.

The behaviour to adopt this week: list the team's repeated work for one week. Mark which tasks pass the 70 percent test. Pick the five highest-leverage ones to start with.

Layer 2: The person doing the work writes the first draft

Documents written by managers in meeting rooms describe the theoretical process. The team that runs the work knows the real one. The first draft of every SOP comes from the person who does the task. The founder edits. The author is whoever opens the file when the work needs to be done.

The behaviour to adopt this week: pick the most expensive task from Layer 1. Sit with the person who runs it for 30 minutes. Capture the steps in their words. Edit later.

Layer 3: One page, visuals where they help

The reason most SOPs collect dust is that they are too long. One page is the working maximum. Seven fields cover most cases: title, owner, trigger, steps, tools, output, and exceptions. A team with members whose first language is Arabic, Hindi, Urdu, Tagalog, or Malayalam reads photos and 90 second screen recordings faster than English paragraphs. The format respects the people who will actually use it. The 70 percent rule applies to compliance too: an SOP followed 70 percent of the time beats a perfect SOP followed never.

The behaviour to adopt this week: take the captured steps from Layer 2 and force them onto one page in the seven fields. If they do not fit, the task is too broad. Split it.

Layer 4: Real use, real review

A SOP without a quarterly review by its owner dates fast. Eighteen months later, the tool has changed and the steps no longer match the work. The team stops opening the file, then stops trusting the system, then writes off the whole effort as something the founder tried once.

The behaviour to adopt this week: roll out the SOP in a 10 minute team walkthrough. Two weeks later, ask which steps got skipped. Fix the cause of skipping before adding more SOPs.

A founder you might recognise

A founder runs a 32 person recruitment business in DIFC. The team places senior candidates across financial services and tech. Onboarding a new consultant has historically taken three to four months. During the ramp-up, the new hire produces minimal billable work while senior consultants spend half their time fielding questions. The founder accepted this as a fixed cost of the business.

In the first quarter of 2026 the founder sat with two senior consultants over four afternoons. They captured five SOPs covering candidate sourcing, intake calls, search note structure, the qualification rubric, and the client report template. The first SOP took 90 minutes to write. The fifth took 40. Each one was one page with a screen recording embedded.

The next consultant joined in March. He was running independent searches in week three. By week six he was billing on his first placement. The documents had made the previous juniors look slow in retrospect, by changing what the team could hand a new hire on day one. The same pages now sit in the team's onboarding folder. A future hire, or a future agent answering candidate-fit questions over a CRM, inherits them in week one.

Working through it

1. List the team's repeated work for one week. Pick five tasks that pass the 70 percent test. Quoting, onboarding, project closeout, invoicing, and client reporting are the usual suspects. Pick the ones with the highest leverage in revenue, compliance, or onboarding speed.

2. Sit for 30 minutes with the person who does the task. Capture the steps in their words. The first draft is theirs and editing comes later. The founder's mental model is a hypothesis to test against the team's reality.

3. Force the steps onto one page in seven fields: title, owner, trigger, steps, tools, output, exceptions. If the task does not fit, it is too broad. Split it.

4. Roll the SOP out in a 10 minute team walkthrough. Owner explains, team asks questions, agree the date it takes effect. The walkthrough is the difference between a file and a discipline.

5. Two weeks later, ask which steps got skipped. Fix the cause of skipping before adding the next SOP. Cadence matters more than coverage.

The deeper working session, with the SOP template, the 70 percent compliance principle, the rollout protocol, and the founder exercise, lives in Standard Operating Procedures: Core Work.

Common mistakes

• Writing SOPs for everything at once. Five revenue tasks first. Land those, then move on. The team that tries to document 30 SOPs in a quarter ships none.
• Making SOPs too detailed. "Open Chrome and click the address bar" insults the team. Write for a competent adult who knows the basics but does not know your specific method.
• Never updating them. An SOP written 18 months ago for a tool you no longer use confuses more than no SOP at all. Each one needs a quarterly review by its owner.
• Skipping the rollout. The 10 minute walkthrough is half the value. Without it, the SOP is a file nobody opens.
• Treating SOPs as control. If the team reads SOPs as surveillance, they will resist. Frame them as how a new person gets good fast. The framing decides whether the team writes alongside the founder or hides from the discipline.

Self-assessment

Y or N for each.

1. Do your top five revenue or compliance tasks each have a one-page SOP with a named owner?
2. Was the first draft of each SOP written by the person who does the work?
3. Can a new hire read an SOP and run the task at 70 percent quality on day one?
4. Do your SOPs include visuals (photos, screen recordings) where the team has multiple first languages?
5. Is each SOP scheduled for a quarterly review by its named owner?
6. Has at least one SOP been updated in the last quarter based on team feedback or skipped steps?
7. Could you show an SOP to an auditor, a regulator, or a new enterprise client without a week of preparation?

Five or more "yes" answers means the team's knowledge has left people's heads and joined the operating system. Three or four is the band where the founder has started but the discipline has not yet taken root. Two or fewer means the business is one departure or one audit away from a quarter of pain.