Skip to content

AI uses for records

Enough seats, wrong access: what an event operations constraint dataset needs

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

An event operations constraint dataset must record accessibility requirements separately from capacity, because a room can seat every registrant and still fail them. Each case needs the plan as decided, the venue's access facts, the requirements coded per session as provided, not provided or not recorded, the disposition with its conditions, and the event-day outcome. Of 1,574 conferences in a public calendar for 2024-2026, only 5.0 percent recorded sign language or captions.

Checklist

Enough seats, wrong access

This page covers enough seats, wrong access: what an event operations constraint dataset needs.Illustrative

Key takeaways

  • Capacity and accessibility fail independently: a 400-seat hall can fit 350 registrants and still lack the wheelchair spaces nine of them need.
  • Access minimums rise in steps while seating grows smoothly, so the share of seats built for access falls from 5.0 percent at 40 seats to 1.0 percent at 800.
  • Five dispositions cover the decision: approve, approve with conditions, substitute, request information and escalate.
  • Code every requirement as provided, not provided or not recorded; a public calendar recorded sign language or captions for 5.0 percent of 2024-2026 conferences and never as false.
  • Keep the disposition and the event-day outcome in separate fields, and treat accommodation requests as health data under privacy review.

What decision does an event operations constraint dataset capture?

It captures the planner's feasibility call: given an event plan and the access requirements documented for it, can the plan run as written, and if not, what should happen next? The answer is rarely a plain yes or no. Many plans that fail on access can be fixed with conditions, moved to another room, or held while someone asks the attendee a better question.

At a glance

What decision does an event operations constraint dataset capture

Capacity and accessibility fail independently, which is what makes the decision hard to automate. A plenary hall can seat 400 people for 350 registrants and still be short of wheelchair spaces, listening receivers or a step-free route to the stage. A model trained only on headcounts, room blocks and floor plans will approve that plan every time, because nothing in those fields can say no.

The data that teaches the decision is the plan as it stood when the call was made, the requirements known at that moment, the disposition chosen and what happened on the day. This guide defines each part, uses U.S. design minimums as the worked rule set, and labels a six-case casebook by script. The five dispositions used throughout:

  • Approve: the plan meets every documented requirement and the applicable minimums as written.
  • Approve with conditions: named fixes, each with an owner and a deadline, close every gap before the event, such as converting removable seats into wheelchair spaces or renting receivers.
  • Substitute: a gap cannot be fixed in place, so the session or event moves to a room or venue that closes it.
  • Request information: a requirement is recorded too vaguely to act on, so the planner asks the attendee, speaker or venue before deciding.
  • Escalate: the fix is beyond the planner's authority, or declining it would need a legal judgment such as whether a cost is an undue burden.

Why a room with enough seats can still fail its attendees

Because access minimums rise in steps while seating grows smoothly, the share of a room built for access shrinks as the room grows, and a plan sized only to headcount misses the gap. The 2010 ADA Standards, as the U.S. Access Board reproduces them, set the minimum number of wheelchair spaces in assembly areas in Table 221.2.1.1: one for 4 to 25 seats, two for 26 to 50, four for 51 to 150, five for 151 to 300 and six for 301 to 500, then six plus one for each 150 seats or fraction between 501 and 5,000.

Each required wheelchair space needs at least one companion seat under 221.3. Assistive listening follows Table 219.3: two receivers for 50 or fewer seats, then two plus one per 25 seats over 50, or fraction thereof, up to 500 seats, then 20 plus one per 33 seats over 500, or fraction thereof, up to 1,000. At least two receivers must be hearing-aid compatible, and from 201 seats one in four, or fraction thereof, unless an induction loop serves every seat, in which case the compatible receivers are not required. Where a circulation path links seating to a performance area, 206.2.6 calls for an accessible route that connects them directly.

Two cautions keep the table honest. These are design minimums for assembly areas, and whether and how they bind a given venue or event is a legal question for counsel. And a minimum is a floor, not a forecast: if nine registrants declare wheelchair use in a hall built with six spaces, the table is met and the plan still fails. The casebook below therefore treats the need as the larger of the table minimum and the declared count, an editorial planning rule.

The minimums for five room sizes, computed by the casebook script:

Why a room with enough seats can still fail its attendees
SeatsWheelchair spaces (221.2.1.1)Companion seats (221.3)Receivers, hearing-aid compatible (219.3)Spaces as share of seats
40222, both compatible5.0%
150446, 2 compatible2.7%
2505510, 3 compatible2.0%
4006616, 4 compatible1.5%
8008830, 8 compatible1.0%

Where an event's access requirements are written down

They are written down in several places that often share no identifier. The event industry's standard handoff document, the Events Industry Council's APEX Event Specifications Guide, has a narrative with an attendee profile that includes an accessibility and special needs field, a housing section with a field for accessibility-equipped guest rooms, and a function set-up order whose Section H is titled Accessibility. The template carries a 2004 to 2005 copyright, so a buyer should ask which version a supplier's records follow.

