The report your office rebuilds every week

Walk into almost any GC’s office on a Thursday afternoon and you’ll find the same scene: a project manager, or sometimes the owner, assembling the weekly owner report by hand. Progress notes from the super’s texts. Photos off somebody’s phone, renamed one by one. Cost numbers exported from the ERP into a spreadsheet, reformatted, pasted into Word. Schedule status retyped from the schedule that already says it.

Every number in that report already exists somewhere in the company. Not one of them travels to the report on its own.

Where the four hours go

The time doesn’t go to writing. It goes to fetching and reconciling: finding the current numbers, deciding which of two versions is right, making the formats match, and remembering how the owner likes it laid out. The writing part, the judgment, the “here’s what you should worry about”, gets whatever minutes are left before it has to go out.

That’s backwards. The judgment is the only part the owner actually needs a human for.

The compounding cost

Four hours a week is two hundred hours a year, per project, done by someone whose real job is running the work. But the hours are the small loss. The bigger one: a report built under deadline from hand-carried numbers is a report nobody fully trusts, including the person who built it. When a number looks off, the meeting becomes an argument about whose export is right instead of a decision about the job.

What fixing it looks like

Not a new platform, and not another tool for the field to ignore. The fix is a pipe: the daily reports, the cost codes, and the photos flow into one place, and the report assembles itself from live numbers, in the owner’s format, every week. The PM opens it, reads it, adds the two sentences of judgment that matter, and sends it.

We’ve built this. The office got its Thursday back, and the owner stopped double-checking the numbers, because they stopped being retyped.