INSURANCE

The Insurance module provides a central operating record for property insurance policies, claims, related documents, lease insurance requirements, Client insurance, property inventory and portfolio-level risk and compliance oversight.

Leaseora Jul 30, 2026 36 min read 12 views

LEASEORA

INSURANCE

Detailed User and Technical Operations Guide

Policies • Renewals • Claims • Blockchain Verification • Analytics • Commercial Portfolio • Renters Insurance • Property Inventory • Corporate Cover • Compliance

For real estate companies, landlords, insurance administrators, claims teams, property managers, commercial portfolio teams, Clients, corporate occupiers, compliance teams and authorised platform administrators

Version 1.0 | July 2026

Purpose of this guide

This guide explains how a real estate company uses Leaseora's Insurance module from portfolio review, policy creation, expiry monitoring and renewal through policy-document registration, claim filing, evidence management, status updates, analytics, commercial portfolio controls, lease insurance-provider notifications, Client renters insurance, digital property inventory, corporate insurance and SuperAdmin compliance oversight. It also provides detailed technical reference based on the supplied models, controllers, mail class, blockchain fields and AI tools.

1 Purpose, Audience and Scope

Item	Description
Primary users	Real estate companies, landlords, property managers, insurance administrators, claims teams, commercial portfolio teams, Clients, corporate tenants and SuperAdmins.
Policy scope	Building, contents, liability, landlord, flood, fire, combined and other configured insurance types.
Claims scope	Incident reporting, documents, adjuster details, status, approved amount, denial reason and settlement.
Evidence scope	Document Hub linkage and policy or claim-document blockchain verification fields.
AI scope	Coverage recommendations, portfolio risk, claim assistance, policy optimisation, commercial cost benchmarking and Client guidance.
Operational boundary	Leaseora records, assists and analyses insurance information. It is not an insurer, broker, claims adjuster, legal adviser or guarantee of coverage, approval, settlement or compliance.

Use Client-facing language

Business instructions use Client where appropriate. Technical controller and model names retain Tenant when that is part of the supplied implementation.

2 Complete Insurance Lifecycle

Figure 1. Complete Insurance lifecycle

Stage	Business outcome
Assess	Identify properties, risk, obligations and coverage needs.
Create	Record policy details, dates, premiums, deductible and insurer.
Verify	Link documents and register tamper-evidence where used.
Monitor	Track Active, Expiring, Expired, Cancelled and Renewed records.
Claim	Record incident, amount, evidence and adjuster information.
Process	Move claims through review, approval, rejection and settlement.
Analyse	Review costs, claims, coverage gaps, risk and optimisation.
Client	Support renters policies, inventory and personal-claim workflows.
Govern	Apply compliance, audit, reporting and violation controls.

3 Roles, Responsibilities and Separation of Duties

Role	Main responsibility	Control
Insurance Administrator	Creates and maintains policy records.	Should not approve unsupported coverage or claims outcomes.
Property Manager	Confirms property facts and incidents.	Should provide accurate property and event evidence.
Claims Coordinator	Files and manages claims.	Should preserve evidence and status history.
Finance Reviewer	Reviews premium, deductible and settlement records.	Should reconcile insurer documents and payment records.
Compliance Officer	Checks mandatory coverage and violations.	Should use jurisdiction-specific requirements.
Client	Maintains renters insurance and personal inventory.	Can access only their own records.
Corporate Insurance Manager	Manages multi-location and specialist corporate cover.	Should document per-location limits and compliance.
SuperAdmin	Provides platform-wide configuration and oversight.	Intervention should be reasoned, authorised and audited.

Recommended control

Policy creation, document verification, claim status approval and compliance resolution should use separate permissions where staffing permits.

4 Before Using the Insurance Module

☐	Properties and ownership records are complete.
☐	Supported policy and coverage types are configured.
☐	Jurisdiction-specific minimum coverage requirements are documented.
☐	Document Hub storage and permissions are configured.
☐	Blockchain registration provider and failure handling are configured if used.
☐	Policy renewal and expiry-alert ownership is assigned.
☐	Claim-number generation and evidence-storage rules are configured.
☐	AI output review and escalation rules are documented.
☐	Client and corporate insurance permissions are configured.
☐	Audit, retention, privacy and export controls are approved.

Pilot with non-critical records

Test the complete policy, expiry, claim, document, analytics and compliance flow with controlled records before relying on the module for live insurance operations.

5 Phase 1 - Landlord Insurance Dashboard

STEP
1

Open the Insurance Dashboard

Primary user: Landlord insurance administrator

Navigate to Insurance -> Dashboard. InsuranceController@index uses OpenAIService and aggregates InsurancePolicy and InsuranceClaim data.

Dashboard area	Purpose
Policy status	Active, expiring, expired, pending and cancelled policies.
Claims status	Open claims and their current workflow stage.
Coverage	Total insured amounts across the portfolio.
Premium	Premium totals and normalised monthly or annual cost.
Deductible	Deductible or excess exposure.
Expiring in 30 days	InsurancePolicy::scopeExpiring(30).
AI recommendations	Coverage gap, over-insurance and cost suggestions.
Risk assessment	Property and portfolio risk indicators.

Dashboard totals depend on currency rules

If a portfolio contains multiple currencies, do not sum amounts without an approved reporting currency and exchange-rate date. The supplied scenario does not define an insurance FX service.

6 Dashboard Review Routine

1. Review policies already expired or cancelled.

2. Review policies expiring within 30, 60 and 90 days where configured.

3. Check properties with no current policy.

4. Review open claims and long processing times.

5. Check rejected claims and denial reasons.

6. Review deductible exposure and premium concentration.

7. Review failed or pending blockchain registrations.

8. Review AI recommendations as advisory observations.

AI method	Purpose	Human review
getAIRecommendations	Coverage gaps, over-insurance and cost optimisation.	Validate policy wording, property value and insurer quotation.
getClaimsAIAssistance	Claim evidence checklist and outcome indicators.	Insurer and authorised claims staff decide the claim.
getRiskAssessment	Portfolio risk identification.	Confirm data quality, exposure and mitigation actions.

AI is advisory

Do not present generated output as professional insurance advice, binding underwriting or guaranteed claim approval.

7 Phase 2 - Create an Insurance Policy

STEP
2

Create the Property-Linked Policy Record

Primary user: Insurance administrator

Use InsurancePolicyController@create and @store.

