Answer attendee questions from the current event bulletin

A polished attendee reply can combine an old room number with a new time or promise a booking that has not happened. Use the supplied bulletin to write a short reply, then check every promise.

Practice goal: Write a source-bound attendee reply that separates confirmed event information, a pending request and unanswered questions.

Use only the invented information below. Do not paste real emails, personnel records, customer details or confidential event records. Changing a name does not establish permission to upload a real record.

• [F1] Fictional Cedar Ideas Exchange bulletin, version 2, issued October 12: the event is October 20 in Room Birch. Doors open at 13:30; the session runs 14:00–15:00. Version 2 replaces version 1 for this event.
• [F2] Archived version 1 named Room Alder and a 13:00 session start. Those room and session-time details are no longer current.
• [F3] The event desk reviews place requests and sends a separate confirmation if a place is allocated. A request acknowledgment is not a place confirmation.
• [F4] The attendee has received only a request acknowledgment. The source gives no current availability count. It does not establish that the event is full.
• [F5] The current bulletin says no recording will be provided. It contains no information about parking or step-free routes. The event desk is the contact for questions; no email address or response deadline is supplied.
• [F6] The attendee asks: “Is my place confirmed? Should I come to Room Alder at 13:00? Can I watch a recording later, and is parking available?”
• [F7] Prepare a draft reply of no more than 100 words, then a separate source map and question for the desk. Do not send it, make a reservation or invent contact details.

You can complete this on paper or in a local document. No external account, upload or purchase is needed.

Draft your answer before reading the correction. Optional: use only this fictional prompt in a tool your organization permits. Do not connect accounts, upload other files or send messages for this task.

Using only F1–F7 below, draft a reply of at most 100 words. Answer each attendee question. Distinguish doors opening from the session start, acknowledgment from confirmation, and missing information from a negative answer. Add a separate source map and one request for the event desk to clarify availability and parking. Do not claim anything was booked or sent.

Complete fictional facts:
- [F1] Fictional Cedar Ideas Exchange bulletin, version 2, issued October 12: the event is October 20 in Room Birch. Doors open at 13:30; the session runs 14:00–15:00. Version 2 replaces version 1 for this event.
- [F2] Archived version 1 named Room Alder and a 13:00 session start. Those room and session-time details are no longer current.
- [F3] The event desk reviews place requests and sends a separate confirmation if a place is allocated. A request acknowledgment is not a place confirmation.
- [F4] The attendee has received only a request acknowledgment. The source gives no current availability count. It does not establish that the event is full.
- [F5] The current bulletin says no recording will be provided. It contains no information about parking or step-free routes. The event desk is the contact for questions; no email address or response deadline is supplied.
- [F6] The attendee asks: “Is my place confirmed? Should I come to Room Alder at 13:00? Can I watch a recording later, and is parking available?”
- [F7] Prepare a draft reply of no more than 100 words, then a separate source map and question for the desk. Do not send it, make a reservation or invent contact details.

Authored flawed sample, not an actual provider response:

Your place is confirmed. Come to Room Alder at 13:00. A recording and free parking are guaranteed. Contact parking@cedar.example and expect a reply within an hour.

1. F1 explicitly supersedes the old room and start time in F2. Room Birch, doors at 13:30 and the 14:00–15:00 session are distinct facts; do not merge them into one arrival promise.

2. F3–F4 establish only acknowledgment. They do not prove a place, a rejection or a full event. Explain the confirmation step without promising its outcome.

3. F5 rules out a recording. Replace the sample’s recording promise with that supported negative answer.

4. Parking is not described in F5. “Not supplied” is different from “unavailable” and from “free.” The invented address and response deadline have no source.

5. The draft can refer to the event desk by its supplied name. Keep the separate question for that desk as a draft; writing it has not contacted anyone.

One supported correction:

Your request acknowledgment does not confirm a place; the event desk sends separate confirmation if a place is allocated. The current bulletin lists October 20 in Room Birch, with doors opening at 13:30 and the session running 14:00–15:00. The old Room Alder and 13:00 session details have been replaced. No recording will be provided. Parking information is not supplied; please ask the event desk. We cannot confirm availability from this bulletin.

Source map: room, date and times: F1–F2; request status: F3–F4; recording, missing parking and contact role: F5.

Separate draft question for the event desk: Can you confirm whether a place has been allocated for this acknowledged request and provide the event’s parking information? No message or reservation has been sent (F7).

Check your answer:

• The attendee reply is at most 100 words before the separate source map.
• October 20, Room Birch, 13:30 doors and 14:00–15:00 session match the current bulletin.
• The acknowledgment is not treated as confirmation, rejection or proof that the event is full.
• No recording is promised; parking is unknown, not declared free or unavailable.
• No contact address, response time, booking or sent message is invented.

Different wording can satisfy these checks. Recheck the facts after any rewrite.

For real authorized communications, record which bulletin version supports each fact and ask the event owner to resolve conflicts. A supplied URL is not proof an assistant opened it. Use an approved process for attendee questions, particularly access requirements, and do not upload attendee names, requests or contact lists for this practice. The desk’s missing accessibility information cannot be replaced by “fully accessible” language.

Primary guidance checked on 2026-10-12. The references support source checking, privacy boundaries and clear presentation; the event facts and sample answers are invented. W3C event guidance informs access questions; these exercises are not event safety, legal compliance or accessibility approval.

• Generative Artificial Intelligence Profile
• Use Clear and Understandable Content
• Making Events Accessible

Keep real work within your organization’s approved data and review process. These exercises do not establish tested accessibility, time savings, job competence or a professional qualification. No provider trial or human professional review is claimed.

Start free Module 1: account sign-in is required; no card is needed. Or read general AI learning guidance. Keep your practice answer in your own local document if you want to return to it; this page does not save it to your account.