Communication access is booked separately. The Justice Department's ADA Title III rule, 28 CFR 36.303, names qualified interpreters on site or by video remote interpreting, notetakers, real-time computer-aided transcription, assistive listening systems and captioning among its examples of auxiliary aids. It says a public accommodation should consult the person and makes the final choice of aid, provided communication is effective, and it excuses an aid only where providing it would fundamentally alter what is offered or impose an undue burden.

Venue choice sets most of what follows. The ADA National Network's planning guide for temporary events says site choice may have the greatest overall impact on accessibility to an event, and advises making accessibility a primary factor when more than one site is available. The records that hold each requirement:

Where an event's access requirements are written down
RecordWhat it holdsDecision it informsCommon gap
Registration answersDeclared needs per attendee and sessionWheelchair spaces, receivers, interpreters neededA yes or no box with no detail
Speaker and performer ridersStage access, presentation format, interpreter placementStage route and set-upCollected after rooms are assigned
Venue specification sheet and floor planFixed and removable seating, wheelchair locations, loops, stage heightsWhether a gap is fixable in placeCapacity listed, access features not
Event specifications and set-up ordersAccessibility instructions per functionWhat the venue was asked to deliverSection left blank or copied forward
Audio-visual and interpreter ordersReceivers, captioning, interpreters bookedConditions actually metOrder placed but not confirmed
Event-day log and feedbackAccess issues reported, fixes made on siteThe outcome labelIssues resolved by phone, never logged

What a public calendar of 1,574 conferences records about access

Public event listings record where and when almost always, and access almost never. We counted the open dataset behind the confs.tech conference calendar, a crowd-sourced list of technical conferences on GitHub, at commit 8d411d2 dated October 16, 2026. Its schema accepts 17 fields, none for capacity, venue, seating or step-free access, and one true-or-false flag, offersSignLanguageOrCC, for sign language or closed captions.

Of 1,574 conferences starting between January 1, 2024 and December 31, 2026, 78 (5.0 percent) carry the flag, every one of them as true; 992 (63.0 percent) link a code of conduct. Among the 1,349 with a city, the in-person and hybrid events, 65 (4.8 percent) are flagged. Even among the 20 conferences filed under the calendar's accessibility topic, 4 carry it. No listing in the window records the flag as false: the 123 conferences recorded as false all started from 2020 to 2023.

That is the pattern a planner's own archive tends to repeat. When an access field exists only to record a yes, silence means unknown, not no, and a model trained to read silence as absence will learn that most events offered nothing. Code each requirement as provided, not provided or not recorded, and keep the third value.

Method: bin/xs0821_conference_access_count.py (W09-main-016 scratch folder) reads only the JSON files under conferences/, decoded as UTF-8 with any byte-order mark removed. Each object is a listing; start dates must parse as real dates (none failed). Listings collapse into events by URL (trimmed, lower-cased, trailing slashes removed), start date and city (trimmed, lower-cased, empty when missing), so a conference filed under several topics counts once; 6,991 listings became 6,107 events. The flag counts as true if any listing of the event has true, and as false if none has true and at least one has false. A code of conduct link is a non-empty cocUrl in any listing; an accessibility-topic event has at least one listing in a file named accessibility.json. An event with no city is online only; one with a city and online set to true in any listing is hybrid; otherwise in person. Each share is computed from whole counts and rounded a single time, half up. Not measured: whether flagged events delivered the service, and anything about capacity, which the schema does not hold. The counts by format:

What a public calendar of 1,574 conferences records about access
Format (2024-2026 starts)EventsFlagged sign language or captionsRecorded as falseCode of conduct link
In person1,00843 (4.3%)0626 (62.1%)
Hybrid34122 (6.5%)0206 (60.4%)
Online only22513 (5.8%)0160 (71.1%)
All formats1,57478 (5.0%)0992 (63.0%)

The disposition label and the outcome that follows the event

Each case carries the planner's disposition, judged against the plan and requirements known on the decision date, and a separate outcome read from what happened at the event. A condition that was promised and never delivered turns a correct disposition into a failed outcome, so the two must not share a field.

Outcome labels come from the event-day log, the audio-visual and interpreter confirmations, attendee feedback and any complaint, and the window should run past the event long enough for feedback to arrive. Requirements that surface on the day, such as an attendee who never registered a need, belong in the record as new requirements with their own timestamp, not as evidence that the original call was wrong.

Five outcome values cover most cases: delivered as planned; delivered after an on-site fix; failed, with the access issue reported; plan changed before the event for an unrelated reason; and unknown, where no event-day record exists. Unknown stays in the set as unknown. Dropping it keeps only the events whose staff wrote things down, which may not be typical of the rest.