Field	How it is used
user_id	Owning landlord.
property_id	Covered property.
policy_name	Internal descriptive title.
policy_number	Insurer policy reference.
policy_type	Building, contents, liability, landlord, flood, fire, combined or configured type.
insurance_company	Insurer name.
insurance_provider	Broker or provider contact.
coverage_type	Comprehensive, third-party, named-perils or all-risk.
coverage_amount	Declared insured value or limit.
premium_amount	Premium under the selected frequency.
deductible_amount	Excess payable per claim.
payment_frequency	Monthly, quarterly or annual.
effective_date / expiry_date	Policy term.
status	Pending, Active, Expired or Cancelled.
policy_document	Stored policy document path.
notes	Restricted internal notes.
renewal_status	Pending, Renewed or Not Renewed.
document_hub_id	Linked document record.

A policy record is not proof of coverage by itself

Confirm the insurer-issued policy, effective date, insured entity, property, endorsements, exclusions and payment status before relying on the record.

8 Fetch and Validate Property Details

InsurancePolicyController@getPropertyDetails retrieves property information to pre-fill policy fields.

☐	The property belongs to the authenticated landlord.
☐	Address and property type are current.
☐	Building value or declared value uses an approved source.
☐	Occupancy and use are current.
☐	Construction, age and risk data are reviewed.
☐	Pre-filled data remains editable and auditable.

Pre-fill reduces entry effort but not responsibility

Property data may be incomplete or stale. The insurance administrator must verify it against current insurer requirements.

9 Policy and Coverage Types

Policy type	Typical purpose
Building	Physical structure and insured building elements.
Contents	Furniture, equipment or landlord-owned contents.
Liability	Third-party bodily injury or property damage liability.
Landlord	Landlord-specific package cover.
Flood	Defined flood-related perils.
Fire	Defined fire-related loss.
Combined	Multiple cover sections in one policy.

Coverage type	Meaning
Comprehensive	Broad configured protection subject to wording and exclusions.
Third-party	Liability to others rather than own-property loss.
Named-perils	Only listed perils are covered.
All-risk	Broad accidental-loss cover subject to exclusions.

Policy wording controls actual cover

Labels in Leaseora are summaries. The insurer-issued schedule, wording, endorsements, exclusions and local law remain authoritative.

10 Coverage, Premium and Deductible

☐	coverage_amount uses the correct currency and valuation basis.
☐	premium_amount corresponds to payment_frequency.
☐	deductible_amount reflects per-claim or other insurer wording.
☐	Taxes, fees or levies are recorded or clearly excluded.
☐	Co-insurance, sub-limits and aggregate limits are documented where relevant.
☐	Coverage is not duplicated across policies without review.

getMonthlyPremiumAttribute and getAnnualPremiumAttribute normalise premium cost from the selected frequency.

Normalised premium is a reporting calculation

It does not alter insurer billing dates or prove that premium instalments were paid.

11 Policy Dates and Status Lifecycle

Figure 2. Insurance policy status and renewal flow

Method / scope	Purpose
scopeActive	Returns Active policies.
scopeExpiring(days)	Returns policies expiring within the configured period.
scopeExpired	Returns expired policies.
isActive	Checks current policy status and dates under model logic.
isExpiringSoon	Checks renewal window.
daysUntilExpiry	Returns days to expiry.

12 Upload and Link the Policy Document

☐	Upload the complete insurer-issued document.
☐	Verify the file belongs to the correct policy and property.
☐	Store it in the protected document location.
☐	Link document_hub_id where the Document Hub is used.
☐	Record version and issue date where supported.
☐	Scan the file for malware.
☐	Restrict access to authorised landlord, compliance and claims users.

Do not overwrite the original policy silently

A revised schedule, endorsement or renewal should retain version history and the original evidence needed for claims or audit.

13 AI Assistance During Policy Creation

InsurancePolicyController@getAIRecommendations may suggest policy types, coverage amounts and providers based on property type, location and value.

☐	Review the property data used by the AI.
☐	Separate objective gaps from speculative suggestions.
☐	Do not send sensitive property or policy data beyond approved processing boundaries.
☐	Obtain insurer or qualified adviser confirmation.
☐	Record whether the suggestion was accepted, modified or rejected.

AI provider suggestions are not procurement approval

A recommendation should not imply that a provider is licensed, available, competitive or suitable in the jurisdiction without verification.

14 View and Manage the Policy Register

STEP
3

Use the Policy Register

Primary user: Insurance administrator

InsurancePolicyController@index lists policies with status, property, type and expiry filters. @show displays coverage, premium, claim history, documents and blockchain status.

Operation	Purpose
edit / update	Correct or update policy metadata.
destroy	Delete under authorised retention rules.
expiring	Dedicated 30-day renewal view.
renew	Records the new term and renewal status.

Deletion should be exceptional

Policies connected to claims, audit, lender requirements or legal retention should usually be archived or retained rather than permanently deleted.

15 Policy Detail Review

☐	Policy and property relationship is correct.
☐	Effective and expiry dates are correct.
☐	Coverage, premium and deductible match the document.
☐	Insurer and provider names are current.
☐	Claim history belongs to the policy.
☐	Document Hub link opens the correct record.
☐	Blockchain status corresponds to the current document version.
☐	Internal notes are restricted.

16 Renew an Insurance Policy

STEP
4

Process a Policy Renewal

Primary user: Insurance administrator

1. Open the Expiring Policies view.

2. Obtain the insurer renewal schedule or new policy.

3. Compare coverage, exclusions, limits, premium and deductible.

4. Upload or link the new policy document.

5. Set the new expiry date.

6. Set renewal_status = renewed.

7. Set last_renewed_at = now.

8. Keep status Active where coverage is continuous.

9. Register the current document hash if blockchain verification is used.

10. Retain the prior term and document history.

Renewal should not merely extend the date

A renewal can change insurer, policy number, coverage, endorsements, premium, deductible and exclusions. Review and record all material changes.

17 Expired, Cancelled and Not-Renewed Policies

☐	Confirm expiry_date has passed or cancellation is documented.
☐	Set status and renewal_status consistently.
☐	Identify affected properties and lease obligations.
☐	Notify responsible staff.
☐	Block false representation of current coverage.
☐	Preserve historical documents and claims.
☐	Trigger compliance review where minimum coverage is required.

18 Phase 3 - Blockchain Policy Verification

Figure 3. Policy and claim-document blockchain verification

Policy field	Purpose
blockchain_hash	Fingerprint of the registered policy document or data.
blockchain_tx_hash	Transaction reference.
blockchain_block_number	Block containing the record.
blockchain_status	Pending, Confirmed or Failed.
blockchain_registered_at	Registration timestamp.

