One of the things we do for contractors every month is prepare a WIP schedule. Owners ask for it because of the numbers: percent complete, over- and under-billings, projected margin by job. But the output that often ends up mattering most is not a number. It is the list of operational fixes that fall out of the process of building it.
That is because you cannot build an accurate WIP without asking project managers a lot of questions. What is the current contract value? Which change orders are approved and which are still pending? What is left to spend on this job? Have we billed everything we have earned? And when we ask those questions, we see the same pattern at almost every contractor we work with.
The pattern
When a project manager is unsure about a job's status, its billings, or what is actually in scope, the uncertainty almost never comes from the PM not knowing the job. It comes from confusion in the underlying documentation. Who has what, and where is it?
- The owner sent a scope change, but it went to the super in a text message and never reached the PM.
- The super and the PM both know a problem is coming on the job. Nobody wrote it down, so the owner hears about it when the bill shows up.
- The super knows a change order was approved in the field. The PM is still carrying it as pending. Accounting has no record of it at all.
- The contract exists, but there are three versions in three inboxes and nobody is sure which one was signed.
Every one of those is an information problem, not a competence problem. Someone had the information. It just was not where the next person could find it.
Why it happens
On most jobs, every stakeholder keeps records in whatever way works for them. The PM has a folder on a laptop. The super has photos and texts on a phone. The owner has an email thread. The office has whatever got forwarded to it. Each system makes sense to the person who built it, and none of them match.
So when a question comes up, answering it means a scavenger hunt. Who has the latest version? Was the approval an email or a text? The PM spends an hour chasing paper instead of running the job, and the answer is only as good as what turned up.
The fix is not sophisticated
What helps is a standard operating procedure for documentation. Not a software purchase. Not a reorganization. A written agreement, across the company, on four things:
- What gets stored. Contracts, change orders, RFIs, submittals, daily logs, pay applications, owner correspondence, closeout documents. The list is finite, and it is the same on every job.
- When it gets stored. A signed change order goes in the folder the day it is signed, not at month-end. A daily log goes in the same day.
- How it gets stored. One naming convention on every job, so the file name tells you the job number, the document type, and the date before you open it.
- Where it gets stored. One folder structure, identical on every job, so the person who worked Job 2412 last year can find the change orders on Job 2501 today without asking anyone.
Two things this does
First, it puts the burden where it belongs. When the procedure says the super uploads the daily log and the PM files the signed change order, every stakeholder owes the team their piece of the record. Nobody gets to hold information in their head, their inbox, or their truck. Contributing to the shared record becomes part of the job, not a favor.
Second, it creates confidence. When files are stored and named the same way on every project, the team stops wondering whether the answer exists and starts going to get it. A PM who knows exactly where the approved change orders live on every job can answer the owner's billing question in five minutes instead of an afternoon. That confidence compounds: people trust the record, so they use it, so it gets better.
Consistency is what makes both of those work. No one filing system is better than another. What matters is that the same system runs on every job, so finding and sharing documentation stops being a skill a few people have and becomes a habit the whole company has.
Sometimes the biggest problems have the easiest fixes
The problems that grow out of scattered documentation are expensive: scope arguments with owners, billings that go out late, surprises at month-end, project managers who spend their time hunting instead of managing. The fix costs almost nothing to write and a few weeks of discipline to install. And the payoff shows up in places you would not expect, starting with a cleaner WIP.
If you want help putting one in place, that is part of what our business operations consulting does. Book a call.
Get your job documentation working for the team
Levvigo helps contractors put practical documentation procedures in place, clarify responsibilities, and connect the field with accounting. Learn more about our business operations consulting.
Book a call with Levvigo to discuss your documentation process and where your team needs support.
