What Public Works CM Teams Are Still Doing in Spreadsheets (And Why It’s a Risk)

The honest truth about Construction Management Software in Public Works

If you’re on the owner or CM side of a public works project, there’s a good chance you’re using software you genuinely like for some things — and spreadsheets for everything else.

That’s not a criticism. It’s just where the industry is.

Tools like Procore have become something close to a field standard, and for good reason. The RFI and submittal routing is excellent — ball-in-court tracking keeps everyone accountable, and the workflow is genuinely hard to argue with. The mobile daily log application is something the whole industry should aspire to. These are real strengths, and teams that have adopted them are better off for it.

But here’s what I’ve noticed after 25 years managing public works projects: the software that was built for construction contractors — even great software — wasn’t designed around the specific contractual obligations that exist on the owner’s side of a public works project.

And those gaps? They’re still being filled with spreadsheets.

Continue reading to learn more about what I see most often.

Gap 1: Weekly Statements of Working Days

On a public works project, the Weekly Statement of Working Days is a contractual document. It tracks the number of working days charged against the contract, compares actual days worked against the contract baseline, and becomes critical evidence if a contractor submits a time extension claim.

Most teams are generating these manually — pulling from daily reports, checking weather records, counting backward from the contract start date. Some are doing it in Excel. Some are reconstructing it at the end of the project when a dispute arises.

💡 What it should look like: a calendar that automatically compares contract days to actual days, generates the weekly statement, and creates a running record that’s defensible from day one.

Gap 2: Bulletins — Field Directives and Cost Requests

When an owner needs to direct a change in the field — whether it’s a design modification, a response to unforeseen conditions, or a clarification — that direction needs to go to the contractor in writing. The document that does this is a Bulletin.

A Bulletin can reference the RFIs and submittals that led to the change. It can issue a cost request to the contractor, track their response, and feed into the change order process. It creates the paper trail that connects a field condition to a contract modification.

🚨 Most teams are doing this in Word or email. The connection between the Bulletin, the RFI it references, and the change order it generates lives in someone’s memory — or doesn’t exist at all.

Gap 3: Quantity Tracking for Pay Requests

Contractor software tracks cost codes. Owner-side public works CM tracks bid items.

These are not the same thing — and the difference matters enormously on state and federally funded projects where pay requests require specific backup documentation by bid item, tied to field measurements and inspector confirmation.

💡 What most teams need is quantity tracking that captures daily quantities by bid item, supports the backup required for progress payments, and produces a pay request that an owner can actually review and approve — not a contractor billing document reformatted for the owner’s use.

Gap 4: Pay Requests That Work for the Owner

Related to the above: the pay request workflow on a public works project runs from contractor submission through CM review through owner approval. That routing — with the ability for the owner to review, comment, request backup, and approve — is different from a contractor’s billing process.

🚨 Most owner-side CM teams are either adapting contractor-facing pay request tools or building their own process in spreadsheets and email. Neither is great when a funding agency asks for documentation of how a payment was reviewed and approved.

Gap 5: Change Orders That Tell the Whole Story

A change order on a public works project isn’t just a cost adjustment. It should include a memo explaining each item — what triggered it, how it’s being paid (force account, agreed price, unit price), how many additional working days are being granted for that extra work, and how those days connect back to the weekly statements.

And critically: once a change order is executed, the extra work items in it should be trackable on daily reports. Your inspectors should be able to log hours and equipment against a specific change order item, so the force account backup is being built in real time — not reconstructed later.

🚨 Most teams write change orders in Word templates. The connection between the change order, the daily reports, and the working day tracking is manual at best.

What happens when all of this lives in one place

Each of these gaps is a problem on its own. Together, they create a much bigger one: when a contractor submits a claim — or a labor compliance question comes up, or a funding agency asks for documentation, or a public records request lands — you’re pulling from five different places to build a coherent picture:

▶️ Weekly statements from a spreadsheet.

▶️ Quantity backup from another spreadsheet.

▶️ Change order memos from a Word folder.

▶️ Daily reports from your CM platform.

▶️ RFI history from your routing software.

The documents exist. They’re just not connected. And the time you spend connecting them manually — under deadline, under pressure, is exactly when the gaps in your documentation become visible.

The Bottom Line: have multiple tools, but make sure it’s actually a system

There’s nothing wrong with using more than one platform. Most public works CM teams do, and it works for them. What matters is that your team knows what gets documented where, that nothing falls through the cracks between tools, and that when you need to reconstruct a project record — for a claim, an audit, a PRA — you can actually do it without spending days hunting.

If you’re generating Weekly Statements by hand, tracking quantities in a spreadsheet, and writing change order memos in Word — that’s not a system. That’s a collection of workarounds. Make it intentional: document your process, assign ownership, and make sure every contractual obligation has a clear home.

How BridgeDoc approaches this

BridgeDoc Core is built specifically for the owner-side gaps described above — Weekly Statements of Working Days generated automatically from your project calendar, Bulletins that reference your RFIs and submittals, quantity tracking by bid item for pay request backup, pay request routing for owner review and approval, and change orders that connect to your daily reports so force account backup is built in real time.

BridgeDoc InSite is the layer on top — connecting your Core data, your existing CM platform data, and any other project documents you upload into a single searchable source. When a claim comes in, you ask one question in plain language and pull working day records, RFI history, daily reports, and change order documentation together in one query, with citations back to every source document.

If you’re already using software you like for RFI and submittal routing and mobile daily logs — keep it. We’re built to work alongside it, not replace it.

Want to see how BridgeDoc fills those gaps?

Book your FREE demo with me HERE!

 Kelly Wheeler is a PE and QSD with 25 years of experience in construction management for public agencies. She is the founder and CEO of BridgeDoc, a construction management software company built for public works CM teams.