Blockchain does not prove truth or legal validity

It can provide tamper-evidence for the registered bytes and timestamp. It does not prove that the policy is genuine, paid, in force, legally sufficient or issued by an authorised insurer.

19 Policy Blockchain Registration Procedure

1. Select the approved policy document version.

2. Create a cryptographic hash.

3. Submit the hash through the configured blockchain service.

4. Set blockchain_status = pending.

5. After confirmation, store transaction hash, block number and registration time.

6. Set status = confirmed.

7. If submission fails, store failed status and error context.

8. Verify later by hashing the same file and comparing the result.

Never register secrets or personal data directly on-chain

20 Version and Amendment Control

☐	Each materially changed document receives a new hash.
☐	The current policy record identifies the current document.
☐	Prior hashes remain linked to prior versions.
☐	Endorsements are stored separately or with clear version labels.
☐	A failed blockchain transaction is retried safely without duplicate ambiguity.

21 Phase 4 - File an Insurance Claim

STEP
5

Create a Claim After an Incident

Primary user: Claims coordinator

Use InsuranceClaimsController@create and @store.

Field	How it is used
user_id	Filing landlord.
policy_id	Policy claimed against.
property_id	Affected property.
claim_number	Unique auto-generated claim reference.
incident_type	Fire, flood, theft, vandalism, storm, liability or configured type.
incident_date	Date of incident.
incident_description	Factual account of what happened.
claim_amount	Amount requested.
approved_amount	Insurer-approved amount when known.
status	Pending, Under Review, Approved, Rejected, Settled or Cancelled.
filed_date	Submission date.
processed_date	Insurer processing decision date.
settlement_date	Settlement date.
adjuster_name / contact	Assigned adjuster information.
documents	Evidence files.
notes	Restricted internal notes.
denial_reason	Reason for rejection.

Record facts, not speculation

Incident descriptions should distinguish observed facts, reported information, estimated loss and unverified assumptions.

22 Claim Filing Checklist

☐	The policy was effective on the incident date.
☐	The affected property is covered by the selected policy.
☐	The incident type is plausibly within the policy section.
☐	Immediate safety and emergency actions were completed.
☐	Insurer notification deadlines are checked.
☐	The claim amount has a documented basis.
☐	Evidence files are original and dated where possible.
☐	Police, fire or authority reports are included where required.
☐	Repair quotations and loss estimates are labelled as estimates.
☐	No admission of liability is made without authority.

23 Claim Document Upload and Evidence

InsuranceClaimsController@uploadDocuments adds photos, repair quotations, police reports or other evidence.

☐	File type and size are validated.
☐	Evidence belongs to the claim.
☐	Original file metadata is preserved where appropriate.
☐	Personal and sensitive information is protected.
☐	Each document links to its Document Hub record where used.
☐	Each blockchain array entry aligns to the same document index.
☐	Upload, creator and timestamp are recorded.

Preserve originals

Image compression, editing or conversion can change the hash and evidential value. Keep the original file and any processed copy separately.

24 Claim Document Blockchain Arrays

Field	Purpose
document_hub_ids	Document Hub record IDs per evidence item.
blockchain_hashes	Hash per evidence item.
blockchain_tx_hashes	Transaction hash per item.
blockchain_block_numbers	Block number per item.
blockchain_statuses	Pending, Confirmed or Failed per item.

Array alignment is critical

All claim-document arrays must use the same document ordering or a structured per-document record. Misaligned arrays can associate the wrong hash with evidence.

25 Claim Status Lifecycle

Figure 4. Insurance claim status lifecycle

Status	Meaning
Pending	Filed and awaiting review.
Under Review	Insurer or adjuster is assessing the claim.
Approved	Claim accepted for an approved amount.
Rejected	Claim denied with a recorded reason.
Settled	Approved settlement completed or recorded.
Cancelled	Claim withdrawn or cancelled under allowed rules.

26 Manage Claims

STEP
6

Review and Update Claims

Primary user: Claims coordinator

Operation	Purpose
index	List claims with status, property, policy, incident and date filters.
show	View incident, documents, adjuster, history and blockchain status.
edit / update	Correct allowed claim data.
updateStatus	Move the claim through its authorised lifecycle.
status	Filter by a selected status.
cancel	Cancel a Pending claim.
addNote	Add restricted internal note.
uploadDocuments	Add evidence.
export	Export authorised claim data.

27 Claim Status Update Controls

☐	Status transition is permitted from the current status.
☐	Actor has authority for the transition.
☐	Approved amount is present before Approved where required.
☐	denial_reason is present before Rejected.
☐	processed_date is recorded for insurer decision.
☐	settlement_date is recorded for Settled.
☐	Notes explain manual overrides or exceptional transitions.
☐	Notifications or reports use the updated source status.

Leaseora status may record an insurer decision but should not fabricate it

Only update Approved, Rejected or Settled from documented insurer or authorised claims information.

28 Claim Notes and Adjuster Information

☐	Adjuster name and contact are accurate and access-controlled.
☐	Notes distinguish internal analysis from insurer communication.
☐	Do not place legal privilege or highly sensitive data in broadly visible fields.
☐	Each note records author and timestamp where implemented.
☐	Corrections preserve audit history.

29 AI Claims Assistance

InsuranceClaimsController@getAIAssistance can produce a document checklist, predicted approval probability, suggested claim amount and process tips.

☐	Provide only approved claim data to the AI service.
☐	Review the suggested checklist against policy wording.
☐	Do not increase a claim amount solely from AI output.
☐	Do not present approval probability as an insurer commitment.
☐	Retain human review and escalation.
☐	Record that output was advisory.

Claims outcome prediction can be misleading

Past claims may not share the same wording, jurisdiction, evidence, cause, exclusions or insurer. The insurer actual decision controls.

30 InsuranceClaim Model Methods and Scopes

Method / scope	Purpose
scopePending	Pending claims.
scopeApproved	Approved claims.
scopeRejected	Rejected claims.
scopeActive	Pending and Under Review claims.
scopeSettled	Settled claims.
isPending / Approved / Rejected / Settled	Status checks.
getProcessingDays	Days from filed date to processed date.
getStatusColorAttribute	UI status colour.
getDocumentHubsAttribute	Linked Document Hub records.
policy / property / user	Parent relationships.

Processing time requires complete dates

Open claims may need a separate days-open calculation because processed_date is not yet available.

