A construction SOP is worth writing only if it governs a decision your company makes every week, by more than one person, where a wrong call costs money. By that test most builders need six: estimate approval, the sale-to-production handoff, change orders, the weekly lookahead, the daily log and billing — money in and money out. Everything else is a legal requirement with its own format, a reference document or a habit that does not need a binder.

Why the binder goes unread

Most SOP libraries are written once — usually after a bad job, or before someone tries to sell the company — filed in a shared drive and never opened again. The reason is structural. They describe tasks, like how to file an RFI, instead of decisions, like who can approve a price change and up to what amount. A task procedure gets read once, during onboarding. A decision procedure gets used every time the decision comes up, because it settles an argument before it starts.

The second failure is length. A 40-page operations manual has no first page anyone needs on a Tuesday morning. The third is the missing trigger. A procedure with no event that starts it is optional, and optional procedures are skipped on busy weeks — which is every week. "When a client asks for anything outside the signed scope" is a trigger. "Change order management" is a chapter heading.

Before writing any procedure, ask three questions. Does this decision come up at least weekly? Do two or more people make it? Has getting it wrong cost money on a job in the last year? Three yeses and it earns a page. Fewer, and it belongs in a checklist or nowhere.

The six, at a glance

Each procedure has an event that starts it, one person who owns it and a record it leaves behind. If you cannot name all three, the procedure is not finished.

  • Estimate approval — trigger: a bid is ready to send — owner: estimator, with owner sign-off below a set margin — record: a locked, versioned estimate the contract references.
  • Sale-to-production handoff — trigger: contract signed — owner: project manager — record: a budget and baseline schedule built from the estimate lines.
  • Change order — trigger: any work, material or time outside the signed scope — owner: project manager, signed by the client — record: a signed change order with price and schedule impact.
  • Weekly lookahead — trigger: a fixed day each week — owner: project manager or superintendent — record: a three-week lookahead with each sub confirmed.
  • Daily log — trigger: end of every site day — owner: superintendent — record: a dated log with crew, weather, deliveries, delays and photos.
  • Billing and paying out — trigger: the billing date, or a sub invoice arriving — owner: bookkeeper — record: an invoice sent, or a payment matched to approved scope and a lien waiver.

What each procedure has to settle

1. Estimate approval

The decision: is this number ready to leave the building? The procedure fixes which rate library the estimate uses — one shared library, not each estimator's personal spreadsheet. It names who checks takeoff quantities, sets the markup floor below which the owner signs off, and requires allowances listed with dollar values and exclusions written out in full. The version sent to the client is locked. Revisions get a new version number, and the contract cites the one that was signed.

2. Sale-to-production handoff

The decision: what is production now committed to? Budget lines come from the estimate line items, not retyped into a second system where they drift. The baseline schedule is built from the same estimate. A 30-minute handoff between whoever sold the job and whoever runs it covers allowances, exclusions, long-lead items and anything promised to the client that is not in the contract. That last category is where margin leaks — the window brand mentioned on a site walk, the finish date said out loud. Written down, it is a commitment the PM can plan for. Unwritten, it is a surprise in month four.

3. Change orders

The decision: does this get done, at what price and with how many days added? The steps are short. Identify the change. Price it from the same rate library as the original estimate. State the schedule impact in days, even when the answer is zero. Get the client's signature before work starts. Update the budget and schedule from the signed document. The procedure also says who in the field can approve anything with a cost attached — usually nobody below the PM.

This is the procedure most likely to cost money if ignored. A change done on a verbal yes becomes a negotiation at final billing, when the work is finished and the client has no reason to agree to your number. For genuine emergencies — water coming in, an inspector's correction — write a field directive on time and materials, photograph the condition and record it in that day's log. Price it within the week and get it signed.

4. Weekly lookahead

The decision: who is on site, when, and have they confirmed? Pick a fixed day. Look three weeks out. Every sub on the lookahead confirms by a set time, and an unconfirmed slot gets a phone call, not a second email. Inspections and material deliveries sit on the same lookahead, because a missed delivery moves trades as surely as a missed sub. The mechanics of running this well are in our piece on subcontractor management built on the lookahead, so they are not repeated here.

5. Daily log

The decision: what happened today that someone might dispute later? The fields are fixed: date, crew count by trade, weather, deliveries, inspections, delays with their cause, visitors and photos. Delay claims and change disputes turn on contemporaneous records, so a log written on Friday for the whole week is worth less than five daily entries. Keep it to about five minutes. A log that takes half an hour gets skipped, and a skipped log is a gap in the one record that protects the job.

