Create cues that can be verified
Use a time, owner, location, action, success condition, service reference, and escalation contact. Examples include provider check-in, caption feed test, accessible document release, quiet-room opening, or attendee instruction window.
Protect privacy in shared documents
The general production crew does not need the underlying request. Give each role the minimum service and logistics facts needed for the cue.
Feed changes back into the plan
A room or time change can affect provider travel, equipment, sightlines, audio, attendee directions, and prior confirmation. Update the source plan and send revised handoffs rather than editing only the run sheet.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
Who owns accessibility cues?
Assign the person who can verify the action: provider coordinator, technical lead, room lead, materials owner, onsite accessibility lead, or another named role.
How much private information belongs in the run sheet?
Only what the assigned role must know for that cue. Use references and scoped instructions rather than copying case notes.
What happens after a cue is completed?
Record the service state or evidence in the operational record and escalate discrepancies immediately; do not leave the result only in a temporary production document.