Casebook: six plans and the call each one supports

The casebook gives each disposition a case and pairs it with the tempting wrong call. All six plans are illustrative, written for this guide, and describe no real event, venue or attendee.

Method: bin/xs0821_feasibility_casebook.py applies the minimums above and a fixed rule order, first match wins. A declared need recorded without enough detail to act on goes to Request information; a communication-access request whose refusal would need an undue-burden review goes to Escalate; a plan with no gaps is Approve; a plan whose every gap can be fixed before the event is Approve with conditions; a plan with a gap that cannot be fixed in place goes to Substitute when another room closes it, and to Escalate otherwise. Wheelchair spaces needed are the larger of the table minimum and the declared count, and a stage used by a presenter who declared a step-free need is a gap that counts as fixable only if the venue confirms a ramp that fits. The script uses receiver rows only up to 1,000 seats and no randomness.

The six plans and their labels:

Casebook: six plans and the call each one supports
Plan (illustrative)Decisive factsLabelHard negativeWhat decides it
A. Breakout, 150 loose chairs4 wheelchair spaces planned, 1 declared; 6 receivers, 2 compatibleApproveAdd conditions out of habitEvery minimum and declared need met
B. Plenary, 400 fixed seats, 350 registered6 spaces listed, 9 wheelchair users declared; removable seats allow 4 more spacesApprove with conditionsApprove because 6 meets the tableAdd 3 spaces, each with a companion seat
C. Same plenary with a hearing loopLoop serves every seat; 16 receivers, only 1 compatible; 3 wheelchair users declaredApproveFlag a compatible-receiver shortfallLoop exception in 219.3
D. Panel room, stepped stagePanelist needs step-free access; venue says no ramp fits; level room freeSubstituteApprove because seating passesStage route cannot be fixed in place
E. Five vague registration answersAccessibility needs answered yes, no detail, three weeks outRequest informationAssume no specific needRequirement not actionable as recorded
F. Interpreters for every sessionRequest for sign language interpreters across three days; budget owner objectsEscalateDecline for cost at planner levelRefusal needs an undue-burden review
Scorecard for illustrative plan B: 400 seats for 350 registrants passes, a code minimum of 6 wheelchair spaces with 6 listed passes, 9 declared wheelchair users is flagged as a gap, removable seats allowing 4 more spaces passes, and 16 receivers needed with 16 held passes, leading to the label approve with conditions: add 3 spaces and 3 companion seats.
Illustrative plan B from this guide's casebook; minimums from the 2010 ADA Standards as reproduced by the U.S. Access Board.

Hard negatives that mark the boundary

Hard negatives are cases where the obvious reading of the record gives the wrong call, and a set without them teaches a model to pattern-match on headcounts. Six families recur in event plans:

  • Minimum met, need unmet: the room satisfies Table 221.2.1.1 but declared wheelchair users outnumber its spaces, as in case B.
  • Shortfall that is not one: a hearing loop covering every seat removes the compatible-receiver requirement, as in case C.
  • Seating passes, stage fails: every seat-based check is green while a presenter cannot reach the stage, as in case D.
  • Silence read as no: a registration field that only records yes, like the public flag counted above, is read as a list of attendees with no needs.
  • Over-provision as safety: booking interpreters or rewiring a room for every vague answer looks careful but spends budget on guesses and still leaves the actual need unknown.
  • Cost as a planner's veto: declining an auxiliary aid because it is expensive skips the undue-burden judgment the federal rule reserves for that refusal.

Specialist review checklist for each plan

Every case needs adjudication by someone who has run accessible events or reviews venues for access, because fixability and the meaning of a vague request are judgment calls. The checklist is what that reviewer signs before a case is labeled in full, narrowed, or excluded:

At a glance

Specialist review checklist for each plan

Checklist · 9 items

  1. Decision-time cut: requirements and venue facts dated after the disposition are excluded from the packet.
  2. Room facts: seat counts, wheelchair locations, removable seating, loops and stage heights come from the venue's specification or a site visit, not from the planner's notes.
  3. Minimums: recomputed from the room's seat count and the edition of the standard named in the record.
  4. Declared needs: counted per session, with each need coded as provided, not provided or not recorded.
  5. Fixability: each condition names the resource, the owner, the deadline and the confirmation that closed it.
  6. Communication access: interpreter, captioning and listening requests are linked to the bookings that met them, or flagged as unmet.
  7. Outcome: set from event-day records and feedback within a fixed window; cases without records are labeled unknown.
  8. Agreement: a second reviewer relabels a sample from the packet alone, and agreement is reported.
  9. Privacy: names, contact details and the wording of individual requests are removed; only counts and coded needs remain.

0 of 9 ticked. Tick each item as you go.

What a planner's records can and cannot show

