.png)
Summarize with:
In an animal research facility, conditions shift by the hour—and precision is just as critical to compliance as it is to ethical obligations. Every cage represents living animal(s) under an approved protocol, and every recorded change- an arrival, transfer, the study endpoint- carries both compliance and financial implications.
That dual weight is what makes vivarium operations difficult to manage well. Facility census, protocol-authorized and in-use animal numbers, and billing data are distinct figures that must reconcile. Disconnected systems cause administrative friction and weaken an institution's ability to demonstrate oversight during an inspection, defend cost recovery decisions, and act on accurate numbers when it matters. Creating a single source of truth brings operational advantages: stronger oversight with less reconciliation effort, and cost recovery that stands up to scrutiny rather than requiring after-the-fact justification.
Vivarium management software is the category built to close that gap. It centralizes census, cage assignments, procurement, and billing so that facility staff, veterinarians, and compliance teams use the same current data, rather than reconciling separate records against each other before an audit or invoicing cycle.
Key Solutions delivers four capabilities as one unified animal research platform, designed to help institutions conduct research in a compliant manner. Rather than standalone products, its four modules work together : eProtocol Institutional Animal Care and Use Committee (IACUC) for protocol review and oversight, Lab Animal Resource Software (LARS) for animal resource and facility operations, Lab Animal Health Software (LAHS) for animal health records, and IACUC-PAM for post-approval monitoring.
This guide explains what the vivarium management category covers, the features and criteria worth evaluating, and how the platform addresses them.
What Is Vivarium Management Software?
Vivarium management software replaces the manual processes that facilities historically used to track colonies, cages, and daily operations. Instead of a facility manager checking a paper cage card against a separate billing spreadsheet, the software centralizes that data.
Coverage varies by vendor, but the category generally spans a few core functions:
- Census and colony tracking : real-time animal counts by cage, room, species, and protocol
- Cage management : assigning, moving, maintaining a healthy environment (cleaning, changing bedding, environmental management- temperature and humidity control, etc.), retiring cages, and capacity planning
- Husbandry and health documentation : veterinary care, treatments, and incident records
- Procurement and requisitioning : ordering animals and tracking delivery
- Billing and per diem calculation : charging responsible parties for animal care costs
- Regulatory reporting : audit-ready documentation and reporting that supports U.S. Department of Agriculture (USDA), and AAALAC International site visit reviews, built from the same operational data used day to day rather than compiled separately for each body.
Because the modules share data, workflows, and a common interface, an approved protocol limit set in eProtocol IACUC is immediately visible to facility staff in LARS. A health flag documented in LAHS is visible wherever that animal appears next, and financial reconciliation runs against the same records used for day-to-day operations. The platform also integrates with institutional financial systems and laboratory information management system (LIMS), so data doesn't stop at the edge of the animal research suite.
Each team, whether facility staff or veterinary staff, works in an interface built around its own workflow. That is an important consideration for institutions evaluating animal facility management software.
Why Vivarium Operations Are Hard to Manage Manually
A mid-sized facility can house animals across dozens of rooms under hundreds of active protocols. Every cage generates activity: animals arrive, get weaned, transfer between protocols, undergo regular cage maintenance, or reach a study endpoint.
Each of those events needs to show up in at least three places. It needs to match the facility's physical records, the Institutional Animal Care and Use Committee (IACUC) protocol's approved animal count, and the billing system charging per diem for that cage.
When census, protocol animal-use, and billing records are maintained separately, discrepancies can emerge. An order, birth, transfer between protocols, or disposition recorded in one system but not another can leave the institution without a reliable view of its current census or remaining approved animal allocation.
A vacated cage may continue to generate per diem charges if the vacancy is not recorded promptly. During an audit, inspection, or accreditation review, facility, compliance, and finance teams may then produce different figures because each is working from a different record.
This operational reality is the reason why institutions need dedicated research animal facility software, without having to rely on multiple spreadsheets or disconnected systems to consolidate every record/change.
Core Vivarium Software Features to Evaluate
A good starting point for decision-makers is to identify the outcomes their institution is accountable for, and then assess which capabilities are best suited to support those priorities.
Compliance
Compliance risk increases wherever facility data and protocol data diverge. A platform supports compliance when census figures update as transactions happen and stay tied to approved protocol numbers in real time, rather than requiring a manual cross-check against a separate spreadsheet.
Audit trail depth matters here as much as accuracy. Every transaction, an arrival, a transfer, a disposition, should be independently traceable, so a U.S. Department of Agriculture (USDA) inspection, an Office of Laboratory Animal Welfare (OLAW) assurance review, or an AAALAC International site visit can be answered from the system directly rather than reconstructed after the fact.
Animal Welfare
Welfare oversight depends on facility staff having current, cage-level visibility rather than a snapshot from the last physical count. Real-time occupancy data supports decisions on room assignments, cage density, and environmental conditions, cleaning schedules, bedding changes, and temperature & humidity control.
Cage-level identification also matters for welfare, not just administration. Barcode-enabled cage cards, supported by RFID tags and readers (where appropriate), can reduce transcription and identification errors, such as misread cage numbers or outdated records following a transfer, that may otherwise result in animals being associated with incorrect records or protocols.
Staff Efficiency
Every manual re-entry point is where staff time gets absorbed by administrative work instead of animal care or research support. A unified animal research platform reduces that burden when census updates happen automatically from transactions, cage identification happens by scan rather than by hand, and vendor communication lives inside the same system instead of a parallel email thread.
The cumulative effect matters more than any single feature. An institution should be evaluating how much reconciliation work a platform removes from facility, compliance, and billing staff collectively, not just how smoothly each function works in isolation.
Capacity
Space planning determines whether a facility can absorb a new protocol's projected animal numbers without a last-minute constraint.
Capacity tracking by room and species lets facility managers verify available space before approving a requisition, and forecast room assignments while planning, rather than discovering a shortfall after animals have already been ordered, or worse, after they arrive.
Research Continuity
Procurement delays and administrative bottlenecks are a direct threat to research timelines, not just an operational inconvenience. A complete requisition-to-receipt workflow- order creation, vendor submission, tracking, and receipt documentation- keeps animal supply moving perfectly with approved research activity instead of stalling behind manual coordination.
Vendor accounts and communication history must live inside the system of record, so institutional knowledge about supplier reliability and account status doesn't depend on any one staff member's inbox.
Cost Recovery
Billing accuracy is a defensibility question as much as an accounting one. Per diem and supply charges calculated directly from live census data, rather than a delayed or separately maintained figure, hold up to scrutiny from a PI questioning an invoice or an auditor reviewing cost allocation.
Beyond reconciliation, financial system integration should also work upstream of billing. Verifying that a funding account tied to the requisition is active before an order is placed prevents orders from being billed against an account that's expired or no longer valid.
Reliable Reporting
Regulatory reporting, including the annual U.S. Department of Agriculture (USDA) report and documentation supporting Office of Laboratory Animal Welfare (OLAW) assurance and AAALAC International site visits, carries less risk when it's generated directly from operational data rather than compiled manually ahead of a deadline. Every manual compilation step is a point where a number can be transcribed incorrectly, and that risk compounds across all reports an institution generates.
The evaluation question for decision-makers isn't whether a platform can generate a report. It's whether the report reflects the same data staff is already relying on day-to-day, so there's no gap between what's operationally true and what's regulatorily reported.
Connected Oversight: Compliance, Veterinary Care, and Inspection Readiness
Compliance, veterinary care, and monitoring aren't separate obligations; they're different views of the same underlying risk: can an institution demonstrate, at any point in time, that what's happening in its facility matches what was approved, documented, and disclosed?
An institution that can't answer that question immediately, without a fire drill of pulling records from three systems, has a governance problem regardless of how well any single function is run.
Compliance administration
Every animal in a facility is there under an approved Institutional Animal Care and Use Committee (IACUC) protocol with a specific numerical limit. When facility activity stays tied to that limit in real time, a requisition that would push a protocol over its approved count can be flagged before the order goes through, not caught after the fact during a review.
Veterinary coordination
Health status and facility status need to move together, not sit in separate records. When a veterinarian documents a health event, that flag should surface immediately on the facility side, showing the animal as temporarily unavailable for procedures until treatment is complete. Veterinarians should also be able to scan a cage card during rounds and see the animal's full medical history alongside protocol-specific details, expected clinical signs, and approved humane endpoints, without tracking down the PI first.
Record traceability
Every transaction, a requisition, a transfer, a health event, a protocol amendment, needs to be independently traceable back to its source. That traceability is what lets an institution answer a regulator's question with an existing record instead of reconstructing one under time pressure.
Animal welfare
The practical welfare payoff of this connectivity is direct: an animal flagged as under treatment can't be inadvertently pulled into an ongoing procedure before it's cleared. Humane endpoints and expected clinical signs stay visible to whoever is making a decision about the animal, irrespective of the system they're working in.
Inspection readiness
This is also where two distinct oversight mechanisms need to be told apart, since they're often conflated. Semiannual facility and program inspections are a mandated, twice-yearly review of the animal care and use program as a whole, required under Office of Laboratory Animal Welfare (OLAW) and U.S. Department of Agriculture (USDA) oversight.
IACUC-PAM is a separate, ongoing process. It monitors individual approved protocols throughout the year, not just at the semiannual review point, and it can be initiated on a routine schedule or triggered by a specific reported event or concern.
Higher-risk activity, survival surgery, U.S. Department of Agriculture (USDA) pain/distress Category D or E animals, controlled substances, or a lab with prior compliance findings, is typically prioritized for more frequent post-approval monitoring (PAM) attention. Findings are documented against standardized checklists tied directly to the approved protocol. So, a deviation is immediately traceable, and follow-up actions are tracked to closure rather than closed out informally.
post-approval monitoring (PAM) data doesn't exist in isolation from the semiannual cycle either. Trends identified through post-approval monitoring (PAM) inspections feed into the semiannual program evaluation, so recurring issues surface as a program-level pattern instead of staying scattered across individual protocol files.
Who Uses Vivarium Management Software
Vivarium software supports a wider set of institutional roles than the facility floor. Each one interacts with the system differently, makes different decisions with it, and is accountable for a different outcome, and how those roles overlap or divide responsibility varies by institution.
Facility managers and animal care technicians work in the system daily, verifying room-level occupancy before approving a requisition and reassigning cages as protocols shift. Their decisions are operational but consequential: approving a requisition that exceeds available space, or missing a vacated cage, creates a downstream problem for compliance and billing alike. Their outcome is a facility record that matches physical reality closely enough to withstand a walkthrough at any time, not just after a scheduled count.
Attending veterinarians and veterinary technicians document care through SOAP-based records during rounds, often scanning a cage card to pull up an animal's full medical history alongside protocol-specific details, expected clinical signs, and approved humane endpoints, without needing to track down the PI first. Their decisions center on clearing or holding an animal for a procedure based on current health status. They're responsible for care consistency and complete documentation that meets AAALAC International, Office of Laboratory Animal Welfare (OLAW), and U.S. Department of Agriculture (USDA) standards.
IACUC coordinators and compliance officers work across protocol review, post-approval monitoring (PAM) inspection scheduling, and the semiannual program evaluation, deciding when a deviation warrants escalation versus routine follow-up. They are accountable for answering whether current facility activity matches the approved decisions. Their outcome is a documentation trail that holds up under a post-approval monitoring inspection or an AAALAC International site visit without weeks of manual compilation beforehand.
Research administrators and billing staff reconcile per diem and supply charges against the institution's financial system, resolving discrepancies before they become disputes. Their decisions include whether a charge is defensible when a PI questions an invoice, and whether an account should be cleared for a new requisition. Their outcome is cost recovery that stands up to scrutiny, which depends on billing being calculated from the same data facility the staff works from, not a separate reconciliation exercise.
Principal investigators interact with the system indirectly, reviewing the animal counts and costs posted against their protocol and grant. Their decision point is usually a dispute or a confirmation, not a daily workflow. What they need from the system is confidence that what they're being charged and reported against reflects what's actually happening in the facility, since it's their protocol and their funding on the line.
Institutional leadership, Institutional Officials, Vice Presidents of Research, and similar roles, engage with this system at the program level rather than the transactional one. Their decisions center around platform investment, risk posture, and how the institution's compliance record is represented to funders and accrediting bodies. Their outcome is institutional credibility: audit-ready, transparent documentation strengthens funder and regulator relationships, while gaps in that record become a governance liability that reaches well beyond any single protocol.
IT and system administrators are usually consulted during platform selection and their requirements shape whether an implementation succeeds. Their decisions concern integration with existing financial, laboratory information management systems (LIMS), and identity systems, data security posture, encryption, role-based access controls, hosting environment, and the operational cost of migration and ongoing maintenance. Their outcome is a system that meets institutional security and compliance standards, SOC 2 or equivalent, without demanding a heavy, ongoing IT lift to keep it that way.
Responsibilities and system access across these roles aren't standardized; a smaller institution may have one person covering functions that a larger R1 splits across several offices. However, one thing remains constant: each role depends on the same underlying data being accurate and up-to-date.
Choosing Research Animal Facility Software: What to Evaluate
Institutions comparing platforms in this category should look past feature lists and ask a few direct operational questions.
Interoperability
Vivarium data needs to reach the institution's financial system, laboratory information management system (LIMS), and potentially IRB, IBC, or other compliance systems. An open architecture that integrates with what the institution already runs is worth more than a platform with siloed and disconnected systems that operate independently.
Data ownership
Institutions should know, in contractual terms, who owns the data once it's in the system, what happens to it if the vendor relationship ends, and how exportable it is. This matters more in a compliance context since the institution - not the vendor - is the one answering to Office of Laboratory Animal Welfare (OLAW) and U.S. Department of Agriculture (USDA).
Configurability
No two institutions run identical committee structures, approval chains, or reporting requirements. A platform that requires the institution to change its process to fit the software, rather than configuring workflows and forms to match existing governance, creates friction that compounds every time policy changes.
Traceability
Every action in the system- a requisition, a transfer, a health event, a protocol amendment- should be independently auditable back to its source and timestamp. This is what separates a system that supports an inspection from one that requires reconstructing a record under time pressure.
Security
Animal health and research data carry real sensitivity, and the platform's security posture, encryption standards, role-based access controls, and hosting environment should meet institutional IT policy. SOC 2 or equivalent certification, and alignment with frameworks like HIPAA or GDPR where relevant, is a reasonable baseline when considering vendors.
Deployment model
Vendors deliver software in different ways, and the model an institution can use often depends on its IT policy, security requirements, and data governance rules. Some institutions need a SaaS solution, where the vendor hosts and maintains the system. Others require a local deployment within their own infrastructure. Ask whether a vendor supports both, and how upgrades, backups, support, and integration work under each one. A platform offered in only one model limits what an institution can choose, and it can force a change to IT or governance policy that has nothing to do with the vendor's capabilities.
Migration
It is crucial to ask vendors specifically about how existing protocols, historical records, and compliance documentation move into the new system, and whether that migration preserves institutional knowledge or forces staff to rebuild records from scratch.
Implementation
A disruptive, all-at-once rollout is a real risk to ongoing research. Institutions should ask whether a vendor supports a phased implementation, starting with one program or workflow and expanding, versus a single hard cutover across the entire animal research operation.
Scalability
What works for a single-species, single-building vivarium may not hold up across multiple facilities, species, or a growing protocol volume. Ask how the platform performs under institutional growth, not just its current-state capacity.
Support
Post-implementation support, response time, escalation paths, and ongoing training determine how much of the platform's value the institution actually realizes versus how much sits unused. This is worth asking about directly, since it's rarely covered in a product demo.
Total cost
Licensing is only one line item. Implementation, migration, integration work, training, and ongoing support all factor into what the platform actually costs an institution over its lifecycle, and vendors should be able to account for each of those separately.
Measurable outcomes
The clearest way to evaluate a platform after implementation is against outcomes that matter to the institution: reduced reconciliation time, fewer billing disputes, faster inspection preparation, and audit findings that decline over time. Ask a vendor what those numbers have looked like for comparable institutions, not just what they claim on paper.
How Key Solutions' LARS Fits This Category
Key Solutions is an ISO 27001:2022 certified company that has spent more than 15 years focused on Life Sciences research, combining that expertise with AI and data analytics to improve research workflows and compliance.
Its platform is web-based, which describes how users access it. How an institution receives the solutions is a separate choice: Key Solutions delivers the platform as a SaaS solution or as a local deployment, so institutions can match the model to their own IT, security, and governance requirements. Within that platform, LARS is the module built specifically for vivarium facility administration.
LARS's scope, stated plainly, covers census tracking, cage management with barcode- and RFID-enabled cage cards, space and capacity tracking by room and species, procurement and requisitioning from order creation through receipt, billing and per diem calculation with financial system integration, and standard and ad hoc regulatory reporting.
LARS connects to eProtocol Institutional Animal Care and Use Committee (IACUC) so requisitions and cage counts stay aligned with approved protocol limits. It connects to LAHS so health-related events are reflected in facility census data without duplicate entry. Additionally, it supports IACUC-PAM inspections by keeping current facility data available for reviewers.
Together, these four modules function as one platform - a change made in any one of them, an approved protocol, a health event, a facility transaction, a post-approval monitoring (PAM) finding, is reflected everywhere else it's relevant, which is what allows facility staff, veterinary staff, and compliance staff to work in a system built around their role while still operating from the same underlying record.
Moving Forward
The institutions that get vivarium operations right treat census, compliance, and billing as one continuous thread rather than three separate jobs. That's not a technology preference. It reflects an operational requirement: an accurate, real-time answer to how many animals are where, under which protocol, and at what cost.
Getting there usually isn't about adding another tool. It's about removing the gaps between the tools already in use, so a transfer recorded in one place doesn't need to be re-entered somewhere else, and a number pulled for an inspection doesn't need to be reconciled first.
Key Solutions built a unified platform to implement that principle through daily operations. The result is a more manageable administrative environment, compliance maintained continuously rather than reconstructed under deadline pressure, welfare decisions informed by current and reliable data, and financial reporting that institutional leaders can trust and defend with confidence.
