Use cases

1. 01

   Authorization

   The head of claims authorizes an agent to settle the simple claims of one line directly, with the duty to escalate if the policyholder objects to direct settlement or a technical report is missing.

2. 02

   Agent act

   The agent builds the file, requests the documents, prepares the preliminary report and proposes the indemnity; it escalates what falls outside. Each act stays tied to the head of claims who authorized it. In 2027 refusal of acts outside authority arrives: a proposal above the delegated cap will not go through.

3. 03

   Signed record

   Each document request, each preliminary report and each proposal is signed with the head of claims who authorized the agent and the moment of the act.

4. 04

   Verification

   The policyholder complains to the supervisor about the settlement. With the evidence package, the supervisor verifies on its own machine who had authorized the agent and when it acted, without entering the insurer’s system.

Dates are projections of the current development plan, not commitments.

1. 01

   Who answers for each act?

   • Today

     Every act of an agent sits under the authorization of an identified person, and that authorization is revoked with immediate effect.

   • 2027

     Refusal of acts that exceed the delegated authority.

   The head of underwriting authorizes an agent only to check that a life insurance application is complete and to pass it to an identified underwriter, who decides. When the head of underwriting changes, their authorization is revoked and the record shows the date. In 2027, with refusal of acts outside authority, the agent will not be able to accept or decline an application.

2. 02

   Does the proof depend on the provider?

   • Today

     Every record is signed and stays in the insurer’s own cloud account, not in the model provider’s.

   • 2027 service · 2028 product

     A verifiable evidence package: the signed records are exported and verified on any machine, without access to Unica and without trusting the insurer, Teipsum or the model provider.

   An agent sends the request to ratify a voluntary insurance sold with a loan, records the customer’s answer and marks as no longer in force what was not ratified when the term ends. With the evidence package, the external auditor receives the quarter’s file in verifiable form, not screenshots or access to production.

3. 03

   What did the system see that day?

   • Today

     The signed record shows who acted, under whose authorization, and when.

   • From 2028

     Rebuilding what the system saw at a given moment (the data, the policy and the authority in force) and explaining it to the people affected.

   A policyholder complains about a settlement made eight months ago. From 2028, the documents and the policy of that day are rebuilt, not today’s.

4. 04

   How is each rule shown to be met?

   • 2027 service · 2028 product

     With the verifiable evidence package, a rule’s obligations (human oversight, event logging, explanation, data residency) are laid out as controls, article by article.

   With the evidence package, compliance shows that every decision on a life insurance application was taken by an identified underwriter, with the system’s record and not with a report written by hand.

5. 05

   How much work does a review take?

   • Today

     Every act is recorded and signed when it happens: who acted, under whose authorization, and when.

   • 2027 service · 2028 product

     The auditor and the supervisor verify the record instead of reading reports: preparing a review goes from weeks of gathering to one signed export.

   With the evidence package, internal audit reviews the claims, underwriting and distribution agents with the same signed record, instead of three reports prepared by hand.

Dates are projections of the current development plan, not commitments.