Production control note
How should staff notes be separated from guest-facing seating files?
Keep staff notes, party labels, tags, and service codes in operations exports only; show exactly which files include them; and require the user to review recipient access before creating or sharing a production packet.
Minimize the note
Record only what the authorized workflow needs, using neutral operational wording supplied by responsible people. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Local storage is still exposure
A shared device, browser profile, backup, screenshot, print queue, or downloaded file can reveal the note. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Deletion requires a wider process
Removing a local record does not delete checkpoints, packets, printouts, emails, vendor copies, or backups. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.