31 Phase 5 - Insurance Analytics

STEP
7

Review Portfolio Insurance Analytics

Primary user: Insurance manager / analyst

InsuranceAnalyticsController@index provides cost, claims, risk, optimisation and reporting views.

Analytics section	Purpose
costAnalysis	Premium cost by property and type, trends and premium-to-coverage ratio.
claimsAnalytics	Frequency, average amount, approval, denial, settlement time and incident type.
riskAssessment	AI-assisted property risk scores and factors.
policyOptimization	Coverage gaps, consolidation, over-insurance and cost reduction.
reports	Custom report by dates, property, policy type or claim status.
export	CSV, Excel or PDF export.

32 Insurance Cost Analysis

☐	Premium frequency is normalised consistently.
☐	Currency is stated.
☐	Cancelled and expired policies are separated.
☐	Coverage amount basis is consistent.
☐	Taxes and fees are included or excluded consistently.
☐	Multi-property policies are not double-counted.
☐	Premium changes are compared against coverage changes.

33 Claims Analytics

Metric	Definition to confirm
Claim frequency	Claims per policy, property, exposure period or another denominator.
Average claim amount	Filed, approved or settled amount.
Approval rate	Approved claims divided by eligible decided claims.
Denial rate	Rejected claims divided by eligible decided claims.
Settlement time	Filed-to-settled or approved-to-settled days.
Claims ratio	Claims amount divided by premium under a defined basis.

Always label the denominator and amount basis

Filed, approved and settled values can produce very different analytics.

34 Risk Assessment and Policy Optimisation

Figure 5. AI, analytics and compliance across Insurance

AI risk scores are prioritisation tools

Do not use them as a substitute for engineering surveys, valuations, legal requirements, insurer underwriting or human review.

35 Analytics Export Controls

☐	Landlord scope is applied.
☐	Date range and reporting timezone are stated.
☐	Currency and exchange-rate assumptions are stated.
☐	Claimant, adjuster and provider personal data are minimised.
☐	Blockchain transaction details are included only where necessary.
☐	Exports are encrypted or access-controlled where appropriate.
☐	Retention and deletion are documented.

36 Phase 6 - Commercial Portfolio Insurance

STEP
8

Manage Insurance Across Commercial Properties

Primary user: Commercial insurance manager

Commercial area	Purpose
portfolio	Total coverage, premiums, claims ratio and coverage gaps.
multiPropertyPolicies	Umbrella or blanket policies covering multiple properties.
renewalManagement	Renewal calendar, bulk processing and negotiation tracking.
claimsProcessing	High-value, multi-property and business interruption claims.
costOptimization	Premium benchmarking, bundle opportunities and risk reduction.
complianceManagement	Regulatory, lender and lease-required coverage compliance.
reports / export	Commercial reporting and data export.

37 Multi-Property and Blanket Policies

☐	The policy is linked to every covered property.
☐	Per-property allocation or sub-limit is recorded.
☐	Aggregate limit is documented.
☐	Property additions and removals retain effective dates.
☐	Claims reduce limits according to policy wording.
☐	Analytics do not count total blanket coverage once per property unless intentionally allocated.

Avoid double-counting umbrella limits

A single aggregate policy limit should not be multiplied by the number of properties in portfolio totals.

38 Commercial Renewal Management

1. Review the portfolio renewal calendar.

2. Prioritise policies by expiry, value and risk.

3. Collect updated property, occupancy and loss information.

4. Track insurer quotations and negotiation points.

5. Compare limits, exclusions, deductibles and premium.

6. Approve the selected renewal under authority.

7. Update each linked property and document.

8. Record the renewal and compliance outcome.

39 Commercial Claims, Cost and Compliance

☐	High-value claims have dedicated authority and evidence review.
☐	Business interruption calculations use documented financial data.
☐	Bundle discounts do not create unacceptable insurer concentration.
☐	Risk-reduction recommendations have cost, owner and due date.
☐	Lender and lease requirements are monitored.
☐	Commercial reports separate aggregate and per-property data.

40 Phase 7 - Lease Insurance Provider

STEP
9

Record a Client Insurance Provider for a Lease

Primary user: Landlord lease administrator

LeaseInsuranceProvider field	Purpose
lease_id	Linked lease.
name	Provider contact name.
email / phone	Provider contact details.
company	Insurance company.
policy_details	JSON policy information.
coverage_amount	Recorded coverage.
policy_start_date / end_date	Coverage period.
email_sent / email_sent_at	Provider notification tracking.

41 Lease Insurance Requirement Review

☐	The lease actually requires insurance.
☐	Required type and minimum amount are clear.
☐	Provider and policy belong to the Client.
☐	Policy dates cover the lease period or renewal reminders are set.
☐	Coverage evidence is stored.
☐	Landlord does not misrepresent that the insurer confirmed coverage unless confirmation was received.

42 Notify the Insurance Provider

STEP
10

Send the Lease Coverage Verification Request

Primary user: Landlord lease administrator

InsuranceProviderNotificationMail is constructed from LeaseInsuranceProvider and Lease. It informs the provider about the property, lease requirements, landlord contact and verification request.

1. Confirm the provider email address.

2. Check that the Client has consented or the communication is otherwise authorised.

3. Build the message with the correct lease and requirement.

4. Send InsuranceProviderNotificationMail.

5. Call markEmailSent after successful sending.

6. Use hasEmailBeenSent to prevent unintended duplicates.

Email sent is not provider confirmation

The model records that the notice was sent, not that the insurer accepted, verified or amended coverage.

43 Provider Notification Privacy

☐	Include only necessary lease and property information.
☐	Do not include unrelated Client financial or personal data.
☐	Use secure communication where required.
☐	Retain the sent message and provider response.
☐	Handle bounced or invalid email addresses.

44 Phase 8 - Client Insurance Dashboard

STEP
11

View Client-Linked Insurance

Primary user: Client

TenantInsuranceController@index lists policies linked to the authenticated Client. @show displays a selected policy.

☐	Client sees only their own policies.
☐	Lease and policy relationships are correct.
☐	Coverage, deductible and dates are clear.
☐	Payment status and upcoming premium dates are clear where available.
☐	Provider contact is displayed appropriately.

45 Client Insurance Recommendations

TenantInsuranceController@recommendations suggests suitable renters insurance based on property type, location, belongings value, lease requirements and budget.

Recommendations are informational

The Client should review actual insurer terms, exclusions, eligibility, price and regulatory disclosures before purchasing or changing a policy.

