Case study · Insurance and public transport
From over 30 days to 2: faster claims, 20% lower insurance costs.
An insurance partner and a regional public-transport operator needed every claim to move forward without losing information or missing a deadline. Nebulas built a custom web and mobile platform that connects the work of both organisations and automates the ANIA workflow.
Anonymous case study · Data and results approvedThe setting
An operating network spread across the region.
The transport operator manages people and vehicles through 12 branches. A single claim can involve a driver, a vehicle, the responsible branch, central administration and the insurance partner.
- 12
- operating branches
- 1,600+
- drivers
- 1,050+
- vehicles
The starting problem
Time lost between teams also meant lost claims.
A claim did not belong to one office. It started with incident, driver and vehicle data, gathered documents and photographs, and then passed through several reviews across branches, central administration and insurance. Repeated communication and partial visibility pushed the cycle beyond 30 days.
ANIA workflows carry firm deadlines. In the previous process, valid claims sometimes arrived too late and were lost because a deadline had been missed, regardless of the quality of the case. Delay therefore had a direct financial effect.
The platform
One shared case, with clear roles and next actions.
Nebulas designed the workflow around how people already worked, turning communication and checks into visible, traceable steps.
Capture at the scene
A driver can open a claim on mobile with incident, vehicle and counterparty details, photographs and documents.
One complete case file
Branches, drivers, vehicles, policies, attachments, notes and versions remain connected to the same claim.
Role-based reviews
The local branch, central administration and insurance partner receive the case at the right time and can see what needs attention.
Automated ANIA workflow
Time-sensitive exchanges and their deadlines are handled by the system, reducing the risk of late claims.
The configured workflow
From incident to closure, with one continuous thread.
Each stage prepares the next while keeping status, documents and ownership visible.
- 01
Report
The driver records the incident and evidence.
- 02
Local review
The branch checks and completes the case.
- 03
Central check
Administration verifies data, policy and documents.
- 04
ANIA workflow
Exchanges and deadlines move automatically.
- 05
Outcome
The insurance partner resolves and closes the claim.
What stayed connected
The platform respected the existing organisation.
The project did not impose a generic process. It retained the established roles, regional structure and insurance references, bringing them into one operational sequence.
- Responsibilities across branches and central administration
- Driver, fleet and policy data
- ANIA workflow rules and deadlines
The results
Speed produced a measurable financial result.
The processing cycle fell from over 30 days to 2. Automating the ANIA workflow prevented delays at critical handoffs: the operator now achieves favourable outcomes on 40% more claims than under the previous process and has reduced insurance costs by 20%.
Processing time
Previously over 30 days
Insurance costs
After the platform was introduced
Claims with a favourable outcome
Compared with the previous process
The results compare the platform-supported process with the previous process. Scale and performance figures were supplied by project stakeholders and approved for publication. The customer’s identity remains confidential.
A similar process?
Deadlines should not decide the outcome of a valid claim.
Show us the roles, handoffs, documents and systems involved. We can identify where automation and visibility would have the greatest effect.
Discuss your process