A business running on good intentions and no systems
The company had ambitions for how operations should run. They had discussed what processes they wanted to build. But nothing had ever been committed to, documented, or trained. The gap between intention and reality was wide — and getting wider as the company grew.
Jobs were running over budget. Foremen were arriving on site without adequate preparation. Administrative tasks were falling apart. And because no reporting infrastructure existed to quantify the damage, the problem was felt everywhere but understood nowhere.
Every job was carrying a hidden cost — and no one could see it
The most damaging pattern was in pre-job planning. Foremen were arriving on site without preparation — plans were being made on the day, after the crew had already arrived. That single failure cascaded into overrun hours, inaccurate quotes, strained client expectations, and crew performance issues that repeated job after job.
When I built the budgeted vs actual reporting system alongside the operational work, the scale of the problem became measurable for the first time. Jobs were routinely exceeding their estimated hours by 15 to 30% — a figure that had been felt anecdotally but never confirmed. Confirmed, it changed everything.
Jobs were routinely running 15–30% over estimated hours — confirmed through the budgeted vs actual tracking I built as part of this engagement. Before this system existed, the overrun was felt but unmeasurable. After, it could be identified at the job level, addressed at the planning stage, and corrected before it compounded.
- No documented processes across any area of field operations — ideas existed, commitment did not.
- Foremen arrived on site without preparation — job planning happened after the crew was already there.
- Jobs routinely exceeding estimated hours by 15–30%, affecting quotes, billing, client satisfaction, and crew performance.
- No PM-to-foreman communication structure — foremen felt thrown into jobs without context or a plan.
- Administrative tasks like receipts and spend tracking were inconsistent and unreliable.
This wasn't a training issue. It was a systems gap.
The business had capable people. It had strong demand. The owner had clear expectations — in his head. What it didn't have was a consistent way to start a job, a shared standard for execution, clear ownership at the crew level, or a structure that removed reliance on memory and judgment calls.
Execution depended on who showed up — not on how the business ran. That's not a people problem. That's a structure problem. And structure is what I build.
Four SOPs. One complete operational day. Accountability at every stage.
I designed and implemented a field execution system built for real-world use — simple, repeatable, and owned by the people doing the work. I built four SOPs covering every critical moment of the operational day, each designed as a visual field-ready booklet rather than a policy document.
Critically, I designed the Pre-Job Planning SOP to break the pattern of foremen arriving unprepared — introducing a mandatory three-signatory checkpoint and a two working day lead time that forced preparation to happen before anyone arrived on site.
- 3-signatory sign-off required
- 2 working day lead time
- Site review checklist
- Utility locate responsibilities
- Crew briefing requirements
- Phase A: Crew Lead at yard
- Phase B: Full crew on site
- LMN sign-in workflow
- Equipment checks
- Daily briefing structure
- Site setup standards
- Safety perimeter requirements
- Equipment positioning
- Client communication Day 1
- Layout confirmation process
- Site cleanup standards
- Equipment storage and checks
- Daily reporting requirements
- Receipt submission process
- LMN closeout workflow
Pre-Job Planning Sign-Off Checkpoint
Required before any job beginsOverrun hours don't just affect one job
When jobs consistently run 15–30% over their allocated hours, the impact compounds across every function that depends on accurate data.
Processes the field actually uses — built at the source of the problem
The most important measure of an SOP is not whether it was written. It's whether it was adopted. I built these SOPs for adoption from the start — plain language, visual formats, field-ready booklets a crew member could reference on site without interpretation. I validated them with senior foremen before rollout and embedded them through the crew orientation.
- Four field-ready SOPs designed and deployed covering the complete operational day — Pre-Job Planning, Start of Day, Jobsite Setup, and End of Day Closeout.
- Jobs running 15–30% over estimated hours — previously felt but unmeasurable — identified, quantified, and addressable at the planning stage for the first time.
- A mandatory pre-job planning checkpoint that broke the pattern of foremen arriving unprepared, forcing PM-to-foreman alignment two working days before site arrival.
- Administrative tasks — receipts, spend tracking, daily reporting — brought into a defined process with clear ownership and deadlines.
- Field buy-in achieved through foreman consultation before finalisation — the crew helped shape the standards they were asked to follow.
Most growing field businesses don't have a people problem. They have a structure problem.
When execution lives in people's heads, performance is inconsistent, growth creates pressure, and leaders become bottlenecks. When execution lives in systems, work becomes repeatable, teams become accountable, and growth becomes manageable. The difference isn't hiring better people. It's building better structure around the people you already have.
The problem was never that the crew didn't know how to do the work. It was that no one had defined how the work should be done.
Once the standards existed, were trained, and had accountability built in — the crew followed them. Jobs that had been running 15–30% over budget had a structural fix for the first time.
Are your crews operating to a standard — or to a guess?
If your field operations rely on individual judgment rather than defined process, every job carries the cost of that inconsistency. I can identify where your execution breaks — and fix it at the system level.
Start with a focused Operational Sprint →