Overview: exception handling in Sherpa

Summit Sherpa (tenant/renters insurance compliance tool) is designed to surface only the proofs that need human attention—then capture consistent decisions and an audit trail. Compliance is Canada-wide; insurance placement is not available in Quebec.

This page focuses on operational exception handling. For the broader enforcement operating model, see Turnkey enforcement. For verification and monitoring concepts, see Real-time verification & lapse alerts.

Who this is for

• Compliance managers and portfolio operators who need consistent proof review

• Site teams working resident exceptions in a queue

• Risk leaders who need auditable decision records

• IT/data owners supporting status sync and reporting

What you can do

• Define “pass/fail/in-review” rules for proof-of-insurance (COIs / declarations)

• Standardize rejection reasons and resident remediation steps

• Allow controlled overrides (with required rationale) for edge cases

• Track an audit trail of decisions, communications, and status changes

• Export exception history for audits, lenders, or internal controls

Common exception types (examples)

Sherpa teams typically categorize exceptions into:

• Identity match issues: named insured doesn’t match leaseholder(s) or spelling differs materially

• Address/unit mismatch: proof doesn’t show the correct civic address/unit

• Date coverage gap: effective date starts after move-in, or expiry occurs during an active lease

• Limit shortfall: liability limit below the portfolio standard

• Evidence quality: incomplete document, missing pages, unreadable image

COI review rules (operational checklist)

When defining your review rules, document:

1. Required fields (minimum set): named insured(s), address/unit, effective date, expiry date, liability limit

2. Tolerance rules: allowed abbreviations, unit formatting, minor name variations

3. Lease rules: how to handle co-tenants, roommate turnover, or lease renewals

4. Status definitions: what triggers “in review,” “rejected,” “verified,” and “lapsed”

If you need more detail on program design and standard-setting, start with Renters insurance compliance.

Rejections: make them consistent and easy to fix

A rejection should answer two questions: why it failed and how to fix it.

Suggested standard rejection reasons:

• Missing required page(s)

• Address/unit missing or incorrect

• Named insured missing / does not match lease

• Effective date does not cover move-in

• Policy expired / renewal proof required

• Liability limit below requirement

Overrides: controlled, documented exceptions

Overrides are useful when:

• A carrier-issued document format doesn’t include an expected field, but coverage can be reasonably confirmed

• A resident is mid-renewal and can provide binding confirmation

• A unit identifier is formatted differently across systems, but the civic address is clear

Operational guardrails:

• Require a written rationale for every override

• Limit override permission to designated roles

• Review override patterns monthly to see if a rule should be updated instead

Audit trail: what to capture

For audit-ready records, maintain:

• Who made the decision and when

• The proof reviewed (or a reference to it)

• The rule(s) applied and the outcome (verified/rejected/override)

• Resident communications sent and timestamps

• Any downstream actions triggered (e.g., status update, export/webhook event)

For integration patterns that transmit status changes, see Tenant insurance webhooks & CSV.

FAQ

Is Sherpa doing legal review of policies? Sherpa supports operational verification against your defined standards. It does not replace legal advice on lease language or provincial tenancy rules.

Can we standardize rejection messages across all properties? Yes—standard reasons and templates reduce back-and-forth and improve consistency.

What if a company operates in multiple provinces? Sherpa can manage compliance Canada-wide; insurance placement is not available in Quebec.

How do we keep exceptions from piling up? Define review SLAs, limit who can override, and tune rules based on the most common exception patterns.

Book a demo

See how Sherpa routes exceptions, captures decisions, and supports audit-ready reporting.

Book a demo