# Software Review Evidence Worksheet

Use this worksheet before publishing a review or making a vendor decision. The goal is to make the evidence level visible and conservative.

## Evidence summary

| Field | Notes |
|---|---|
| Product/vendor | |
| Page or decision owner | |
| Date checked | |
| Evidence level | Hands-on tested / researched / vendor evidence only / needs refresh |
| Hands-on testing performed? | Yes / no |
| Summary of evidence | |
| Key limitations | |

## Evidence inputs

| Input | Reviewed? | Notes |
|---|---:|---|
| Vendor product documentation | Yes / no | |
| Vendor pricing or packaging page | Yes / no | |
| Security/trust materials | Yes / no | |
| Trial or product account | Yes / no | |
| Import/export tested | Yes / no | |
| Admin/security controls tested | Yes / no | |
| Support or contract terms reviewed | Yes / no | |
| Practitioner/customer interview | Yes / no | Name only if publishable and consented |

## Conservative publishing rules

- If no current product account was used, do not mark the review as hands-on tested.
- If pricing was observed from public pages only, say it needs direct confirmation.
- Do not invent practitioner quotes, customer counts, screenshots, or unsupported ratings.
- If material plan gates are unclear, add a limitation rather than smoothing it over.