Stop chasing dec pages in email
Stop chasing dec pages in email
The dec page problem
Every Ontario personal auto producer knows the request: "Can you send your prior policy dec page?"
It sounds simple. In practice, the dec page is one of the most chased documents in the file.
It may arrive as a PDF attachment in email. It may arrive as a screenshot from a prior insurer's online account. It may arrive as a photo that cuts off the policy number. It may never arrive at all until someone notices the morning of a bind.
Meanwhile, the driver's abstract, signed application, and disclosure records are scattered across other channels. Nothing ties them together on one client record.
Why dec pages stall quotes
The declaration page confirms prior coverage, policy dates, and claims history context. Carriers and MGAs expect it early in the submission.
When the dec page is missing:
- Rating may be delayed or based on incomplete information.
- The producer sends another email — and another.
- The CSR searches three inboxes for an attachment from last week.
- The client wonders why they are being asked for the same document again.
Email has no concept of "the dec page is still outstanding." Only a human remembers — until they forget.
A better approach: dec page as a tracked checklist item
Instead of treating the dec page as a one-off email request, add it to a reusable personal auto intake checklist.
On each client file, the checklist might include:
- Prior policy declaration page (or letter of experience) — tracked
- Government-issued photo ID
- Driver's abstract
- Vehicle registration
- Signed application
- Disclosure and CISRO/Fact Sheet records
When the dec page is a line item with a status — todo, submitted, approved, rejected — the whole team sees whether the file is ready to quote.
If a client uploads a blurry photo, the producer can reject it with a reason and ask for a clearer copy through the same portal. The client does not need a new email thread.
How Hivi-X helps
Hivi-X is document-collection software for Ontario insurance brokers. Producers build reusable Ontario auto intake templates once and attach them to each client record.
Clients upload the dec page and other items via a secure guest link (no account needed) or the my-id.ca portal. Your team approves or rejects each submission. When the package is complete, export a PDF for your BMS client folder.
Hivi-X complements Applied Epic, Vertafore SIG, Power Broker, and similar BMS tools — it does not replace policy admin or rating.
The result
Stopping the dec-page chase is not about one document. It is about making every required item visible before the quote leaves the building.
Start a free trial or use the free Ontario auto application checklist PDF as a starting template.
Answers are general operational information only — not legal, tax, regulatory, clinical, privacy, immigration, or professional advice. Requirements vary by matter, client, and regulator.
Frequently asked questions
- Why is the dec page so hard to collect?
- Clients often need to log into a prior insurer's portal, only have a paper copy, or send a cropped photo that is unreadable. Without a checklist, the broker discovers the gap late — usually when rating or binding.
- What else should be collected with the dec page?
- Personal auto intake typically also needs ID, driver's abstract, vehicle details, signed application, TAC quote log fields, CISRO/Fact Sheet delivery, and disclosure-at-quote records. A single checklist keeps the full package visible.
- Can clients upload a dec page through Hivi-X?
- Yes. Clients upload through the my-id.ca portal on the checklist item for the prior policy dec page. Your team can approve, reject, or request a correction if the file is unreadable.
Organize broker client files without the email chase
Hivi-X helps Ontario insurance brokers collect application documents with reusable checklists, a Canadian-hosted client portal, self-hosted AI summaries, and exportable PDF packages for Applied, Epic, SIG, or your BMS. Hivi-X is document-collection software — it does not replace your BMS or guarantee RIBO compliance.
More Insurance guides
- Email is not document collection for insurance brokersOntario insurance brokers lose time collecting application documents through email, text, and carrier portals. A checklist-first workflow keeps client files complete before quote or bind.
- Missing documents cost brokers binds and renewalsHow missing documents create delays, repeated follow-ups, and weaker client experience for Ontario insurance brokers.
- Better client document collection for insurance brokersClient experience is a competitive advantage for Ontario insurance brokers. Clear document collection helps policyholders feel guided and keeps client files defensible.
- Why a BMS alone does not fix the document chaseApplied Epic, Vertafore SIG, and Power Broker handle policy admin — but pre-bind client intake often still lives in email. Hivi-X fills that gap without replacing your BMS.
- Ontario personal auto new business document checklistA practical document checklist for Ontario insurance brokers collecting personal auto new business — ID, dec page, abstract, application, TAC quote log, and disclosure records.
- Auto insurance renewal document workflowHow Ontario insurance brokers organize renewal documents — updated dec pages, change requests, disclosure records, and bind-ready packages.
- Driver abstract collection for Ontario auto applicationsHow Ontario insurance brokers collect driver's abstracts and motor vehicle records as part of personal auto intake — and track them on the client file.
- High-risk auto documentation checklistOntario brokers writing high-risk auto need extra intake discipline — abstracts, loss history, payment records, and defensible advice notes on the client file.
- Home insurance application documents for Ontario brokersWhat Ontario insurance brokers typically collect for home insurance applications — property details, prior policy, photos, and signed forms — tracked on one client file.
- Take-All-Comers quote log documentationHow Ontario auto brokers document Take-All-Comers quote records — premium, market, and broker comments — in defensible client files.
- CISRO and RIBO Fact Sheet distribution recordsHow Ontario insurance brokers document delivery of CISRO Principles and the RIBO Fact Sheet in client files since September 2022.
- Documenting quote-only interactions in client filesOntario insurance brokers must keep records for quotes that do not bind — including disclosures, needs analysis, and advice notes.
- How to prepare for a RIBO spot checkPractical steps Ontario Principal Brokers and producers can take to prepare client files for RIBO spot checks — disclosures, TAC logs, and organized intake.
- Ontario insurance broker record retentionHow long RIBO members must keep client records under O. Reg. 991, what records count, and how to store electronic files you can produce on demand.
- RIBO mandatory disclosures at time of quoteRIBO-002 requires mandatory disclosures no later than quote. What must be in the client file and how Ontario brokers document delivery.
- RIBO client file checklist for Ontario brokersWhat RIBO spot checks look for in client files — disclosures, suitability docs, TAC quote logs — and a practical checklist for defensible intake.
- RIBO Responsible AI guidance for Ontario brokersHow RIBO's May 2025 Responsible AI guidance applies to Ontario insurance brokers — and how self-hosted AI supports vendor-vetting requirements.
- FNOL claims intake document workflowHow Ontario insurance brokers organize first notice of loss documents — photos, police reports, proof of loss, and correspondence — on the client file.
- Voice notes for insurance advice documentationHow Ontario insurance brokers use voice notes and self-hosted AI summaries to document advice and call recaps on client files.
- AI summaries for insurance client filesHow Ontario insurance brokers use self-hosted AI summaries on client checklists to understand file status without reading every attachment.
- Co-agent workflow for insurance CSRs and producersHow Ontario brokerages use Hivi-X co-agent access so CSRs and secondary producers can complete intake on a shared client file.
- Exportable PDF packages for BMS uploadHow Ontario insurance brokers export organized checklist PDF reports from Hivi-X into Applied Epic, Vertafore SIG, or Power Broker client folders.
- Canadian-hosted document collection for insurance brokersWhy Ontario insurance brokers choose Canadian-hosted document collection — PIPEDA alignment, RIBO AI vetting, and client trust.
- Secure client portal for insurance document uploadsHow Ontario insurance brokers collect ID, dec pages, and applications through the encrypted my-id.ca client portal instead of email attachments.
- Principal Broker client file oversightHow Ontario Principal Brokers standardize intake, sample file completeness, and prepare for RIBO spot checks across producers.
- Document standardization for small insurance brokeragesHow small Ontario brokerages with a handful of producers standardize client intake without enterprise BMS projects.
- CSR document collection workflow for insurance brokeragesA practical document collection workflow for Ontario insurance CSRs — checklist handoffs, portal follow-up, and BMS-ready packages.
- Commercial insurance submission document checklistThe documents Ontario brokers typically need for commercial insurance submissions — loss runs, SOV, financials, schedules — tracked before MGA review.
- How brokers collect loss runs for commercial submissionsLoss runs expire, arrive late, and scatter across email. Ontario commercial brokers need a tracked workflow for five-year loss history before MGA submission.
- SABS 2026 reforms documentation for Ontario brokersWhat Ontario auto brokers should prepare before July 2026 SABS reforms — consultation records, optional benefits advice, and defensible client files.
- DocuSign is not document collection for insurance brokersWhy e-signature tools and document collection tools solve different problems for Ontario insurance brokers.