Reports Overview

Overview

Reports Overview is the first page operators see when they open the Report System. It does not edit safety records directly. It gives the current partner scope a quick read on total reports, open work, watchlist entries, active bans, reminders, recent reports, recent bans, recent updates, and recent incidents.

Use this page to decide where to work next. Use the route-specific pages for edits, decisions, or formal appeal handling.

Dashboard route

• /reports

Inputs and controls

Input or control	What it changes	Before relying on it
Partner scope selector in the dashboard shell	Changes which partner’s report counts, reminders, and recent lists are loaded.	Confirm the active partner name before interpreting totals or opening records.
+ New report layout action	Opens /reports/new to create a new incident report.	Use only when the incident has enough facts to become a formal record.
Reports subnav	Opens Overview, My Reports, All Reports, Watchlists, Bans, Profiles, and FPH-admin Cross-ban Requests.	Pick the page that matches the action; Overview is for orientation only.
KPI cards: Total, Open, Watchlisted, Active bans	Summarize the currently visible report dataset.	Treat them as scope-sensitive counts, not network-wide proof unless the current user has network visibility.
Open reminders callout	Highlights open reports needing follow-up.	Open the linked report before deciding the reminder is stale or complete.
My recent reports	Shows the newest reports filed by the current organization.	Confirm whether the report is still open before handing it off.
Recent bans	Shows recently visible ban records.	Check the Bans page or Report Detail before treating a ban as active.
Recent report updates	Shows recent revision activity.	Open Report Detail to see revision history and changed fields.
Recent incidents	Shows recent incident report records.	Use All Reports for filtering and Detail for source evidence.

Workflow

flowchart TD
  open["Open /reports"] --> scope["Confirm partner scope"]
  scope --> totals["Read KPI cards and reminders"]
  totals --> choose{"What needs work?"}
  choose -->|New intake| newReport["Open New Report"]
  choose -->|Find existing case| allReports["Open All Reports"]
  choose -->|Own org follow-up| myReports["Open My Reports"]
  choose -->|Restriction review| bans["Open Watchlists or Bans"]
  choose -->|Identity linking| profiles["Open Person Profiles"]
  choose -->|Network decision| crossBans["Open Cross-ban Requests"]
  click newReport "../new-report/" "Open New Report docs"
  click allReports "../all-reports/" "Open All Reports docs"
  click myReports "../my-reports/" "Open My Reports docs"
  click bans "../bans/" "Open Bans docs"
  click profiles "../person-profiles/" "Open Person Profiles docs"
  click crossBans "../cross-bans/" "Open Cross-ban Requests docs"

State behavior

State	What the operator sees	What to do
Loading	KPI cards and list cards show placeholder values.	Wait before making decisions.
Empty partner scope	Cards show empty states or zero-like counts.	Confirm the partner scope and user access.
Load error	The affected card shows an error alert.	Reload after confirming dashboard auth; do not assume no reports exist.
FPH admin	Cross-ban Requests appears in the reports navigation.	Use that page only for network-level review work.

Related pages

• All Reports for filtering and opening any visible incident report.
• My Reports for records filed by the current organization.
• Report Lifecycle for intake, review, action, and closure expectations.

End-to-end operator runbook

1. Confirm scope: Check the dashboard partner selector before reading any metric.
2. Read reminders: Open any open reminder that looks urgent or stale.
3. Choose the surface: Move to New Report, All Reports, Watchlists, Bans, Profiles, or Cross-ban Requests based on the next action.
4. Verify evidence: Open the specific report before deciding a count or card proves the case state.
5. Record handoff: Share the report number, current status, route, and owner rather than a screenshot of the overview.

Common mistakes

Do not treat Overview counts as an audit log. Counts tell you where to look; Report Detail, Manage Report, Bans, Appeals, and revision history provide the proof.