Keep the right to be paid
for the work you do.
Every notice clock and every requirement with what proves it, so a missed deadline or missing backup does not cost you the right to claim.
to give written notice of a claim, or it is waived.
The clock starts at the event or when you first recognise it, whichever comes first, and notice is also due before the work begins. General Provisions §50-17.
Source: DFW Data Center 1Public bid package
The work moved. The record didn't.
Changes, notices and evidence end up in different places, and the right to be paid goes with them.
Field instructions and RFIs create new scope, but the commercial impact isn't always captured.
Deadlines are easy to miss when responsibilities are unclear and information is scattered.
Read moreIt's spread across RFIs, site records, emails and folders, which makes it hard to find when it's needed.
Read moreBut the commercial status never caught up, and the right to be paid is at risk.
One event.
Every clock.
See how a single event starts the notice clocks the contract sets, and what the record shows against each one.
- Day 0Event, or first recognition of the condition§50-17 · Whichever comes first starts the clockTriggerTrigger
- Before workWritten notice before beginning the claimed work§50-17 · "in all cases"Notice requiredNotice required
- Day 10Written notice of intention to claim, to the Engineer§50-17 · Within ten (10) calendar daysDeadlineDeadline
- Work doneUpdate the written claim within 5 calendar days§50-17 · Failure to do so is a waiverDeadlineDeadline
- CloseoutNo differing-site-conditions request after Substantial Completion or final payment§50-17 · Whichever comes firstCut-offCut-off
Keep the commercial position visible while the job moves.
- 01Bring your project records.
The contract, RFIs, submittals, correspondence and change log, as copies. Nothing to install.
- 02See what needs commercial attention.
Notice requirements, their triggers and the requirements that go with them.
- 03Keep a connected record.
Every item linked to the contract requirement, so your team acts in time.
No more hunting for the project history.
Changes, notices and evidence stay connected, so your team can act inside the window.
- Notice requirements with their trigger and deadline
- Changes connected to the documents that support them
- Open commercial items with the responsible party and next action
- The source record ready when your team needs it
Common questions
What does Halozen track during a job?
Every notice clock, submittal deadline and commercial requirement in the contract, each with what would prove it was met and whether that evidence is on file.
What happens if a contractor misses a notice deadline?
It depends on the contract, and many are strict. On the public DFW Airport contract on our site, written notice of a claim is due within 10 calendar days and before the work starts, or the claim and any time extension are waived. Halozen shows each clock and its trigger so your team can act in time.
Will Halozen send notices or RFIs for us?
No. Notices, RFIs and correspondence stay with your team. Halozen shows what is due, when and why, cited to the clause.
Does Halozen show what a missed requirement could cost?
Where the contract states the amount, the register shows the exposure in the contract's own terms, such as $2,500 a day of liquidated damages or the value of a claim at risk, with the source cited. Your team decides what to pursue.
Does Halozen connect to Procore or our project systems?
No connector is needed. Halozen works on copies of the documents you already hold, and your systems stay exactly as they are.
Show us the project
that's giving you trouble.
Scope and fee agreed up front. Findings in two weeks. NDA first.
No implementation. Start with the records you already have.