The most orderly digital journey is often designed around a person who has the required information, can reach the required device and understands the next question. Insurance regularly serves people for whom one of those assumptions is false. A loss may have damaged the document being requested. A renewal instruction may arrive through a channel the programme regards as temporary. I believe the exception route must be part of the service design, with its own capacity, evidence and accountable owner.
This is not an argument for leaving every process open-ended. An insurer needs reliable information and clear controls. The question is whether a particular requirement expresses the actual insurance decision or merely the convenience of the preferred form. When those are confused, a technical restriction can determine who receives attention. A CIO should help the operating function identify that distinction before it is discovered by a colleague handling an urgent call.
Name the circumstances the main journey assumes
I find it useful to ask a team to describe the person for whom its demonstration works. Can that person enter the property? Do they have access to the policy documents? Can they receive the proposed confirmation? Are they acting for themselves or helping somebody else? These questions expose assumptions without requiring the team to predict every unusual event. They also invite service colleagues to contribute the cases that a technology demonstration is least likely to include.
During a regional storm response at Caldermere, 390 urgent notifications were held behind a mandatory photograph field. The insurer had received 9,600 notifications over seventy-two hours, and claims supervisors were trying to prioritise human attention. Some people could not safely visit the property. The form nevertheless treated a photograph as an immediate condition of progress. A requirement intended to help assessment had become a barrier to reaching the assessor.
We did not solve that problem by declaring photographs unnecessary or by changing the terms of a policy. Claims management authorised a restricted route around the intake requirement, with the missing evidence left visible and a follow-up task where appropriate. Technology made the route available and recorded its use. Supervisors reviewed the affected cases during the following thirty-six hours. That action concerned triage, and the resulting count said nothing by itself about coverage, settlement or payment.
The distinction matters because an exception can otherwise be misunderstood in both directions. One person may think a missing field means the file is unacceptable; another may think permission to proceed means the evidence has been waived permanently. A well-designed record should show what was missing, why work continued, who authorised that step and what still needs attention. It keeps the temporary operating choice separate from the later professional judgement.
Give the exception an owner and a record
An exception route becomes fragile when it depends on a knowledgeable colleague remembering whom to call. The immediate problem may be solved, but the insurer cannot reliably explain the decision or repeat the service when that colleague is absent. I want the operating owner to specify the route, its authority and its handover. The technology team can then support that process without creating a separate collection of informal notes that nobody regards as the official file.
This is particularly important when somebody changes channel. A member may begin a renewal online and then ask an agent or service colleague for help. If the next conversation begins from an empty record, the member has to repeat information and the insurer may retain contradictory versions. The service needs to establish which instruction is current and what remains incomplete. A high completion percentage within the web form does not answer those questions about the wider relationship.
Our renewal pilot deliberately funded an assisted route. Of 7,600 invited members, 6,100 completed online and 1,500 used telephone or post. We retained eight colleagues' capacity and budgeted USD540,000 for assisted service. The cost made the digital proposal less attractive when viewed narrowly. It made the operating commitment more credible when viewed across the population we had invited. We could discuss staffing and handovers without pretending the remaining members would disappear after a better launch message.
There are boundaries to preserve. An assisted route must not become an invitation for someone without authority to alter a policy or release private information. The appropriate checks depend on the request, the person's role and the insurer's obligations. Those decisions belong with the relevant specialists. My concern is that the approved checks can be performed in the alternative route and that colleagues know how to escalate a situation the ordinary process does not cover.
Measure the whole population the insurer promised to serve
Digital measures are useful when their denominator is clear. Online completion can indicate whether a form is understandable for the people who use it. It cannot, alone, establish that every invited member was served well, or explain why someone moved to another channel. I would put the alternative routes, unfinished requests and handover costs beside the online result. That gives the executive team a view of the service it is actually funding rather than only the part designed by the digital programme.
The same discipline applies after a catastrophe. A count of cases moved through an intake exception is not a claim-settlement result. It tells us that a barrier to qualified review was removed for a defined group. We should then ask what happened to the outstanding evidence and whether colleagues could use the route as intended. Those follow-up questions can reveal a poorly designed control or a sensible control that needs better operational support. Neither conclusion should be predetermined by the programme's original presentation.
I would test exception routes with people who handle them, using scenarios in which information is missing for a credible reason. The exercise should include a change of channel and a handover between colleagues. It should ask whether the next person can understand the record without hearing the entire story again. A clean screen is not enough. The service must carry the unresolved question forward, together with the authority and context needed to answer it responsibly.
Capacity also deserves an explicit decision. An alternative route that exists on a process diagram but has no available people may offer little practical help. If the organisation intends to reduce that capacity, it should explain which demand has disappeared and what evidence supports the change. It should not use an aspiration for digital adoption as though it were already an observed reduction in assisted work. The difference belongs in the budget and in the operating review.
The point of designing the exception is to make the insurer's promise usable under less convenient conditions. I want technology to reduce unnecessary effort for members and colleagues, including the person who cannot finish the preferred journey today. Giving that person a coherent route need not weaken the insurance decision. Done carefully, it helps the right specialist obtain the right evidence while keeping the member connected to a service the institution can explain.