Make an offline plan before the venue loses signal

A phone-friendly workspace is useful until a dead battery, poor signal or locked device takes it away. The fallback should be planned while everyone has time to understand it, not improvised during the ceremony.

A practical sequence

1. Print the current approved run of show, contacts and critical venue information.
2. Give the lead coordinator and a named backup separate copies.
3. Agree which person can call a change when the shared system is unreachable.
4. When connectivity returns, reconcile decisions before sending delayed notifications.

Work through an example

The ceremony moves indoors while two vendors cannot load the live page. The coordinator uses the agreed phone tree, writes the revised room and time on the field copy, and asks each critical role to repeat back the instruction. Later, the online record is updated with the decision and its actual notification history.

Where judgement matters

Do not label an application offline-capable merely because a page remains visible after losing signal. A readable cached page, queued edits and safe conflict resolution are different capabilities. Test the exact failure you expect and state what remains unavailable.

Make it usable

Open the working tool and change the example to match your own event. Then adapt the structured template. Keep the original assumptions visible until the people responsible have confirmed them.

Work the decision

A practice case

An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.

The venue has poor mobile coverage. A coordinator last refreshed the runbook at 14:10; a second coordinator published a change at 14:18. The offline device still shows the earlier instructions. The device needs to be useful while making this uncertainty visible, rather than presenting stale data with the confidence of a live connection.

Three decisions and why each matters

Decision	Why it matters
Print the most recent accepted version before arrival.	The printed timestamp and a named contact provide a fallback when batteries or accounts fail.
Keep pending offline changes visibly separate.	A locally checked task has not necessarily reached anyone else.
Resolve revision conflicts after reconnecting.	Blindly overwriting a newer change can reverse an important day-of decision.

Make one usable artifact

Prepare a one-page fallback containing version time, emergency contacts, fixed anchors, role assignments and the process for reconciling pending notes.

Then test the difficult case

One device records a ten-minute delay offline while another changes the same event online. Explain which facts a human must compare before applying either change.

Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.