Production control note
What should be handed to a venue after seating changes?
Provide the current staff roster, table lists, service-code legend in host-approved wording, change register, affected-table summary, proof identifier, and explicit limitations; confirm the venue’s own format, deadline, and review process separately.
Do not silently translate codes
An opaque host code should map to exact supplied wording. The software must not infer a meal, allergy, disability, or service action. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Confirm receipt outside the app
A downloaded packet is not delivery evidence. Use the vendor’s accepted channel and obtain human confirmation. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Preserve the editable backup
The production packet is passive. Keep the integrity-checked project checkpoint separately for later revisions. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.