Disability Services and Accommodations Software: Keep ClockWork or Accommodate, and Build Only the Scheduling Layer

When is off the shelf genuinely the right call here?

ClockWork is well established, Accessible Information Management is used widely and seriously, and Symplicity Accommodate integrates with a broader student services suite many institutions already own. The case management half of this category is genuinely well served, and you should not rebuild it lightly.

Buy, and stop reading here, if this describes you:

• Under roughly 2,500 students, with a testing room rather than a testing centre.
• A modest interpreting and captioning need, managed by one coordinator.
• A caseload that one person can hold, on one campus.
• Alternate format requests that arrive with enough lead time to be met.
• Finals week that fits without anyone drawing a grid on a whiteboard.

At that size a build is not a good use of institutional money, and the same budget spent on staff will do more for your students.

Two further points that hold at any size. If your complaint is that intake is clumsy or notes are hard to find, that is a configuration and training problem rather than a build. And if you are considering replacing your case record, know what that is: intake, documentation, determinations and interactive process history is roughly a doubling of a first release, plus a migration you do not need in year one.

When does a custom build actually pay off?

It pays off at the point where your testing centre stops being a room with a calendar and becomes a constrained resource pool.

Consider the Monday of finals week. Twenty two seats, four of them reduced distraction rooms, three proctors on shift, sixty one exams in the queue. Nineteen students have double time, so a three hour exam occupies a seat for six, and four need a reader or a scribe, which consumes a proctor entirely. Nobody in that room is careless. They are solving a capacity constrained problem in a spreadsheet that does not know a double time student consumes twice the seat hours, or that the reduced distraction rooms are the real bottleneck.

Build when two or more of these are true:

• Your testing centre exceeds roughly 3,000 proctored exams a year and finals week is scheduled by hand.
• You run multiple campuses with a shared interpreting or proctor pool.
• Alternate format production regularly misses course start dates.
• You have handled a complaint reaching the Office for Civil Rights and assembled the evidence by hand from email.
• Your current tool is not itself accessible to the students using it, which is a position no institution should be comfortable defending.

The evidence signal deserves its own note. In the disability services projects we have delivered, the recurring theme is an office doing careful, thoughtful work that cannot prove it, because the record of what was requested, what was decided, why, and what actually happened is spread across email, a case file and a whiteboard. Failure here is a legal matter and your documentation is the defence.

How do they compare on the things that matter in this industry?

Scheduling as optimisation. Booking software treats a room as a slot. A testing centre is a set of typed resources consumed for durations that depend on entitlement: standard seats, reduced distraction rooms, private rooms, workstations with licensed screen reading software, proctors, readers and scribes. Ask any supplier how they would schedule 300 exams across 22 seats and three proctors. If they describe a calendar, they will build a prettier version of your current problem. What you want is a model that reports which day is infeasible and by how much.

Notification against live enrolment. The common failure is not a system failure. The letter went out in week one, the student added a course in week three, and one instructor never received it. When that student is later denied extended time, the record shows a letter sent to the wrong list. Ask how notification stays correct when enrolment changes mid term. A start of term batch is the exact design that produces complaints.

Alternate format as a production queue. Commercial tools track a request. What the operation actually is, is a queue with capacity, lead times, dependencies on publishers responding and escalation. Ask whether the due date derives from the course start or from the request date, because only one of those tells you a job will miss.

Interpreting as a market, not a rota. Team assignments for long classes, skill matching for technical content, travel between campuses and a cancellation policy where a late cancellation still costs you the booking. This is one of the largest lines in a disability services budget and it is frequently run from a spreadsheet.

The interactive process record. Requests, determinations, denials with a reason from a defined set plus a narrative, alternatives offered, appeals and their outcomes. A denial with no recorded rationale is the worst artefact to bring to an investigation.

The accessibility of the tool itself. Ask what conformance level a supplier commits to and how they will test it. A developer who has not planned screen reader testing with real assistive technology users should not be building for this office.

What does total cost of ownership look like at your scale?

