The Broker as Orchestrator: A Job That Has Changed in Nature

The African insurance broker no longer sells only policies. He orchestrates a portfolio of partner insurers, each with its own rules, SLAs, document formats, web portals, and hotlines. When the portfolio passes 5 partner companies, time spent coordinating exceeds time spent advising the client.

The orchestrator broker is not an administrator -- he is a conductor. His role: ensure each file flows correctly between actors, without loss of information, without hidden delay, without visible seam for the end client.

The 5 Daily Frictions of a Multi-Insurer Broker

1. Heterogeneous Formats

One insurer demands photos in JPEG, another in compressed PDF, a third via a limited-upload web form. Reformatting a claim file for each partner takes between 15 and 30 minutes per file. At 60 files per month, this represents half a day of weekly administrative work.

Lever: store the artifacts in a canonical format (your central file) and generate the partner-specific format on the fly when sending.

2. Incompatible SLAs

Insurer A settles a claim in 5 days, insurer B in 15 days, insurer C has no published SLA. The broker who treats his 3 insurers with the same yardstick respects no SLA -- he chases everyone all the time.

Lever: per-insurer SLA in your tool, alert at 50% of elapsed time, automatic escalation if needed.

3. Paper-Based Deadline Tracking

Without a follow-up tool, the broker tracks deadlines in his head or spreadsheets. When he manages 200+ active files with 5+ insurers on different SLAs, missed deadlines are costly: penalties, client attrition, team burnout.

Lever: single dashboard per insurer with elapsed time, remaining time, overdue files -- refreshed in real time.

4. Constant Re-Entry

The broker enters the same information (policy number, client details, claim description) into each insurer portal. With each re-entry, the error risk increases -- and so does the lost time.

Lever: single entry into your central file, automatic distribution to partner portals.

5. Missing Consolidated Reporting

When the brokerage director asks "how many active claims per insurer per month", the answer takes 3 days to compile. Or never arrives at all. Without consolidated reporting, it is impossible to negotiate better SLAs or detect the under-performing insurers.

Lever: automated per-insurer reporting -- median delay, dispute rate, payment rate, post-claim churn.

The 3 Pillars of Orchestration: Single File, Adapted Workflows, Consolidated Reporting

Orchestration rests on 3 pillars that must be put in place simultaneously. Any one alone is insufficient.

Pillar 1 -- The Single File

Each claim, regardless of insurer, has one single file in your central tool. That file aggregates documents, statuses, notes, communications, and history. It is the single source of truth -- the insurer portals are only peripherals you feed.

Pillar 2 -- Per-Company Adapted Workflows

A workflow per partner insurer rules the sequence of actions: who to notify, which format to send artifacts in, which portal to use, which target deadline. Each company's specificities are coded once and applied automatically to every new file.

Pillar 3 -- Multi-Insurer Consolidated Reporting

A single dashboard that aggregates all files by insurer, by month, by claim type. Numbers speak: this insurer is too costly, that one is reliable, this third one has no SLA. Portfolio decisions (which to keep, which to replace) become factual.

Set Up a Single Multi-Insurer File: Step by Step

Here is the deployment plan in 5 steps. Budget 30 to 45 days for the whole.

Step 1 -- List Your Partners and Their Specificities

List your 5 to 8 partner insurers. For each, note: target SLA delay, document format, sending portal, dispute process, dedicated contact. This sheet is the foundation of your workflows.

Step 2 -- Define Your Canonical File Model

Choose the minimum information to centralize in each file: insured identity, policy number (multi-company), claim type, date, location, photos, documents, status, comments. This model is the file you consult -- the external portals are mirrors fed from this file.

Step 3 -- Build Workflows Per Insurer

For each partner, code the workflow: on filing, send such type of email; at 50% of deadline, verify that the insurer has acknowledged receipt; at 75% of deadline, escalate; on overrun, commercial action. The more the workflow is coded, the less the broker decides case by case.

Step 4 -- Measure Time Saved

During the first 30 days, measure time spent per file on coordination (vs advisory). In practice, brokerages that set up this framework observe a 40 to 60% reduction in coordination time.

Step 5 -- Negotiate Your SLAs with Data

At 90 days, you have the numbers to renegotiate. Compare your actual delays per insurer to their published SLAs -- if insurer A promises 5 days and delivers in 9, you have concrete data to negotiate compensation or shift volume.

Measuring the Coordination Load: 4 Indicators

To run your brokerage as an orchestrator, track these 4 indicators continuously.

  • Number of active files per insurer -- identifies partners that over-load your team
  • Median delay per insurer -- reveals insurers that waste your time
  • Transmission-without-redo rate (file sent without manual re-entry) -- measures the gain of your framework
  • Coordination time per file (management hours vs advisory hours) -- measures the global impact

A brokerage that tracks these 4 indicators in real time can justify every renegotiation or portfolio switch on numbers -- not impressions.

Classic Mistakes of Brokers Who Want to Orchestrate

Three recurring mistakes break orchestration projects:

Mistake 1 -- Trying to Do Everything at Once with a Single Tool

Orchestration requires workflow rigidity. If every insurer keeps manual specific handling, you orchestrate nothing. Choose 3 pilot insurers to start, code their workflows, measure.

Mistake 2 -- Confusing an Insurer Portal with Orchestration

A broker who sees "insurer A's portal can do X" thinks he has an orchestration tool. Each portal is a one-insurer convenience -- that is not orchestration. Orchestration enforces an upstream single file.

Mistake 3 -- Believing That Negotiation Is Enough

Some brokers negotiate aggressive SLAs with insurers but have no tool to verify the commitments are met. Without measurement, negotiation remains an announcement effect. Insurers quickly forget unchecked promises.

First Step: Choose THE Right Insurer to Orchestrate as Pilot

The classic mistake is trying to orchestrate 8 insurers in parallel. More effective: choose ONE pilot insurer, deploy orchestration in 30 days, measure, replicate.

  1. Choose the most structuring insurer: the one that represents the most volume or the most pain in your operations.
  2. Code its workflow: starting from a single typical case, document all steps.
  3. Build the single file: adapt your canonical model to that insurer's constraints.
  4. Measure before / after: coordination time, median delay, redo rate.
  5. Replicate: at 60 days, move to the next insurer using the same template.

With this incremental approach, you orchestrate your entire portfolio in 6 to 9 months -- without upsetting your partners, without overloading your team, with a measurable result at each step. Brokerages that follow this path typically observe a 40 to 60% reduction in coordination time, a 30% improvement in settlement delays, and 1 to 2 extra days per week of commercial time -- without major transformation or rupture with partners.