Invitation, RSVP and registration test sheet
Editable event planning worksheet. Replace the placeholders and duplicate records as needed.
Event: [name]
Guest record owner: [name]
Provider: [name]
Test date/version: [detail]
Invitation release
Audience/list owner: [name]
Message approver: [name]
Response owner: [name]
[ ] Confirmed event facts and invitation promise match.
[ ] Response status and meaning of confirmation are defined.
[ ] Assistance/questions route is visible.
[ ] Guest-information handling agreed with responsible owner.
[ ] Change-message owner named.
Arrival assumptions
Total working count: [number/status]
Expected pattern: [spread/concentrated/groups/unknown]
Source of assumption: [invitation/transport/other evidence]
Venue-reviewed queue/help/onward arrangement: [plan version and owner]
Test the actual transaction
Record 1
Test case: Confirmed record
Intended process: [steps]
Observed issue: [observation]
Process/system owner: [name]
Revision: [change]
Retest status: [status]
Record 2
Test case: Missing confirmation
Intended process: [steps]
Observed issue: [observation]
Process/system owner: [name]
Revision: [change]
Retest status: [status]
Record 3
Test case: Name correction / duplicate
Intended process: [steps]
Observed issue: [observation]
Process/system owner: [name]
Revision: [change]
Retest status: [status]
Record 4
Test case: Unlisted guest
Intended process: [authorisation route]
Observed issue: [observation]
Process/system owner: [name]
Revision: [change]
Retest status: [status]
Record 5
Test case: Provider-assessed system interruption
Intended process: [approved fallback]
Observed issue: [observation]
Process/system owner: [name]
Revision: [change]
Retest status: [status]
Do not turn observed interaction times into a guaranteed service rate or a universal desk ratio.
Concentrated arrival scenario
Hypothetical scenario: [e.g. 500 guests released from shared transfers together]
Risk: [arrival/registration/onward conflict]
Common failure to avoid: [uncoordinated release / unsupported holding arrangement]
Fact owners: [transport / guest / venue]
Reviewed response and decision checkpoint: [plan]
Guest message owner: [name]
Programme consequence owner: [name]
Intended outcome: [coordinated handovers; do not guarantee no queues]