Owners and leadership

How to build standard operating procedures for construction

Write SOPs for the handful of processes that cost money when they go wrong, keep each one to a page or a short checklist, have the people who do the work help write and test it, and review them on a schedule.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

To build standard operating procedures for construction, start with the 8 to 12 processes where mistakes cost real money: estimate-to-project handoff, change orders, pay applications, purchasing, subcontractor onboarding, daily logs, job closeout, and new-hire onboarding. Write each as a one-page checklist with a trigger, an owner, the steps, and the definition of done. Have the person who does the work draft it, test it on a live job, fix it, and train the team. Then review each SOP once a year or whenever it fails. Short and used beats long and perfect.

Most contractors run on knowledge in people's heads. That works until the person who knows how pay apps get assembled goes on vacation, or the company adds its fourth PM and every job gets run a different way. SOPs turn the owner's way of doing things into the company's way.

Which construction processes need an SOP first

Pick processes that repeat, involve more than one person, and cost money or time when they fail. A good starting list:

High-value SOPs for a contractor
ProcessOwnerWhat goes wrong without it
Estimate to project handoffEstimator and PMField builds what was not priced; assumptions are lost
Change ordersPMWork done without a signed change; no payment
Pay applications and invoicingPM and billingLate or rejected pay apps; slow cash
Purchasing and POsPM or purchasingOver-budget buys, wrong cost codes, late deliveries
Subcontractor onboardingPM and officeExpired insurance, missing scope letters, unsigned subcontracts
Daily logsSuperintendent or foremanNo record for delays or disputes
Job closeoutPMRetainage held for months over missing documents
Employee onboardingOffice and field leadMissing paperwork, unsafe first week

How to write a construction SOP, step by step

  1. Pick one process. Start with the one that hurt most last quarter. Do not try to write the whole manual in a month.
  2. Watch it happen. Have the person who does the work walk you through a real example. Note each step, every form, and every handoff.
  3. Write the trigger and the done. What starts the process (signed contract, change request from owner) and what finished looks like (signed change order in the system, budget updated).
  4. List the steps in order. Short verb-first lines. "Enter the change in the change order log. Price it with the standard burden and markup. Send to the owner within 3 business days."
  5. Name one owner per step. If a step has no name, it will not happen.
  6. Attach the tools. Link the template, form, or screen used in each step.
  7. Test on a live job. Have someone other than the author follow it. Every question they ask is a gap in the SOP.
  8. Train and launch. Walk the team through it at a meeting, then use it. Spot-check the first few times.
  9. Set a review date. Once a year, or right after the process fails.

What a good SOP looks like

One page. A title, purpose in one sentence, trigger, owner, numbered steps, links to forms, and the definition of done. Anything longer than two pages usually means it is really two processes. Write it at the reading level of a new hire, not a 20-year veteran.

Checklists for the field

Field SOPs work best as checklists on a phone or a laminated card: pre-pour inspection, end-of-day site securing, equipment start-up checks. Keep them short enough to use with gloves on. Safety procedures that come from regulations should link back to the official requirement and to your site safety plan.

Process maps for the office

Office processes with several handoffs, like billing or change orders, are often clearer as a simple flow: who does what, in which order, and what they hand to the next person. A box-and-arrow sketch often fixes more confusion than paragraphs of text.

Worked example: a change order SOP

As an example, a $7 million mechanical contractor finds that roughly a third of its field changes in the last year were done before anyone priced them, and some were never billed. The operations manager and two PMs write a one-page change order SOP:

  1. Trigger: anyone hears of a change in scope, verbal or written.
  2. Foreman notes it in the daily log the same day with photos.
  3. PM opens a line in the change order log within one business day.
  4. PM prices it using the standard labor rates, burden, overhead, and markup, and sends it within three business days.
  5. No work starts on changes over $2,500 without a signed change order or written directive, unless it is a safety issue (then the PM notifies the owner in writing the same day).
  6. Once signed, billing adds it to the next pay app and the PM updates the budget.
  7. Done: signed change order, budget updated, change billed.

They test it on two jobs for a month. The foremen point out that they cannot tell which changes are over $2,500, so the rule becomes "call the PM before doing anything not on the drawings." After the fix, the PM opens the line the same day, and the owner reviews the change order log weekly. For more detail, see how to get change orders signed before doing the work.

How long it takes to build a set of SOPs

Plan on one or two SOPs a month, not a manual in a weekend. At that pace a contractor has its core set in six to nine months, each one tested on real jobs. Put the next SOP on the leadership meeting action list with a name and a date, the same as any other project. The companies that finish are the ones that treat SOP writing as part of the job, not something to do when it rains.

Mistakes to avoid when building SOPs

  • Writing in the office alone. SOPs written without the people who do the work get ignored in the field.
  • Writing a binder nobody opens. Store SOPs where the work happens: in the job folder, the app, or taped to the plan table.
  • Too much detail. Explain decisions and handoffs, not how to use a tape measure.
  • No owner for the SOP itself. Someone must update it when the process changes.
  • Never enforcing it. If the owner skips the change order SOP for a favorite customer, the PMs will too.

Templates and tools that support SOPs

Most SOPs point to a form. Start with the construction change order template, construction daily report template, subcontractor scope of work template, and project closeout checklist. Related reading: how to hand off a job from estimating to operations and how to onboard new construction employees.

Smart Business Automator builds common SOP steps into the workflow, such as change order approvals, invoice routing, and subcontractor document checks, so the process runs the same way on every job. See construction workflow automation.

Frequently asked questions

What is an SOP in construction?

A standard operating procedure is a written, step-by-step description of how a recurring task is done in your company, such as processing a change order or onboarding a subcontractor.

How many SOPs does a construction company need?

Start with 8 to 12 covering the processes that cost the most when they fail. Add more only when a process keeps going wrong or the company grows into new work.

Who should write construction SOPs?

The people who do the work should draft them, with a manager reviewing for consistency. That keeps them accurate and makes the team more likely to follow them.

How long should an SOP be?

One page for most processes. If it runs longer than two pages, it is usually two separate processes.

How do I get crews to follow SOPs?

Involve them in writing, keep field SOPs short and on the phone or a card, spot-check use, and make sure leaders follow them too.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment