Every requirement, what proves it, and what your team decided.

Halozen reads the contract and the project document set, turns every clause into a requirement, catches what the package amended, states what would prove each one, and holds the evidence and your team’s review against it.

Behind it are construction engines trained on contract documents that senior estimators annotated by hand, 1,200 for one engine alone. On documents it never saw, our engine cites the right clause and page 95% of the time. A reviewer approves every finding.

Clauses
Requirements
Amendments
Acceptance Criteria
Evidence
Review
Halozen
Reasoning
Ledger
The six pieces

From the clause to the evidence, as one record.

01Clauses

Every clause in the contract and the project document set, indexed and cited to document, section and page.

02Requirements

Each clause turned into what it actually requires, and of whom.

03Amendments

Where the package rewrites the standard form, with the original beside the replacement.

04Acceptance Criteria

What would prove each requirement, stated before anyone goes looking.

05Evidence

What your team files against each requirement, matched to its stated test.

06Review

Your team's decision on every item, kept in the record and never silently overwritten.

The obvious question

We look for what happened between the two.

Put ChatGPT on a folder of documents and it will answer good questions well. Your systems of record manage what your team entered. Both are good at their jobs. But six months later, where did the reasoning go? AI can answer the question. The project needs to remember the answer.

General AI assistants
ChatGPT · Claude · Copilot
Core job

Answers what you ask

Reads project records

When supplied

Finds what was never entered

Custom analysis

What each item cites

Whatever was in the prompt

Traces finding to outcome

Session / task

Systems of record
Procore · Autodesk · Trimble · Aconex
Core job

Compiles what your team enters

Reads project records

Own system

Finds what was never entered

Not what they are for

What each item cites

The record somebody entered

Traces finding to outcome

Entered workflow

Halozen
Reasoning Ledger
Core job

Looks for what happened between the two

Reads project records

Across records

Finds what was never entered

Yes, starting from the contract

What each item cites

Document, revision and page

Traces finding to outcome

Across the commercial chain

Your systems manage what entered the process. Halozen looks for what never did.

Boundaries

What stays exactly where it is.

We read, we do not replace

Your systems of record stay exactly as they are. Nothing to migrate, nothing to install.

We hold no credentials

You upload the documents, privately, encrypted in transit and at rest. We do not connect to your ERP, your accounts or your project systems.

We do not speak for you

Notices, RFIs and correspondence go out from your team, in your name.

No citation, no output

Every item is traced to document, section and page, or it is not in the record.

Get started

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.