Every carrier that works through managing general agents makes the same trade. It hands underwriting pen to a partner who can reach a niche market faster, and in return it accepts that someone outside its own walls will bind risk on its paper. The delegated underwriting authority agreement is the instrument that makes that trade safe. It defines what the MGA may write, where, at what limits and rates, how the money moves, and what the carrier can inspect.
The trouble is rarely the drafting. Most program agreements are carefully negotiated and reviewed by counsel. The trouble is what happens after signature. The authority terms sit in a PDF in a shared drive or a legal folder, while the monthly bordereaux, premium remittances and claims reports arrive in a different system, owned by a different team, on a different schedule. Nobody holds both in view at the same time.
That gap is where oversight breaks down. A delegated authority program manager is expected to confirm that every bound risk sat inside the authority granted, that premium reached the trust account on time, and that audit findings were closed. Doing that from memory and spreadsheets does not scale past a handful of programs.
What a delegated underwriting authority agreement actually controls
Program agreements vary by carrier, line and jurisdiction, but the operative terms fall into a consistent set of categories. Each one is a control that someone has to test against real activity, not just a clause that someone once read.
- Binding authority limits, the permitted lines and classes of business, eligible territories, maximum limits per risk and in aggregate, and any prohibited exposures or referral triggers that require carrier approval before binding.
- Rates and underwriting guidelines, the filed or approved rating plan, allowed deviations, minimum premiums and the guideline manual version the MGA must follow, often incorporated by reference and updated during the term.
- Premium trust and remittance, the requirement to hold collected premium in a fiduciary or trust account, the permitted uses of those funds, and the timing for remitting net premium to the carrier.
- Bordereaux and reporting, the cadence and format of premium and claims bordereaux, required data fields, reconciliation expectations and deadlines for corrections.
- Claims, audit and exit, any delegated claims authority and its settlement thresholds, the carrier's audit and inspection rights, termination triggers, notice periods and run-off obligations for in-force business.
Read together, these terms describe a control framework: grant authority, set boundaries, require evidence, and reserve the right to check. The agreement is only as strong as the carrier's ability to perform that checking on a regular cycle.
Authority terms live in documents. Bordereaux data lives in spreadsheets and data warehouses. When the two are never compared field by field, a program can drift outside its authority for months before anyone notices, usually at audit or at a large loss.
Why oversight fails when terms stay in PDFs
Delegated authority teams usually know what their agreements say in broad terms. What they lack is a structured, current record of the specific parameters for each program, tied to the data that proves compliance. That shortfall shows up in predictable ways.
- Authority is checked by sampling, not by rule. Without structured limits, reviewers spot-check a slice of the bordereau and hope the rest conforms, which leaves out-of-authority risks undetected between audits.
- Amendments are not reflected in reviews. Program agreements are amended for new territories, revised limits or updated guidelines, and reviewers keep testing against the terms they remember rather than the terms now in force.
- Remittance timing is tracked by finance alone. Late premium is visible to the cash team, but it is rarely linked back to the contractual deadline and escalated as an agreement breach.
- Audit findings lose their owners. Findings from an on-site or desk audit sit in a report, remediation dates pass, and the next audit rediscovers the same issue.
- Termination and run-off are improvised. When a program ends, teams search for notice periods, claims handling duties and data return terms under time pressure, often after the notice window has started.
A five-step roadmap for structured delegated authority control
Step 1, Build a single inventory of programs and agreements
Start with a complete list of every active and run-off program, the MGA or coverholder, the governing agreement, all amendments and side letters, and any related addenda such as claims administration or data processing agreements. Link each document set to one program record. Agreements amended by side letter and never filed with the base contract are a common finding, and they need to be closed first.
Step 2, Abstract authority parameters into structured fields
For each program, capture the operative terms as data rather than prose: permitted lines and classes, territories, per-risk and aggregate limits, referral triggers, rating plan and guideline version, commission terms, remittance deadlines, bordereaux cadence and claims settlement thresholds. AI-assisted extraction speeds this work, but a delegated authority analyst should confirm each value, because a misread limit defeats the purpose. Record the effective date of each parameter so amendments create a history rather than overwriting it.
Step 3, Test bordereaux against the abstracted authority
Once limits exist as fields, each incoming premium bordereau can be compared automatically. Risks outside permitted territories, limits above authority, classes not in the grant and rates below the approved plan can be flagged on receipt instead of at the next audit. The same approach applies to claims bordereaux against delegated settlement thresholds. Exceptions go to a named reviewer with the specific clause attached, so the conversation with the MGA starts from the contract language.
Step 4, Track remittance, reporting and audit as obligations
Treat every recurring duty in the agreement as an obligation with an owner, a due date and evidence of completion: bordereau submission, premium remittance, trust account reconciliations, annual certifications, and audit response deadlines. The approach mirrors the one described in our obligation management datasheet for financial services. Late or missing items escalate automatically, and the history becomes the evidence file for regulators and reinsurers.
Step 5, Run a documented audit cycle and plan for exit
Schedule audits by program risk, not just by calendar, and log findings against the clause they relate to, with remediation owners and dates. Keep termination triggers, notice periods and run-off obligations on the program record so that an exit follows the agreement rather than a scramble. This fits naturally within a broader third-party risk contract automation program, since MGAs are among the most consequential third parties a carrier has.
See delegated authority controls in practice
Aavenir abstracts program agreement terms into structured data and tracks remittance, reporting and audit obligations for every MGA.
What good looks like for a carrier delegated authority team
In a mature program, the delegated authority manager can open any MGA record and see the current authority grant, the amendment history, the last three bordereaux with their exception counts, the status of every remittance, and open audit findings with owners. Reviews shift from reading PDFs to working exceptions. Teams commonly report that the biggest change is not speed but confidence: they know which programs are inside their authority today, not only which ones passed their last audit.
Mapping agreement terms to oversight evidence
The table below shows how common delegated authority terms translate into structured fields and the evidence a carrier should be able to produce for each. Exact terms differ by program, so treat it as a starting template.
| Agreement term | Structured field | Oversight evidence |
|---|---|---|
| Binding authority | Lines, classes, territories, per-risk and aggregate limits | Bordereau exception report by program and month |
| Rates and guidelines | Rating plan reference, guideline version, allowed deviations | Rate adequacy exceptions with reviewer sign-off |
| Premium trust and remittance | Trust account requirement, remittance deadline, reconciliation cadence | Remittance log with on-time status and escalations |
| Claims authority | Settlement threshold, reporting deadline, referral rules | Claims bordereau exceptions and referral records |
| Audit, termination and run-off | Audit rights, notice period, run-off duties, data return | Audit findings tracker and exit checklist per program |
Delegated underwriting works when the carrier can prove, at any moment, that its partners are writing inside the lines it drew. That proof depends on turning agreement terms into data and checking them against what the MGA actually reports.
For related guidance, see Legal ops guide to a contract signature authority matrix, Bank fintech partnership agreements, the control questions and Sub-custodian oversight: the agreement duties that matter.
