Keep the Right to Be Paid

Know which requirements you can prove,
and which you can't.

Every requirement is marked by what is on file: evidence matched, insufficient evidence, or nothing yet. Your team works the list down while there is still time to fix it.

See the Register
One item, worked

Evidence matched
against a stated test.

The requirement states what would prove it before anyone goes looking. The gap names itself rather than being argued about later.

See a Sample Review
How an item moves

Every requirement carries two states, not one.

  1. 01
    Review state

    Did a person confirm what came out of the documents? Unreviewed, accepted, corrected or rejected.

  2. 02
    Compliance assessment

    Can the job show it did the thing? Not assessed, insufficient evidence, compliant or non-compliant.

  3. 03
    Insufficient is not non-compliant

    One says the paperwork is not in front of you. The other says the job failed. Your team never has to record the second when it means the first.

Work it down

Your team's work list
for the week.

Filter to the items nobody has looked at, or to everything with insufficient evidence. Figures on this screen are illustrative.

See a Sample Review
When the documents change

An addendum should not cost you three weeks.

Nobody reviews hundreds of items twice. Items touched by an addendum are flagged stale for re-review; every other decision stands.

  • Stale items flagged, never silently overwritten
  • Every decision your team made is kept
  • The requirement's test stays with it
  • Each item carries document, section and page
Where we stop

We show it. Your team decides.

You decide what counts as enough

Halozen states the test and shows what is filed against it. Whether that satisfies you is your call.

You keep your team's judgement

A re-extraction flags earlier reviews as stale. It never silently overwrites one.

You can check every item

Each requirement carries the document, section and page it came from.

Continue the commercial lifecycle
Every clock known before it starts.

Notice triggers and windows as your package writes them.

Notice Deadlines
The queue your team works down.

What is unreviewed, what has nothing behind it, what is closed.

Action Register
Know what you can still prove at closeout.

What the contract requires before the account is agreed.

Final Account & Closeout
FAQ

Common questions

What is an evidence review on a construction project?

Checking each contract requirement against a stated test of what would prove it, and recording whether the project record shows it was met.

What two states does each requirement carry?

A review state (did a person confirm what was extracted) and a compliance assessment (can the job show it did the thing).

Who decides whether the evidence is enough?

Your team. Halozen states the test and shows what is filed against it.

Get started

Put one project
under review.

Scope and fee agreed up front. Findings in two weeks. NDA first.

No implementation. Start with the records you already have.