Report System Glossary

Use The Terms In Context

Use this guide when a safety, accountability, or follow-up record needs careful handling. In this guide, Report System Glossary narrows that work to plain definitions for report-system words, roles, records, and dashboard surfaces. Because this is a reference 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 The Terms Are For

This is a lookup page, but the definitions still belong to real operations. Read the term, then connect it to the record, screen, file, or decision where the word appears. The intended readers are All users. 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.
• Records or contracts involved: Glossary terms.
• 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.

How To Read A Definition Safely

1. Find the exact term used by the system: Begin by naming the Report System situation, the owner, and the exact item involved in Report System Glossary.
2. Read the surrounding workflow: Use /reports to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the term consistently in notes: Keep Glossary terms in view so the work stays tied to the records or contracts it can affect.
4. Ask for review when two terms sound similar: 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.

Before You Use A Term In A Note

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 - Confirm the term or page. Look up unclear words before operating the dashboard, especially status, scope, payment, check-in, appeal, or record terms. This anchors the work to the correct scope before any record changes.
2. Step 2 - Check the related context. Use the exact term from the dashboard when writing notes so another operator can find the same state later. Pause here and confirm the note is factual, fair, and reviewable.
3. Step 3 - Apply the guidance. If two terms seem similar, open the related reference or lifecycle page before deciding. This keeps the report useful to the next reviewer instead of only to the person writing it.
4. Step 4 - Return to the workflow. After the term is clear, return to the workflow page and complete the documented steps. This leaves a handoff trail another operator can understand.

People

Term	Meaning
Reporter	Person who gave the information or filed the report.
Subject	Person the report is about. This does not prove guilt.
Victim	Person harmed or targeted, if known.
Witness	Person who saw, heard, or has relevant information.
Officer	Staff member handling the report.
Investigator	Staff member checking evidence and context.
Reviewer	Person checking a report, action, appeal, or old record.

Records

Term	Meaning
Incident report	Main structured record of a safety incident or concern.
Revision	Saved history showing what changed in a report.
Watchlist entry	Marker telling staff to check context before acting.
Ban	Restriction from an event, partner space, or network.
Cross-ban request	Request to share or apply action beyond one partner.
Appeal	Request to review a restriction or network action.
Person profile	Record grouping reports believed to involve the same person.
Profile link	Connection between a profile and a report.

Statuses

Status	Meaning
New	Filed but not yet reviewed.
Triage	Staff are deciding urgency, owner, and next step.
Investigating	Staff are checking evidence or collecting information.
Resolved	Decision and action are complete.
Closed	No further action is planned, or the record is archived.

Scope

Term	Meaning
Local	Applies inside one partner or event scope.
Network	Shared across trusted Furries PH partner organizations.
Event ban	Restriction from a specific event.
Community ban	Broader partner-level restriction.
Network ban	Restriction that affects the partner network.