© Copyright 2026 Mastersinlibraryscience.org.
A practical framework for MLIS grads to audit ILS performance, costs, and workflows before problems escalate.
Library systems age in ways that don't show up until someone asks the wrong question at a board meeting. A library technology health check is a structured review of your integrated library system's performance, costs, and alignment with current operational goals. It moves beyond "is the software running?" to ask whether the system still fits how staff work, how patrons search, and how the institution measures success.
MLIS graduates increasingly inherit systems selected five or ten years earlier, often by staff who have since moved on. A repeatable evaluation method, covering warning signs, operational symptoms, performance metrics, audit steps, vendor criteria, and budget realities, turns inherited uncertainty into documented decisions.
Some ILS reviews start with a budget crisis. The smarter ones start earlier, triggered by organizational shifts that have nothing to do with the software itself. School Library Journal's September 2026 piece "A Routine Check on the Health of Your ILS," written by longtime ILS vendor TLC, lays out three prompts worth watching for. None of them mean your system has failed. They mean it's time to look.
Leadership turnover is the most natural trigger.7 A new library director or department head arrives without inherited assumptions about why things work the way they do. That fresh perspective often surfaces questions nobody had asked in years: why a workflow requires seven clicks instead of two, or why a report takes an afternoon to compile. Use the transition, don't just survive it.
Many districts now write strategic plans around data-driven decision-making, operational efficiency, and staff sustainability. If your ILS can't produce the data leadership wants, or requires heroic manual effort to approximate it, that gap is a signal, not a footnote. A mismatch between stated goals and system capability tends to widen over time rather than resolve itself.7
Staff departures, whether retirement, resignation, or reassignment, often expose how much institutional knowledge was propping up the system. Watch for reports that only run correctly when one person handles them, training that consists entirely of shadowing a predecessor, and configuration settings nobody will touch for fear of breaking something. These are structural warning signs, not personnel problems.7
Treat all three as invitations to explore, not verdicts. The goal is an honest look at whether your ILS still matches how your library actually operates.
Signs point outward, toward leadership shifts and strategic plans. Symptoms point inward, toward the daily grind of running the system. TLC's September 2026 School Library Journal piece on ILS health checks draws the same distinction: an ILS can look fine on an org chart while quietly draining hours from every shift.
The first symptom is financial fatigue. Maintenance fees, support contracts, and staff time spent babysitting the system creep upward year after year, but the payoff doesn't keep pace. Libraries end up paying more for the same functionality they had five years ago, sometimes less, because vendor support has thinned out or add-on modules have become mandatory just to keep core features working.8
The second symptom shows up in the day-to-day mechanics of circulation, acquisitions, and cataloging. Manual steps get bolted onto automated processes. Exceptions to standard procedure exist only in someone's memory, never in writing. Staff develop private systems for handling the tasks the ILS won't handle cleanly.8 None of this shows up in a budget line, but it shows up in every shift.
The third symptom is the reporting bottleneck. Circulation counts, collection turnover, overdue summaries: these should be a few clicks away. Instead, staff spend hours exporting spreadsheets, cleaning data, and reconciling numbers by hand before a report is even usable.8
Any one of these three might be tolerable on its own. Together, they describe a system that has become a full-time management project rather than a tool. That's the practical takeaway from TLC's assessment: when cost, workflow friction, and reporting delay all show up at once, it's less a maintenance issue than a signal that the platform itself has fallen behind what the library actually needs to do.8
Before comparing vendor options or building a migration budget, you need a clear picture of how your current integrated library system is actually performing. The metrics below give you a structured starting point. Each one can be tracked with data you likely already have access to through vendor dashboards, server logs, or your service level agreement.
| Metric | What It Measures | Typical Benchmark or Target |
|---|---|---|
| System uptime percentage | The proportion of time the hosted ILS platform is available for staff and patron access over a defined period, calculated as uptime divided by total period (minus any SLA exclusions), times 100. | Leading cloud-hosted platforms report rolling 12-month uptime at 99.99% for production instances. If your vendor cannot document uptime at or near this level, that gap deserves a conversation. |
| Operating-hours reliability level | The percentage of the library's posted operating hours during which the automated system is fully functional, determined by subtracting downtime from total operating hours. | Contract specifications commonly call for 98% reliability during the first three years after installation and 97% from the beginning of the fourth year through the end of the fifth year. Performance below these thresholds may trigger financial penalties under your SLA. |
| OPAC search response time | How quickly the catalog returns results to patron queries, measured by grouping completed transaction log entries into defined response-time ranges (in seconds). | If log analysis shows nearly all transactions completing in 10 seconds or less, that range is generally treated as an acceptable baseline. Response times consistently above that window may signal communication or indexing problems worth investigating. |
| Z39.50 / Z-server response time | The speed at which Z-servers respond to broadcast search requests, evaluated alongside factors like network congestion and concurrent local OPAC usage. | Research indicates that most Z-servers respond rapidly under controlled test conditions, with network congestion and local catalog traffic not significantly degrading performance. Sluggish Z39.50 responses in your environment likely point to a configuration or infrastructure issue rather than an inherent protocol limitation. |
| Downtime percentage | The portion of total operating hours during which the ILS or key components are unavailable, calculated to the nearest one-tenth hour and expressed as a percentage of operating hours. | This metric is the inverse of reliability. Track it monthly and compare against contracted thresholds. Rising downtime percentages over successive quarters are one of the clearest signals that your system's infrastructure is aging or that vendor support is slipping. |
| Service-level compliance | The degree to which your vendor meets contracted reliability percentages, often tied to financial consequences such as withholding a portion of the monthly maintenance fee when reliability drops below agreed levels. | Compliance should be reviewed at least quarterly. If your agreement includes penalty clauses, verify that the vendor is self-reporting accurately and that you are exercising the remedies available to you when targets are missed. |
A structured audit turns gut feelings about your integrated library system into actionable data. Work through each step in order, assign an owner and a deadline for every item, and score each area on a 1–5 scale (5 = fully meets needs, 1 = critical gap). Any category that lands at a 2 or below should be flagged for deeper investigation and brought to leadership immediately.
Does your catalog actually work for a patron using a screen reader or navigating by keyboard alone? If nobody on staff can answer that with confidence, accessibility auditing belongs in the same audit cycle as your performance metrics, not a separate initiative tackled someday. A discovery layer that scores well on uptime but locks out patrons using assistive technology is not a healthy system.
In 2026, the practical floor for catalog and discovery-layer interfaces is WCAG 2.1 Level AA2, which the American Library Association points to as the baseline for library web content. Where feasible, WCAG 2.2 Level AA is the preferred target since it's the current W3C Recommendation and adds nine success criteria, including focus not obscured (2.4.11), target size (2.5.8), dragging movements (2.5.7), consistent help (3.2.6), redundant entry (3.3.7), and accessible authentication (3.3.8), while removing the older parsing criterion.3 WCAG 2.2 is backward compatible with 2.13, so moving toward it does not mean abandoning existing compliance work.
A usable accessibility pass does not require a specialist, just a deliberate walk through common patron tasks:
Catalog interfaces are covered under current federal accessibility rules for public entities, with compliance timelines that vary by the population a library serves.5 Beyond legal exposure, many state library grant programs now require documented accessibility compliance before releasing funding, which means an outdated catalog can quietly cost a library money it never realizes it's losing.6 Building this check into your regular ILS audit keeps accessibility from becoming its own crisis project later.
A system can technically function while still failing the people who rely on it every day: that gap between running and healthy is exactly what a technology audit is built to find.
Library systems migrations involve more than a new software license. When building a realistic budget, it helps to see how costs distribute across the major categories. The breakdown below reflects typical proportions reported by public and school library systems undertaking mid-sized ILS migrations.
ILS evaluation, vendor comparison, and technology auditing are not reserved for dedicated systems librarians. MLIS graduates in a range of roles can, and increasingly do, take on these responsibilities. The table below shows national median salaries for occupations where ILS assessment skills are directly applicable, drawn from the 2025 Occupational Employment and Wage Statistics published by the U.S. Bureau of Labor Statistics. If you are early in your career, volunteering for an ILS audit committee or requesting systems librarian duties within a generalist position can set your resume apart. Hiring managers notice candidates who can speak concretely about performance benchmarking, workflow analysis, and vendor support evaluation, and that experience often commands movement toward the upper quartile of these salary ranges.
| Occupation | National Employment | 25th Percentile Salary | Median Salary | 75th Percentile Salary |
|---|---|---|---|---|
| Librarians and Media Collections Specialists | 133,790 | $56,310 | $68,270 | $84,480 |
| Librarians, Curators, and Archivists (Broad Category) | 234,910 | $45,480 | $60,470 | $78,000 |
| Library Science Teachers, Postsecondary | 3,630 | $64,080 | $80,340 | $100,910 |
