Common pressure
Without a baseline, post-storm review starts with assumptions.
Use case
Post-storm review
Compare a storm event to a known baseline so teams can isolate new change instead of arguing about prior condition.
Why this use case exists
Without a baseline, post-storm review starts with assumptions.
Baseline → event capture → comparison → finding → claim-ready decision pack.
Cleaner evidence for claims, scope review, and stakeholder alignment.
Record workflow
Baseline → event capture → comparison → finding → claim-ready decision pack.
Typical output
Cleaner evidence for claims, scope review, and stakeholder alignment.
Where this fits best
- Owners and facility teams after a hail or wind event
- Insurers and consultants reviewing pre-loss vs post-event condition
- Roofs where prior issues need to be separated from new change
Operating model
Portfolio
Property
Building
Roof
Baseline
Event
Artifact
Finding
Decision Pack
Action
Closeout
Need to move this use case into a real record?
The fastest path is still to install baseline on the roof or portfolio that matters first.