What are the best methods for providing accommodations during a whole-class assessment in 2027

A concrete scenario that frames the problem

Picture a 240-person revenue org running its quarterly product-knowledge assessment. Sales, customer success, and solutions engineering all sit the same 90-minute exam in the same window, because the enablement team wants a clean cohort comparison before the next territory planning cycle. Roughly nine percent of the cohort — a normal share for a workforce this size — has a documented accommodation on file with HR.

The needs are not interchangeable. One rep with a documented processing disorder needs time-and-a-half. Two others need text-to-speech for the dense reading-comprehension items in the pricing module. A CS manager who dictates everything needs speech-to-text for the three open-response scenarios. A solutions engineer with a migraine condition needs a separate room away from the open-plan floor and permission to pause. Two remote employees need to sit the exam at home rather than commute to a hub office they normally never visit.

Here is where it breaks. The enablement lead schedules the assessment in the LMS on a Monday. The accommodation flags live in the HRIS, in a field that was never mapped to the LMS user record — nobody built that mapping because accommodations were historically handled by a manager walking someone to a quiet conference room. So the LMS sees 240 identical learners. Time limits render identically for everyone. The rep who needs 135 minutes gets 90 and runs out mid-section, and because the platform auto-submits on timeout, there is no recoverable state.

Meanwhile the proctoring layer creates a second, independent failure. Remote proctoring tools watch for screen readers, secondary audio streams, and clipboard activity, because those are also cheating signals. A screen reader reading questions aloud looks, to a naive rules engine, exactly like a candidate reading questions to an off-camera helper. Two of the text-to-speech users get flagged. One session gets terminated automatically. The employee now has a suspected-integrity note attached to a record that exists only because the organization failed to configure the tool it had already approved.

The third failure is quieter and shows up weeks later. Scores get rolled into a competency dashboard. Nobody tagged which sittings were accommodated and which were not, so the accommodated scores — some depressed by the missing supports, one voided entirely — sit next to standard scores in the same distribution. A manager reading that dashboard draws performance conclusions from data that measures configuration failure, not knowledge.

Every one of those failures is operational rather than clinical. Nobody disputed a diagnosis. Nobody refused a request. The accommodations were approved and then simply did not arrive, which is the most common way accommodation programs fail inside a business.

How the mechanism actually works

The delivery path has four layers, and accommodations get lost at the seams between them rather than inside any one of them.

Layer one is the record of decision. An employee requests, HR runs an interactive process, and an outcome is recorded: what functional limitation exists, what support addresses it, and what the effective dates are. This record should be stored as structured codes, not free text in a case note. "EXT_TIME_1.5X" and "TTS_ALLOWED" can be transmitted; "extra time as needed per Dr. note" cannot.

Layer two is translation. Every assessment platform expresses accommodations in its own vocabulary — time multipliers, exception rules, override groups, proctor profiles. Something has to map the HR code to that vocabulary. In small organizations, that something is a person with a checklist. Above roughly 500 employees or two assessments a quarter, a person with a checklist starts missing cases, and teams move to a middleware layer that reads approved accommodations and writes platform configuration.

Layer three is application and confirmation. This is the layer teams skip. Writing a configuration is not the same as the configuration taking effect: exception groups can be overwritten when a course is republished, time multipliers can be dropped when an assessment is cloned from a template, and a user provisioned after the sync runs inherits nothing. The fix is a read-back check. After writing, query the platform for the learner's effective settings and compare them to the intended state. Only mark the accommodation active when the read-back matches.

Layer four is the proctoring and integrity stack, which sits outside the LMS and needs its own configuration. Approved assistive tools have to be allowlisted per employee, and the allowlist has to persist across assessments rather than resetting per event.

Two design details matter more than they look. First, the confirmation to the employee should go out before test day, not on it — an employee who can see "150 minutes, screen reader permitted, separate room booked" 48 hours ahead can flag an error while it is still fixable. Second, the loop closes back to the record of decision, because effectiveness data is what justifies changing an accommodation next quarter.

Real numbers, ranges, and benchmarks

Cost is the first thing leadership asks about and usually the least interesting constraint. The Job Accommodation Network's long-running employer survey work has consistently found that a majority of accommodations cost employers nothing, and that those with a cost tend to be one-time purchases rather than recurring expenses. That pattern holds for assessments specifically: extended time, a quiet room, a paused timer, and a flexible submission format all cost zero in software. What costs money is proctor coverage — a separate-room sitting consumes staff hours that a group sitting does not — and per-seat licenses for commercial assistive software where the organization has not already standardized on the accessibility features built into its operating systems and browsers.

That last point is worth acting on. Windows, macOS, iOS, and Android all ship screen readers, dictation, and magnification at no incremental cost, and modern browsers expose reading and zoom controls natively. Before buying licenses, check what employees already have. Many "we can't afford accommodations" conversations dissolve once someone inventories the built-in stack.

Timing benchmarks are where planning actually lives. Set your calendar backward from test day:

