Customers
AuraScore 81/100

Commercial Tenant Fit-Out Delay Notification Checklist

Practical checklist for asset managers communicating construction milestone delays and lease compliance updates to commercial tenants.

Deploy this template when construction delays impact commercial tenant fit-out schedules or base-building handover dates. It creates an exhaustive verification checklist to align email correspondence with lease obligations and mitigate dispute exposure.

Template

Role: Senior Commercial Asset Manager specializing in mixed-use development handovers and landlord-tenant relations.

Context

  • Tenant Account: {{tenant_entity}}
  • Demised Premises: {{lease_premises_id}}
  • Critical Delay Root Cause: {{milestone_delay_cause}}
  • Target Handover Schedule: {{revised_completion_date}}
  • Contractual Exposure: {{liquidated_damages_status}}
  • Tenant Delivery Partner: {{fit_out_contractor}}

Task

Develop an exhaustive operational and commercial audit checklist to review formal tenant-facing delay notification emails, ensuring alignment with lease covenants, base-building contractor accountability, and commercial dispute mitigation.

Method

  1. Review the legal notice mechanisms required under the lease agreement for {{lease_premises_id}} to verify proper formal notice transmission channels.
  2. Evaluate how {{milestone_delay_cause}} is articulated to avoid premature exposure under {{liquidated_damages_status}} while upholding commercial transparency.
  3. Establish checks to confirm clear articulation of base-building handover criteria versus tenant contractor obligations for {{fit_out_contractor}}.
  4. Design verification checkpoints assessing whether the technical critical path leading to {{revised_completion_date}} is supported by certified project manager reports.
  5. Create audit criteria for landlord concessions, early access for surveying, and staged fit-out permissions.
  6. Formulate tenant relationship retention checks to protect long-term landlord reputation and joint tenant coordination.
  7. Detail mandatory review sign-offs from internal legal counsel, project directors, and leasing executives.

Constraints

  • Checkpoints MUST be written using imperative verbs tailored to commercial property asset management.
  • MUST NOT draft the email message itself; output strictly the review checklist.
  • Checkpoints MUST cover commercial lease compliance, technical contractor scheduling, and risk mitigation.
  • The total checklist must feature exactly four named verification phases.

Output format

1. Lease Covenant & Notice Compliance Checks

  • 4-5 bulleted checklist items evaluating legal notice validity and formal lease alignment.

2. Technical Schedule & Critical Path Verification

  • 4-5 bulleted checklist items reviewing construction data credibility and milestone feasibility.

3. Commercial Exposure & Concession Risk Assessment

  • 4-5 bulleted checklist items evaluating financial exposure, rent-free adjustments, and penalties.

4. Stakeholder Governance & Pre-Send Approvals

  • 4-5 bulleted checklist items detailing mandatory internal sign-offs before customer dispatch.

Self-review

  • Ensure every checklist item directly reflects the variables {{tenant_entity}}, {{revised_completion_date}}, and {{milestone_delay_cause}}.
  • Confirm that no generic real estate fluff is present and all criteria focus on high-stakes email verification.
  • Verify adherence to the four-section output structure.
AuraScore breakdown
81/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 engineering12/12 · Strong

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.

emails
emails-customers
real-estate-construction
commercial-leasing
tenant-relations
fit-out-management