The Paper Pedigree: A Sceptic's Guide to Reading UK Primate Studbooks

You are handed a spreadsheet. It has more columns than a train timetable, several animals share the same house name, and someone has written "assumed" next to a parent like a whispered disclaimer. Congratulations: you are looking at a studbook. It is one of the least glamorous documents in primate conservation, and one of the most useful.

First, what a studbook is not

A studbook is not a rescue intake log, a keeper's diary, or a biography. It is a breeding and population-management record. In the UK, studbooks sit inside a wider system: BIAZA collections, EAZA breeding programmes (EEPs and ESBs), and international studbooks for species that need global coordination. Much of the data now lives in Species360's ZIMS software, but the logic is old-fashioned ledger work. Each animal gets a studbook number. Each entry records sex, birth date, sire and dam, where the animal has lived, and when and where it died.

That is roughly it. No personality notes. No "likes grapes, dislikes the new keeper". If you want to know whether an animal is bold, anxious, or fond of dismantling enrichment, you need the keeper records, not the studbook.

The columns that actually matter

For a sceptical reader, four fields do most of the work. The studbook number is the anchor: ignore house names and follow the number. Sire and dam give you the pedigree. Location history shows transfers between collections. Date of birth and death let you check ages and generations without guessing.

Then come the calculated columns: mean kinship and inbreeding coefficients. These are where studbooks become genuinely powerful, and genuinely easy to misread. Mean kinship is a measure of how related an animal is to the rest of the managed population; lower is generally better for breeding recommendations. Inbreeding coefficients estimate how closely an animal's parents were related. Both are statistical models built on assumptions about the founders of the population. They are not moral verdicts on an animal, and they are not behaviour predictions.

Names are not the story

A surprising amount of studbook confusion comes from names. House names get reused across decades and collections. Two animals called Bella may have nothing to do with each other. A name might travel with an animal between zoos, or be changed on arrival. The studbook number does not.

This is why a transfer that looks dramatic on paper — an animal moved from Cornwall to Cheshire, say — is often just a breeding recommendation playing out. Population managers look at mean kinship, age structure, and space, then suggest moves. It can look like a soap opera if you read it as one. It is closer to a very slow game of chess, with paperwork.

Where the record runs thin

Studbooks are honest about uncertainty if you know where to look. Wild-caught founders are often assumed to be unrelated because nobody can prove otherwise. Parentage may be listed as assumed where observations were incomplete. Early records can be patchy, especially for animals that arrived before modern database habits. A blank cell is not a scandal; it is usually just a blank cell.

Genetics is the other place to tread carefully. A studbook can tell you that two animals are closely related. It cannot tell you whether they will get on, whether they will breed, or whether a particular enclosure will suit them. Those are welfare and husbandry questions, answered by people with clipboards and decades of experience.

Studbooks versus rescue records

UK primate sanctuaries keep intake records, and they answer different questions. An intake record might tell you why an animal arrived, what its legal status is, what health checks it needed, and how it behaved in the first fortnight. A studbook tells you where an animal sits in a managed breeding population. Neither is a substitute for the other. Confusing them is how you end up treating a pedigree as a police file, or a rescue history as a genetic one.

How to follow a family line without inventing drama

Start with one studbook number. Find the dam and sire. Find their numbers, then their parents. Write it out on paper if you can; screens encourage skimming. Note every "assumed" flag and every missing founder. Count generations rather than years. If a line disappears into a wild-caught founder, that is normal — most managed primate populations trace back to a small number of founders, which is precisely why the maths matters.

And resist the urge to narrate. A transfer is not an exile. A death is not a plot twist. A breeding recommendation is not a judgement on an individual animal. The studbook is a ledger of conservation decisions, not a family saga with chapter headings.

Why this dull document matters

Genetic diversity in managed populations is fragile. A studbook lets collection staff and programme coordinators see the whole picture: who is related to whom, which lines are over-represented, where the next generation should come from. Under the UK's zoo licensing framework, good record-keeping is part of responsible management. But the deeper point is simpler. A well-kept pedigree is conservation infrastructure hiding in plain sight — the sort of thing nobody photographs and everybody needs.

So next time you see a primate collection's records, read the numbers first. The names are just labels. The lines are the story, and even then, only if you keep your scepticism handy.