# Reports and evidence

Product design

This page describes the product model and requirements. Examples illustrate the model, not a guaranteed API or completed feature. Check the [application contracts](/stormtrust/apps/) and [dataset inventory](/stormtrust/product/platform-and-data/datasets-and-source-contracts/) for implemented scope. Use [operations guides](/stormtrust/engineering/operations/) for runnable procedures.

A StormTrust report packages scope, evidence, interpretation, provenance, confidence, revision, disclaimers, branding, and audit history. It is not merely a map screenshot.

## Storm reports

[Storm Report](/stormtrust/product/platform-and-data/intelligence/storm-report/) is the storm-intelligence capability that packages a reviewed briefing for supervisors and canvassers. Its [first-release contract](/stormtrust/product/platform-and-data/intelligence/report-contract/) owns county and work-area priorities, publication, email delivery, mobile use, and acceptance before parcel matching. This page owns the shared evidence and report concepts used by later property and weather-history reports.

## Property impact reports

A property report may contain the property, event, estimated exposure, maximum estimated hail, confidence, nearby observations, warnings, imagery, and provenance.

It does not claim confirmed physical damage unless a qualified source confirms that damage.

## Weather history reports

A weather-history report summarizes relevant events around a property or location for a requested time range.

## Evidence dossiers

A dossier is richer than a static report:

```txt
Dossier
├── canonical web representation
├── revision history
├── source evidence
├── generated PDF
├── related files
├── annotations
├── review state
└── share permissions
```

## Evidence vault

Evidence files preserve original bytes when appropriate, content hashes, sources, timestamps, tenant context, related entities, metadata, and retention policy.

## Provenance manifests

A provenance manifest summarizes the data lineage behind a report or derived conclusion.

## Chain of custody

For claim, appraisal, legal, or expert-review workflows, StormTrust may retain original acquisition, transformations, hashes, reviewers, exports, corrections, and report-generation history.

StormTrust does not claim legal evidentiary status beyond its documented procedures and applicable law.

## Branded reports

Tenant branding may include an approved logo, company name, representative, contact details, colors, and messaging. Source and evidence labels remain visible regardless of branding.