What World Class Contracting Actually Looks Like on the Ground
Most contractors talk a big game about world class standards and then deliver exactly what they quoted, when they quoted, and no more. That is fine for residential repaints. It falls apart the moment you are managing a commercial job with twenty trades, change orders flying in every direction, and a project manager who has never held a hardhat. World Class Contracting by Gregory Garrett is less of a branded system and more of a set of operating habits that separate the builders who finish on budget from the ones who are still chasing retainers two years later. I first ran into this approach when a general contractor on a mixed-use renovation in Charlotte was bleeding about $40,000 on change order administration alone. He was doing everything by email and paper. Subcontractors were submitting verbal scope changes, getting vague verbal approval, and then billing whatever they felt like at the end of the month. The gap between what was authorized and what was being paid was massive. That is exactly the problem World Class Contracting Gregory Garrett was built to solve.
World Class Contracting Gregory Garrett Approach Explained
The core mechanism is straightforward. You create a mandatory change order protocol before the first shovel hits dirt. Every scope deviation, whether it comes from an architect, a homeowner, or a hidden condition you did not see on the initial walk, gets logged through a standardized form. The form requires a dollar figure, a schedule impact, and a signature before work proceeds. Not after. Before. That single rule stops the revenue leak that kills most mid-size contractors. The second piece is the pre-construction documentation pack. This is not just your drawings and specifications. It is a written scope narrative that explicitly states what is excluded. I found this part almost more important than what is included. When you spell out exactly what is not in the contract, the number of surprise change orders drops by roughly sixty percent in my experience. You need to list things like existing condition assumptions, material substitution protocols, and how delay claims will be handled. Then there is the subcontractor flow-down clause. This is where most people mess up. Your prime contract might have strict change order procedures, but if your subs are working off a different set of rules, you end up eating the difference. Every subcontract needs a flow-down clause that mirrors your owner contract terms. I use a standard addendum that takes about ten minutes to attach and has saved me from three separate bad situations in the last year alone.
The scheduling component uses a look-ahead method instead of relying on the master schedule once it is baselined. The master schedule is filed away and referenced monthly. Every two weeks you pull the next three-week window and verify it with each trade lead directly. This catches drift early. A two-day slip on framing becomes a two-week crisis by the time drywall is scheduled if you are not checking back regularly. I spend about ninety minutes every other Friday doing these look-aheads and it prevents whole categories of schedule damage.
Get the Full Details
The Practical Setup and Why It Is Not for Everyone
Setting up this system takes time. If you are running a three-person operation and closing deals through word of mouth, the full documentation stack feels like overkill. I would recommend starting with just the change order protocol and the exclusion list in your scope narratives. Those two pieces alone will likely pay for themselves on your first project after implementation. The rest can come online gradually over a few months. You need a digital document system that all parties can access. Something like Procore, Buildertrend, or even a well-organized Google Drive folder if you are keeping costs down. The software does not matter as much as the discipline of using it consistently. I have seen contractors spend thousands on fancy tools and still run change orders through text messages. That is worse than nothing because it creates a false sense of control while the actual processes remain unmanaged. Here is a specific edge case I ran into last fall that illustrates why the flow-down clauses matter. We had a mechanical subcontractor who pulled out mid-project on a medical office build. Their original bid was solid, but when the owner changed the HVAC zoning plan halfway through, the sub claimed it was a major change and demanded a twenty-two percent increase. Because I had the flow-down clause in place referencing the prime contract change procedure, we were able to invoke the same process they signed up under. The dispute was resolved in three weeks instead of dragging into something that would have needed a lien or arbitration. Without that clause, I would have been arguing from a position of weakness with no contractual leverage.
There are real limitations to this approach. It does not help if your team refuses to follow procedures. I know contractors who tried to implement World Class Contracting principles and failed because their project managers treated the paperwork as administrative busywork rather than a control mechanism. The forms get filled out, but the signatures are rubber-stamped without review. That is not world class contracting. That is a paperwork theater that wastes time and creates a false audit trail. Another limitation is the upfront cost. For small residential jobs under a hundred thousand dollars, the administrative overhead of full documentation can eat into your margin. You are spending billable hours on contract administration instead of field supervision. I usually recommend a scaled-down version for smaller jobs: a written scope with exclusions, a simple change order template, and a weekly coordination meeting. That gives you eighty percent of the benefit with twenty percent of the effort.
Implementation Steps That Actually Work
Start with your contract templates. If you are still using a one-page agreement you found online in 2019, you need to replace it. Get a construction attorney involved. The cost is probably less than one bad change order dispute. The new contract should include your change order protocol, your flow-down clause requirement, your schedule update expectations, and your documentation standards. Next, build the change order form. It needs fields for a description of the change, the cost impact, the schedule impact, the authorizing party, and the date. Keep it to one page. If it is longer, nobody will fill it out correctly. I use a simple digital form that routes to the project manager for approval and then to the client for signature. The average change order takes about eight minutes to process through this system. Before implementing it, the same process took two days of back-and-forth emails and phone calls. Train your team on the system before you put it on a live project. I run a half-day workshop with my project managers and superintendents where we walk through five real scenarios and practice filling out the forms. This usually takes about three hours total and ensures everyone understands when a change order is required versus when it is just a routine adjustment. Most disputes come from people not knowing the difference.
For the pre-construction documentation pack, compile your drawings, specifications, geotechnical reports, and any environmental assessments. Write the scope narrative in plain language. Avoid legal jargon where possible. If a subcontractor reading it cannot understand what is included and what is not, your architect probably would not have caught the ambiguity either. I have revised scope narratives three times before sending them out because the first two drafts were too vague for my own standards. The look-ahead scheduling process requires buy-in from your trade partners. Call them individually and explain that you will be reviewing the next three weeks every two weeks. Most will appreciate it because it gives them visibility into upcoming work. Some will push back because they prefer the flexibility of not having a fixed short-term plan. Those are the ones who tend to cause problems later. A firm but friendly conversation usually resolves the resistance within the first week.
Common Mistakes That Undermine the Whole System
The biggest mistake I see is incomplete documentation. People fill out the forms but skip the attachments. A change order without the supporting photos, emails, or sketches is just a claim waiting to be disputed. Always attach the evidence. This habit alone has prevented two payment disputes for me in the last eighteen months. Another mistake is inconsistent enforcement. You establish a strict change order protocol, and then you verbally approve a five-thousand-dollar change on a job site because the client is pressuring you and you do not want to slow things down. Now your entire system loses credibility. Every subsequent change order will be questioned because you proved you are willing to bypass the process when it is inconvenient. Consistency matters more than speed. A two-day delay to process a change order correctly saves weeks of argument later. There is also the mistake of treating the system as a one-time setup. Contracts need updating as laws change and as you learn from your own projects. I review and revise my contract templates every six months. Each project teaches you something about where your previous templates were weak. The ones from my early years in commercial contracting look almost amateurish compared to what I use now. That is normal. The improvement comes from actively maintaining the documents rather than assuming they are finished products.
Finally, do not confuse documentation with bureaucracy. The goal is clear communication and risk management, not creating paperwork for its own sake. If a process does not serve those goals, it should be simplified or eliminated. World Class Contracting Gregory Garrett is about discipline, not volume. The best systems I have seen are the ones that are thorough but not exhausting to use. When your team can complete the required documentation in under ten minutes per task, you know you have struck the right balance.
