Certificate work across a commercial book is not a volume problem spread evenly across accounts. It concentrates. A small number of clients generate most of the certificates, and the operational answer is to standardise how those few are handled rather than to add capacity across the whole team.
Updated September 2026.
Where the volume actually sits
At one national brokerage, roughly five percent of accounts carried more than ninety percent of certificate production. Those accounts range from dozens of certificates at renewal into the thousands. Everything else is a handful of straightforward certificates that the core production system already handles well.
That distribution should determine where effort goes. Trying to improve certificate handling evenly across a book spends most of the effort on the ninety-five percent that was never the problem. The accounts worth building a process around are the ones where a single renewal produces more certificates than a person can reasonably check.
The three things worth standardising
The template. Most brokerages run on whatever template came with each office or each acquired book. Every acquisition adds another variant rather than resolving the pattern, and nobody notices until two offices issue visibly different certificates to the same client. One approved library applied across every office removes a whole category of inconsistency.
The source of truth. Certificates should be checked against the contract that defines the requirement, not against a requirement list somebody typed in at onboarding. Lists age silently. Contracts do not.
The record. Who checked it, against what, and when. This is the part teams skip because it produces nothing today, and it is the only part that matters when a question arrives three years later.
What to measure
- Certificates produced per renewal cycle, by account
- Time from request to issued certificate
- Reissues caused by an error rather than a genuine change
- Deficiencies caught before the certificate went out
- How many accounts sit in the top five percent by volume
The last one is the planning number. Knowing which accounts drive the workload tells you which renewals need preparation weeks ahead rather than days.
What changes when the batch stops being manual
The common workaround is an export from the BMS, a mail-merge in Word, a print to PDF, then splitting that file page by page and renaming each one. At ninety certificates that is about three hours. It is also the step most likely to produce a wrong name on a right certificate.
During a nine week pilot at Westland Insurance, fourteen users processed roughly eight hundred and forty documents and produced three hundred and ninety-two certificates, with zero incidents recorded on issued certificates. A ninety-five certificate batch was produced in three minutes and fifty-four seconds, timed, against the team's own three hour benchmark. Licensed staff reviewed and issued every one.
The capacity question underneath
Brokerages usually frame this as a headcount problem during renewal season. It is more often a distribution problem. When a handful of accounts absorb most of the certificate hours, the team is not short of people in general, it is short of people during the specific weeks those accounts renew.
Fixing the batch changes the shape of that week. It also frees the comparison work that gets dropped first under pressure, which is checking what actually changed on the expiring policy.