The job moves faster
than the contract.
Nobody on a live job re-reads hundreds of requirements. Halozen holds what the contract asked for, so your team can see what nobody has dealt with yet.
to give written notice of a claim, or it is waived.
The clock starts at the event or first recognition, whichever comes first, and notice is also due before the work begins. General Provisions §50-17.
Source: DFW Data Center 1Public bid package
Your systems record what your team did.
Not what the contract asked for.
The gap nobody is watching sits between the two.
Nobody checked which notice window the answer just started running.
Read moreThe log shows what was raised. Not the submittal the contract requires that nobody has raised.
What it amended in the contract was never re-read.
Nobody linked it to the requirement it was supposed to satisfy.
Read moreOne event.
Every clock.
What the contract says starts the clock on each time-bound requirement, and what the record shows against it.
- 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 every system you already run.
- 01Bring the executed contract and the package.
Plus the project record, as copies. Nothing to install.
- 02See what the contract still requires.
What is unreviewed, what has no evidence, what is still open.
- 03Work the register down.
Evidence matched against a stated test, while the people who know are still on the job.
Closeout is assembly, not archaeology.
Every closeout argument your team has ever lost was winnable while the job was running.
- The test for every requirement written before anyone goes looking
- What starts each notice clock, cited to the clause
- What is outstanding this week, in a form somebody can work
- Evidence attached while the people are still here
Common questions
What does a project executive get from Halozen?
A view of what the contract still requires on a live job: open notice, submittal and commercial requirements, what proves each one, and what nobody has dealt with yet.
Can Halozen start on a project that is already underway?
Yes. Upload the executed contract and the project documents you hold, and the review covers what is open now.
Who acts on the findings?
Your team. Each finding has a state and an owner, and nothing is sent to your client on your behalf.
Put one live project
under review.
Bring the executed contract and the package. Your team keeps every system it already runs.
No implementation. Start with the records you already have.