ova
Two people at a desk filling in an insurance form on a clipboard.

Insurance

Claims-history certificates without the spreadsheet

Requests prepared with assistance and followed up in one register, with a staff member confirming each one.

All use cases

The problem

Clients regularly need a certificate of their claims history. It's a simple request, but one with a real deadline for the client, and the volume adds up.

Follow-up happens in a spreadsheet rather than in the core system. Gathering the data is manual, and it's hard to see what is still open, how long it has been waiting and who is handling it.

The journey

  1. A certificate is requested

    Your team

    The client or adviser asks for a claims-history certificate.

  2. The data is prepared

    Nova

    The relevant claims data is gathered and the certificate is drafted.

  3. A team member confirms

    Your team

    A staff member checks the certificate and confirms it before it goes out.

  4. One follow-up register

    Your systems

    Every request is visible with its status and waiting time, replacing the spreadsheet.

Nova's solution direction

  • Turnaround you can see

    Time per request is measured from the start, so the effect is known rather than assumed.

  • A complete follow-up

    Nothing gets lost in a spreadsheet, and anyone on the team can pick up a request.

  • A person confirms

    A certificate has consequences for the client, so the final check stays with the team.

  • Fits the existing set-up

    The solution works alongside the core systems, within the existing governance framework.

Anonymised use case, based on a real brief in our studio. Names and identifying details have been left out. It describes a solution direction, not a measured result.

More use cases

What's the use case you would start with?