46 Client Property Inventory

Figure 6. Client renters insurance and property inventory flow

TenantInsuranceController@propertyInventory provides a digital belongings inventory.

Inventory field	Purpose
Item name	Clear item identification.
Description	Brand, model, features and condition.
Purchase date	Acquisition date.
Purchase price	Original cost.
Current value	Current estimated value and valuation date.
Serial number	Unique identifier where applicable.
Photos	Ownership and condition evidence.

47 Add and Maintain Inventory Items

STEP
12

Create a Personal Property Inventory Item

Primary user: Client

1. Open Property Inventory.

2. Enter the item name and description.

3. Record purchase date and price.

4. Estimate current value with a date and basis.

5. Add serial number where applicable.

6. Upload clear photographs and receipt evidence where available.

7. Save the inventory item.

8. Update the record after sale, disposal, replacement or appraisal.

Inventory value is not automatically the insured settlement value

Insurers may apply limits, depreciation, replacement-cost rules, exclusions, proof requirements and deductibles.

48 Inventory Evidence, Appraisal and Exports

☐	Photos do not expose unnecessary home-security details.
☐	Serial numbers and receipts are access-controlled.
☐	High-value items have appraisal or specialist evidence where appropriate.
☐	Original files are retained.
☐	Deleted or disposed items remain in history where needed.
☐	Exports are stored securely.

Operation	Purpose
requestAppraisal	Requests professional appraisal support for a high-value item.
exportInventoryPDF	Human-readable insurer submission or personal record.
exportInventoryCSV	Structured data export.

An inventory export contains sensitive asset information

Protect it with appropriate storage, sharing and deletion controls.

49 Client Files an Insurance Claim

STEP
13

Submit a Client Claim

Primary user: Client

TenantInsuranceController@fileClaim or @claimsFile opens the form. @storeClaim or @claimsStore submits the record. @uploadDocuments adds evidence.

☐	The selected policy belongs to the Client.
☐	The incident date and description are complete.
☐	Claimed items are linked to inventory where appropriate.
☐	Receipts, photos or authority reports are uploaded.
☐	The Client understands that submission is not approval.
☐	The claim status can be tracked through claimsIndex and claimsShow.

50 Client Claims AI Assistance

TenantInsuranceController@claimsAssistance and @getAIAssistance explain potential cover, documentation and claim steps.

Do not state that an item is covered without checking the policy

AI guidance should clearly separate general process information from insurer-specific coverage and decision-making.

51 Client Policy and Premium Management

Operation	Purpose
payments	View premium payment history and upcoming payments.
updatePolicy	Submit or record allowed policy changes.
cancelPolicy	Cancel under permitted rules.

Policy changes may require insurer approval

Updating a Leaseora record does not itself amend the insurer contract or create cover.

52 Phase 9 - Corporate Tenant Insurance

STEP
14

Manage Corporate Cover Across Locations

Primary user: Corporate insurance manager

Corporate area	Purpose
liabilityInsurance	Public, product and professional liability.
workersCompensation	Employee and location coverage under local law.
businessInterruption	Revenue loss and waiting-period cover.
multiLocationInsurance	Consolidated and per-location limits.
claimsManagement	Commercial, multi-location and liability claims.
complianceDashboard	Regulatory, lease and certificate compliance.
reports / export	Corporate reports and data export.

☐	Every covered location is listed.
☐	Per-location limits and aggregate limits are clear.
☐	Employee counts and payroll basis are current where relevant.
☐	Business interruption waiting periods and indemnity periods are recorded.
☐	Certificates of insurance are current.
☐	Local labour and liability requirements are reviewed.

53 Phase 10 - SuperAdmin Insurance System

STEP
15

Monitor the Platform Insurance System

Primary user: SuperAdmin

System area	Purpose
platformManagement	Total policies, claims, approvals, settlements and fee tracking.
userManagement	View authorised user insurance records and support disputes.
analytics / systemAnalytics	Platform policy, premium, claims and provider metrics.
systemConfiguration	Policy types, coverage types, minimums, fees and blockchain settings.
systemMonitoring	Active, expiring, open-claim and blockchain queue monitoring.
reports / export	Platform-wide reporting.
updateConfiguration	Controlled configuration changes.

SuperAdmin override is high-impact

Override of claim status, policy data or compliance result should require authority, reason, previous value and notification to the affected user where appropriate.

54 Platform Configuration Checklist

☐	Supported policy types are maintained.
☐	Coverage types and minimums are jurisdiction-aware.
☐	Insurance service fees are transparent.
☐	Blockchain network and retry settings are controlled.
☐	Default expiry windows and alerts are configured.
☐	Export and retention rules are configured.
☐	Provider performance definitions are documented.

55 Phase 10 - Insurance Compliance

STEP
16

Review Insurance Compliance

Primary user: SuperAdmin compliance officer

Compliance operation	Purpose
regulatoryOversight	Jurisdiction requirements and filing deadlines.
policyCompliance	Coverage minimums, lapse and lease-required status.
auditTrail	Policy, claim, document and blockchain actions.
riskAssessment	Coverage inadequacy, concentration and claim-pattern risks.
reports / complianceReports	Compliance reporting.
updateSettings	Compliance configuration.
triggerComplianceReview	Manual review.
resolveViolation	Resolve a compliance issue.

56 Compliance Violation Workflow

1. Detect a lapsed, inadequate or missing policy.

2. Create or identify the violation record.

3. Record jurisdiction, requirement, affected property and evidence.

4. Assign an owner and due date.

5. Notify the responsible party.

6. Upload replacement or corrective evidence.

7. Review the correction.

8. Use resolveViolation with resolution notes and date.

9. Retain the violation and audit history.

Compliance configuration is not legal advice

Requirements can differ by country, state, property type, lender, lease and insurer. Use qualified local review.

57 Audit Trail Requirements

☐	Policy creation, update, renewal, cancellation and deletion are logged.
☐	Claim filing, status updates, approval, rejection and settlement are logged.
☐	Document upload, replacement and deletion are logged.
☐	Blockchain submission and status changes are logged.
☐	SuperAdmin overrides record previous and new values.
☐	Violation creation and resolution are logged.
☐	Export activity is logged where appropriate.

58 Backend Models Reference

Model	Purpose
InsurancePolicy	Policy, property, coverage, premium, dates, documents, renewal and blockchain.
InsuranceClaim	Incident, amounts, status, adjuster, documents and blockchain arrays.
LeaseInsuranceProvider	Client insurance provider linked to a lease.

