Claims settled on time, with every decision on file.
An example of claim handling run in Bridge: from the declaration form to the payment, with the deadlines in view and the reasons for each decision kept.
| Case | For | Current step | Status |
|---|---|---|---|
| CLM-7713 | H. Jebali | Assess the damage | Running |
| CLM-7712 | T. Hamdi | Investigate | Due soon |
| CLM-7709 | N. Ayari | Register the claim | Running |
| CLM-7704 | Y. Saidi | Settle the payment | Incident |
| CLM-7698 | A. Chaabane | Claim closed | Completed |
Sample data
The example: a claim, from declaration to payment.
An example drawn in BPMN and run on Camunda 8. Your own process will differ; what Bridge brings to each step stays the same.
- Claim declaredFormio form
- Register the claimClaims handler
- Assess the damageAdjusterA case is here
- Fraud signals?Yes: Investigate · No: Settle the payment
- InvestigateFraud team
- Settle the paymentClaims handler
- Claim closed
How each step looks in Bridge.
Claim declared
Start · Formio form
The policyholder's declaration form starts the claim, its fields mapped to process variables with no code.
Register the claim
User task · Claims handler
The claim appears in the handlers' inbox to claim, with the declaration and the policy details from the form.
Assess the damage
User task · Adjuster
The adjuster completes the assessment form, which is kept as a draft if they leave it half done.
Fraud signals?
Decision
The checks that route a claim to investigation can live in a decision table built in Bridge.
Investigate
User task · Fraud team
Investigation is given to the fraud team's group, so only its members see it, and it is recorded in the audit trail like every other action.
Settle the payment
User task · Claims handler
The SLA tracker warns before the settlement deadline, and the heatmap shows which step holds claims longest.
Claim closed
End
The closed claim stays searchable, with every step it went through.
What an insurer asks of the workflow.
- Settlement times under control
- Deadline lanes, SLA warnings at the threshold you set and a heatmap of slow steps show where claims wait before a deadline is missed.
- The reason behind every payment or refusal
- The audit trail keeps who decided what and when, and token replay shows a claim's path with the variables at each step.
- Handlers and investigators kept apart
- Each step is a task for its own group, and a task given to a group only appears for people whose role carries it.
Questions insurers ask first
Does Bridge come with this workflow?
No. It is an example of what an insurer can build in Bridge's BPMN designer, or sync from an existing Camunda 8 cluster.
Can adjusters attach photos and documents?
Forms are Formio forms, so the file fields you design in the form are available in the task.
Where is our data kept?
Tell us your hosting and data-residency requirements with your trial or demo request, and we will confirm the setup that fits.
Other sectors
By role
Handle your claims in Bridge.
Start a free trial with your own Bridge organisation, or book a 30-minute demo around a workflow like yours.