As-Built Documentation Organizer
Structure and organize as-built drawing markups and record document requirements for a construction project. This prompt helps architects define the as-built documentation scope, organize contractor-submitted markups, and establish a systematic process for assembling a complete project record that will serve the owner through the building's life.
This prompt produces an as-built documentation organization plan covering the required scope of record documents by discipline, markup quality standards for evaluating contractor-submitted redlines, a step-by-step reconciliation process for incorporating markups into the contract drawing set, BIM record model update requirements (if applicable), file naming and delivery format requirements, and a drawing-by-drawing completeness checklist. The architect's role is to compile record documents from the contractor's field markups — the architect does not certify the accuracy of field conditions they have not personally observed. It is for licensed architects managing project record assembly during closeout on commercial or institutional construction projects.
The prompt
You are a licensed architect experienced in project record management, as-built drawing compilation, and BIM record model coordination for complex construction projects. Help organize the as-built documentation process for the following project: Project information: - Project name: [PROJECT_NAME] - Project type: [PROJECT_TYPE] - Drawing set scope: [DESCRIBE — e.g., 120 sheets across architectural, structural, MEP disciplines] - BIM model: [YES / NO — if yes, what authoring software] - Contractor's markup format: [RED-LINE PRINTS / DIGITAL MARKUPS / BIM COORDINATION MODEL] Contractor's submitted markups (describe what has been received): [DESCRIBE MARKUPS RECEIVED] Known as-built conditions / changes from contract documents: [LIST KNOWN CHANGES — e.g., relocated equipment, field-modified connections, added cleanouts] Provide an as-built documentation organization plan: ## As-Built Documentation Scope What disciplines and drawing types are included in the as-built set. What minimum information is required in each. ## Markup Quality Review How to evaluate the completeness and legibility of contractor-submitted markups. Standards for acceptable vs. insufficient markups. ## Reconciliation Process Step-by-step process for reconciling markups with the contract drawing set. Who reviews, in what order, and how conflicts between disciplines are resolved. ## BIM Record Model Requirements (if applicable) If the project uses BIM, what updates are required to produce a compliant as-built BIM. Who is responsible for model updates. ## Filing and Delivery Requirements File naming convention, format requirements for delivery (PDF, DWG, Revit), and archiving protocol. ## Completeness Checklist A drawing-by-drawing checklist confirming that each sheet in the set has been reviewed and as-built conditions incorporated.
Runner beta coming — join the waitlist.
In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.
How to use this prompt
1. Define the as-built documentation scope and requirements with the contractor at project kickoff — not at closeout. Establish the markup format, frequency of updates, and delivery requirements in the construction phase kickoff meeting.
2. Review contractor markups regularly during construction, not just at closeout — catching gaps early is far more effective than a last-minute completeness scramble.
3. Use the completeness checklist to confirm that every drawing sheet has been reviewed before issuing record documents to the owner.
Customization tips
Sample output
Related prompts
Frequently asked questions
This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of a licensed architect. Always verify code compliance, structural calculations, and design decisions with qualified professionals.