Invitation, RSVP and registration test sheet

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.

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 case	Intended process	Observed issue	Process/system owner	Revision	Retest status
Confirmed record	[steps]	[observation]	[name]	[change]	[status]
Missing confirmation	[steps]	[observation]	[name]	[change]	[status]
Name correction / duplicate	[steps]	[observation]	[name]	[change]	[status]
Unlisted guest	[authorisation route]	[observation]	[name]	[change]	[status]
Provider-assessed system interruption	[approved fallback]	[observation]	[name]	[change]	[status]

Do not turn observed interaction times into a guaranteed service rate or a universal desk ratio.

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]

ThreeSixZero · Event planning worksheet. Adapt to your agreed scope and responsibilities.