Preconstruction Directors

You cannot read
every package.

You sign off on numbers built by people reading different documents to different depths. Halozen gives every package the same pass, cited to source, before the price is locked.

See a Sample Review
571

pages of specifications in one data center bid package.

Each one can carry an obligation the number has to cover, and nobody on a bid team reads them all twice.

Source: DFW Data Center 1Public bid package

The challenge

None of these look like
a problem on the day.

Your team isn't short on judgment. It's short on time.

A real example

One obligation.
One decision.

Every finding cited to document, section and page, so your estimator can check the work rather than trust it.

How it works

The same pass on every package.

  1. 01
    Send the bid package.

    The contract, conditions, specifications, addenda and drawings, as you received them.

  2. 02
    Every obligation, cited.

    What each clause commits you to, who owes it, and where the package rewrites the standard form.

  3. 03
    Your estimators decide.

    Price it, qualify it or carry it, with the clause and page in front of them.

What your team gets

Halozen gives your judgment evidence.

Your team keeps its estimating process and gets the review before the number goes out the door.

  • Every bid read the same way, whoever on your team is running it
  • Every item cited to document, section and page
  • What needs a decision before the number goes out the door
  • Nothing asserted without a source
Get started

Start with
one live bid.

Pick the package on your board you are least comfortable about. Scope and fee agreed up front. Your documents. NDA first.

No implementation. Start with the records you already have.