Why it matters
Without this, prioritisation can misalign with conservation goals, miss up-to-date risk signals, and risk policy violations, leading to poor welfare outcomes, failed permits, and gaps in accreditation.
From design to safety
Design
AI guides collection scope
AI ingests Red List status, IUCN SSC guidance, SSP and EEP priorities, One Plan inputs, and species feasibility matrices to propose target species and subpopulations for assessment and transfer readiness.
- ZIMS Animal Records Database
- CITES Permit Archive
- Conservation Genetics Lab Freezer
- Quarantine Holding Area
Build
data pipelines for planning
Data pipelines unify kinship matrices, studbook health histories, population management metrics, and permit pre-approvals to generate an initial plan and risk score for introductions.
- Studbook File Cabinet
- CITES Permit Archive Room
- Quarantine Holding Area
- Conservation Genetics Lab Freezer
Operation
ongoing prioritisation checks
Continuous ingestion of Red List updates, permit changes, SSP/EEP shifts, and field programme outcomes to re-prioritise and reallocate space, funding, and genetic resources.
- ZIMS Animal Records Database
- Studbook File Cabinet
- Enrichment and Welfare Monitoring Station
- Quarantine Holding Area
Maintenance
records governance and refresh
Periodic audits of genetic diversity metrics, permit compliance, and population viability analyses to refresh prioritisation and support timely transfers.
- CITES Permit Archive Room
- Conservation Genetics Lab Freezer
- Breeding Population Register
- ZIMS Population Module
Safety
compliance and safeguards
Licensing, zoonoses prevention, and transfer protocols remain under oversight by the animal welfare committee and licensing inspector, with documented decision logs in registrar records.
- Quarantine Holding Area
- CITES Permit Archive Room
- Enrichment and Welfare Monitoring Station
- Breeding Population Register
Part by part
- 1
ZIMS Animal Records Database
- Watch for
- Data drift in field notes, missing entries, or inconsistent patient identifiers across modules.
- AI action
- Flag mismatched IDs and trigger data reconciliation workflow.
- 2
Studbook File Cabinet
- Watch for
- Outdated kinship values, missing transfer eligibility, or invalid generation numbers.
- AI action
- Flag invalid pedigrees for curator review and update transfer readiness score.
- 3
Conservation Genetics Lab Freezer
- Watch for
- Sample accession mismatches, degraded DNA, or missing genotype records.
- AI action
- Trigger re-sequencing queue and verify chain-of-custody in the system.
- 4
Quarantine Holding Area
- Watch for
- Unrecorded quarantine departures, incomplete health screening, or protocol deviations.
- AI action
- Activate risk flag and schedule veterinary review.
- 5
CITES Permit Archive Room
- Watch for
- Permits near expiry, missing specimen permits, or ineligible transfer documents.
- AI action
- Generate renewal alerts and pre-transfer compliance checklist.
- 6
Enrichment and Welfare Monitoring Station
- Watch for
- Enrichment plans not linked to species priorities, welfare indicator gaps, or inconsistent observation logs.
- AI action
- Recommend enrichment alignment to priority species and prompt welfare note updates.
Worked example
Catching a verification gap in a high-priority transfer
Illustrative scenario with sample data.
A planned transfer of a high-priority primate species requires up-to-date studbook data, genetic diversity metrics, and current permits to proceed.
Signal in
statusRedList: Vulnerable; iucnSignal: elevated; population: 12; kinship: moderate; permits: valid through 2027-12-31; zimsUpdated: 2026-10-01; quarantineFit: yes; transferWindow: 2027-03-01 to 2027-06-30
System out
alertRaised: speciesTransferReadyStatus = 'pending; requires kinship audit and permit revalidation'; owner: Conservation Manager; action: schedule kinship review and permit recheck; dueDate: 2026-11-15
Human sign-off: Conservation Manager reviews kinship and permit revalidation and signs off on continued transfer planning.
How to roll it out
Phase 1
Weeks 1 to 4
Baseline data alignment across ZIMS, studbooks, permits, and SSP/EEP priorities for initial prioritisation model.
Phase 2
Weeks 5 to 12
Prototype prioritisation run with simulated transfer scenarios; governance review and adjustment of thresholds.
Phase 3
Weeks 13 to 20
Operational deployment with live data feeds, alerting, and documented decision logs in the registrar records.
Where people stay in charge
- Only a qualified conservation scientist or registrar signs off on transfer prioritisation decisions affecting permits and species lists.
- All genetic and health data handling must be reviewed by the animal welfare committee, ensuring privacy and ethical compliance.
- Transfer decisions require explicit licensing inspector sign-off prior to any grant of permit or space allocation.
Questions owners and crews ask
What does AI-based species prioritisation consider for zoo collection planning?
AI integrates Red List status, IUCN SSC guidance, One Plan inputs, and SSP/EEP priorities to rank candidate species and determine transfer feasibility, space needs, and genetic considerations. It also tracks evolving permits and quarantine capacity to ensure compliant planning.
Who approves the prioritisation outputs before action?
A conservation scientist and registrar jointly review the outputs, then the zoo director signs off on final collection decisions and permit applications, with licensing body endorsement when required.
How are records kept and audited?
Records from ZIMS, studbooks, permits, and genetic data feed a central audit log reviewed quarterly by the animal welfare committee and licensing body, with tamper-evident logs and renewal tracking.
What datasets are required to start the program?
Red List, IUCN SSC guidance, SSP/EEP priorities, studbook data, permit records, and current quarantine capacity must be available and linked, plus population viability analyses and genetic diversity baselines.