Skip to content
PROCESS MAP

Insurance

The process landscape of an insurer, from application through policy to the reported claim.

3 categories10 groups40 processes
14 of 40 modelled

MANAGEMENT PROCESSES

2 groups · 8 processes
2/8 modelled

Steering, quality and compliance.

  • Strategic planning

    Company strategy, annual planning & objectives.

    • Develop company strategy
    • Annual planning & budgeting
    • Management review
    0/3

  • Quality management

    ISO 9001, audits & improvement.

    2/5

CORE PROCESSES

4 groups · 14 processes
4/14 modelled

Value created directly for the customer.

  • New policy

    From application to signed policy.

    2/4

  • Policy changes

    Record and decide on changes to existing policies.

    • Record change
    • Decide on change
    • Document change
    0/3

  • Claims handling

    From reported claim to provided benefit.

    1/4

  • Customer service

    Enquiries and grievances from existing customers.

    1/3

SUPPORT PROCESSES

4 groups · 18 processes
8/18 modelled

Functions that carry every area.

Open the map in ProceviaDownload the package

The map lands in a new project with every process. You then tell the AI what is named differently or missing at your company.

WHAT THE PACKAGE HOLDS

Four levels, from overview to single step

LEVEL 1

The map

Three categories with 10 groups, each described.

Shown above
LEVEL 2

40 processes

Named, described, with maturity and group assignment.

Shown above
LEVEL 3

14 BPMN diagrams

Complete flows with lanes, decisions and events.

After unlocking
LEVEL 4

Process record per diagram

Goal, trigger, inputs and outputs, metrics, risks, standards.

After unlocking
CONTEXT

Why the map comes before the first diagram

The most common mistake at the start

At insurers the three core strands of new business, policy changes and claims usually sit in different systems and often in different departments. The map shows them side by side, and that makes visible how often the same customer runs through several strands without those strands knowing about each other. It is exactly at these transitions that the queries arise which customers experience as bureaucracy.

Why planned processes belong on the map

Most processes on this map carry only a name and a description. That is deliberate. A map where everything looks finished is either polished up or the result of two years of work. Start with the processes causing trouble today and leave the rest as placeholders until somebody needs them.