Evidence Handling Best Practices

Apply This Operating Standard

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Evidence Handling Best Practices narrows that work to how to describe, preserve, and limit evidence in report records. Because this is a best practices page, read it as part of the Report System learning path rather than as an isolated checklist.

A report is a written memory of something important. The goal is to protect people, keep facts clear, and leave enough context for future reviewers. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What Good Operation Looks Like

This page is a judgment aid. Use it before and during sensitive work, especially when a action that looks valid on screen could still confuse attendees, staff, reviewers, or support leads. The intended readers are Report writers and Investigators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /reports/new and /reports/manage?id=:incidentId.
• Records or contracts involved: Evidence notes, Witness notes, and Markdown uploads.
• Main care point: Watch for incomplete facts, unfair wording, privacy exposure, or a decision that another reviewer cannot understand later.
• Proof worth keeping: report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner.

Use The Standard Before You Act

1. Identify the policy or risk behind the task: Begin by naming the Report System situation, the owner, and the exact item involved in Evidence Handling Best Practices.
2. Compare the planned action with the standard: Use /reports/new and /reports/manage?id=:incidentId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Adjust the action before saving if the standard is not met: Keep Evidence notes, Witness notes, and Markdown uploads in view so the work stays tied to the records or contracts it can affect.
4. Record any exception and who approved it: Before handing off, save proof such as report ID, saved status, revision history, person profile, evidence note, reminder, reviewer decision, and handoff owner so another reviewer can understand the facts without relying on memory.

Signs The Standard Was Met

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on people, privacy, fairness, evidence, and the trustworthiness of the record.
3. Proof is findable: The handoff points to evidence that another reviewer can understand the facts without relying on memory.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Choose the right path. Open the related workflow page and confirm you are working on the correct record or event. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Use this best-practice page as a checklist before making changes in /reports/new, /reports/manage?id=:incidentId. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Do the operating action. Check policy, permissions, affected people, money, privacy, and communication impact before saving. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Verify the result. Make the smallest accurate change, then verify Evidence notes, Witness notes, Markdown uploads show the intended result. The next action should still protect privacy, evidence, and due process.
5. Step 5 - Hand off remaining work. Write down unresolved questions and escalate anything that could affect safety, fairness, money, or trust. This leaves a handoff trail another operator can understand.

Evidence is support, not decoration

Evidence helps staff check whether a claim is true, partly true, false, mistaken, or still unknown. Add evidence because it helps the decision, not because it makes a report look bigger.

Types of evidence

Evidence type	How to describe it
Screenshot	What it shows, date/time if visible, source, and whether it is cropped.
Chat log	Platform, people involved, date range, and who exported it.
Witness statement	Who gave it, how they know, and what they personally saw or heard.
Link	Destination, why it matters, and whether it may disappear.
Photo/video	What it shows, where it came from, and whether consent/privacy issues exist.
Staff observation	Which staff member saw it and when.

Privacy rule

Collect only what is needed to understand and review the case. Do not store extra personal details just because they are available.

Evidence notes should answer

• What is the evidence?
• Who provided it?
• When was it created or received?
• What does it show?
• What does it not prove?
• Where can an authorized reviewer find it?

Markdown-ext use

Use markdown-ext formatting to make evidence lists readable:

• Use bullet lists for multiple files or links.
• Use tables for short evidence inventories.
• Use code formatting only for exact handles, IDs, or URLs.
• Do not paste huge logs directly if a summary and secure source location is safer.

Chain of understanding

For serious action, a future reviewer should be able to trace:

report text -> evidence note -> source material -> staff decision -> action note -> appeal path