Appeal Lifecycle

Overview

The appeal lifecycle starts when a partner requests FPH-admin review of an active network ban. The appeal can be pending, approved, denied, edited while pending, or resubmitted after denial.

Flowchart

flowchart TD
  network["Active network ban"] --> partner["Partner opens Network Ban Appeal"]
  partner --> create["Submit reason"]
  create --> pending["Status: pending"]
  pending --> edit["Partner may update reason"]
  edit --> pending
  pending --> admin["FPH admin opens Ban Appeals"]
  admin --> decision{"Decision"}
  decision -- Approve --> approved["Status: approved; ban review succeeds"]
  decision -- Deny --> denied["Status: denied; review notes visible"]
  denied --> resubmit["Partner updates and resubmits"]
  resubmit --> pending
  click partner "../surfaces/network-ban-appeal/" "Open Network Ban Appeal docs"
  click admin "../surfaces/ban-appeals/" "Open Ban Appeals docs"

Lifecycle states

State	Who acts	Surface	Evidence
Create	Partner	Network Ban Appeal	Appeal reason and active partner.
Pending	Partner or FPH admin	Network Ban Appeal, Ban Appeals	Submitted time, current reason, revisions.
Updated	Partner	Network Ban Appeal	Revision history shows previous and new reason.
Approved	FPH admin	Ban Appeals	Decision status and optional review notes.
Denied	FPH admin	Ban Appeals	Decision status and review notes.
Resubmitted	Partner	Network Ban Appeal	Updated reason after denial and revision history.

Inputs that control appeals

Input	Surface	What it affects
Reason for appeal	Network Ban Appeal	Partner’s request and evidence for review.
Updated reason	Network Ban Appeal	Resubmission or pending edit.
Review notes	Ban Appeals	FPH-admin response shared with partner.
Approve - lift ban	Ban Appeals	Approves the appeal.
Deny appeal	Ban Appeals	Denies the appeal.
Confirm decision	Ban Appeals	Writes the final appeal decision.

End-to-end operator runbook

1. Partner submits: Confirm active partner scope and write a specific appeal reason.
2. Partner tracks: Edit while pending if new facts appear.
3. FPH reviews: Open the source report and appeal detail before deciding.
4. FPH decides: Approve or deny with review notes where useful.
5. Partner verifies: Read decision state and resubmit only with new or clearer information.

Common mistakes

Do not use an appeal as a hidden chat with FPH admin. The appeal reason and review notes are part of the decision record.