MGA AND DELEGATED AUTHORITY · SPECIALTY INSURANCE

Manage delegated authority across carriers and MGAs

Program Card@4x
THE PROBLEM

Authority breaches surface late

By the time a breach shows up in a bordereau, the risk is already on the books.
inbox

Authority sits in agreements

Products, territories, limits and referral conditions are held in documents and checked by hand.
icon2

Exceptions move through email

Risks outside authority are referred without a consistent workflow or full audit trail.
warning

Bordereaux carry exposure

Carriers see written business only after files are submitted, validated and reconciled.
IN PRACTICE

From binding agreement to oversight

MGAs work within agreed authority. Carrier underwriters approve referrals and review performance.
  1. Configure

    Set products, territories, limits, capacity and referral conditions for each agreement.

  2. Onboard

    Give each MGA or coverholder access to the products and workflow in its agreement.

  3. Write

    Appetite, pricing and authority rules apply as the MGA underwrites.

  4. Refer

    Risks outside delegated terms follow your approval chain.

  5. Validate

    Premium and claims bordereaux are validated against agreement on arrival.

THE CONTEXT

Keep carrier rules inside the MGA workflow

Limits, territories, capacity and referral conditions travel with each program, so MGAs and carriers work from the same terms.

MGA WORKSPACE

  • Products, documents and workflows by carrier agreement
  • Several carrier programs in one workspace
  • Portal or API access by program

AUTHORITY APPLIED

  • Binding limits by agreement
  • Referral triggers and approval paths
  • Products, territories and capacity controls

CARRIER OVERSIGHT

  • click-here-handReferrals routed to carrier underwriters
  • click-here-handBordereaux validated against the agreement
  • click-here-handPerformance and compliance visible for each MGA or cover-holder
CONNECTIVITY

Work with MGAs through portals, APIs or bordereaux

MGAs can quote and bind through a Tinubu portal or API, or continue using their own systems and send bordereaux for validation.
icon2

IN THE WORKFLOW

MGAs quote and bind through a Tinubu portal or API. Authority is checked before binding.

inbox

THROUGH BORDEREAUX

MGAs keep their own systems. Bordereaux are validated on arrival and exceptions flagged for review.

Start with one binding agreement

We’ll map the limits, referrals and bordereaux it needs.