War-game a report queue SLA by testing whether age capacity, review gates, and freeze deadlines still shrink soft ages when several surfaces share one queue and the next board chart is close.
Report queue SLAs fail when "handled" means a checkbox without a decision artifact, when teams dual-count a draft as both reviewed and live, and when money-adjacent abuse paths still pin to one thin queue because the map is incomplete. The review needs one written inventory of report classes, one owner who can deny a risky age extension, and a documented consequence when a failed review ages past the deadline.
Assemble the queue packet
List report classes by surface, weekly volume, review gate, last age-out reason, owner of record, and evidence required to keep the SLA. Attach open findings, overdue drafts, and any emergency skip in the last quarter. Name which classes are out of scope and why. If a payments-adjacent abuse class is omitted, show the residual risk in the same packet.
Decide allow, revise, or hold in advance. Include the fields that compute overdue-review status so two reviewers reach the same label from the same exports.
Claim matrix
| Claim | Evidence required | Fail condition |
|---|---|---|
| Class is staffed | Named reviewer roster and measured time-to-first-human | Roster is empty or still points to a single untested analyst |
| Age is complete | Queue export showing handled state for the claimed fields | Ticket closed while export still shows open |
| Priority is unique | Sample queue proving no double-booked severity | Priority invents uniqueness the queue never enforced |
| Override is controlled | Logged use with time-bound restore of review | Shared override or unlogged use |
Walk four cases in Pingpong: a surface still pinned to one overloaded queue, an age that left a creator path live without trust review, a class that mixed spam and harassment content, and a request to skip a payments abuse report because volume is rare. Start from the documented SLA language. Ask who can extend a freeze window and which export proves review. Any step that depends on an unnamed person becomes a queue condition.
Replay one prior enforcement incident under the proposed rules. If the incident would still age without a reverse owner, revise the rules before calling the SLA ready.
Pair with the trust and safety lead seat, a ban appeals ladder stress test, and a spam threshold change review. More operating decisions live in the war-game decisions hub.
Close only when handled and blocked labels can be reproduced from stored exports without a verbal override.