Know which supplier sites are hit before the reports come in.
After a flood, quake or cyclone, Supplier Impact Assessment checks your named sites against the damage footprint and flags visible damage, from the first clear image of the region.
- GSD
- ≤0.5 m (VHR)
- Cadence
- Event driven
- Platform
- VHR satellite / aerial
- Spectral
- RGB
The job today
Where waiting for reports runs out
The cyclone has crossed the coast and your list has supplier sites all along it. Somebody pulls up the hazard map and plots addresses against it, one at a time. Then the emails and calls go out and you wait.
The sites that took the worst of it tend to be the last to answer, because the people who would answer are dealing with the site. Meanwhile the allocation call is due, or the first reserve, or the decision on which adjuster gets in a vehicle first.
After an event, step by step
| Step | Reports and drive-outs | With Supplier Impact Assessment |
|---|---|---|
| 01Knowing a site is in the path | The news, the hazard map and a person matching addresses to it by hand, a site at a time. | Your named site list is already registered. When the event is declared, each site gets a footprint call, inside or outside. |
| 02Hearing how bad it is | You email or phone the supplier and wait for their own damage report, which arrives when they can send it. | Each site carries a damage flag from the imagery, visible damage or none seen, without anyone having to answer the phone. |
| Still yoursCalling the supplier. The imagery shows the roof and the yard, and the supplier knows what is inside. | ||
| 03Choosing who to send first | The first adjuster goes by the order of the notices, or to whichever site is nearest. | Sites the imagery shows damaged go to the front of the list, and sites outside the footprint wait. |
| Still yoursWho goes, and every adjuster's inspection once they are there. | ||
| 04Making the allocation call | Orders are held or moved on whatever the supplier has said so far, or on a guess about the region. | The control tower has a footprint call and a damage flag for each named site when the pass is processed, to set against what the supplier says. |
| Still yoursThe allocation decision, the contact with the supplier, and the date you expect them back. | ||
| 05Keeping the record | Emails, phone notes and a spreadsheet someone updates by hand. | A trigger log says which event started the read and when the image of the region was taken, so the record shows what was seen and when. |
What comes back for each event
Footprint call
Per siteInside or outside the event's damage footprint for every site on your named list. It serves the first row of the ledger. It comes back as a table you can open next to your supplier master, or as a GIS layer.
Ledger row 01Damage flag
Per siteVisible damage, or none seen, described in plain words for each site inside the footprint. It serves the "hearing how bad it is" and "who goes first" rows. It is a flag, not a loss figure.
Ledger rows 02, 03Trigger log
Per eventWhich event started the read, which clear pass it used and when that pass was taken. It is the record you attach to the incident log or the claim file.
Ledger row 05
An event, start to finish
Register the sites ahead of time. When an event is declared, we pull or task the first usable pass over the region, check each site against the footprint, and send the calls once that pass is processed.
Site list, before the season
You send the named site list: each supplier site by address or coordinates. Keep it current at your supplier reviews and renewals.
Event declared
A flood, quake or cyclone is declared over a region, by you or on your say-so, and that starts the read. Nothing runs on a schedule.
First usable pass
We task or pull the earliest clear image over the region at 0.5 m or finer. How soon that is depends on the weather and on the satellite or aircraft available.
Per-site calls out
When the pass is processed you get the footprint call and the damage flag for each site, with the trigger log. If cloud covers the region, the read waits for the next clear pass and we tell you so.
Where it fits in your workflow
Ahead of the supplier's report and the drive-out
It sits at the top of the post-event chain. The control tower uses it for the allocation call. The claims team uses it for the first sort of sites.
The supplier's report and the field adjuster's inspection still follow.
Limits
- The read waits for a clear pass
- Optical imagery needs a clear view. Cloud over the region, which is common with a cyclone or a flood, delays the read to the next usable pass, and that can be days away. We do not promise a turnaround.
- Resolution floor
- At 0.5 m a pixel is about 20 inches across. A collapsed roof, a flooded yard or debris around a building show up. A cracked wall, a hairline fracture or a damaged machine inside a building do not.
- What it cannot see from above
- Interior damage, stock, power loss and a flooded basement are invisible to this read. A site can be marked "none seen" and still be shut. That is why the supplier's report stays in the chain.
- No dollar figures
- The output is a footprint call and a damage flag. It gives no loss estimate and no reserve.
- Quake damage is harder to see
- Shaking often leaves a building standing and unusable. Only collapse and large visible damage show, so a quake read says less than a flood or cyclone read.
- The footprint is only as good as its source
- A site just outside the footprint line can still be hit. Edge sites are flagged as edge sites.
Who it's for
Switch if
- You run a control tower and have to make the allocation call before the suppliers have answered
- You triage first reports of loss for an insurer and need to pick where the first adjuster goes
- You have a named list of supplier sites that stays fairly steady between events
Stick with the supplier report and the adjuster if
- You need a monetary loss figure or a reserve
- You need to know what is inside a building or whether it is running
- You want monitoring of sites when no event has been declared
Questions before your first event
Does this replace a field adjuster?
No. It tells you which sites to send one to first. The inspection and the claim stay with the adjuster.
How fast is a read?
As fast as the first clear image of the region can be taken and processed. It depends on weather and on what satellite or aircraft can get over the region, so we do not promise a fixed time.
What if cloud covers the whole region?
The read waits for the next clear pass. We say so rather than guess.
How do we check it against what suppliers report?
Take an event you have already worked, send the site list without the supplier reports, and compare our calls with what they said and what the adjusters found.
Do you assess dollar loss?
No. The output is inside or outside the footprint and visible damage or none seen.
What do we send, and how does it come back?
You send the named site list. After an event you get the per-site calls and the trigger log as a table or GIS layer. We do not write into your ERP or your claims system.
Who owns the imagery and the results?
Ownership and licence terms are agreed in writing when the pilot starts. If your legal team needs them earlier, ask.
How is a pilot bought and priced?
The price depends on how many sites you register and what imagery is used. Tell us how you run your site list and we will scope a pilot to that.
Get your site list ready for the next event.
Send us the named sites from a past event on your desk and we will tell you what the imagery would have shown.