As Built Documentation

What This Skill Does

The As-Built Documentation skill is designed to bridge the gap between construction site field changes and finalized project records. It provides a structured framework for managing the lifecycle of project documentation, ensuring that all physical changes made during the construction process are systematically documented, verified, and incorporated into final handover sets. The skill enables users to create document registries, log specific site markups with precise location data, track the review status of revisions, and programmatically verify that all documentation meets the criteria for project closeout. By centralizing this data, the skill eliminates common issues like lost field notes, inconsistent drawing versions, and the stressful last-minute scramble to find missing compliance certificates or manuals.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal or command interface: clawhub install openclaw/skills/skills/datadrivenconstruction/as-built-documentation

Use Cases

• Project Handover: Automating the collation of finalized 'as-built' drawings and warranties to prepare turnover packages for building owners.
• Field Change Management: Providing a real-time log for field engineers to track, status, and assign markup tasks to design teams.
• Quality Assurance: Running automated completeness checks to ensure every document labeled as 'Final' actually has all associated field markups marked as 'Incorporated'.
• Regulatory Compliance: Maintaining an audit trail of who marked up a drawing, when it was verified, and the status of the approval workflow.

Example Prompts

1. "Register a new drawing with document number ARCH-001, title 'Level 1 Reflected Ceiling Plan', and type DRAWING under the Architectural discipline."
2. "Add a markup to document DOC-0001: Change light fixture location in North corridor to match field conduit installation; status is pending."
3. "Run a completeness check for the current project and provide a report of all documents that have pending markups or are not yet set to Final status."

Tips & Limitations

• Data Consistency: Ensure that your naming conventions for document_number match your existing document control software to prevent confusion.
• Verification Workflow: Use the verified_by field systematically; this acts as an electronic signature for your quality control process.
• Limitations: This skill manages the metadata and status of documents. It does not perform OCR or image editing on the drawing files themselves. Ensure that your physical file paths are accessible to the environment where the OpenClaw agent is running.