A planner's archive can teach how plans fail on access and how coordinators fix them; it cannot show that a model is safe to approve plans without a person. A sector label settles neither the rights to license these records nor their fitness for decisions that affect people's ability to attend, and five limits follow:

  • Health data: an accommodation request can reveal a disability, and under Article 9(1) of the EU's General Data Protection Regulation data concerning health is a special category whose processing is prohibited unless an Article 9(2) exception applies; U.S. and other laws add their own rules, so privacy counsel reviews any use.
  • One rule set: the worked minimums are U.S. design standards; other countries, older buildings and outdoor or temporary sites follow other rules, and whether any standard binds a given event is a legal question.
  • Recorded needs only: the archive holds requirements someone wrote down, and the public listing count shows how often that does not happen.
  • Several parties' records: venues own their floor plans and specification sheets, vendors their orders and attendees their requests, so the planner may not be free to license all of them.
  • Bounded use: the set supports drafting conditions, flagging gaps and checking plans for a reviewer, not automated approval or refusal of an accommodation.

Requesting event plans with their access records

Ask for event packets, not attendee lists: the plan as decided, the venue facts, the coded requirements per session, the disposition with its conditions, the bookings that met them and the event-day outcome, joined by an event and function identifier. State the event types and years wanted, how unrecorded requirements are coded, and the share of cases that must carry an outcome.

SourceX finds data like this on request from businesses that hold it, rather than keeping a catalog in stock, and a buyer's request names the scope, volume, language, format, timing and license the use needs. Add the intended use and an acceptance test, for example: every case codes each requirement as provided, not provided or not recorded, every condition links to a confirmation, and no packet contains a personal name. The supplying company approves the scope and terms and signs before records move, and nothing here implies that such records are available or that a given set will pass.

Frequently asked questions

How many wheelchair spaces does a 400-seat room need?

Under Table 221.2.1.1 of the 2010 ADA Standards, an assembly area with 301 to 500 seats needs at least six wheelchair spaces, each with a companion seat. That is a design minimum; if more registrants declare wheelchair use, the plan needs more spaces regardless of the table.

What counts as an auxiliary aid for an event?

The Justice Department's rule at 28 CFR 36.303 lists examples including qualified interpreters on site or by video remote interpreting, notetakers, real-time computer-aided transcription, assistive listening systems and captioning. The organization should consult the person and choose an aid that makes communication effective.

Why code accessibility needs as not recorded instead of no?

Because many records only capture a yes. In the public confs.tech conference data, no 2024-2026 listing recorded the sign language or captions flag as false, so a missing value cannot be read as a service not offered or a need not present.

Can an AI model approve an event plan for accessibility?

It can compute minimums, flag gaps, draft conditions and check that bookings match requests for a planner to review. Refusing an accommodation or judging an undue burden involves legal and human judgment, so a qualified person should decide.

Are accessibility requests personal data?

Usually yes, and often health data, since a request can reveal a disability. Under the EU's GDPR, data concerning health is a special category, so a dataset should keep coded needs and counts and remove names and the wording of individual requests.

Sources

  • The U.S. Access Board's reproduction of the 2010 ADA Standards, Chapter 2: Table 221.2.1.1 wheelchair spaces by seat count; 221.3 one companion seat per required space; Table 219.3 assistive listening receivers and hearing-aid-compatible share, with the induction loop exception; 206.2.6 accessible route between seating and performance areas. Source
  • 28 CFR 36.303 lists auxiliary aids including qualified interpreters on site or by video remote interpreting, notetakers, real-time computer-aided transcription, assistive listening systems and captioning; the public accommodation should consult the individual and makes the final choice if communication is effective; fundamental alteration and undue burden limit the duty. Source
  • The ADA National Network's planning guide for temporary events says site choice may have the greatest overall impact on an event's accessibility and advises making accessibility a primary factor when several sites are available. Source
  • The APEX Event Specifications Guide template is the industry's standard format for event requirements, with an accessibility and special needs field in the attendee profile, a housing field for accessibility-equipped rooms and a function set-up order section titled Accessibility; the template dates from 2004-2005. Source
  • The confs.tech conference dataset at commit 8d411d2 (October 16, 2026): 1,574 conferences starting 2024-2026 after collapsing topic duplicates; 78 (5.0 percent) flagged for sign language or captions, none recorded as false; 992 (63.0 percent) with a code of conduct link; 4 of 20 accessibility-topic conferences flagged; 123 conferences recorded as false, all 2020-2023 starts. Source
  • The conference dataset's list of valid fields has 17 entries, including the offersSignLanguageOrCC flag and none for capacity, venue, seating or step-free access. Source
  • Article 9(1) of the GDPR prohibits processing data concerning health, a special category, unless an exception in Article 9(2) applies. Source

Tell us what data you need

Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.

See if your company qualifies