The report approves or denies the payout.
Today it is assembled in Word.
In claims adjusting, payment does not move without the inspector's report. That report establishes cause and causal link, checks the event against the policy and decides whether the indemnity goes out, how much and to whom. Yet it is still assembled in Word, with loose photos in a drive and findings over WhatsApp. uInspect runs the adjusting through a single track, from claim notice to audited report, with photos geotagged at the source and a chain of custody from evidence to file.
The regulatory clock is running, and the evidence is born fragile.
The inspector goes to the field, takes photos and assembles the report in Word or PDF afterwards.
The case conversation lives on WhatsApp, which strips the date and time off the photo when it compresses it.
Evidence is scattered across email, spreadsheets and drives, with no guarantee of where it came from, when, or who recorded it.
Every adjuster writes in their own format, and comparing two reports from the same portfolio becomes an excavation.
From notice to report, everything runs through uInspect
The claim notice comes in and drops to the inspector with the location, the policy and the right report template. The investigation happens at the loss site, and out comes a standardized report with photos geotagged at the source and a chain of custody from capture to file.
From request to auditable report.
- 1 The case drops to the inspector, dispatched with the location, the policy and the right report template, with video triage first when the case allows it.
- 2 The investigation happens on site even without signal: an offline app, with the route and distance traveled logged as evidence of presence.
- 3 The evidence is born at the loss site, before the repair: photos of the damage, video and audio findings through the camera, with GPS, date and time recorded on the image.
- 4 The report is born in the field with cause and causal link, expenses and chat, and comes out ready, traceable and standardized on completion.
The capabilities that turn the inspection into evidence.
The same horizontal platform, with the features this industry actually uses. Everything inside the inspection, not in spreadsheets and scattered chats.
Field work in the app concludes cause and causal link on site, and the case closes without days of rework assembling the report in Word
The photo of the loss arrives with GPS, date and time on the image before the repair, so the evidence is born reliable instead of a loose photo with no origin
A chain of custody from evidence to file, plus bureau checks on individuals and companies, turns the photo in the drive into a case file that supports paying or denying
A standardized report for the whole network of inspectors, generated on completion, brings back the comparison between two reports from the same portfolio
An offline app with route and distance on the map records the inspector's presence at the loss site, even in an industrial plant with no signal
Remote triage by video cuts the visit that does not need to happen, and travel expenses enter the inspection itself with a photo of the receipt
Concrete use cases in this industry.
Field investigation of large property losses, with the inspector on site before the repair erases the scene
Adjusting waves of weather claims, with a concentrated volume of cases and the regulatory clock running for all of them at once
Remote triage by video for low-complexity residential claims or losses in distant locations, before sending an inspector
Claim intake by the policyholder, guided and under the insurer's brand, for the simplest cases
An evidence case file for litigation, with photos geotagged at the source and a chain of custody from capture to file
The regulatory clock on claims settlement
Insurance regulators set hard deadlines to settle a claim and to justify a denial formally. In Brazil, where uInspect runs at scale, the regulator gives 30 days from delivery of the documentation, and large losses can stretch the adjusting up to 120 days.
The inspection that holds up, side by side with today's.
- Report assembled in Word, days later
- Photos over WhatsApp with metadata lost
- Evidence scattered across email, spreadsheets and drives
- A unilateral report with weakened evidentiary weight
- The report born in the field, on completion
- Evidence with GPS and time before the repair
- A chain of custody from capture to file
- A case file that holds up in litigation
Evidence is born trustworthy at capture, and the buyer controls what it releases.
Every photo leaves capture with its provenance, GPS, date and time, and the inspection carries the questionnaire and the chain of custody of the media all the way to the report. With document bureau checks (individuals and companies), anti-fraud stops being a talking point: it is provenance plus a verified document. More than 100,000 inspections on record, and more than 15,000 per crop season, all to the same standard. The report stops being a loose sheet and becomes evidence that holds up when disputed, and the payer controls what it releases.
uInspect leads on the defensible horizontal axis: auditable evidence, chain of custody, offline and three modalities. It is the field app and the evidence layer of the adjusting, and it plugs into whatever claims management system the insurer already has.
Questions from teams operating in claims adjusting.
How do regulatory deadlines shape the adjusting?
Deadlines vary by market, but they are hard. In Brazil, the regulator gives 30 days from delivery of the documentation, with a justified denial due within the same deadline, and large losses can stretch to 120 days. The timeline of who did what and when, which uInspect records on every case, is exactly what those deadlines demand you prove, and it puts the volume and productivity of the inspector network in a single dashboard.
Does the uInspect case file hold up in court?
A report produced unilaterally by the insurer carries less evidentiary weight, and the court-appointed expert's report tends to prevail unless there is robust evidence to the contrary. A case file with evidence recorded at the source, geotagged, with date and time on the image and under a chain of custody from capture to file changes that position: it stops being a Word document with loose photos and starts supporting the decision to pay or deny.
Does it work where there is no signal?
Yes. In an industrial plant or a remote location, the app captures the evidence, fills the report and logs the route without a connection, and syncs on reconnection preserving the original GPS, date and time. The route and distance traveled stay on the map as evidence that the inspector was at the loss site.
How does uInspect ensure the provenance of the photo?
The photo of the loss is born through the camera, at the exact site, with GPS, date and time recorded on the image before any repair erases the scene. When media comes from the gallery, its provenance is logged with the device data. The chain of custody follows the evidence from capture to report, and anti-fraud works through logged provenance plus bureau checks on individuals and companies.
Is the report standardized for the whole inspector network?
Yes. A configurable template becomes your operation's report, the same for the whole network, generated on completion and exportable. The patchwork of every adjuster writing in their own format ends, and two reports from the same portfolio become comparable again.
Does uInspect replace the insurer's claims management system?
No, and it does not need to. uInspect is the field app and the evidence layer of the adjusting: on-site field work, geotagged evidence, chain of custody, offline and three modalities. It plugs into whatever claims management system the insurer already has, and teams with their own system use just the field app.
Can a claim be triaged without sending an inspector to the field?
Yes. For low-complexity residential claims or losses in distant locations, the same platform triages by live video, with the same standard of evidence, and cuts the visit that does not need to happen. The policyholder can also open the claim themselves, guided and under the insurer's brand, in the simplest cases.
Can uInspect absorb a spike of claims after a weather event?
Yes. The platform has absorbed more than 15,000 inspections in a single season in Brazil, and has accumulated more than 100,000 audited inspections. That is the kind of concentrated volume that appears when claims come in waves after a weather event, with the regulatory clock running and every inspector in the field at once.
The same evidence, in any inspection mode.
This industry starts with the mode that makes the most sense, but the platform is one. Explore the three modes, or see the other industry solutions.
Put evidence at the center of your claims adjusting operation.
Talk to the team and see uInspect running on your use case.