search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Sector content and pathways

    Events: registration, changes and closure

    An event site must remain consistent before, during and after its holding. Program information, advertised capacity and registration messages must be linked to the same validated version.

    These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.

    All sectoral files
    Empty event room with seating and reception area
    AI-generated illustration

    Explore all 28 review cases — A venue change is forgotten

    Identify dates and program

    View Year, Location and Times, with the time zone when the public participates remotely. Distinguish confirmed speaker and provisional program. Each session must be able to be recognized without depending on a poster. A downloadable version should remain aligned on the page that shows the latest changes.

    Set registration status

    Explain whether the action reserves a place, submits a request, or adds to a waiting list. Describe the next step and confirmation channel. Only display a number of remaining places if its source and update are reliable. Demo registrations remain in the test environment.

    Prepare for changes

    Define who validates a location, schedule or session change. Update the page and channels used to inform registrants. The site should help recognize the current version without deleting the information needed to understand an old confirmation.

    Test the full course

    Check registration, duplicate, waiting list, correction and cancellation with test data. Check the confirmations in all the languages offered. On mobile, the main action must remain understandable even with long titles and names; On the keyboard, errors must be accessible.

    close without losing context

    Close the registration at the right time and present the event as completed. Publish a report only after validation of the facts. Keep authorized media with their credits and remove private participation information. For a new edition, create a dated page rather than mixing multiple programs.

    Information to gather before writing

    • Year, useful schedules and time zone
    • Confirmed or provisional program
    • Registration status and confirmation
    • Responsible for changes
    • Closing and Rules of the Archives

    For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.

    A case for preparing the content

    Calculate remaining places using active tickets

    Fictional case: capacity is 120 places, with 100 tickets issued, 10 cancelled and 81 arrivals checked in. Each ticket admits one person here.

    Fictional teaching exercise: these texts and values describe no real business, course or product.

    Path to check

    1. Set the capacity
    2. Count active rights
    3. Separate arrivals
    4. Display remaining places

    Compare the wording

    Avoid in this example

    39 places remain because 81 people have entered.

    More precise wording

    90 active tickets for 120 places: 30 places remain in this case. The 81 arrivals are a separate counter.

    Scroll the table horizontally if needed. With a keyboard, focus the table and use the arrow keys.

    Three checks based on the supplied information
    Starting informationWhat it establishesWhat still needs checking
    Capacity of 120 placesLimit used for the exerciseIs there another allocation or hold?
    100 tickets less 10 cancellations90 tickets still activeDo reissues create duplicates?
    81 checked-in arrivalsAttendance observed at the snapshotDoes checking distinguish first entry from re-entry?

    The 30 places assume no other holds; do not subtract arrivals from ticket inventory.

    Separate admission rights from attendance

    One hundred issued tickets include ten cancellations. Ninety admission rights remain active, and eighty-one have been checked in. The other nine rights are active without a recorded admission at this moment; that does not make them available for sale.

    Keep a stable identifier when a ticket is resent or reprinted. A second passage does not create another person. The thirty remaining places assume that no other quota, hold or right reduces this example’s capacity.

    This workshop uses its own fictional snapshot. Do not combine its figures with those of another example on the page.

    Each bar states its own total: 120 places, then 90 active rights.

    The diagram values are listed below with their labels.

    Find the values behind the diagram
    MeasureValue
    Stated capacity120
    Issued tickets100
    Cancelled tickets10
    Active rights90
    Remaining places30
    Recorded admissions81
    Rights without recorded admission9
    A person preparing ticket checks in an empty performance venue.

    Keep the information consistent

    When to review
    Capacity, allocation or status changes
    Who validates
    The ticketing owner reconciles issues, cancellations and active admission rights.
    Journey to replay
    Cancel a fictional ticket and check inventory, confirmation and admission control.

    Test booking states →

    Understand an indicator

    Registration does not guarantee attendance

    Fictional teaching example: these figures are neither market statistics nor measured client results. They illustrate a calculation and its limits.

    A fictional event has 150 distinct people with confirmed registration. After check-in, 120 of them are recorded as attending. Unregistered companions are outside this group.

    The proportion in this example

    80%120 / 150 × 100

    People in that group recorded as attending
    120
    People with confirmed registration
    150

    What this figure means

    80% of confirmed registrants are recorded as present. Total admissions may differ if people attend without registration or join several sessions.

    Define the count before comparing

    Count distinct people and match attendance to the corresponding registration. State whether the record covers a day, a session or the whole event.

    The 150 registrants could comprise 120 recorded attendances, 20 confirmed absences and 10 unknown states. A missed scan does not turn unknown attendance into absence. Checking the same person in twice must not create a second attendee.

    A practical check on the website

    Review confirmation information: date, time zone where needed, venue or access link, practical instructions and how to report a cancellation.

    What the calculation cannot establish

    This calculation assumes reliable reconciliation. Unrecorded attendance remains missing data; it does not prove absence.

    Try with your own counts

    Use two counts from the same group and period, with the same unit. The selected cases must belong to the reference total. Leave unknown values blank.

    Whole counts only, up to one billion. Formula: selected cases ÷ reference total × 100. The displayed percentage is rounded to one decimal place.

    These values stay in this page without being sent or saved. The calculation provides no benchmark, prediction or quality score.

    To document real data, keep its origin, scope and quality limitations clear. Method reference : W3C · Data on the Web Best Practices (in English) · Consulted on . This source does not supply the fictional figures above.

    A content model to maintain

    Connect an event’s identity with distinct sessions and confirmed status. For the exercise, prepare a meeting with one in-person and one remote session, then change only one. An old shared link should explain what changed without silently moving every registration to a new date.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    A content model to maintain
    InformationContent to retainConsistency check
    Event and occurrenceRetain an event identifier and a reference per session with organizer, title and links between the original occurrence and updated information.Postpone one session and reopen an old link: readers should recover its context while other sessions remain identified and unchanged.
    Date and participation modeDescribe start, end, relevant timezone and venue or remote format for each session. Keep private access details within an appropriate confirmation channel.Compare page, listing and registration summary for a participant in another timezone. Time should be interpretable without exposing a private access link publicly.
    StateScheduled, full, rescheduled, cancelled or ended as confirmed.Booking is disabled or adapted to the announced state.
    ParticipationConditions, contact and confirmation instructions.A received request does not become a confirmed place without validation.
    Date, place and statusGive each session its date, time zone where needed, exact venue and state: open, full, postponed or cancelled.Follow a link shared before a postponement; the reader should find the new date and what happens to their registration.

    A focused next step

    On a working copy, cancel one session and replay a previously started registration without sending real messages. Check visible status, request handling and offered contact. Have the organizer confirm instructions; where an alternative exists, present it as an explicit choice.

    Schema.org: Event — a reference for describing information, not evidence of a particular business or a guarantee of search features. · Source consulted

    A review case to reproduce

    A venue change is forgotten

    Situation to examine
    The event page is corrected but confirmation email and downloaded directions still show the old venue or entrance.
    Proposed check
    Test the complete journey with a fictitious registration. Compare address, entrance, hours and instructions. Define change approval and how the organisation informs people already registered.
    Evidence to retain
    Keep the support inventory, test message and organiser approval. Access information points to the same venue and clearly communicates a relevant change.
    Fictional finding example
    Event DEMO-E1 moves from room A to room B. The page is corrected, but the confirmation email and plan retain A.
    Interpret this outcome
    The correction remains incomplete in two places. Check the planned communication to existing registrants before treating the venue change as resolved.

    Method reference : W3C — Data on the Web Best Practices · Source consulted

    Method reference : Schema.org · Event · Source consulted

    Learning scenario

    A scenario for planning the user journey

    Preparation exercise: A participant chooses a date, consults the program, registers and searches for the arrival information. Use a demo event. Test a room change and close registrations. Separate the announced program from the confirmed program and identify the items that may still change. An acknowledgment of receipt, a reserved place and a validated payment correspond to different states: the messages must resume exactly the state known to the system.

    Documents and information to prepare

    • Dates, place, access and contact validated
    • Program with Intervention Status
    • Ability and real registration process
    • Arrival information and response to changes
    • Responsible for updates before and during the event

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. A change of room updates program and access.
    2. The closing of registrations is visible before the entry.
    3. A pending registration does not become a confirmed place.
    4. The program distinguishes an announced speaker from an experienced speaker.
    5. The date and time zone are explicit for a remote session.
    6. The participant finds the arrival information after registration.

    Understand pre-launch checks

    Ongoing management and handover

    Assign an owner to each information that can change quickly. Prepare a usable page and update message without changing the entire presentation. After the event, turn the practical information into a dated archive and remove calls to registration that have become invalid. Photos from the previous edition should be captioned with their context and publication permission.

    Organize site maintenance

    Compare two approaches

    Registration can express interest, request a place or obtain confirmation. Choose a workflow whose status remains clear even when capacity changes.

    Request requiring approval

    When to choose it
    Suitable when organisers select applicants or confirm information. Collect what is needed for this stage.
    What to plan for
    Distinguish receipt from confirmation. Plan responses to declined requests, waiting-list contact requests and requests received after closing.

    Confirmed registration or ticketing

    When to choose it
    Suitable when a maintained system manages places. The summary identifies the event, session and number of people.
    What to plan for
    Test the last place, repeated requests and interruptions. Explain the organiser’s approved change procedures.

    A risk to anticipate

    A page shared well before an event must remain correct after postponement. Check the page, documents and sharing previews when details change.

    How to decide

    Simulate successful registration and an unavailable session. Users should understand their status and find updated information without restarting unnecessarily.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare programme, dates, registration and any ticketing. Distinguish an enquiry from a confirmed place; price tool connections and full-capacity cases.
    Recurring operation
    Separate edition costs, subscriptions and variable charges. Record reference volume and inactive periods; multiplying a busy month across the year may distort comparison.
    Exit and handover
    Plan programme recovery, useful archives and registration rules. Define ongoing-enquiry handling and old-journey closure; an archived site must not keep accepting outdated registrations.

    Compare the costs of three web solutions

    Separate the session, time zone and availability

    Two sessions of the same workshop can share a date; during a clock change even the time can repeat. A stable reference prevents a registration being assigned to the wrong session.

    1. Keep the session identifier with its instant and display zone.
    2. Check the last available place in the booking system, separately from time conversion.
    3. Test rescheduling: the new public date, internal record and confirmations must remain consistent.

    Open the date and time zone comparison →

    Frequently asked questions

    How should received registrations, waiting lists and confirmed places differ?

    Use explicit status wording on the page and in the message. A waiting list does not allocate a place; state who will follow up and what action remains. Also test the last available place and a cancellation to check capacity and message consistency.

    How should times be shown for a remote audience?

    Show the date, time and reference time zone beside the relevant session. If the interface offers local time, distinguish it from programme time and retain the corresponding date. Test day changes and translated confirmations; a time difference can also shift participation to the previous or following day.

    What should be checked before releasing a cancelled place?

    Define how capacity is released and any waiting-list order. Rehearse cancellation, status changes and reassignment using a demonstration case. The interface, count and messages should describe the same state without confirming the same place to several people.

    How should an event postponement be announced in several languages?

    Update the main source, then every language version and linked registration service. Keep a postponement notice when it helps people already informed. Recheck downloadable documents and sharing previews.

    Further reading

    Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.

    Browse other resources