Catch the change before
you sign it, not after.
Most exposure does not arrive labelled as a change. It arrives as a supplementary condition that deletes a clause of the standard form and replaces it with something worse. By the time it bites, the document is executed.
What did this package change from the standard?
Scope and fee agreed up front. No implementation. NDA first.
Right-of-way still to be acquired “as of December 4th, 2025”, and a permit list dated September 11th, 2024: both reported as baseline gaps, not skipped.
You should see what it replaced, not a note that it changed.
Contract Time now runs to Final Acceptance, and a daily incentive or disincentive arrived with the new definitions. Your team reads both versions side by side and decides in a minute what a description would have taken an afternoon to argue about.
Contract Time—The number of days or the dates stated in the Agreement to: (i) achieve Milestones, if any and (ii) complete the Work so that it is ready for Final Acceptance.
Contractor—The individual or entity with whom City has entered into the Agreement.
Contract Time – The designated time to achieve Final Acceptance as stated in the Agreement.
Contractor-Specified Time of Completion – The number of Days specified by the Offeror in the Proposal form … which becomes the Contractor’s agreed to number of Days to Achieve Substantial Completion.
Daily Value – The City-determined value in dollars … for the purposes of determining the Incentive or Disincentive relative to the Contractor-Specified Time of Completion and achievement of Substantial Completion.
Not every change announces itself as one.
A clause of the standard form is struck and nothing takes its place. Nothing in the package announces the absence, and your team prices as though the clause is still there.
A defined term is rewritten, or a new incentive regime appears in the definitions. The clause still exists, which is why it reads as familiar and gets skimmed.
The package rewrites a clause of a document that is not in the set. Nobody on your team can say what the clause used to require, so nobody can price the change.
An amendment only exists between two documents.
Reading the conditions on their own tells your team what they say. Reading them against the form tells you what they changed. Your set goes in whole, in the formats you already receive.
The call stays
with your team.
What you will carry and what you will push back on is a risk-appetite call, and it is yours to make.
Clarifications, RFIs and notices go out from your team, in your name. Halozen never contacts the owner or the design team.
Every change is reported with the text it replaced and the page it came from, so your team can check the work.
No citation, no output.
Put one package
through it.
Bring a live bid or an executed contract. We return the amendments, the defects and where each change came from.
No implementation. Start with the records you already have.