Compliance & Cyber Intelligence for Insurance
Menu
Log in ↗

Operating file · Binder governance

Keep the working record
together.

A practical evidence workflow for operating profiles, written binder arrangements, recurring bordereaux work and outsourced-function reviews. The outputs are dated records for the relevant team or authorised reviewer to assess.

For brokers → For UMAs → See pricing →

What is delivered

Feature → evidence → user → qualification

Operating profileOutput: A tenant-owned record of declared operating functions and selected capacity context. Intended user: Broker or UMA operations and compliance teams Qualification: A declaration organises workflow; it does not grant an entitlement or decide legal applicability. Status/source: Shipped capability · applicability policy governs audience claims
Binder lifecycle and renewalsOutput: Arrangement authority, dates, owners, review cadence and append-only renewal history. Intended user: Binder holders and authorised insurer reviewers Qualification: Use only for the written agreement and functions actually authorised. Status/source: Shipped capability · applicability policy governs audience claims
Bordereaux workflowOutput: Due-period schedules, submissions, validation and review history. Intended user: Binder, finance and operations teams Qualification: A recorded workflow does not prove completeness, accuracy or insurer acceptance. Status/source: Shipped capability · applicability policy governs audience claims
Outsourced-function registerOutput: Vendor-linked functions, contract controls, review history and remediation links. Intended user: Broker, UMA and insurer oversight teams Qualification: Materiality remains a recorded, qualified decision; the register is not a regulatory submission. Status/source: Shipped capability · applicability policy governs audience claims
Portfolio oversight reportsOutput: Consent-bound internal entity, portfolio and board reporting from explicitly shared records. Intended user: Insurer oversight teams in a scoped relationship Qualification: Internal reporting evidence only in explicitly shared, entitled and separately scoped relationships; no approval, assurance, submission or acceptance claim. Status/source: Shipped capability · applicability policy governs audience claims

Applicability stays qualified

The audience label does not decide the duty.

01

Broker

Do not infer binder-holder status from being a broker. Exact amended Binder Regulation sub-regulation numbers remain withheld pending consolidated-text review.

02

UMA / binder holder

Describe only the binder functions actually authorised. Exact amended Binder Regulation sub-regulation numbers remain withheld pending consolidated-text review.

03

Insurer reporting

JS1 applies directly to licensed insurers, other than Lloyd's and branches of foreign reinsurers, for material outsourced functions. The insurer retains regulatory accountability. General compliance was due by 1 June 2025; qualifying pre-existing arrangements transition by 1 December 2026 or earlier renewal or renegotiation.

Applicability is policy-derived and should be confirmed against the firm’s actual capacity, agreement, processing role and arrangement. This workflow does not submit to a regulator.

Start with the relevant route

A working file, not a certificate.

Broker practice

Use a self-service practice plan for readiness records, remediation and dated evidence.

Compare plans →

UMA / binder holder

Discuss a relationship-shaped workspace for binder governance and insurer-specific evidence.

Discuss UMA Oversight →

Internal insurer oversight

Portfolio and board views are shipped internal oversight reporting, available only for explicitly shared records in entitled, separately scoped relationships. No generic deployment or approval claim is made.

Review the boundary →