• Request intake to decision: allow two to four weeks when medical documentation is involved, because the bottleneck is usually the employee's provider, not your process. Publish this expectation so employees request early.
• Decision to platform configuration: target under five business days. This is entirely inside your control and is the step most worth automating.
• Configuration freeze: lock the accommodation roster 48 to 72 hours before the assessment opens, then run reconciliation against it. Late additions get a make-up sitting rather than a rushed config change.
• Proctor vendor allowlist submission: at least five business days out, because vendors route these through support queues rather than self-service consoles.
• Dry run: one full practice sitting with a test account per distinct accommodation profile, no later than 72 hours out.

On volume: plan capacity as though somewhere in the range of five to ten percent of a general workforce cohort will have an active accommodation on file, and expect that number to climb as an organization normalizes requesting. A cohort of 240 therefore needs planning for roughly a dozen to two dozen accommodated sittings, not one or two. Extended time is consistently the most-requested category, with assistive reading technology and separate settings behind it — which means your scheduling model, not your software budget, is the real constraint.

Extended time multipliers cluster at 1.5x and 2.0x. A 90-minute assessment at 1.5x runs 135 minutes; at 2.0x, 180. That has knock-on effects nobody models: room bookings, proctor shifts, and the fact that a three-hour sitting needs a documented break policy or you have created a new accessibility problem while solving an old one.

Error rate is the benchmark that should drive investment. Track it explicitly as accommodated sittings delivered correctly divided by accommodated sittings scheduled. Manual, spreadsheet-driven programs reliably miss cases; automated, read-back-verified pipelines reliably do not. Any nonzero miss rate is a legal and morale problem well before it is a data problem, so measure it, publish it internally, and treat a single miss as an incident with a written cause.

Trade-offs and alternatives

The core tension is between individualization and comparability. The more the sitting experience varies across a cohort, the weaker the claim that a single score distribution measures one thing. Ignoring that is intellectually dishonest; overreacting to it is worse, because it becomes an argument for withholding supports.

The honest resolution is to be precise about what the assessment is for. If it is a knowledge check that gates certification — pass or fail against a fixed standard — then accommodations do not threaten validity at all. Extended time on a knowledge check removes a speed constraint that was never part of the construct being measured. If, instead, the assessment feeds a stack-rank or a comp decision, you have a much harder problem, and the correct answer is usually that a timed multiple-choice test should not have been feeding that decision in the first place. Fix the decision process rather than the accommodation policy.

Universal design for assessment is the strongest structural alternative. Instead of building a narrow default and bolting on exceptions, build the default wide: generous time for everyone, optional read-aloud and dictation available to all, plain-language item writing, no unnecessary color-dependent or timed-animation content, and a choice of setting. The upside is real — fewer exception configurations to get wrong, no disclosure required to get a usable experience, and a better test for everyone, since most people do better on an assessment that measures knowledge rather than reading speed under stress.

The limits are equally real. Universal design widens the floor; it does not eliminate the ceiling. An employee who needs a scribe, a specific screen-reader configuration, or a medically necessary pause still needs an individual arrangement. And a permanently generous time window has scheduling costs and can dilute a genuine speed component when speed is legitimately part of the job being tested.

Most mature programs land on a hybrid: universal design for structure and item writing, individual accommodations for anything universal design cannot reach. That framing also changes procurement — you start evaluating platforms on whether accommodation settings survive cloning and republishing, whether they expose a read-back API, and whether their proctoring partner supports persistent per-user tool allowlists.

There is an adjacent workflow worth borrowing from: hiring assessments. Pre-employment testing teams have had to solve the same problem under sharper legal scrutiny, and their standard practice — publish the accommodation request path on the invitation itself, before the candidate opts in — transfers directly. Putting "need an accommodation for this assessment? request here, by this date" in the enrollment email surfaces needs from employees who never filed a formal HR request because their day-to-day job did not require one. Reading-heavy assessments surface needs that a normal workday never does.

Common pitfalls and how to avoid them

The silo. Accommodation approved in HR, invisible to the LMS. Prevent it with the read-back check described above, plus a manual reconciliation against the frozen roster before every whole-class administration. Do not let the HR record show "active" on the strength of an API call returning 200 — a write succeeding is not the same as a setting being in effect.

Proctoring false positives. Assistive technology and cheating share surface signals. Submit the tool list to the vendor in writing at least a week out, get per-employee allowlisting confirmed rather than blanket "we'll review flags after," and — critically — instruct proctors that a flagged accommodated session is escalated for human review, never auto-terminated. Run at least one proctored practice sitting per assistive tool.

Extended time as the universal answer. It is the easiest lever, so it becomes the default response to every request, including requests where it helps not at all. More time does not make dense text readable to someone who needs it read aloud. Require every approved accommodation to name the functional limitation it addresses, and audit the roster for suspicious uniformity — if ninety percent of your accommodations are time extensions, your intake process is collapsing distinct needs into one lever.

Settings that do not survive the section boundary. Multi-section assessments frequently apply a time multiplier to section one and drop it thereafter, especially when sections were built at different times or cloned from a template. Same failure appears when an assessment is duplicated for a new quarter and the exception group does not come along. Test with a dummy account that carries every accommodation profile, and walk it through every section to the end.

