Every contractor knows how to start a job. The question is whether they know how to start a job they’re not on. That is what a documented job start process answers.

The SOP Baseline from Article 32 identifies which processes need documentation. The job start process is the first one to build. It is the SOP that runs every day, on every job, by whoever is in charge. It is also the SOP most often done differently depending on who shows up.

This article is about the repeatable job start process. It is different from the pre-job documentation in Article 11. That article covers what to document about this specific job before mobilization. This article covers the standard sequence every job follows when the crew arrives on site.

The Job Start SOP is four steps that together ensure every job begins from the same conditions, regardless of who is running it.

Why Job Starts Vary and What That Costs

The obvious problem is inconsistency. The owner who starts a job knows to check access, confirm scope, brief the crew, and stage tools before the first task. The lead who hasn’t been taught that sequence skips some steps and improvises others. The job starts differently every time based on who is first on site.

The less visible cost is the mid-job discovery. A scope detail that should have been confirmed at job start surfaces on day three. A sub’s arrival time that should have been coordinated in the morning becomes a delay by noon. The problems that appear mid-job were preventable by a consistent job start.

The deepest cost is the owner dependency it creates. An owner who knows that jobs start differently when they’re not there cannot leave. Every job requires their presence at startup. The documented job start SOP is what removes that dependency.

The Job Start SOP

The Job Start SOP is four steps that run in sequence at the start of every work day. Each step takes two to five minutes. Together they take less than fifteen minutes and produce a consistent starting condition for the day’s work.

Step 1 confirms the site is ready before the crew starts work

Step 1 is the site check: access, hazards, staging, and any conditions that affect the day’s work. The lead does a brief walk of the site before any tools come off the truck.

What they are looking for: Is access clear for the crew and materials? Are there any conditions that have changed since yesterday that affect today’s scope? Is the staging area ready for the first task?

Step 2 orients the client at the start of each work day

Step 2 is the client check-in: a brief conversation about what the crew will accomplish today and what the client needs to know.

Most clients who become difficult do so because they did not know what to expect from the day. A thirty-second check-in at job start changes that. The lead tells the client what’s happening today, when the crew will leave, and whether anything affects access.

Step 3 briefs the crew on the day’s scope and sequence

Step 3 is the crew brief: three minutes where the lead tells the crew what they’re doing, in what order, and the handoffs. This is also where the Toolbox Talk from the field safety system runs.

The crew brief is not a meeting. It is a brief. The lead talks, the crew listens, everyone knows their first task before the first tool comes out.

Step 4 confirms the day’s progress at the end of the day

Step 4 is the day-end confirmation: what was accomplished, what is staged for tomorrow, and what the client needs to know before the crew leaves. One minute at the end of the day prevents the calls that come in after hours.

Before: The lead arrives and the crew starts based on what they remember from yesterday. After: The first fifteen minutes of every day follow the same four-step sequence, regardless of who is running the job.

How the Conductor Surfaces the Job Start SOP

The lead is running a job the owner is not on. Before the crew starts, they ask the Conductor for the job start steps.

The job start SOP lives in the Living Library, organized in the Operations Collection alongside the other process documentation the business has built. The Conductor reads from that collection and surfaces the job start checklist. The four steps, the site-specific notes, and any flagged conditions from the last time this job type was run.

The lead runs the start from the document rather than from memory. Every step is completed before the first tool comes out. The owner did not need to be there.

Write the SOP From What You Actually Do

Don’t write the job start SOP from memory. Observe yourself starting the next job and write down what you actually do.

The step sequence will be clearer from observation than from recollection. Things you do automatically that you would not have included in a written list will surface when you watch yourself work through the actual start.

Write the four steps from that observation. Then refine them on the next three starts. The SOP that reflects what actually happens is more useful than the one that reflects what you think should happen.

When the Job Start Is Documented, the Owner Can Leave

A job start that runs the same way regardless of who is in charge is a job start that doesn’t require the owner. That is the value of the Job Start SOP: not consistency for its own sake, but the freedom it creates for the owner. Try Kiluma free for 14 days at kiluma.ai.