Track As-Built Drawings Without the Handover Chaos

Where this fits

A project coordinator is two weeks from handover and cannot get a straight answer on which drawing sets are approved, which need resubmittal, and which never left the "in progress" pile. as-built-tracker gives agents a structured way to track as-built documentation, submissions, revisions, and approval status so this last-mile question becomes a data lookup rather than a folder-by-folder panic.

Why agents benefit

• Converts a messy drawing register into a structured dataset with statuses like not_started, submitted, under_review, approved, and rejected.
• Applies date-aware logic to find late submissions, stale revisions, and documents that missed a 30-day resubmit deadline.
• Groups documents by type or status so agents can summarize project-wide handover readiness in one response.
• Keeps a traceable record of status changes, making it possible to answer "what happened to this drawing?" during an audit.
• Feeds escalation prompts: an agent can proactively call out rejected or resubmit drawings before they block turnover.

Practical scenarios

Weekly handover health check

Every Friday, the agent scans the as-built register, groups drawings by DocumentStatus, and posts a summary to the team channel. The summary names drawings stuck in in_progress too long, and flags approved sets ready for final inclusion.

Revision review queue

When a new revision lands, the agent updates the row and checks whether the previous version was approved or rejected. It can then build a review queue sorted by the age of the under_review items, so the PM knows which revisions are blocking closing out the architectural package.

Pre-submission gap analysis

Before a formal handover, the agent compares received drawing types against the project's required list. It outputs a simple completeness table: architectural, structural, mechanical, electrical, each with a count and status, plus a gap list when something like "as-built plumbing" has no submission at all.

Add it to your agent workflow

Install the skill into your agent runtime with:

npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill as-built-tracker

Then point your agent at the project register and ask a question that matters: "Use as-built-tracker to list every approved drawing older than 30 days and flag any that have a newer revision available." The agent will load the tracker logic, inspect the documentation state, and return a prioritized action list instead of a raw file dump.

Compare before adopting

Before wiring this skill into your agent, compare it on four axes: quality signals (are issues and README examples up to date?), maintenance freshness (has the repo changed recently?), alternatives (a generic PDF parser or spreadsheet prompt may be enough for simple cases), and workflow fit (does it map to your existing drawing register or require you to adapt your folder names?).

Why it is worth tracking

The project has 300+ stars and comes from datadrivenconstruction, a building-data-focused author who ships construction-specific agent skills rather than generic boilerplate. The skill is small, focused, and uses Python/pandas, so it is easy to audit and extend. It is worth tracking now because it targets a real bottleneck—handover documentation—and the pattern can be folded into any construction AI agent. You can browse the full listing at https://www.openagentskill.com/skills/datadrivenconstruction-as-built-tracker to see how it compares with related construction skills.