Facilities Maintenance Dispatch Agent Incident Briefing
Draft a post-incident review email to property asset owners detailing an autonomous dispatch event and corrective rules.
Use this template after an automated facilities maintenance agent resolves or mishandles an emergency work order. It informs building owners of root causes, budget impacts, and updated agent guardrails.
Role: Head of Facilities Automation and Asset Management with extensive expertise in commercial real estate building management systems (BMS) and emergency workflows.
Context
- Commercial or multifamily asset: {{property_asset}}
- Date of maintenance event: {{incident_date}}
- Autonomous dispatch agent identifier: {{dispatch_agent_name}}
- Trade contractor category involved: {{vendor_category}}
- Current operational status: {{resolution_status}}
- Asset owner or investment contact: {{owner_contact}}
Task
Draft a concise, high-accountability incident briefing email to {{owner_contact}} explaining an autonomous vendor dispatch decision made by {{dispatch_agent_name}} on {{incident_date}}, including financial impact, remediation steps, and updated safety triggers.
Method
- Summarize the initial telemetry or tenant maintenance trigger received at {{property_asset}}.
- Detail the autonomous decision logic that caused {{dispatch_agent_name}} to dispatch {{vendor_category}}.
- Evaluate whether the agent's spending authorization remained within pre-approved emergency limits.
- Explain the current physical state of the building and confirm {{resolution_status}}.
- Identify the specific decision parameter or threshold adjusted to prevent false-positive dispatches in the future.
- Offer a brief summary of financial accountability and warranty claims if contractor performance was flawed.
- Provide an open invitation for a review call with the property management leadership team.
Constraints
- MUST maintain an objective, transparent, and accountability-driven tone.
- MUST NOT conceal automation edge cases or shift inappropriate blame to third-party APIs.
- MUST clearly separate physical damage mitigation from software configuration changes.
- Word count MUST be between 350 and 550 words.
Output format
- Subject: Incident Summary & Agent Dispatch Review: {{property_asset}} [{{incident_date}}]
- Section 1: Executive Summary & Current Site Status (under 100 words)
- Section 2: Autonomous Agent Action Timeline (chronological bullets)
- Section 3: Financial Impact & Vendor Assessment
- Section 4: Corrective Agent Guardrails Applied
- Section 5: Next Steps & Direct Contact Details
Self-review
- Is the financial consequence and authorization ceiling clearly stated?
- Does the timeline explicitly show the role of {{dispatch_agent_name}} at {{property_asset}}?
- Are all 6 variables incorporated accurately?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.