Why Do Construction Companies Keep Repeating the Same Expensive Mistakes?

Construction companies repeat the same expensive mistakes because the lesson lives in the wrong place. It sits in one senior person's head, or it gets logged into a register nobody opens until an audit. Neither one is a system. So the next project relearns the lesson at full price, and the price is usually five figures.

This came up in a recent r/GeneralContractor discussion started by a civil engineer in tier-one construction. His point landed because every builder recognizes it. A problem hits a new job that somebody already solved on another job. There is no practical way to find that out. The knowledge either walks out the door with a person or dies in a document.

Here is the thing most owners miss. This is not a memory problem. It is a systems problem. And a systems problem has a systems fix.

Run the Skill Match assessment if you want to see where your own knowledge is trapped before you read the fix.

What is the most common contractor mistake?

The most common contractor mistake is treating hard-won knowledge as a person instead of a system. Your best estimator knows which subs no-show in July. Your lead PM knows the framing detail that failed inspection twice. That knowledge is real, and it is worth money. It is also stored in exactly one place, and that place drives home at 5 PM.

Builders in narrow, repetitive work feel this the sharpest. If you build the same kind of home over and over, repetition should make errors easy to kill. Instead the same errors keep showing up, because the fix never left the head of the person who found it.

The register was supposed to solve this. A place to write down what went wrong so it never happens again. In practice the register becomes a graveyard. People write to it after a project, and nobody reads from it before the next one. A document that only gets opened during an audit is not a system. It is a filing cabinet you pay to ignore.

The number that should stop you cold

Rework is the tax you pay for repeating mistakes. The Construction Industry Institute puts direct field rework at an average of 5% of total project cost, with a range of 2 to 20 percent depending on the job. On a $1.5M custom home, 5 percent is $75,000. That is not a rounding error. That is a person's salary, redone work, and a margin you already spent.

Now the part that ties rework straight to the knowledge problem. A 2018 study by PlanGrid and FMI surveyed nearly 600 construction professionals. It found that 48% of all rework traces to two causes: poor communication at 26 percent and bad or missing project data at 22 percent. Almost half of your redone work starts as information that did not get where it needed to go.

The same report put U.S. rework tied to communication and missing information at more than $31 billion a year. It also found $177.5 billion in annual U.S. labor lost to non-optimal activity, which means fixing mistakes, hunting for project data, and resolving conflict over who said what.

Read those numbers again with your own jobs in mind. Half of your rework is a message that never landed and a fact nobody could find. That is the lessons-learned graveyard, measured in dollars.

What are 90% of accidents caused by?

The old safety rule of thumb credits most incidents to the worker. In the 1930s, Herbert Heinrich reviewed thousands of accident reports and concluded that 88% of workplace accidents came from unsafe acts, not unsafe conditions. Over the decades that 88 percent got rounded up to the "95 percent is human error" line you still hear on job sites.

So why does that matter for your operation? Modern safety science pushed back hard on Heinrich, and the correction is the whole point. His numbers came from supervisor reports that blamed workers without investigating the root cause. The real driver of most incidents is the system around the person, not the person.

That is the same lesson your operation keeps skipping. When the same mistake repeats, the reflex is to blame the guy who made it. Write him up. Move on. But if it keeps happening across different people, the person was never the cause. The system that let it happen was the cause. Safety figured this out and built controls around it. Operations mostly did not.

Why your lessons-learned register is a graveyard

Three things turn a lessons-learned document into a graveyard. Each one is fixable.

First, it is written to, never read from. The register lives at the end of the project, when everyone is exhausted and moving to the next job. Nobody builds a habit of opening it at the start of the next one. So it grows and grows and gets less usable the bigger it gets.

Second, it is idealized. Most SOPs describe how work is supposed to go, not how it really goes. They skip the bottleneck, the miscommunication, and the part where the sub shows up a day early. A document that pretends the mess does not exist cannot help you fix the mess.

Third, it was handed down, not built up. When a procedure gets written by one person and dropped on the crew, the crew treats it like homework. They skim it and sign the acknowledgment. Training modules and mandatory reading are famous for going in one eye and out the other. People follow a procedure they helped write. They ignore one that was handed to them.

That last point is the hinge. It is the difference between a document that changes behavior and a document that collects dust.

Every Beyond the Bid episode digs into how real builders turn tribal knowledge into a system that runs without them. Listen if you want the field version of this playbook.

Who pays when a contractor makes a mistake?

On a repeated mistake, you pay. Not the sub, not the client, not the person who forgot. The company eats it, and it eats it quietly, one job at a time.

This shows up most clearly in change orders. The pattern we see with remodelers is brutal and consistent. Roughly $2,847 per project in changes that get done but never invoiced. About 40 percent of change orders never billed at all. That adds up to near $91,000 a year walking out the door on a shop doing steady volume, plus about three disputes per project over work nobody wrote down.

Every one of those is a repeated mistake. The verbal approval that never became a signed change order. The scope creep nobody logged. The crew added the lumber, the invoice total never moved, and the margin left the building. It is the same lesson, unlearned, on every job.

