A practical workflow
Record public essentials
List the campaign name, intended location and approved invitation text. Keep the QR artwork in a known place.
Assign maintenance
Name the responsible role for identity changes, destination checks and replacing damaged signs. Use authorised account access.
Document checks
Include the phone test and what a successful handoff looks like. Note that copying a draft is not a confirmed post.
Avoid this mistake
Do not put passwords, API keys or database backups in a shared campaign handover.
What to check
Ask another authorised staff member to identify and test the correct campaign from the handover alone.
Verify the actual setup
A feature can be present in the interface while still needing service configuration. Check the relevant connection, allowance and approval state before telling the team it is ready. Keep credentials in authorised administrator settings and private backups. Use sample data for routine checks and avoid sending real requests, publishing replies or making payments simply to prove a screen loads.