HomePlatformProject controls

Project controls

Buyout, submittals, documents and the field — on one register.

Four modules share the same documents, the same classifications and the same audit trail as the takeoff and the estimate. The scope sheet that priced the job is the scope sheet you buy out against.

Two crew members reviewing a tablet on siteP-03 · Project controls
Four modules, one thread

What each one covers.

Watch the coordination walkthrough

03 / Module

Buyout & Procurement

Scope sheets generated from the estimate, subcontract and purchase-order registers, and budget versus committed on one page. When a scope gap appears at buyout, you can see which quantity it came from.

04 / Module

RFIs & Submittals

AI drafts the RFI from the drawing and the relevant spec section, and drafts submittal transmittals with the right references attached. A person reviews and approves before anything is logged or sent. No autonomous sending.

05 / Module

Document Control

Specifications parsed and classified to CSI division and section, drawing revision tracking, and answers that cite the current sheet rather than the version someone downloaded in March.

06 / Module

Field & Closeout

Daily logs, quality-control records, punch list and closeout compliance, tied back to the same documents and classifications the estimate was built from.

Buyout & Procurement

Every package, budget to award

Commercial package control from frozen Estimate ownership through solicitation, leveling, award, and downstream execution.

PackageBudgetBiddersLow bidVarianceStatus
03 · Cast-in-place concrete$110,0000——scope ready
05 · Structural steel$142,5000——scope ready
22 · Plumbing$96,8000——scope ready

Buyout Log · estimate ownership, solicitation, leveling, award and execution

RFIs / Decisions

Questions & Clarifications

Drafted from source gaps, answered with impact, and connected to potential changes.

NumberSubjectSpecOriginDueCostStatus
RFI-041Connection responsibility05 12 00spec gapOct 03—sent
RFI-042Sleeve location at Grid C422 05 00drawing conflictOct 06—draft
RFI-043Finish transition detail09 65 00spec gapOct 10—draft

RFIs / Questions · source gaps, response dates, impact and potential changes

Watch an RFI resolve a conflict

Submittals

Submittal Log

Canonical durable artifacts with source obligations preserved beneath each workflow row.

NumberTitleSpecBall in courtDueStatus
SUB-005-03Structural steel shop drawings05 12 00ContractorOct 08GC review
SUB-033-02Concrete mix design03 30 00EngineerOct 02overdue
SUB-022-04Plumbing fixtures22 40 00VendorOct 14requested vendor

Submittal Log · canonical requirements, ball in court, due dates and approvals

Watch a submittal move through review

Document Control

Bring in the source

The Document Vault creates the authoritative project file before downstream work begins.

Documents · create the authoritative source record

Field & Closeout

Before anyone breaks ground

Document-derived checks and human-confirmed field readiness stay separate and visible.

Pre-Con & Mobilization · resolve document-derived field gates

Actual PiloBuild screen structure and module states · fictional project data · human decisions remain explicit

Browse all workflow videos

The gate

AI drafts. A person decides.

Every drafted RFI, submittal and transmittal stops for review and approval. That is not a setting, and it is not a beta limitation we plan to remove.

01 / Draft

Drafted with references

The draft arrives with the drawing detail, the spec section and the revision it relates to, so the reviewer is checking a position rather than assembling one.

02 / Review

Reviewed by a named person

Approval is attributed. The log shows who approved what and when, which is the part that matters when the schedule is being reconstructed months later.

03 / Log

Logged only after approval

Nothing is transmitted to a design team, an owner or a subcontractor until your team has said yes. PiloBuild does not send correspondence on its own.

Connected, not siloed

Why one register beats four tools.

The reason a scope gap costs money is that it crosses systems. It is measured in one tool, priced in a spreadsheet, bought out in a second tool, argued about in email, and discovered in the field. Each handoff drops context.

When buyout, submittals, document control and the field share the takeoff’s classifications and the estimate’s line items, the context travels with the item. That is the whole argument for an operating layer instead of four more point solutions.

See the 3-step pilot

Next step

See it on one of your projects.

Bring one drawing set and the estimate you already have. You keep everything the pilot produces.

Call PiloBuild+1 (872) 804-7023