From Digital Heroes delivery experience, a focused first release runs $55,000 to $120,000 and ships in 12 to 16 weeks, covering intake and determination records with a structured interactive process, continuous per term faculty notification tied to live enrolment with acknowledgement, and capacity aware exam scheduling. Accessibility conformance is inside that number rather than added afterwards. A full platform runs $140,000 to $320,000 over 6 to 12 months, adding alternate format production queues with publisher request tracking, interpreter and captioning assignment with cost tracking, note taker management, assistive technology loans and multi campus operation.

A public university of roughly 22,000 students, one testing centre with 22 seats, four reduced distraction rooms, three proctors and about 4,500 proctored exams a year, keeping its existing case management product, priced its release one at $104,000 over about fifteen weeks: intake and interactive process history $18,000, capacity aware exam scheduling with a constraint solver $34,000, continuous faculty notification $16,000, student information system integration with reconciliation reporting $14,000, conformance across every screen including testing with assistive technology users $12,000, and the student booking portal with a consolidated faculty view $10,000. Phase two adds roughly $110,000 to $170,000 and brings the programme to around $240,000 across the year, with the interpreter and captioning module at $30,000 to $60,000 depending on pool size and campus travel constraints.

Annually, plan 15 to 25 percent of build value, so roughly $16,000 to $26,000 on a $104,000 release, covering hosting, support and a change budget. Two lines sit outside it. Accessibility retesting is recurring, because conformance is a state rather than an event. And if you keep your existing case management product, that renewal continues, which belongs in the comparison as a deliberate trade.

On the buy side, compare four figures from your own records: renewal plus consulting days, staff hours spent scheduling by hand in the fortnight before finals, interpreting spend lost to late cancellations never charged back, and complaint handling over the last three years. If you retain the case product, its renewal appears in both columns and cancels out.

What does the hybrid look like, and when is it the honest answer?

For most offices this is not a compromise, it is the recommendation. Keep the case record. Build the scheduling layer around it.

Intake, documentation storage, determinations and case notes work adequately in the products you already run, and reusing them removes an entire data migration from release one while keeping the build inside the lower half of the band. The integration between the two is a modest line rather than a major one.

What you build, at roughly $60,000 to $75,000 of the worked example, is three things:

• Capacity aware exam scheduling, $34,000. Typed resources, entitlement driven durations, hard constraints for entitlements and soft ones for preferences, and an honest infeasibility report rather than silent overbooking. It says no at booking time rather than on the morning, which is the difference between an inconvenience and a complaint.
• Continuous faculty notification, $16,000 plus integration. Any new enrolment for a student with active accommodations notifies the instructor of record within a day, per course elections respected, acknowledgement recorded with a timestamp, and one consolidated view per instructor rather than eight separate letters.
• Conformance across every screen, $12,000. Priced inside the sprint cycle rather than as a final audit, because deferred conformance becomes a remediation project.

Sequence interpreting second, once a full term has closed. It carries the largest budget exposure and frequently pays for a share of its own cost, because modelling interpreters as a resource pool with qualifications, availability, cost rate and a cancellation policy tends to reveal spend going to late cancellations that were never charged back.

Which should you choose, by operator size and stage?

Find your row and act on it.

• Under 2,500 students, testing room, one coordinator. Buy ClockWork, Accessible Information Management or Symplicity Accommodate. Spend the difference on staff.
• 2,500 to 8,000 students, testing centre under 3,000 exams a year. Still buy, but write down your testing centre rules now: what counts as an eligible exam window, how a private room is allocated when demand exceeds supply, what happens when an instructor uploads a paper late. That documentation is free and it is what makes any future build cheaper.
• Above 8,000 students with more than 3,000 proctored exams a year. This is the decision point. Keep the case product and build scheduling plus continuous notification, roughly $60,000 to $105,000 depending on how many resource types your centre carries.
• Multiple campuses with shared proctor or interpreting pools. Build, and treat multi campus as a second project rather than a percentage uplift, because campuses with genuinely different testing centre layouts behave that way.
• A live resolution agreement, or a tool your own students cannot use. Build, and start with the interactive process record and conformance rather than with scheduling. Those two are what an investigator asks about.

Two conditions apply. Go live at the start of a term, run the testing centre in parallel for a few weeks, and prove the scheduler against a midterm before relying on it. Never cut over into finals week. And spend three to four weeks of discovery writing down the rules that live in staff judgement, because that is where a project either gets a real constraint model or a calendar.

If you would rather someone argued with your brief than agreed with it, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.