Multi-Site Mouse Colony Management Guide

Multi-site mouse colony management gets messy fast. One campus tracks cages in a spreadsheet, another relies on memory, and the PI only sees the gaps when a shipment is late or a genotype report is inconsistent. If your colony spans multiple rooms, buildings, or institutions, the problem is not just distance. It is a lack of shared process.

This guide walks through a practical way to manage a mouse colony across multiple sites without losing visibility. You will see what to standardize, what to track locally, and where teams usually make mistakes.

Why Multi-Site Colonies Break Down

A single-site colony already has moving parts: matings, litters, weans, genotypes, transfers, protocol limits, and cage capacity. Add a second site and you introduce new failure points:

different naming conventions for animals, cages, and rooms
inconsistent genotype entry between teams
transfer requests handled in email or chat instead of a shared system
delays in updating deaths, weans, or breeders removed from use
reporting that does not line up across institutions or vivaria

A common example is a lab with a breeding colony in one facility and experimental cohorts in another. Site A records a litter as weaned on Tuesday. Site B still expects those animals to be available on Monday because nobody updated the transfer date. That small mismatch can disrupt genotyping, surgeries, and study timelines.

Start With One Shared Colony Structure

Before you worry about dashboards or exports, make sure every site is using the same basic structure.

Standardize IDs and Naming

Your team should agree on:

how cages are named
how animals are identified
how rooms, racks, and sites are labeled
how strains and genotypes are written

For example, if one site records a genotype as Cre+/- and another uses Cre heterozygous, your filters and exports will split the same animals into different groups. Standard naming matters more in multi-site colonies because you cannot rely on hallway conversations to correct mistakes.

Define Site-Level Ownership

Every cage or workflow should have a clear owner. That does not mean one person does all the work. It means someone is responsible for confirming that the record is current.

A simple model is:

site manager owns transfers in and out
colony manager owns breeding records
study lead owns cohort assignment and sample collection

When ownership is unclear, record quality degrades first at the handoff points.

Track Transfers as Operational Events

Transfers are where multi-site colonies most often drift out of sync.

If you are still handling transfers in email threads, you probably have at least one of these problems:

a cage marked as moved at the destination but not the origin
animals assigned to a study before arrival
transport dates missing from audit trails
health-status or quarantine notes lost during the move

Treat transfers as first-class records, not side notes.

What to Record for Every Transfer

For each move, capture:

origin site and destination site
transfer date
animals or cages included
reason for transfer
receiving owner
status such as planned, in transit, received, or canceled
any quarantine or health notes

A practical mouse colony example: Site A sends six Cx3cr1-CreER; Rosa26-tdTomato mice to Site B for tamoxifen induction. If the transfer record only says "sent to B," you still do not know whether the receiving team confirmed arrival, whether all six animals arrived, or whether they were ready to schedule dosing.

Keep Breeding Central, Let Execution Be Local

Multi-site teams often fail in one of two ways. Either every site manages breeding differently, or one site tries to micromanage every action across the network.

A better pattern is to centralize breeding strategy and decentralize routine execution.

Centralize the Decisions That Affect Colony Supply

Keep these visible across all sites:

active breeder pairs and trios
planned expansion or contraction of lines
expected litter timing
genotype yield trends
retirement decisions for breeders

These decisions affect the whole colony, so they need one shared source of truth.

Let Sites Execute Day-to-Day Tasks

Each site can still handle:

cage checks
local husbandry timing
room-specific logistics
site-specific scheduling constraints

That balance prevents duplicate planning while respecting local realities.

Build Reports Around Site Questions

Multi-site reporting should answer operational questions, not just dump tables.

Useful reports include:

animals currently housed at each site
breeders by line and location
upcoming weans by site this week
transfer backlog or animals in transit
genotype pending counts by location
study cohorts reserved at each facility

The important part is consistency. If one site exports weekly numbers from a spreadsheet and another exports from a live system, leadership loses confidence in the totals. A shared reporting workflow avoids debates about whose sheet is correct.

Common Mistakes in Multi-Site Colony Management

Duplicating the Same Animal in Multiple Systems

This usually happens when a destination site creates a new local record instead of receiving the original animal record through a transfer workflow. Later, the lab has two versions of the same mouse with different statuses.

Updating the Move but Not the Context

A cage may be marked transferred, but the study assignment, rack location, or ownership field is still tied to the old site. The result is confusion during audits and missed task reminders.

Ignoring Time Lag

Not every site updates data at the same hour. Build your process around explicit status changes instead of assumptions. "Planned" and "received" are not the same thing.

Mixing Policy With Convenience

Some teams create informal shortcuts for one site because "everyone there knows the system." Those shortcuts usually become your biggest reporting problem later.

A Simple Rollout Plan for Your Lab

If your multi-site workflow is currently ad hoc, do not try to fix everything in one week.

Week 1: Standardize the Core Fields

Align naming for sites, rooms, genotypes, and owners.

Week 2: Clean Up Transfer Workflow

Make every move require an origin, destination, date, and receiving confirmation.

Week 3: Review Breeding Visibility

Confirm that all sites can see breeder status, expected litters, and planned cohort demand.

Week 4: Audit One Real Transfer Path

Pick a common workflow, such as moving weaned mice from breeding to experimental housing, and check every handoff for missing data.

What Good Looks Like

A healthy multi-site colony does not mean every site works the same way minute to minute. It means your team can answer basic questions without chasing people down:

Where is this mouse now?
Who is responsible for it?
Was the transfer completed?
Is the genotype confirmed?
Is this cohort ready for the next study step?

If those answers are easy to find, your colony is scalable. If not, growth will keep exposing the same gaps.

Final Takeaway

Multi-site colony management is really a coordination problem disguised as a data problem. The labs that stay organized are not necessarily doing more work. They are making handoffs visible.

If your team is managing mice across multiple locations, start by standardizing structure, then make transfers explicit, then build reporting around site-level decisions. That is what keeps your breeding colony, study cohorts, and compliance records aligned as the colony grows.