# Evidence map template

One row per record. The point is not to list documents; it is to show which
facts have something behind them and which do not.

| Record | Record type | Who holds it | Status | Date requested | Supports which event | Relationship | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Police report #2024-1188 | Incident report | Responding agency | Held | | Rear-end collision at a stop light | Supports | Timestamp differs from the client account by 40 minutes |
| Treatment records | Medical record | Treating provider | Requested | 2024-04-20 | First treatment for neck pain | Supports | Second request sent |
| Employer wage statement | Employment record | Employer payroll | Missing | 2024-04-20 | Employer told of missed shifts | Would support | No response yet |
| Dashcam footage | Video | Client | Held | | Rear-end collision at a stop light | Partly supports | Captures the moment of impact only |

## Relationship values

Use one of: **Supports**, **Contradicts**, **Mentions**, **Would support** (for
a record you do not hold yet), or **Needs review**.

Recording "Contradicts" honestly is the point of the column. A record that
disagrees with the account is something to understand early, not something to
leave out of the list.

## Reading the map

Any event with no row pointing at it is unsupported. Any row marked Requested
with an old date is a follow-up nobody has chased. Those two readings are the
reason to keep this as a table rather than a folder.