Creative work · SINGAPORE
Singapore arts producers: confirm access arrangements before publishing audience information
Connect each production-specific support claim to the person who can confirm it, the segment it covers and the audience message that remains valid when plans change.
By Boardzip · Published · Updated
Boardzip uses AI-assisted guide research, writing and review. Read how we research guides and check sources →
Start with these checks
- A production-planning or practitioner session can examine a support coordination example
- Relevant venue, production or service responsibilities can be discussed explicitly
- Participants can separate confirmed arrangements from proposed ones
The problem
You are preparing audience information for a Singapore arts production, but a venue’s general accessibility page has been copied into publicity before anyone confirms which arrangements apply to the actual performance.
Name the arrangement and the part of the event it covers
Start with the exact audience-support statement you intend to publish. Separate the performance, introduction, interval and any post-show discussion when their arrangements differ. “Accessible event” is too broad to tell a colleague what needs confirmation. A seating position, an assistive listening system, captions and sign interpretation answer different needs. Record the actual request or planned provision without deciding what a person needs from an assumed profile. You are coordinating the production’s information, not assessing individual suitability or certifying access. Ask which part of the audience journey the statement addresses and what remains outside its confirmed scope.
Keep venue context separate from the production decision
Esplanade’s accessibility page says production requirements can affect the availability of its accessible seating arrangements. That is a specific venue example of why a general facility description cannot settle a particular performance. It does not establish your production’s layout, remaining places or booking terms. Put the venue reference under context, then obtain the applicable confirmation through the actual production and venue route. Record the event, room, performance or session and arrangement the reply concerns. A venue address or a previous show’s information is insufficient if the current layout or programme differs. Do not copy a service into publicity merely because the building describes it.
- Esplanade accessibility information ↗ · Source checked
Build a confirmation-to-message register
Use eight columns: support arrangement; event segment and location; person or role able to confirm it; question still unresolved; confirmation and its scope; approved audience wording; publication owner and channel; change that requires rechecking. For a seating enquiry, the unresolved question may concern the arrangement in the current layout and the route an audience member must use to enquire. Leave the wording provisional while that answer is missing. Keep the confirmation in the team’s approved working location and refer to its date or version. Use the register as the team’s working note, alongside the actual venue process. Store only the information the team is authorised to use; the register does not require audience members’ private personal records.
Agree which role confirms and which role communicates
Identify responsibilities with the people actually involved. A venue contact may confirm venue arrangements for a layout; a production contact may confirm the programme segment; a service provider may confirm what it has agreed to deliver. Those responsibilities must be agreed for the particular work rather than inferred from job titles. Name who resolves a mismatch and who approves the audience statement before publication. The person editing the webpage may be able to change wording while unable to confirm the arrangement behind it. Give that editor the approved scope and the route for a question, instead of asking them to turn an incomplete conversation into a promise. A peer at a planning session can help expose a missing role without taking that role for your team.
Compare three fictional states of the same publicity line
This example is invented. A draft show page says wheelchair seating is available because a venue brochure describes it. State A has only that brochure: mark the performance arrangement unconfirmed and obtain the show-specific answer before publishing the claim. State B has a reply for the named show and layout identifying the applicable arrangement and enquiry route: ask the responsible team to approve wording limited to that confirmation, without promising remaining capacity it did not establish. State C has a later layout change: recheck the affected arrangement and audience statement before treating the earlier reply as still applicable. The brochure, confirmed scope and changed plan lead to different actions; none is a real Singapore booking or an instruction issued by Esplanade.
Check the boundary between the performance and discussion
In another fictional planning question, support is confirmed for the main performance but a post-show conversation has been added. The missing answer is whether that added segment is included, where it happens and how the audience learns its conditions. Do not extend the earlier statement to spontaneous speech or another room without confirmation. Ask the roles responsible for the added segment and the support arrangement to settle that scope. Ask which languages, sightlines and event segments the arrangement covers, then record the responsible team action and approved audience wording. If the segment remains unresolved, keep that limit visible in the approved information rather than using one broad label for the whole evening.
Recheck the statement when the confirmed plan changes
Record a recheck trigger that affects the actual statement: altered room or seating layout; changed programme segment; changed service arrangement; or a revised booking or enquiry route. When one occurs, identify the affected entry and ask the responsible role what remains valid. Use the team’s agreed communication process to update relevant audience channels and respond to people affected; this guide does not prescribe a universal notification rule. Keep the earlier scope and the revised confirmation understandable to colleagues. A changed webpage is evidence of a wording edit, not of a changed support arrangement. Conversely, a confirmed arrangement hidden in a team message does not show that the published audience information has been corrected.
Bring the unresolved coordination question to a suitable session
Prepare an authorised or fictional extract with the planned statement, the confirmation it has, the gap and the role whose answer is needed. A useful peer question is: “This confirmation covers the main performance; who needs to settle the added discussion before our editor can describe it?” Ask whether the arts-production session permits this kind of working example. Seek a process question, not a private audience case or a claim that the room can approve your event. Use Boardzip’s free event search for practitioner planning and audience communication formats, then confirm actual participation and sharing conditions. If no verified working session fits, follow the production’s existing coordination route. Event attendance cannot supply a missing venue or service confirmation.
Questions and answers
Can I use the venue’s accessibility page as our show’s access statement?
Use it as context and verify the arrangements for the actual production. Esplanade specifically notes that production requirements can affect accessible seating. The statement you publish should identify only the scope the responsible team has confirmed.
Does the publicity editor need to decide whether the arrangement is suitable?
Give the editor approved information and the enquiry route. Identify the actual role that can confirm or resolve the arrangement instead of assuming the person who writes the page can approve it. Keep individual suitability and any specialist assessment outside a peer publicity exercise.
What if support is confirmed for only one segment?
State the confirmed segment accurately and resolve the other segment through its responsible roles. Do not extend performance support to an introduction or post-show discussion without an applicable answer.
Must the coordination register contain personal audience details?
The template concerns arrangements, confirmation scope, roles and published wording. Use the team’s approved process for any individual request; a public peer session does not need identifying or private personal information.
What if the layout changes after we receive confirmation?
Use that change to recheck the affected entry, ask what remains valid and update the audience information through the agreed process. Retain both the original scope and later answer so the team can see which statement applies.
Does a completed register prove the production is fully accessible?
It records what was confirmed, what was communicated and what remains unresolved. It is not an access audit, certification or guarantee that every need is met. Use the actual arrangements and the appropriate enquiry or specialist route for questions beyond that record.
Sources and further reading
These references provide the guide’s source context and further reading. They do not confirm a current event, admission or an available place; check each listing’s organiser terms for those conditions.
- Esplanade accessibility information ↗Source checked
Each date belongs to the linked source check. These references provide source context; a recorded date does not by itself establish a completed independent review. Current event admission is checked separately in each listing. How to read the source dates →
Current listings to check
Topic matches from the verified Singapore feed. A matching topic does not confirm audience suitability, accessibility or available places; read the organiser’s terms.
No current verified listings match this guide’s search terms. Try a broader search or suggest an organiser we should check.
Browse the broader event category →Suggest a relevant organiser →