Review and Update a Report

Work Through The Task

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Review and Update a Report narrows that work to how to triage, edit, status, and maintain report records without hiding context or confusing future reviewers. Because this is a basics 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 This Task Changes

This is a practical workflow. Read it from top to bottom the first time: the early checks set scope, the middle steps make the change, and the final checks prove the result. The intended readers are Trust and Safety staff and Partner admins. 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/detail?id=:incidentId and /reports/manage?id=:incidentId.
• Records or contracts involved: Incident reports, Status changes, and Revisions.
• 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.

Follow The Work In Order

1. Confirm the exact scope before opening the tool: Begin by naming the Report System situation, the owner, and the exact item involved in Review and Update a Report.
2. Read the visible state before editing anything: Use /reports/detail?id=:incidentId 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. Make only the change this guide describes: Keep Incident reports, Status changes, and Revisions in view so the work stays tied to the records or contracts it can affect.
4. Verify the result where another operator would look: 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.

Finish With Proof

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 - Identify the report and scope. Open the report detail page from the report list or direct report link. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the existing facts before acting. Read the whole existing record before editing so you do not overwrite context. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Make the smallest factual update. Confirm whether the new information changes facts, status, risk, people involved, or actions taken. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Check fairness, privacy, and risk. Edit only the fields that need correction or update, and explain why the change was made in notes. The next action should still protect privacy, evidence, and due process.
5. Step 5 - Verify the saved record and history. Save, reload the detail page, and check revision history or visible fields for the expected update. A later reviewer should be able to understand this step from the saved record.
6. Step 6 - Hand off the next responsibility. Tell the next owner what changed and whether any appeal, reminder, or enforcement action is now required. This leaves a handoff trail another operator can understand.

Review first, edit second

When you open an existing report, read the record before changing it. Look for:

• Current status.
• Subject and victim identifiers.
• Evidence notes.
• Action notes.
• Revision history.
• Related person profile links.
• Whether it is local or network-scope.

Safe update flow

1. Action 1. Open the report detail page. Pause long enough to confirm the record says only what is known.
2. Action 2. Read the current record and previous revisions. Check the saved value before adding more context.
3. Action 3. Decide what needs changing. Use the report history as the source of truth before continuing.
4. Action 4. Open the manage page. Pause long enough to confirm the record says only what is known.
5. Action 5. Edit only fields that need correction or new information. Check the saved value before adding more context.
6. Action 6. Keep older context unless it is wrong or unsafe to retain. Use the report history as the source of truth before continuing.
7. Action 7. Add clear action notes if action changed. Pause long enough to confirm the record says only what is known.
8. Action 8. Save. Check the saved value before adding more context.
9. Action 9. Reopen the detail page and confirm the saved version. Use the report history as the source of truth before continuing.

Status guidance

Status	Use when
New	The report was just filed and not reviewed.
Triage	Staff are deciding urgency, ownership, and next steps.
Investigating	Staff are actively gathering or checking evidence.
Resolved	Staff completed the decision and action.
Closed	No further action will be taken, or the report is archived.

When information changes

If new information changes the meaning of the report:

• Update the relevant field.
• Say where the new information came from.
• If severity changes, explain why.
• If action changes, explain the new decision.
• If a previous note was wrong, correct it plainly instead of hiding the correction.

When not to update

Do not update a report just to:

• Make a decision look cleaner than it was.
• Remove uncomfortable context.
• Change wording to punish someone harder.
• Hide a staff mistake without noting the correction.

Use Record Maintenance when a record needs careful correction, archiving, or reopening.