Production control note
How can an event planner hand off seating revisions without a shared account?
Export a passive packet containing guest-facing HTML, staff CSV files, the service legend, host reminders, change register, affected-table output, findings, proof summary, reprint plan, manifest, and checksums; send it through an authorized channel and confirm receipt.
Passive means no report code
HTML files should contain only escaped content and print CSS, with no scripts, forms, remote fonts, trackers, or live application dependency. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Checksums are integrity aids
They can reveal accidental file changes but do not authenticate the sender or replace secure transfer. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Keep editable state separate
The recipient may not need the private project checkpoint. Share the minimum file set required for their role. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.