One record that every party on a job can see, and an observer that catches mistakes in planning before they become RFIs.
Admin accounts are not set up yet, so nothing is checked here. Use Enter the platform for now. When accounts are added, each person signs in with their own account and sees only their own party's records.
PLAN TO FIELD
One place for every party. The owner, GC, subs, engineer, and field work from the same job record and the same documents, so nobody is working from a different copy.
The gaps in communication, filled. What was agreed at the meeting, what was sent, what is still missing, and who owes the next step, each with a date.
Mistakes caught before an RFI. Drawings are checked against the spec and the manual as they are issued. Each possible conflict goes to the person who can fix it while the drawing is still in planning.
Nine stages, from the first meeting to closeout. Each one says who acts and what it leaves on the record. The platform does not certify compliance. It flags possible conflicts for a person to resolve.
Working now
The GC project manager enters the owner, GC, engineer, governing entity, and job number once. Everything else on the record refers back to these.
Planned
The engineer issues the project manual at the preconstruction meeting, and the GC uploads it with the drawings. The platform indexes the manual by spec section and maps each drawing sheet, so every answer can cite the sheet and the section.
Planned
The standards of the governing entity are pulled from public sources and ranked under the contract, the manual, and the drawings. Where sources disagree, the record shows the conflict. A person confirms the basis, and gaps stay listed until someone fills them.
Working now
Roles, the escalation chain, submittal dates, late-submittal windows, payment holds, notice to proceed, mobilization, and missing submittals are confirmed at the meeting and kept with the minutes. The minutes remain the official record.
Working now
Sixteen status states, shared by both sides. The record blocks submission to design until the GC review stamp is signed, allows fabrication only after approval or approval with corrections, and flags late reviews to both sides.
Planned
Installed work is checked against the approved submittal. Questions that need a design answer become RFIs, linked to the sheet they concern.
Planned
Runs on a schedule. It compares drawing schedules and notes with the spec basis and flags possible conflicts, such as an equipment tag that does not match the capacity the spec requires. A reviewer decides each flag.
Counsel review first
A dated, append-only record of a negative matter. Each entry cites the sheet, spec section, and revision. Exports are prepared for counsel and are not for live use until counsel has reviewed them.
Planned
O&M manuals, warranties, as-builts, and commissioning reports are tracked against their own deadline until the item closes.
The top source wins when sources conflict. Confirm the order against the contract.
Record what was confirmed at the meeting. The signed minutes remain the record.
Every change is kept with its author and date.
Each trade adds its own glossary and sources. The submittal and conflict workflow stays the same across all four.
Lift stations, water plants, wastewater treatment plants, and potable wells with ground storage.
Sources in hand: Houston Public Works open data for lift stations, treatment plants, and layers; TCEQ 30 TAC Chapter 217 design criteria; EPA ECHO, FRS, and SDWIS directories. Still needed: a full lift station set, a treatment plant set, and a well-with-storage set.
Chillers, air handling, controls, and the spec sections that carry them.
Sources in hand: Divisions 23 and 26 criteria from UFGS, ASHRAE terminology (linked, not copied), and a learning set from the NWACC Burns Hall chiller replacement. Open issue: the drawing schedule tags a 215-class unit where the spec calls for 200 tons. This is the kind of mismatch the compliance check exists to catch.
Contract plans, proposals, and state letting packages, including off-system bridges and federal-aid terms.
Sources in hand: a Fort Bend County bridge and utility set. Still needed: state DOT specifications. The TxDOT FTP site blocks automated fetching, so those files come from upload.
Buildings, including elevators and other vertical transportation.
Sources in hand: the HACP Murray Towers project manual and its attachments. Open issue: the elevator scope is not confirmed in the spec divisions, so it stays unverified until the drawings are mapped.
Working in this version. The job record with its governing entity, the preconstruction checklist, and the submittal log with its sixteen states, the GC review gate, the fabrication gate, and the late-review flags.
Not built yet. Reading drawings and answering questions from them, which waits on attorney review of related patent filings. The spec finder and the public spec pull by governing entity. The periodic compliance check. The dispute record and its export, which wait on counsel review. Markup that opens in Bluebeam: the platform writes standard PDF annotations only, because Bluebeam's own data is proprietary. Admin sign-in with separate accounts for each party.