See the source library organize itself.
This demonstration uses the actual PiloBuild Document Vault structure: source identity, processing state, classification, and the entry points that carry a file into the next workflow.
Document Control
Bring in the source
The Document Vault creates the authoritative project file before downstream work begins.
Documents · create the authoritative source record
Actual PiloBuild screen structure and module states · fictional project data · human decisions remain explicit
01 / Workflow
Identify the source
Drawings, specifications, contracts, estimates, and addenda enter the project with a visible document type and processing state.
02 / Workflow
Keep revision context
The current project record stays distinguishable from earlier revisions so downstream work has a clear source basis.
Watch a drawing revision check Watch Specifications Watch Contract Intel
03 / Workflow
Carry the reference
Takeoff, requirements, questions, and deliverables retain the document context that supports them.

See it on one of your projects.
Bring one drawing set and the estimate you already have. You keep everything the pilot produces.






