Docs & technical writing
AuraScore 79/100

Facility Handover Documentation Readiness Assessment

Analyze building operations and maintenance documentation to verify asset data completeness and warranty operational readiness.

Use this template during the closeout phase of a construction project to review Operations & Maintenance (O&M) manuals and asset information models before client handover. It highlights missing maintenance workflows, data discrepancies, and commissioning documentation gaps.

Template

Role: Principal Building Information & Handover Technical Writer specializing in asset lifecycle documentation and facility management integration.

Context

  • Built asset name: {{asset_name}}
  • Building classification: {{building_class}}
  • Commissioning scope: {{commissioning_scope}}
  • Draft O&M documentation: {{om_documentation_draft}}
  • Client asset management standard: {{client_maintenance_standard}}
  • Handover and warranty timeline: {{warranty_milestones}}

Task

Deliver an exhaustive technical readiness analysis of the draft closeout and O&M documentation, establishing whether facilities teams can safely, efficiently, and compliantly operate the asset from day one.

Method

  1. Review {{om_documentation_draft}} against {{client_maintenance_standard}} to confirm asset tagging, naming conventions, and data structure consistency.
  2. Cross-examine system operating narratives against the physical systems listed in {{commissioning_scope}} to identify missing MEP subsystems.
  3. Audit preventative maintenance schedules for clear intervals, consumable specifications, and required technician skill levels.
  4. Evaluate vendor warranty documentation against {{warranty_milestones}} to detect ambiguities in activation triggers and void conditions.
  5. Check spare parts schedules, special tool lists, and emergency isolation procedures for operational completeness.
  6. Identify discrepancies between digital twin asset attributes and written maintenance manuals.
  7. Synthesize findings into a categorized readiness score with prioritized remediation requirements.

Constraints

  • MUST evaluate documentation against the criteria defined in {{client_maintenance_standard}}.
  • MUST NOT accept vague maintenance frequencies (e.g., 'periodically' or 'as needed') without flagging them as defects.
  • Every warranty gap identified MUST explicitly tie back to {{warranty_milestones}}.
  • Keep recommendations focused on information architecture, technical clarity, and operational utility.

Output format

Structure the assessment as:

  1. Handover Documentation Readiness Scorecard (overall readiness rating and executive summary, max 200 words)
  2. Asset Data Structure & Tagging Audit (evaluation against {{client_maintenance_standard}})
  3. Systems Coverage Gap Analysis (subsystem-by-subsystem breakdown comparing to {{commissioning_scope}})
  4. Maintenance Procedure & Warranty Risk Matrix (table: System, Identified Documentation Gap, Operational Impact, Required Revision)
  5. Pre-Handover Resolution Roadmap (numbered sequence of required document updates)

Self-review

  • Did I verify alignment with {{client_maintenance_standard}} across all sections?
  • Are all systems in {{commissioning_scope}} accounted for in the coverage analysis?
  • Are warranty risks directly tied to the dates in {{warranty_milestones}}?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

writing-content
writing-docs
real-estate-construction
facilities-management
handover
om-manuals