59 Controllers Reference

Controller	Purpose
InsuranceController	Landlord dashboard, AI recommendations, claim assistance and risk.
InsurancePolicyController	Policy CRUD, expiring view, renewal, property pre-fill and AI.
InsuranceClaimsController	Claim CRUD, status, notes, documents, AI and export.
InsuranceAnalyticsController	Costs, claims, risk, optimisation, reports and export.
CommercialInsuranceController	Commercial portfolio, multi-property, renewals, claims, cost and compliance.
TenantInsuranceController	Client policies, claims, inventory, appraisals, payments and AI.
CorporateInsuranceController	Corporate liability, workers compensation, interruption, locations and compliance.
InsuranceSystemController	Platform management, users, analytics, configuration, monitoring and reports.
InsuranceComplianceController	Regulatory, policy compliance, audit, risk and violations.

60 Services, Mail and Relationships Reference

Component	Purpose
OpenAIService	Portfolio, risk, policy and claim advisory outputs.
InsuranceProviderNotificationMail	Provider lease-requirement notification.
InsurancePolicy.documentHub	Central document relationship.
InsurancePolicy.claims	Claims filed against the policy.
InsuranceClaim.policy / property / user	Claim ownership and context.
LeaseInsuranceProvider.lease	Lease relationship.

61 AI-Powered Features Reference

AI feature	Controller / service	Purpose
Portfolio recommendations	InsuranceController@getAIRecommendations	Coverage gaps, over-insurance and cost opportunities.
Claims assistance - landlord	InsuranceController@getClaimsAIAssistance	Claim analysis and evidence guidance.
Portfolio risk	InsuranceController@getRiskAssessment	Property risk and exposure overview.
Policy recommendations	InsurancePolicyController@getAIRecommendations	Suggested types, limits and providers.
Claim assistance	InsuranceClaimsController@getAIAssistance	Checklist, approval indicator and amount guidance.
Analytics risk	InsuranceAnalyticsController@riskAssessment	Risk dashboard.
Policy optimisation	InsuranceAnalyticsController@policyOptimization	Consolidation and coverage-gap analysis.
Commercial cost	CommercialInsuranceController@costOptimization	Benchmarking and bundle opportunities.
Client recommendations	TenantInsuranceController@recommendations	Renters insurance suggestions.
Client claims help	TenantInsuranceController@claimsAssistance	Step-by-step process guidance.

62 Security, Privacy and Confidentiality

☐	Policy numbers, tax information and insurer contacts are restricted.
☐	Claims evidence and incident details are access-controlled.
☐	Client inventory, receipts, serial numbers and photos are protected.
☐	Adjuster and provider personal data are minimised.
☐	Blockchain stores hashes rather than documents or personal data.
☐	Document Hub permissions follow landlord and Client ownership.
☐	Exports are protected and retained appropriately.
☐	AI processing uses approved data boundaries.
☐	SuperAdmin access and overrides are audited.

Insurance data is highly sensitive

It can reveal property value, security exposures, incidents, belongings, injuries and disputes. Apply least-privilege access and secure retention.

63 Daily, Weekly and Monthly Operating Procedures

Frequency	Recommended activities
Daily	Review new claims, urgent evidence requests, failed blockchain registrations and policies already expired.
Weekly	Review expiring policies, open claims, processing days, denied claims, compliance violations and provider responses.
Monthly	Close premium and claim analytics, review coverage gaps, insurer concentration, inventory security and document versions.
Quarterly	Review policy types, compliance rules, AI governance, blockchain configuration, access, retention and audit completeness.

64 Worked Example 1 - Building Policy Creation and Renewal

Scenario

A real estate company records annual building insurance for a residential block.

Stage	What happens
1. Assess	The administrator confirms property, value, insurer and required cover.
2. Create	The policy record is created as Pending.
3. Document	The insurer PDF is uploaded and linked to Document Hub.
4. Verify	The policy hash is submitted and Confirmed.
5. Activate	Status becomes Active for the effective term.
6. Monitor	scopeExpiring identifies the policy before expiry.
7. Compare	The renewal schedule is compared with the prior term.
8. Renew	New dates, premium, coverage and document are recorded.
9. Preserve	Prior document and blockchain evidence remain in history.

65 Worked Example 2 - Flood Claim

Scenario

A covered property suffers flood damage and the landlord files a claim.

Stage	What happens
1. Safety	Emergency action and damage mitigation occur first.
2. Validate	The policy was effective on the incident date.
3. File	Claim number, date, description and estimated amount are recorded.
4. Evidence	Photos, report and repair quotation are uploaded.
5. Hash	Each evidence item receives aligned blockchain fields.
6. Review	Status changes to Under Review and adjuster is recorded.
7. Decision	Approved amount or denial reason is documented.
8. Settle	Settlement date is recorded after insurer payment outcome.
9. Analyse	Processing time and claim type feed analytics.

66 Worked Example 3 - Client Theft Inventory Claim

Scenario

A Client reports stolen electronics listed in their digital property inventory.

Stage	What happens
1. Inventory	Items already contain serial numbers, purchase values and photos.
2. Incident	The Client records theft details and police report.
3. File	The claim links to the Client policy.
4. Evidence	Receipts, inventory exports and report are uploaded.
5. AI help	The assistant suggests a checklist but does not decide coverage.
6. Track	The Client follows the claim status.
7. Insurer	The insurer evaluates wording, limits, deductible and evidence.

67 Worked Example 4 - Commercial Multi-Property Renewal

Scenario

A commercial portfolio has one blanket policy covering six buildings.

Stage	What happens
1. Link	The policy is linked to all covered properties.
2. Allocate	Per-property values and sub-limits are recorded.
3. Monitor	The renewal calendar identifies the approaching expiry.
4. Update	Occupancy, values and loss information are refreshed.
5. Benchmark	AI supports cost comparison and bundle analysis.
6. Review	The team checks concentration, aggregate limits and deductible.
7. Renew	The selected terms are recorded once without double-counting aggregate cover.

68 Worked Example 5 - Lease Insurance Provider Notification

Scenario

A lease requires the Client to maintain renters liability insurance.

Stage	What happens
1. Record	LeaseInsuranceProvider is created with provider and policy details.
2. Check	Coverage amount and dates are compared with the lease requirement.
3. Consent	The authorised communication basis is confirmed.
4. Send	InsuranceProviderNotificationMail requests verification.
5. Mark	markEmailSent records the successful send.
6. Response	Provider confirmation or exception is stored.
7. Monitor	Expiry is tracked through the lease period.

