The questions teams ask before they upload a page.

Halozen reads the contract and the project document set and turns every clause into a requirement. For each one it shows what the requirement says, cited to document, section, page and sheet, who owes it, what would prove it was met, and whether that evidence is on file.

At three moments: before award, to see what the bid commits you to that is not properly priced; during the job, to see which notice, submittal and commercial requirements are open; and before final account, to see which requirements you can still prove.

Yes. On a negotiated job the closeout question changes. It is less about missed notices and more about reconciliation: which costs count under the GMP, how contingency and allowances were used, how savings are shared, and what the owner's audit rights reach. Retainage is still held on most of these jobs. The review reads those clauses against the record you upload, each line cited to the page.

The contract and the project document set: agreement, conditions, specifications, addenda and drawings, plus any project records you want checked as evidence. Copies, in the formats you already keep them in. If a document set is incomplete, the gap is part of what we report rather than a reason to stop.

Two weeks. For a single-project review, you get the findings within two weeks of us receiving your documents. The scope and the fee are agreed before we start.

Yes, and that is where it is worth more. Running against a live project means the commercial record is built as the job goes rather than reconstructed at the end, when people have moved on and the trail has gone cold.

No. Halozen is not a law firm. Our findings support your team's decisions and are not a substitute for advice from your own counsel. Your team decides whether and how to act on any finding.

You upload it, privately. The contract, the conditions, and whatever project record you have: pay apps, submittals, RFIs, notices, correspondence. Copies, in the formats you already keep, into a space that is yours alone, encrypted in transit and at rest. No system access, nothing to install, no integration. The requirements come from the contract, which no system holds as data; the evidence comes from your record; the gaps are what the contract says should exist and the record does not contain.

No. Procore, Autodesk, Trimble, Aconex and SharePoint stay exactly where they are, and so does your ERP. There is nothing to install, nothing to migrate and no new system for anyone to adopt.

No. We hold no credentials for your ERP, accounts or project systems, and write nothing into any system of record. We work on copies of the documents you upload.

You choose: your own private space in our cloud, or your own private cloud account on the enterprise tier. Either way the documents are never pooled with another customer's.

No. Your documents are kept apart from every other customer's and never used to train anything another contractor benefits from.

By default, we delete your documents and our working files within 30 days of the engagement ending, and from backups within 60 days. Ask and we delete them sooner, and confirm in writing. On a private cloud deployment we hold nothing. Your agreement can set different terms.

Yes. We sign your NDA first, then answer your security questionnaire within five business days. Your team decides before any project data moves.

Never. Findings go to your team. Notices, RFIs and every conversation with the owner stay yours, in your name and on your timing. What to pursue is your team's call.

That is the only way we start. One project, a live bid, an active job or one heading into final account. Scope and fee agreed before work begins, NDA first. You keep the findings either way.

It depends on the project and the scope we agree. The fee is fixed for that scope and agreed before any work starts.

Most teams do one of two things. They run the same review on the next closing project, or they put a live project under continuous review so the record stays connected while the job runs. Neither is a condition of the first one.

A small number of contractors work with us closely: their real projects reviewed, a direct line to the team building Halozen, partner pricing, and a say in what we build next.

General contractors and specialty subcontractors: the preconstruction, project, commercial and finance teams who answer for the number before award, during the job and at final account.

Public and private construction, including civil and infrastructure, data centers, commercial buildings, energy and utilities, and government and institutional work.

Halozen reviews contracts for projects in the United States, Canada and Australia. In Australia that includes head contracts under AS 4000 and amended forms.

Every requirement in the contract and project documents, with who owes it and what would prove it, plus notice clocks, liquidated damages, payment and retainage terms, changes to the standard form, conflicts between documents, and requirements with nothing on file.

Standard forms such as AIA A201, the A102 and A133 cost-plus and GMP agreements, and AS 4000, their supplementary conditions, and owner-written contracts like the public airport and city packages shown on our site.

Every finding is cited to the document, clause and page, so your team can check it in one step. If there is no citation, there is no finding.

A register of cited requirements with their state and what would prove each one, delivered in the formats your team uses, such as XLSX, PDF or CSV.

General AI assistants answer what you ask about what you paste in. Halozen reads the whole contract and project document set, cites every finding to the page, and keeps the record of what was required and what your team decided for the life of the job.

No. It does not replace Procore, your document control or your ERP. It reads copies of the documents those systems already hold.

Your project system compiles the closeout package from what was entered. Claims consultants review the contract against the record after a dispute, by the hour. Nobody sits in between at closeout with the contract open. That is the review: before the dispute, in two weeks, at a fixed fee.

They read it at award. By closeout that was months ago, addenda have moved the clauses, and the people who priced the job are on the next one. Nobody has read the contract against everything the job produced, at the point where it decides the money. That is the review: every requirement that touches final payment, checked against what is on file, with the gap shown on each line. Your team keeps the list and decides what to pursue.

No. Halozen reviews documents for your team. Your commercial team decides what to pursue, and your counsel decides legal questions.

No. It is a review of your contract and records, done for your team, not an audit of your company.

Yes, to do the reading. Every output is cited to its source page and goes through your team's review before anyone relies on it.