Send the package. Nothing to install.

No connector, no credentials, no IT project before you see anything. Your systems stay exactly where they are and we read copies of the documents you already hold.

HALOZENDFW Data Center 1
Package intake
22 documents · 803 pages
DocumentPages
13-PA1971 Specifications571
15-PA1971 Sample Agreement144
12-Exhibit B SBE Contract Provisions31
14-PA1971 Plans19
11-Exhibit A Insurance Requirements7
16-Special Provisions7
9-Instructions to Bidders4
8-Bid Detail3
3-SBE Commitment Form2
4-SBE Schedule of Subs2
12 further documents13
Total803
Bring one project this week

Three steps, none of them involving your IT team.

01
Export it

Pull the package out of Procore, Autodesk, Trimble, Aconex, SharePoint or a shared drive. Whatever your team already does to send a package to a sub works here.

02
Send it

PDFs as they are. Scanned documents are fine, we run OCR where the text is not selectable and report what it recovered.

03
Get the register back

Every obligation the package creates, cited to document, section, page and sheet, with what would prove each one.

What we read

Incomplete sets are normal.

Where a document the package references is missing, that gap is reported as a finding rather than treated as a failure.

Contracts and agreements
General and supplementary conditions
Specifications and divisions
Addenda and bulletins
Instructions to bidders
Bid forms and bonds
Drawings and sheet references
Prevailing wage schedules
What your security review will ask

We hold no credentials.

There is nothing to approve beyond receiving copies of documents. No write access to any system of record, no ERP credentials, and nothing you send trains anything another contractor benefits from.

No credentials held

We never receive a login to Procore, Autodesk, Trimble, Aconex, SharePoint or your ERP.

Nothing written back

Read-only by design, not as a phase one. There is no write path to build later without you asking for it.

Per-tenant, self-hostable

Your records stay yours, and the whole thing runs in your own environment where the work cannot leave.

On integrations

A connector would save your team an export. It would not change what comes back.

We would rather earn a connection after the register has proved useful on one project than ask for system access before you know whether this works. Upload is the whole intake today, and we would rather say so than imply otherwise.

Bring a Project

Send one package. Keep every system you run.

An export is enough to start. We return the obligations, the conflicts and what would prove each one.

No migration. Scope and fee agreed up front. Source-cited output.