Republish wipes config. Related but distinct: editing and republishing an assessment after configuration can silently reset overrides. Freeze content edits at the same moment you freeze the accommodation roster, and re-run the read-back check after any post-freeze edit.

No make-up path. Something will fail on the day — a room double-booked, a license not provisioned, a home internet outage during a remote sitting. Decide the make-up policy in advance and publish it, so the employee's recourse is a scheduled second sitting rather than an appeal.

Untagged results. Accommodated scores flow into dashboards with no marker. Tag the result record at write time, and be explicit internally about how accommodated results are interpreted — for a pass-fail certification, identically to everyone else's, which is the whole point.

No effectiveness review. Nobody asks the employee whether the accommodation worked. Send a short survey to accommodated participants within a week, ask two questions — did you receive everything approved, and did it do what you needed — and feed answers back into the record of decision. This is also your best early warning for silent delivery failures the reconciliation missed.

Privacy leakage. Separate rooms, visible tool badges, and public roster spreadsheets disclose medical information by inference. Keep the roster access-restricted, avoid announcing who is testing where, and prefer arrangements that do not visually single people out.

Related questions

Do accommodations have to be re-approved for every assessment?

No. Approve the accommodation once against a documented functional limitation, with effective dates, then apply it to every eligible assessment automatically. Re-approval per event creates delay and pressures employees to re-disclose repeatedly, which is exactly the friction that suppresses requests.

How do you handle a request that arrives the day before the test?

Approve what can be delivered safely and schedule a make-up sitting for anything requiring configuration or proctor changes. Rushing a config change past the freeze is how other people's settings get broken. Publish the deadline in advance so late requests are rare.

Should managers see who received accommodations?

Generally no. Managers need scores and completion status, not accommodation details, which are confidential medical-adjacent information. Access to the accommodation roster should be limited to HR and the specific administrators configuring the platform.

Does universal design remove the need for an accommodation process?

No. It shrinks demand by making the default experience workable for more people, but individualized needs — scribes, specific assistive configurations, medical pauses — still require a formal process. Treat universal design as a way to reduce exception volume, not eliminate it.

What if the assessment platform simply cannot apply an accommodation?

Deliver it outside the platform — an offline sitting with a human proctor, a printed or alternate-format version, or a different assessment modality entirely — and record the result manually. Platform limitations are not a reason to deny a reasonable accommodation, and they belong on your next procurement checklist.

FAQ

What are the best methods for providing accommodations during a whole-class assessment?

Design the assessment wide by default, sync approved accommodations from the HR record into the platform automatically, verify the configuration with a read-back before the sitting opens, allowlist assistive tools with the proctoring vendor a week out, run a dry run per accommodation profile, and survey participants afterward.

How much should we budget for assessment accommodations?

Less than expected on software, more than expected on time. Most accommodations carry no direct cost, and operating-system-native screen readers and dictation cover many needs. Budget instead for proctor hours for separate sittings, room capacity for longer windows, and the engineering time to build and maintain the HR-to-platform sync.

Which accommodation is requested most often?

Extended time, consistently. Assistive reading technology and separate or low-distraction settings follow. Plan capacity around that distribution, but do not let it become the intake default — an accommodation should be matched to a stated functional limitation, not chosen for administrative convenience.

Can employees take an accommodated assessment from home?

Yes, provided remote proctoring is configured not to conflict with assistive tools and the employee has adequate connectivity and a workable space. Home sittings often are the accommodation for employees who need a low-distraction environment. Verify tool compatibility with a proctored practice session first.

How do we score accommodated sittings fairly against the rest of the cohort?

For pass-fail certification against a fixed standard, score them identically — the accommodation removed an irrelevant barrier, not the standard. If scores feed ranking or compensation, the harder question is whether a timed test should drive that decision at all; add performance evidence rather than adjusting individual scores.

What legal framework applies in the United States?

The Americans with Disabilities Act requires covered employers to provide reasonable accommodation absent undue hardship, and EEOC guidance describes the interactive process employers must engage in. Comparable duties exist under the UK Equality Act, Canadian human rights legislation, and equivalent frameworks elsewhere — check the jurisdictions your cohort spans.

Sources

• https://askjan.org/topics/costs.cfm
• https://www.eeoc.gov/laws/guidance/enforcement-guidance-reasonable-accommodation-and-undue-hardship-under-ada
• https://www.ada.gov/topics/reasonable-accommodations/
• https://www.access-board.gov/
• https://www.w3.org/WAI/standards-guidelines/wcag/
• https://www.dol.gov/agencies/odep
• https://www.shrm.org/topics-tools/topics/disability
• https://www.intestcom.org/

Related on PULSE

• [How do you structure a math block to include direct instruction, guided practice, and independent work](/knowledge/tr19)
• [What are the best tools for tracking student behavior data without a complicated system in 2027](/knowledge/tr18)
• [How do you design a unit plan that naturally incorporates spiral review](/knowledge/tr17)
• [What are the most effective ways to communicate with non-English speaking parents in 2027](/knowledge/tr16)