Contents

Your BMS entry is not the client file

Your BMS entry is not the client file

"Binder issued — docs pending" in Applied Epic is a to-do, not proof. Spot checks open attachments and written disclosure records — not your optimism.

Direct answer

Separate policy admin (BMS) from document collection (checklist portal). Export completed intake PDFs into Epic. Diary lines supplement — they do not replace — disclosures and uploads.

RIBO’s 2023–24 spot checks (n=61) found 57% of brokerages lacked written documentation of disclosure in client files. That is a disclosure-record problem — often made worse when teams treat a BMS note as if the underlying PDF existed. See RIBO spot check guide.

What BMS entries miss

BMS showsFile still needs
Policy boundSigned application PDF (or kit equivalent)
Activity: emailed clientActual attachment received and filed
Note: “disclosures done”Written confirmation / disclosure package on file
Note: TAC quotedTAC / rating documentation your brokerage process requires
Renewal processedMaterial-change / renovation questions answered where asked

Stack that works

Hivi-X checklist → QC → PDF export → Epic attachment
Epic → bind, bill, service

See Hivi-X with Applied Epic stack.

Principal Broker view

Epic reports premiums. It rarely shows which producers have open missing items before bind. A missing-item dashboard fills that ops gap — it is not a RIBO certification.

How Hivi-X helps

Reusable intake templates, guest link, approve/reject, optional voice notes and AI summaries, exportable PDF for BMS upload, co-agent for CSRs. Canadian-hosted collection.

Not a BMS — not automated email chasers — not compliance certification.

Related guides

Start a free trial

Start a free trial and put documents in the file — not just diary entries.

General information only. Not insurance, legal, or compliance advice. Not affiliated with Applied Systems, RIBO, or FSRA. Confirm disclosure timing and record content against current RIBO-002 guidance, Reg. 991, and your principal broker.

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

Isn't Epic my client file?
Epic holds policy administration. Supporting documents and quote-time disclosure records must be attachable and complete — not implied by diary notes.
What counts as supporting documents?
Typically applications, ID where required, driver's abstracts, disclosure/confirmation records, CISRO Principles and RIBO Fact Sheet delivery evidence where your process uses them, and needs notes — follow current RIBO-002 guidance and your PB plan.
Do CSRs create the same gap?
Yes — service changes need documented client instructions and uploads.
Can I fix this without new software?
Strict attachment discipline helps — checklists scale better across producers.
Does Hivi-X replace Epic?
No. Collect upstream; export PDF into Epic.

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.

BMS Entry Is Not the Client File Ontario | hivi-x Docs