At William & Mary, a Banner registration crash was severe enough that the university split students into “Green” and “Gold” groups with staggered 15-minute registration windows just to keep the system standing. Students called the experience the Hunger Games, telling the student newspaper Flat Hat News that a 15-minute window “feels like basically 15 seconds to go through and get the courses that you want.” The episode became part of the case for eventually replacing Banner’s registration workflow with a new system. Nothing about that failure required registration week specifically. A quiet Tuesday in February would have absorbed the same underlying defect without a single student noticing.
That is the uncomfortable fact at the center of Banner maintenance planning. The defect does not get worse during registration week. The audience does.
The Math That Changes for One Week a Year
Banner Student runs the rest of the year at a manageable pace: a few hundred concurrent sessions, staff correcting a record here, an advisor pulling a transcript there. Registration week changes both variables that determine how visible a failure becomes. Transaction volume spikes as thousands of students hit the same tables in the same few hours. Attention spikes at the same moment, because students, parents, advisors, and faculty are all watching the same system succeed or fail in real time.
A configuration change that causes a two-second delay on a form nobody uses in March becomes, in the first hour of registration, a queue of frozen sessions and a hallway of angry advisors. The system did not get more fragile. The room got more crowded and better lit.
Registration outages are common enough that they barely register as news anymore. Columbia University’s own systems went down during spring course registration in November 2025, an incident covered directly by the Columbia Spectator. That system is not Banner, but the pattern holds across platforms and institutions: registration week is the one week a year when even a minor stability gap becomes a campus-wide story.
A Patch Calendar That Doesn’t Know Your Academic Calendar
Ellucian ships Banner updates on its own schedule, not on any single institution’s registration calendar. The University of Toledo’s IT department documents the rhythm plainly: Ellucian releases updates four times a year, with periodic emergency bug fixes and regulatory releases layered in outside that normal cadence. Toledo’s own policy is to intentionally stay one release behind the newest version, specifically to avoid absorbing bugs from a release that hasn’t been proven elsewhere yet.
Miami University’s IT team documented a similar rhythm for the 2022 cycle: three major Banner releases, spaced roughly three months apart, in March, June, and September. Universities that hold to a real cadence, applying, testing, and verifying each release on a fixed schedule, know exactly where their environment stands relative to Ellucian’s own calendar at any given moment.
The risk shows up when that discipline slips. A patch queued for “next sprint” or “when things calm down” has no relationship to the academic calendar unless someone builds that relationship deliberately. Left alone, a skipped or delayed patch drifts until it collides with whatever is happening on campus that week, and there is a real chance that week is registration week, because registration week comes twice a year and idle patch queues tend to grow steadily in between.
Customization Turns a Routine Patch Into an Unknown
Ellucian’s patch itself is tested against a standard Banner install. Most institutions are not running a standard Banner install. EDUCAUSE’s 2023 ECAR research on ERP implementation in higher education describes campus ERP environments broadly as misaligned, overly customized, and costly to maintain, and found that nearly half of surveyed institutions had recently upgraded their ERP or were planning to within five years. Years of local customization, workarounds built by a functional analyst who has since retired, and integrations nobody fully documented all sit between a vendor’s tested patch and what actually happens when that patch runs in production.
That gap is exactly why a patch that passed Ellucian’s own testing can still misfire against a specific institution’s configuration. Under normal load, that kind of conflict shows up as a support ticket and a workaround. Under registration load, it shows up as a system-wide outage with the registrar’s office fielding calls and the CIO explaining to the provost’s office why students can’t add a class.
What Banner Support Services Should Guarantee Before Registration Opens
A patch cadence and a pre-registration environment check are not the same thing, and both need to happen on a fixed schedule, not whenever there’s time. This is the standard a Banner support arrangement should be held to, not as a favor before a big week, but as a baseline. A working readiness checklist covers four areas.
Patch verification. Confirm which Ellucian patches have actually been applied against which are still pending, and test the pending ones in a staging environment that mirrors production, including local customizations, not a clean vanilla install. Verify this at least two weeks before registration opens, not the day before.
Load and capacity check. Run a load test that simulates the actual concurrent session count expected at the specific hour registration opens, not an average day’s traffic. Check database connection pool limits, application server thresholds, and network capacity against that peak, not against typical usage.
A tested rollback plan. Document exactly how to reverse the most recent patch or configuration change, name who is authorized to execute that rollback, and confirm how long it actually takes. A rollback plan that has never been rehearsed is a hope, not a plan.
A defined escalation path and communication plan for registration week specifically. Name an owner for the application layer, the database layer, and the network layer, with an on-call schedule that covers the exact registration window, not a general help desk queue. Pre-draft status page language and agree in advance on the threshold that triggers a notice to the registrar’s office and to campus communications, so that decision isn’t made live while the system is down.
Discipline, Not Adrenaline
None of this requires more heroics during registration week. It requires less of them, because the work happens earlier and on a schedule that doesn’t depend on anyone’s memory or availability that particular week. This is the discipline STG runs for Banner clients as a standing part of managed services coverage: patch cadence tracked against Ellucian’s own release calendar, environment checks scheduled ahead of both registration periods every year, and an escalation path that exists on paper before anyone needs to use it. It is diagnostic work done in a quiet month so that a loud week stays quiet too.
If your team hasn’t walked through a version-by-version patch audit or a load test against this fall’s registration numbers, the window to do that is now, months before the semester opens, not the week students start logging in. STG will run a short pre-registration environment review with your Banner team, patch status, capacity headroom, rollback readiness, and escalation coverage, and hand over a written punch list either way, no obligation attached.
Sources
- University of Toledo Information Technology, “Banner 9 Updates”: https://www.utoledo.edu/it/banner9/updates.html
- Miami University, “Ellucian Announces Banner 2022 Release Schedule”: https://sites.miamioh.edu/banner9/2021/11/ellucian-announces-banner-2022-release-schedule/
- Flat Hat News (William & Mary student newspaper), “Campus prepares for new PATH registration system replacing Banner 9”: https://flathatnews.com/2024/03/05/campus-braces-for-new-path-registration-system-replacing-banner-9/
- EDUCAUSE, “More than ‘Going Live’: Achieving Institutional Transformation through ERP Implementation” (2023 ECAR research): https://www.educause.edu/ecar/research-publications/2023/more-than-going-live-achieving-institutional-transformation-through-erp-implementation/introduction-and-key-findings
- Columbia Spectator, “University sites experience outage amid spring course registration”: https://www.columbiaspectator.com/news/2025/11/18/university-sites-experience-outage-amid-spring-course-registration/