6. Billing and paying out

The decision: who gets paid, how much and against what? Money in: bill on a fixed cadence tied to the draw schedule or schedule progress, include only signed change orders and track retainage by job. Money out: match each sub invoice to approved scope and signed changes, then collect a waiver before releasing payment — the difference between conditional and unconditional matters, and it is covered in how lien waivers work in construction. In BuilderSolve, purchase orders are in development and not shipped, so the purchasing side of this procedure still lives in QuickBooks, which stays your book of record.

What stays off the list

Leaving something off the six does not mean it does not matter. It means it is a different kind of document.

  • Safety program — required, and its format is set by your insurer, your jurisdiction and the work you do. It is not optional and it is not this kind of procedure.
  • Document naming and filing — a rule, not a decision. It is covered in construction document control as an enforced naming rule.
  • Hiring, time off and vehicle use — the employee handbook. Necessary, but not a decision made across jobs every week.
  • RFIs and submittals — on commercial work these can earn a seventh procedure. For most residential builders they fold into the weekly lookahead.
  • Closeout and punchlist — happens once per job. A checklist covers it; a procedure is more paper than the decision needs.

How to write one that gets used

Hold every construction SOP to one page and one format: trigger, owner, the decision being made, numbered steps — roughly seven at most — the record it produces and where that record lives. If it needs a second page, it is describing two decisions. Split it.

Then put it where the work happens. A procedure in a binder competes with memory, and memory wins on a busy day. A procedure built into the tools does not need to be remembered: a change order that cannot go to the client without a price and a schedule impact, a daily log form with the fields already there, a schedule that comes from the estimate rather than being rebuilt. That is how job management that runs from the estimate is set up in BuilderSolve — line-item estimating on a shared rate library, scheduling built from it, daily logs, change orders with an audit trail and budget against actual. The AI assistant drafts change orders, logs, schedule shifts and time entries, and a person approves or rejects each one. That approval step is the procedure.

Review the six once a quarter, and do it against a job, not a document. Take the last job that came in under margin and ask which of the six decisions went wrong. The answer tells you which page to rewrite.

Who runs them

Procedures fail most often when their owner is also running three jobs. Estimate checks, change order paperwork, billing and sub payments are back-office work, and they slip first when the field gets busy. Some builders hire an estimator, a project coordinator and a bookkeeper. Others use a trained construction back-office team that runs estimating, operations and admin, and finance against these same procedures, priced at roughly 60% less than hiring those roles. Either way, each of the six needs a named owner whose job it actually is.

What to do this week

  1. Pull the last two jobs that finished under margin. For each, name which of the six decisions went wrong.
  2. Write that one procedure first — one page, with trigger, owner, decision, steps and record.
  3. Run it on every active job for 30 days before starting the next one.
  4. Archive any existing SOP that nobody has opened in a year. It is not doing anything.
  5. Add the next procedure only once the first one is happening without anyone reminding the team.

Common questions

what is a construction SOP

A construction SOP is a written procedure that settles a repeated decision the same way every time — who approves an estimate, when a change order gets signed, what goes in a daily log. A useful one names the event that starts it, the person who owns it, the steps and the record it produces. If it describes a task rather than a decision, it rarely gets used after onboarding.

how many SOPs does a construction company need

Most builders running 5-40 jobs need six: estimate approval, the sale-to-production handoff, change orders, the weekly lookahead, the daily log and billing and paying out. A procedure earns a place if the decision comes up weekly, involves more than one person and has cost money when it went wrong. Commercial builders may add RFIs and submittals as a seventh.

what should a change order SOP include

A change order SOP should require the client's signature before any work starts. The steps: identify the change, price it from the same rate library as the original estimate, state the schedule impact in days, get it signed, then update budget and schedule. It should also name who can approve costed changes in the field, and cover emergencies with a time-and-materials directive and same-day photos.

what goes in a construction daily log

A construction daily log should record the date, crew count by trade, weather, deliveries, inspections, delays with their cause, visitors and photos. Write it at the end of each site day, not at the end of the week. Disputes over delays and changes turn on contemporaneous records, and a log that takes about five minutes is far more likely to get filled in every day.

should construction SOPs be in a binder or in software

Procedures work best when built into the tools the team already uses, because a binder relies on memory. If the change order form requires a price and schedule impact, or the daily log has fixed fields, the procedure runs without anyone looking it up. Keep a one-page written version for training and quarterly review, but let the workflow do the enforcing.