WEBINAR INFORMATION WORKSHEET Use one completed copy as the reference for your public page, confirmation, calendar entry and joining instructions. This worksheet does not schedule an event, create registrations or send invitations. EVENT Working event name: Intended audience: One useful task participants will work on: Session format: Preparation or attendance conditions: Recording decision and access arrangements, if any: DATE AND TIME Full date including year: Host start time: Host time zone and zone identifier: End time or duration: Audience location 1, zone identifier, converted full date and start/end: Audience location 2, zone identifier, converted full date and start/end: Conversion tool/data checked and date checked: Guest calendar view checked by/date: ATTENDANCE How registration is recorded: What the confirmation tells an attendee: Where the attendee gets their joining instructions: Are links public, private or unique to an attendee?: Attendance requirements to explain before registration: Who controls the session and attendee access: Support contact for attendee problems: Promised messages/reminders and evidence each one works: Unresolved decision, owner and date to resolve: MESSAGE PLAN (repeat for each confirmation, reminder or change notice) Message purpose: One sending system and person responsible for checking this message: Other tools that could send it and settings checked: Eligible registration status (including any approval requirement): Trigger or send date/time and time zone: Late-registration or catch-up rule: Repeat-registration and intentional resend rule: Statuses or event changes that should stop or replace this message: REGISTRATION TESTS Use an authorized test event and recipients you control. Check each case: - Normal registration reaching the required attendance status. - Late registration after an earlier reminder window has passed. - Repeat registration for the same test attendee. - Canceled or rejected registration after a reminder is queued, where supported. - Rescheduled or canceled event after reminders are prepared. TEST RECORD (copy for each case) Case and allowed test context: Event date/time/zone and test registration date/time/zone: Expected registration status and record behavior: Expected messages, recipients, due times and any messages that should NOT send: Actual registration state and record reference: Actual received messages and evidence references: Queue/send-history evidence, if available: Observation window (start/end/time zone) and time checked: Result: PASS / FAIL / NOT VERIFIED: Unresolved behavior, next action and responsible person: An empty inbox check alone does not prove a reminder was stopped. Inspect the available queue/send history and check through its due time. Mark unobservable or untested behavior NOT VERIFIED. A preview or simulation is not delivery. CONSISTENCY CHECK Registration page date/time/content checked by/date: Confirmation date/time/next step checked by/date: Calendar start/end/zone checked from guest view by/date: Joining instructions and attendee permissions checked by/date: CHANGE HISTORY Change recorded on: Previous full date, start, zone and duration: New full date, start, zone and duration: Audience times recalculated for the NEW date: Page, confirmation, calendar and instructions updated: Obsolete queued reminders canceled/replaced and evidence checked: Revised reminder schedule and eligible recipients checked: How existing registrants receive the change: Evidence the change notification reached its intended destination: Attendee view checked after the change by/date: