Introduction

This library standardizes exactly what to capture when documenting renters insurance compliance for residential portfolios using common property management systems. It specifies the required artifacts, decision keywords, alt-text and caption templates, file naming, and governance so auditors, owners, and lenders can verify compliance quickly without rework.

Scope and prerequisites

• Applicability: residential rental portfolios managed in Canada (excluding Quebec), including student housing and mixed-use assets with residential tenants.

• Systems in scope: Yardi Breeze (or Yardi Breeze Premier), Buildium, and any alert/notification tool used to prompt tenants or staff regarding insurance status.

• Policy context: this library is evidence-focused and complements brokerage services such as Property Management Insurance and Landlord Insurance. It does not replace policy documents or certificates on file.

Artifact taxonomy and file naming

• Artifact types

• Dashboard status: portfolio- or property-level compliance summary.

• System sync: system-of-record view showing policy status fields as of capture time.

• Proof upload: certificate or declarations page attached to a tenant/unit record.

• Alert configuration: rules, recipients, and timing used to trigger notices.

• Canonical decision keywords (use verbatim in alt text and captions)

• Compliant, Non-Compliant, Pending, No Policy On File, Expired, Active, Renewal Due (X days), Certificate Received, Certificate Rejected, Proof Required

• File naming template

• {YYYY-MM-DD}{asset-or-portfolio}{artifact-type}.png

• Example: 2025-10-30_West-4th-Portfolio_Yardi-Breeze_system-sync_property-level.png

Artifact index (one-table quick map)

Screenshot set A1 — Compliance dashboard (portfolio view)

• Capture goal: a single image showing total tenant count, compliant count, non-compliant count, and pending reviews.

• When to capture: after nightly data refresh or immediately before monthly owner reporting.

• Alt-text template

• “Portfolio compliance dashboard — Compliant: {#}, Non-Compliant: {#}, Pending: {#}. Decision: {Compliant|Non-Compliant|Pending}.”

• Caption template

• “A1 Portfolio: {property/portfolio name} — {date}. Compliance ratio {compliant%}. Exceptions flagged: {top 3 reasons}.”

• Required on screen

• Portfolio or property identifier, date/time, counts and/or percentages by status, filter state (if any).

• Validation checklist

• Date/time visible; filters = ‘All properties’; totals equal sum of categories; screenshot resolution ≥ 1440 px width.

Screenshot set A2 — Yardi Breeze policy sync (status fields)

• Capture goal: evidence that tenant insurance fields are populated and current in Yardi Breeze (or Breeze Premier).

• Typical fields to include if configured: unit/property, policy status, effective date, expiration date.

• Alt-text template

• “Yardi Breeze policy status — Unit {ID}: {Active|Expired|No Policy On File}; Expiry {YYYY-MM-DD}. Decision: {Active|Expired|No Policy On File}.”

• Caption template

• “A2 Yardi Breeze sync — {property name}, {date}. Records reviewed: {#}. Exceptions: {

Expired}, {

No Policy On File}.”

• Required on screen

• Column headers visible; sort order shown; last-updated timestamp; pagination indicator if multi-page.

• Validation checklist

• Timestamps present; sample includes at least one Compliant and one Non-Compliant entry; export icon or audit trail icon visible if available.

Screenshot set A3 — Buildium proof upload (tenant record)

• Capture goal: proof-of-insurance artifact attached to a resident/lease record with status outcome (received/rejected) and expiry date.

• Alt-text template

• “Buildium tenant proof — Certificate {Received|Rejected}; Expiry {YYYY-MM-DD}. Decision: {Certificate Received|Certificate Rejected}.”

• Caption template

• “A3 Buildium upload — {property name}, unit {ID}. File attached on {YYYY-MM-DD}. Reason if rejected: {missing pages|mismatched named insured|expired}.”

• Required on screen

• Document title, upload date, reviewer note or status, visible expiry date matching certificate.

• Validation checklist

• Expiry date corresponds to certificate; named insured matches tenant/lease; notes field captures rejection rationale when applicable.

Screenshot set A4 — Alert setup (renewal and proof required)

• Capture goal: configuration evidence for automated reminders to residents/staff about missing or expiring insurance.

• Required rule types

• Proof Required (trigger on No Policy On File or Pending).

• Renewal Due (X days) (trigger X=30, 15, 7 by policy expiry date).

• Alt-text template

• “Alert rules — {Proof Required|Renewal Due (30 days)} targeting {tenants|staff}; cadence {daily|weekly}. Decision: {Proof Required|Renewal Due (X days)}.”

• Caption template

• “A4 Alerts — {property/portfolio}. Start {YYYY-MM-DD}, stop {YYYY-MM-DD}, recipients {role or group}, throttle {limit}.”

• Validation checklist

• Time zone set; recipient group defined; throttle/quiet hours set; escalation path present for serial non-response.

Redaction and privacy controls

• Mask personally identifiable information (PII): names, emails, phone numbers, full policy numbers (show last 4), and exact street addresses where not essential for audit.

• Keep visible: property/portfolio name, unit ID, policy effective/expiry dates, status fields, counts and percentages, decision keywords.

• Store redacted PNGs only; retain originals in secure repository with access controls aligned to least privilege.

Evidence packaging and delivery

• Minimum package for each monthly cycle

• A1 x1, A2 x3 (different properties or filtered subsets), A3 x3 (accepted/rejected mix), A4 x1 per alert type.

• Bundle structure

• /{cycle-YYYY-MM}/A1_dashboard/, /A2_yardi-breeze/, /A3_buildium/, /A4_alerts/.

• Chain-of-custody

• Log capturer, timestamp, and hash (SHA-256) for each PNG; include manifest.txt listing filenames and hashes.

Exception handling and notes

• If Yardi Breeze or Buildium screens are customized, capture the custom field map in an additional screenshot and annotate which field drives each decision keyword.

• If third-party renters insurance programs are used, include a screenshot of the integration mapping that sets status to Compliant/Non-Compliant.

• For student housing, capture term-based exceptions (e.g., short leases) with Pending status plus due date.

Quality bar for acceptance

• Screens are legible at 150% zoom with no cropping of critical fields.

• Decision keywords appear verbatim in alt text and captions.

• All screenshots include visible date/time and scope (portfolio/property/unit).

• All artifacts pass redaction checks prior to archival.

Related insurance context

• For liability arising from resident incidents in common areas, see Commercial General Liability.

• For handling resident data and incident notifications securely, see Cyber Insurance.

FAQ for reviewers and auditors

• How often should we refresh evidence? Monthly for owner reporting, and within 24 hours upon lender or insurer request.

• What constitutes sufficient proof? A clear linkage between system status (A2), underlying document (A3), and portfolio summary (A1), plus alert logic (A4) that governs remediation.

• What if a tenant opts out? Mark as Non-Compliant and attach waiver/exception approval per property policy; do not mark Compliant without proof.