69 Implementation and Onboarding Checklist

Policy and document setup

☐	Policy and coverage type catalogues are configured.
☐	Property ownership and valuation data are available.
☐	Document Hub relationship and storage are configured.
☐	Expiry and renewal alerts are assigned.
☐	Blockchain provider and retry rules are configured if used.

Claims setup

☐	Claim number generation is unique.
☐	Incident types and status transitions are configured.
☐	Evidence upload limits and security are configured.
☐	Approved, rejected and settled permissions are separated.
☐	Claim exports and reports are scoped.

Client, commercial and compliance setup

☐	Client policy and inventory permissions are tested.
☐	Corporate location and certificate data are configured.
☐	Commercial multi-property allocation rules are defined.
☐	Compliance minimums are jurisdiction-aware.
☐	SuperAdmin override and audit controls are configured.

70 User Acceptance Testing and Go-Live

Test area	Acceptance test
Dashboard	Validate policy, claim, premium, deductible and expiry totals.
Currency	Validate reporting currency or prevent invalid sums.
Create policy	Required fields, property scope and dates.
Property pre-fill	Correct property and editable values.
Policy document	Upload, scan, link and access control.
Premium attributes	Monthly and annual calculation.
Scopes	Active, expiring and expired results.
Renewal	New term, document and history.
Cancellation	Reason and effective date.
Blockchain policy	Pending, confirmed and failed.
Document version	New hash after amendment.
Create claim	Claim number, policy and incident.
Evidence	Multiple files and aligned blockchain arrays.
Claim transitions	Pending, review, approved, rejected, settled, cancelled.
Required status data	Approved amount, denial reason and dates.
Claim notes	Authorised internal visibility.
AI claim help	Advisory wording and human review.
Analytics	Cost, claims, risk and policy optimisation.
Commercial	Blanket policy without double-counting.
Lease provider	Create, send, mark and prevent duplicate.
Client dashboard	Own policies only.
Inventory	CRUD, photos, values and serial number.
Appraisal	Request and result linkage.
Inventory exports	PDF and CSV privacy.
Client claim	Submit and track own claim.
Policy payments	History and upcoming payments.
Corporate	Locations, liability, workers comp and interruption.
System configuration	Types, minimums, fees and blockchain.
Compliance	Violation, review and resolution.
Audit	Policies, claims, documents and overrides.
Security	Landlord, Client, corporate and SuperAdmin scope.
Exports	Privacy, date range and retention.

Go-live gate

Do not rely on the module for live compliance or claims decisions until policy status, renewal, evidence, permissions, audit and jurisdiction-specific rules have been validated.

71 Common Issues and Troubleshooting

Issue	Recommended action
Policy missing from dashboard	Check landlord scope, property, status and date.
Expiring policy not shown	Check expiry date, timezone and scopeExpiring logic.
Monthly premium is wrong	Check payment frequency and calculation basis.
Renewal overwrote old document	Restore version history and separate renewal term.
Blockchain remains Pending	Check provider queue, credentials and confirmation worker.
Hash does not verify	Use the exact original bytes and correct document version.
Claim uses wrong policy	Validate property, incident date and policy ownership.
Duplicate claim number	Enforce unique atomic generation.
Evidence arrays are misaligned	Use a structured document record or rebuild array order.
Rejected claim lacks reason	Require denial_reason before transition.
Settled claim lacks date	Require settlement_date and documented outcome.
AI claims output sounds guaranteed	Add advisory language and human escalation.
Analytics double-count blanket cover	Allocate or count aggregate limit once.
Provider email sent twice	Check hasEmailBeenSent and idempotent mail handling.
Client sees another inventory	Fix user ownership policy.
Inventory export exposes serial numbers	Restrict and protect export.
Compliance violation reopens	Review resolution evidence and monitoring rule.
SuperAdmin override missing history	Log actor, reason, previous and new values.

72 Frequently Asked Questions

Can a landlord record multiple policies for one property?

Yes, where different covers or terms apply. Review overlap and double-counting.

Does Active status prove the insurer will pay?

No. Coverage depends on the policy, premium, exclusions, incident and insurer decision.

What does scopeExpiring do?

It returns policies whose expiry falls within the configured number of days, such as 30.

Can an expired policy be renewed?

The supplied renew action supports expiring or expired records, but production backdating and coverage gaps require confirmation.

What does blockchain verification prove?

It can prove that a later file matches the registered hash. It does not prove coverage or legal validity.

Can claims documents be registered separately?

Yes. The supplied claim model uses per-document blockchain arrays.

Who decides whether a claim is approved?

The insurer or authorised claims process, not the AI assistant.

Can Clients maintain a belongings inventory?

Yes, including values, serial numbers and photos.

Can the inventory be exported?

Yes, as PDF or CSV.

Can Leaseora notify a Client insurer?

Yes, through InsuranceProviderNotificationMail.

Does email_sent mean cover was verified?

No. It records only that the message was sent.

Can commercial policies cover several properties?

Yes, through the supplied multi-property and blanket policy workflow.

Can corporate tenants manage workers compensation?

The CorporateInsuranceController includes that operational section.

Can SuperAdmin override claim status?

The supplied user-management flow describes intervention, but strong audit and authorisation are required.

73 Technical Matters to Confirm Before Production

Area	Confirmation required
Status enums	Confirm exact policy and claim enum values and allowed transitions.
Policy activation	Confirm who activates Pending policies and required evidence.
Date automation	Confirm automatic expiry status and alert jobs.
Renewal history	Confirm new record versus term/version history.
Currency	Confirm multi-currency aggregation and exchange-rate source.
Premium calculations	Confirm monthly and annual formulas, including quarterly rounding.
Coverage basis	Confirm property values, limits, sub-limits and aggregates.
Document Hub	Confirm ownership, versioning and deletion behaviour.
Blockchain provider	Confirm network, credential, fee, queue, retry and verification endpoint.
Blockchain arrays	Confirm document ordering or separate document-verification model.
Claim number	Confirm unique format and concurrency.
Claim amount	Confirm currency and filed, approved, settled separation.
Status authority	Confirm roles allowed to approve, reject and settle.
Notifications	The supplied scenario does not list policy or claim notifications; confirm production notifications.
Claim payments	Confirm whether settlement payment records exist and how they reconcile.
AI data	Confirm prompts, retention, redaction and advisory display.
Analytics	Confirm formulas, denominators and reporting currency.
Commercial policies	Confirm property linkage and aggregate allocation.
Lease provider	Confirm consent, provider response and duplicate email rules.
Client inventory	Confirm model, storage, appraisal and export schema.
Client payments	Confirm premium payment model and payment gateway integration.
Corporate insurance	Confirm location, employee and certificate models.
Compliance	Confirm jurisdiction rule source, versioning and review frequency.
SuperAdmin override	Confirm approval, audit and user notification.
Retention	Confirm policy, claim, inventory, audit and blockchain retention.

