One Commercial Story, Rebuilt Three Times

We have artificially separated preconstruction, delivery and closeout. Different teams, different tools, different files. They get treated almost like three information worlds that happen to share a project number.

But they are the same commercial story. The questions just change with the stage.

• At bid time: what am I committing to?
• During construction: what changed?
• At closeout: what happened to all of those commitments and changes?

Each question depends on the answer to the one before it. And on most projects, each one gets answered from scratch.

Rebuild number one: the handover

The estimating team reads the package under deadline. They find the amended conditions, the unusual notice periods, the requirement that shifts a cost onto the contractor, and they make decisions about what to price, what to qualify and what to carry as risk.

Then the job is awarded and the project team takes over. What moves across? Usually the estimate, the schedule and the executed contract. What often doesn't move across is the reasoning: why a clause was priced a certain way, which assumptions the number depends on, which obligations the estimator was worried about.

The contract doesn't die after award. But the understanding of it often does.

Rebuild number two: the change

Months in, something changes. To value it properly the team needs to know what was priced, what was assumed and what the contract says about notice and entitlement. That context was established before award. Now someone has to find it again, usually by re-reading the same documents the estimator already read.

Rebuild number three: the final account

At closeout the question is whether the project can show it did what the contract required, and whether every change was dealt with. By now the people who priced the job and the people who ran it may have moved on. The evidence is scattered across systems and inboxes. The commercial team reconstructs the story from whatever survived.

We're building billion-dollar projects, and sometimes the explanation for an important commercial decision is sitting in somebody's email from eighteen months ago.

Why this matters more than it looks

Every rebuild costs time, but the bigger cost is what gets lost between rebuilds. A reasonable decision made at bid time can't be explained six months later. That's reasoning debt, and projects pay it back at the worst possible moment: when the account is being agreed and nobody can say why.

Commercial leakage usually starts long before anyone sees a dollar figure. It starts as one clause nobody carried forward, one assumption nobody wrote down, one notice nobody knew was due.

One record from bid to final account

The fix isn't another report at each stage. It's keeping one record alive across all three: what the contract requires, what would prove it, what the team decided and why, with the clause and page attached to each item. The assumptions behind the bid shouldn't disappear when the project team takes over. The project history shouldn't need reconstructing at final account.

That context should survive the job.

That's the record Halozen keeps: every obligation from the contract and project documents, cited to its source, with the evidence and the review attached, from before award to final account.