War-game a visitor log rewrite by proving each lobby class has a named owner, a measured retention window, and a reverse path before the calendar starts governing every visitor claim.
Visitor log rewrites fail when "checked in" means a status without a decision artifact, when teams dual-count a draft exception as both approved and live, and when high-risk lobby paths still pin to one thin roster because the map is incomplete. The review needs one written inventory of visitor classes, one owner who can deny a risky shortcut, and a documented consequence when a failed exception ages past the deadline.
Write the rewrite under fire
State the rewrite scope, the effective date, which lobbies are protected, how exceptions work, and what happens to visitor records already in flight. Name the teams that feel it first and the audit commitments that depend on complete logs. If the memo mixes a visitor rewrite with a badge policy and an evacuation cut, split them.
Also write the reverse criteria: the completeness miss, retention gap, or landlord deadline that would force a rewrite release within a stated window. If you cannot name the owner or the reverse criteria, the rewrite is decoration.
Hostile seats
- Facilities seat: lobby timing, completeness math, and what the visitor forecast hides if exceptions soften after the rewrite.
- Security seat: escort risk, contractor load, and the first ninety days of thinner lobby coverage.
- Legal and privacy seat: retention promises that break in process, DSAR risk, and relationship damage with landlords.
- Reception and workplace seat: dual-counted check-ins and the message that would leave orphan visitor rows open past lock.
- Skeptic seat: the claim that looks strongest and is least sourced.
Attach the same source pack to every seat: open visitor rows, exceptions in flight, protected lobbies, retention commitments, and the exception policy you actually intend to use.
Private pass
Run that package in Pingpong. Sequential review helps because an early pass can defend the completeness upside while later passes try to kill soft clearances and dual-counted lobby equity. Keep a change log of classes cut, sequenced, or clarified. If survival requires silence about a single hero lobby or a heroic retention guess, stop. Rewrite the packet or delay the "ready" label.
Pair with the facilities ops lead seat, a badge access policy review, an evacuation drill script stress test, and the privacy ops lead seat. More operating decisions live in the war-game decisions hub.
Ship the rewrite only when approved and blocked labels can be reproduced from stored visitor exports without a verbal override.