The reason it repeats is the same reason the register is a graveyard. The fix lives in one person's discipline instead of a system the whole team runs. When that person is busy, distracted, or gone, the leak opens right back up.

When your best PM leaves, the company relearns everything

One builder in that thread made the honest counterpoint. He said keeping experienced PMs and holding both staff and subs accountable had cut his repeat mistakes. Nobody wants to keep absorbing five-figure losses on the same error. Fair. That works.

Then he got pressed on it. Does that actually solve the problem, or does it just work as long as the right people stay? His answer was straight. It works while people stick around.

That is the trap. In 2024, according to CFMA data, construction turnover ran about 14.5%, and larger contractors ran higher, near 16.5 percent. Call it one in seven people on your team turning over in a year. When your knowledge lives in people, a 14.5 percent turnover rate is a 14.5 percent knowledge loss rate. Every departure restarts the learning curve, and the company pays tuition again.

A business that only runs while the right people stay is not a system. It is a bet. The whole point of building an operation is so it does not depend on any single person, including you.

The fix: build the SOP your crew helped write, then pick the tool

Builders do not need more software. They need documented process first, then the simplest tool to run it. Reach for an app before the process exists and you get shelf-ware. Here is the sequence that makes a lesson stick.

Map how the work actually happens. Not the clean version. The real one, with the bottleneck and the handoff that fails. Pull the crew into a room and whiteboard the process the way it runs on a bad Tuesday. The Association of Professional Builders teaches this same discipline for builder business systems, and it works because the people who do the work own the map.

Test it by hand, ten times or more. Run the process manually on real jobs before you touch a tool. Watch where it breaks. Fix it. Manual reps are how you find the gap between the SOP you imagined and the SOP that survives contact with a job site. This is field-level operational detail, the kind good building science gets right, and the lesson holds: the process has to work on paper before it works in an app.

Turn it into a checklist people help shape. A short checklist beats a thick binder every time. Keep it to the steps that actually prevent the mistake. When someone hits a new failure, they update the checklist. That is what makes it a living document instead of a graveyard.

Then pick the simplest tool to run the proven process. Now, and only now, put it in a tool. Every tool has to pass one test. A non-technical person on your team is operational in under an hour. If it fails that, it is the wrong tool. For most residential builders, this is where a platform like JobTread earns its keep, because it runs the process you already proved instead of forcing you to invent one.

Notice what changes. The lesson stops being a person and becomes a step in a checklist the crew helped write. The next job runs the step whether or not the person who learned it is still around.

What "using" a lesson actually looks like

The strongest answers in that thread all pointed the same direction. Stop treating the register as a place to write and start treating the process as a thing you run.

One project manager in telecom construction described a peer review step. Before documents go to the authority having jurisdiction, the team redlines them and pushes for revisions first. His guiding rule was simple. Get people talking, and make everyone at every level voice concerns out loud instead of assuming someone else will catch it. The mistake gets caught before it gets built.

A continuous-improvement operator gave the most complete version. Write SOPs for the tasks you repeat most. Document how the work really happens, mess and all. When a mistake occurs, revisit the SOP and update it so it cannot happen the same way twice. Use the document actively, for training and accountability, and let the people doing the work shape it.

That is the difference between a lesson learned and a lesson filed. Modern Craftsman talks often about the owner who is the single point of failure in his own company. This is how you climb out. The knowledge lives in a process the team runs, not in your head or a binder nobody opens.

The format of the document matters less than whether anyone opens it before the next mistake. Get that right and the same five-figure error stops showing up on job after job.

Questions builders are asking

Who pays when a contractor makes a mistake? On a repeated mistake, the company pays, and it pays quietly. The client rarely covers rework caused by your own miss, and the sub only covers it when you documented the scope well enough to hold them to it. That is why undocumented change orders bleed roughly $91,000 a year on a busy remodeling shop. The fix is a system that captures the change before the work starts, not after.

What type of contract has the most risk for a contractor? The one with the loosest scope. A fixed-bid job with vague scope carries the most risk, because every gray area comes out of your margin. Cost-plus shifts some risk to the client but only if your documentation is clean. The contract type matters less than whether your process forces scope and changes to get written down before anyone swings a hammer.

What are 90% of accidents caused by? The old line credits about 88 to 95 percent to human error, from Heinrich's 1930s data. The modern correction is the useful part. Most incidents trace to the system around the person, not the person. The same logic applies to your operational mistakes. If it repeats across different people, the system is the cause.

What are the signs your own company has a systems problem? Reframe the "bad contractor" question at your own shop. The signs: only one person can quote a job, the same mistake shows up on multiple projects, knowledge leaves when a PM leaves, and your lessons-learned document only opens during an audit. Any two of those means the knowledge lives in people, not a system.

What's next

You have two moves from here.

First, find out where your own knowledge is trapped. The Skill Match assessment shows you which of your operation's lessons live in a person instead of a system, and which one is costing you the most right now. It takes a few minutes and it is built for a builder, not a technician.

Second, hear how other builders climbed out. Beyond the Bid is where residential builders and remodelers walk through turning tribal knowledge into an operating system that runs without them. Subscribe and take the next episode with you to the job site.