Specification basis

This guide preserves the terminology and workflow supplied for the Leaseora Insurance module. Undefined production behaviour is listed for confirmation rather than silently assumed.

74 Quick Reference - 40-Step Insurance Operating Flow

1. Open the Insurance dashboard.

2. Review Active, Expiring, Expired and Cancelled policies.

3. Review open claims and risk indicators.

4. Select the correct property.

5. Fetch and verify property details.

6. Choose the policy and coverage types.

7. Enter insurer, provider and policy number.

8. Enter coverage, premium, deductible and frequency.

9. Enter effective and expiry dates.

10. Upload the insurer-issued policy document.

11. Link the Document Hub record.

12. Create the policy as Pending or approved starting status.

13. Review AI recommendations as advisory.

14. Activate the verified policy.

15. Register the document hash if blockchain verification is used.

16. Monitor days until expiry.

17. Obtain and compare renewal terms.

18. Record the new term, dates and document.

19. Preserve prior policy history.

20. When an incident occurs, confirm safety and notification duties.

21. Select the correct effective policy.

22. Create the claim and unique reference.

23. Record incident facts and claim amount basis.

24. Upload evidence and preserve originals.

25. Register per-document hashes where used.

26. Move the claim to Under Review.

27. Record adjuster information.

28. Add authorised notes and additional evidence.

29. Record Approved amount or Rejected reason.

30. Record settlement outcome and date.

31. Review claim-processing and portfolio analytics.

32. Manage commercial blanket and multi-property coverage carefully.

33. Record lease-required Client insurance provider details.

34. Send and track the provider notification.

35. Allow Clients to view their policies and maintain inventory.

36. Allow Clients to file and track their own claims.

37. Manage corporate multi-location insurance.

38. Monitor platform configuration and blockchain queues.

39. Run compliance review and resolve violations.

40. Retain auditable policy, claim, document and status history.

Business value

Leaseora's Insurance module gives a real estate company one connected workflow for property policy administration, renewal monitoring, claim evidence, Client insurance, commercial portfolio oversight, tamper-evident documents, analytics and compliance governance.

LEASEORA

INSURANCE

Manage property policies, claims, Client cover, evidence and compliance from one connected platform.

Support and onboarding

For Insurance onboarding, policy configuration, renewal workflows, claim evidence, Document Hub, blockchain verification, Client inventory, analytics or compliance assistance, contact Leaseora through support@leaseora.com.

leaseora.com

Was this article helpful?

Your feedback helps us improve our documentation.

Back to Knowledge Base More in INSURANCE

Article Info

Category INSURANCE

Reading Time 36 min

Published Jul 30, 2026

Tweet Share

🤝

Need more help?

Our support team is available to assist you.

Contact Support

INSURANCE

1 Purpose, Audience and Scope

2 Complete Insurance Lifecycle

3 Roles, Responsibilities and Separation of Duties

4 Before Using the Insurance Module

5 Phase 1 - Landlord Insurance Dashboard

6 Dashboard Review Routine

7 Phase 2 - Create an Insurance Policy

8 Fetch and Validate Property Details

9 Policy and Coverage Types

10 Coverage, Premium and Deductible

11 Policy Dates and Status Lifecycle

12 Upload and Link the Policy Document

13 AI Assistance During Policy Creation

14 View and Manage the Policy Register

15 Policy Detail Review

16 Renew an Insurance Policy

17 Expired, Cancelled and Not-Renewed Policies

18 Phase 3 - Blockchain Policy Verification

19 Policy Blockchain Registration Procedure

20 Version and Amendment Control

21 Phase 4 - File an Insurance Claim

22 Claim Filing Checklist

23 Claim Document Upload and Evidence

24 Claim Document Blockchain Arrays

25 Claim Status Lifecycle

26 Manage Claims

27 Claim Status Update Controls

28 Claim Notes and Adjuster Information

29 AI Claims Assistance

30 InsuranceClaim Model Methods and Scopes

31 Phase 5 - Insurance Analytics

32 Insurance Cost Analysis

33 Claims Analytics

34 Risk Assessment and Policy Optimisation

35 Analytics Export Controls

36 Phase 6 - Commercial Portfolio Insurance

37 Multi-Property and Blanket Policies

38 Commercial Renewal Management

39 Commercial Claims, Cost and Compliance

40 Phase 7 - Lease Insurance Provider

41 Lease Insurance Requirement Review

42 Notify the Insurance Provider

43 Provider Notification Privacy

44 Phase 8 - Client Insurance Dashboard

45 Client Insurance Recommendations

46 Client Property Inventory

47 Add and Maintain Inventory Items

48 Inventory Evidence, Appraisal and Exports

49 Client Files an Insurance Claim

50 Client Claims AI Assistance

51 Client Policy and Premium Management

52 Phase 9 - Corporate Tenant Insurance

53 Phase 10 - SuperAdmin Insurance System

54 Platform Configuration Checklist

55 Phase 10 - Insurance Compliance

56 Compliance Violation Workflow

57 Audit Trail Requirements

58 Backend Models Reference

59 Controllers Reference

60 Services, Mail and Relationships Reference

61 AI-Powered Features Reference

62 Security, Privacy and Confidentiality

63 Daily, Weekly and Monthly Operating Procedures

64 Worked Example 1 - Building Policy Creation and Renewal

65 Worked Example 2 - Flood Claim

66 Worked Example 3 - Client Theft Inventory Claim

67 Worked Example 4 - Commercial Multi-Property Renewal

68 Worked Example 5 - Lease Insurance Provider Notification

69 Implementation and Onboarding Checklist

Policy and document setup

Claims setup

Client, commercial and compliance setup

70 User Acceptance Testing and Go-Live

71 Common Issues and Troubleshooting

72 Frequently Asked Questions

73 Technical Matters to Confirm Before Production

74 Quick Reference - 40-Step Insurance Operating Flow

Was this article helpful?

Table of Contents