The job that ran well last Tuesday ran poorly this Tuesday: same job type, different crew. The problem is not the crew. The problem is that the way to do it right lives in the owner’s head and nowhere else.

Standard operating procedures, or SOPs, are not bureaucratic documents for large companies. For a trades business, an SOP is the documented way to do a recurring task correctly. Without documented process, the business depends on the owner being physically present to produce a consistent result. That dependency is what limits how the business can grow.

SOPs do not take weeks to build. The most valuable ones take thirty minutes each. The business that builds the SOP for its five highest-impact recurring processes has most of what it needs.

The SOP Baseline is three components that give the business a starting point for systematic documentation. The goal is not a library of policy manuals. It is a small set of clear documents the crew can actually use.

Why the Same Problems Keep Recurring

The obvious problem is that undocumented processes drift. The job that was done right the first time gets done differently the second time because the first-time approach was never captured. The second crew member does it the way they learned it, which may or may not match the first.

The less visible cost is the compounding. An undocumented process that produces inconsistent results will produce inconsistent results on every similar job, for every crew, until it is documented. The owner who fixes the problem on-site without writing down the fix will fix it again next time.

The deepest cost is the ceiling it creates. A business built on undocumented processes can only be run by the owner, present for every job. Article 33 addresses the most impactful SOP to build first. But before building it, the business needs to know what processes exist.

The SOP Baseline

The SOP Baseline is three components that together give the business a complete picture of what processes exist, which ones to document first, and what a useful SOP looks like in practice.

Component 1 identifies every recurring process the business runs

Component 1 is the process inventory: a simple list of every recurring task the business performs. Not every task. The tasks that happen on most jobs or most weeks and whose outcomes vary depending on who does them.

The list for most small trades businesses runs ten to twenty items. Job setup, materials ordering, sub briefing, daily progress reporting, punch list, and job closeout. Each item on the list is a candidate for an SOP.

Component 2 prioritizes which processes to document first by impact

Component 2 is the prioritization filter: for each process on the list, ask two questions. First: how often does this process go wrong? Second: when it goes wrong, what does it cost?

The processes that go wrong frequently and cost the most in time, margin, or client satisfaction go to the top of the list. The first three to five SOPs the business writes should be the ones where documentation will change the most.

Component 3 defines what a useful SOP looks like for trades work

Component 3 is the documentation standard: a simple format that produces a useful SOP in thirty minutes. Not a policy document. Not a training manual.

A trades SOP has four elements: what the process is for, who performs it, the steps in order, and what completion looks like. One page. Plain language. Specific enough that a person doing it for the first time can follow it correctly.

Before: The job startup process varies by crew. Some steps get missed. The owner addresses issues on-site. After: The job startup SOP is one page, followed by every crew lead, producing the same starting conditions on every job.

How the Living Library Keeps Your SOP Picture Current

An owner who has never mapped their documented processes does not know what they have and what they are missing. The diagnosis usually produces a surprise: the business has been running on memory for years, with almost nothing formally captured.

With the Operations Collection active in the Library, the SOP picture is maintained and visible. The Library organizes the documented SOPs by process type and flags where documentation is absent. The Conductor reads across that picture and returns the gap map. Which priority processes are documented, which are missing, and which were documented but not updated when the process changed.

The owner leaves that query knowing where to spend the next two hours.

Write the Job Start SOP Before the Next Job Starts

Don’t build the full SOP Baseline before the next job. Build the one SOP that would have the most immediate impact.

For most trades businesses, that is the job start SOP: what the crew checks and who does what before work begins. Write that one first, in thirty minutes, using the four-element format from Component 3. Put it on the job site at the next start.

Do the same for the next high-impact process the following week. After five weeks, the five most important SOPs exist.

The Business That Runs the Same Way Every Time

The same problems keep recurring because the same undocumented processes keep producing the same inconsistent results. The SOP Baseline is the starting point for changing that. Every process documented is one fewer problem the owner has to solve in person. Try Kiluma free for 14 days at kiluma.ai.