Reptile breeding tracking — pairings, clutches and hatch dates

A pairing records the sire, the dam, the species and when they were introduced. The clutch or litter that follows hangs off that pairing, carrying what was laid or conceived, when it emerged, and how many were live and weaned. Individual offspring are promoted into full animal records when you are ready, and they keep their parents.

That last step is the one that matters six months later. An animal promoted out of a clutch already knows its lineage, so pedigrees and inbreeding coefficients work without anyone re-typing a family tree.

Egg-layers and live-bearers do not have the same timeline, and an egg-layer's timeline has two legs rather than one. Breeding to laying is a different interval from laying to hatching, and using either on its own puts the projection weeks out.

HerpSync keeps both, per species, and projects a due date from the pair of them — pre-lay plus incubation for an egg-layer, gestation for a live-bearer. When a species has no usable interval recorded, it returns nothing rather than a made-up date.

Most collections are not started from scratch. If you already have eggs in the incubator or a litter on the ground, HerpSync works backwards from that date to estimate when the pairing happened, gives a window rather than a single day, and tells you in plain language what it assumed to get there.

An estimate is stored as an estimate. A back-computed introduction date is flagged as one and never overwrites a date you actually observed, so a projection can never quietly become a record.

Expected lay, birth and wean dates appear on a breeding calendar because they are derived from the pairings and clutches you already recorded. There is nothing to enter twice, and nothing to remember to update when a clutch comes early.

Fertility is worked out per pairing against the eggs or ova you recorded as set, so it is a real rate rather than a guess. If you did not record a denominator, it reports nothing at all — never zero, and never a percentage invented from an empty divisor.

The same per-pairing view carries revenue, cost, net profit and revenue per offspring, so a project that produced a lot of animals and very little money is visible as one. A fertility drop against a pair's own history can raise an alert rather than waiting to be noticed.

• Fertility rate against recorded eggs or ova set
• Offspring count, live count and weaned count per clutch
• Revenue, cost, net profit and ROI for the pairing
• Revenue per offspring, for comparing projects of different sizes

Because the parents' genes are on their records, a planned pairing shows the odds for the clutch before the animals go together — across several loci at once, with allelic genes, lethal super forms and sex-linked genes handled properly rather than as a Punnett square that quietly gets them wrong.

All features