One date line for feeds, sheds and temperatures
Log a ball python's feeds, sheds and enclosure temperatures in a single running record where each date carries all three, because in this species the three explain each other. A refused meal means one thing during a shed cycle and another in the middle of a temperature dip, and only a combined log shows which story you are in. For each feed, write the prey type and size, whether it was taken, struck at and dropped, or ignored entirely. For sheds, note when his eyes turn blue and cloudy, when they clear, and when the shed itself happens. For temperatures, record the warm hide reading and the cool end reading at a consistent time of day, so comparisons across weeks are honest.
Feeding entries that capture a ball python's refusals
A ball python's feeding log earns its place during his fasts. Ball pythons commonly refuse food for weeks or longer, especially mature males in cooler months, and the log is what separates a normal fast from a worrying one. Record every offer, including refusals, and note his weight once a month so a fast can be judged by condition rather than by anxiety. Write down presentation details that matter with this species: whether the prey was warmed, offered at dusk, or left in the enclosure, and whether he showed interest from his hide. When he does eat after a break, that entry closes the episode, and the whole stretch becomes a reference the next time he stops, which for many ball pythons is a when, not an if.
Shed entries that watch the eyecaps
A ball python's shed log should track quality, not just dates. Note the start of the blue phase, the shed date, and whether the skin came away in one piece or in fragments. Pay written attention to the eyecaps and the tail tip, the two places retained shed causes trouble, and record the humidity steps you took during the cycle, such as adding a humid hide or misting. A run of poor sheds in the log, read alongside your temperature entries, often points at humidity or warmth drifting in the enclosure rather than at the snake. If retained eyecaps or repeated incomplete sheds appear despite good conditions, that written history is exactly what an exotic vet needs to see at the appointment.
Temperature entries built around his hides
A ball python's temperature log should be organised around where he actually lives: inside his warm hide, inside his cool hide, and the general air between them. He is a shy, ground-dwelling snake who judges his enclosure from inside a hide, so a thermometer reading taken in open space can look perfect while his warm hide runs cold. Log those hide readings at the same time each day, note any thermostat or heat mat change beside the date it happened, and watch for the pattern where he stops using one hide entirely, which usually shows in behaviour before it shows in numbers. Stable hide temperatures, recorded steadily, also explain good sheds and reliable feeding better than any single measurement can.
Reading the log as one story
A ball python's log pays off when its three threads are read together at the end of each month. Feeding gaps line up against shed dates, shed quality lines up against temperatures and humidity, and slow weight change puts every refusal in proportion. That monthly read turns record-keeping from chore into diagnosis of your own husbandry, and it gives a vet a timeline instead of a recollection. Keep the log where anyone who feeds him can add to it, because gaps appear when only one person holds the notebook. KinsLe keeps that shared record tidy through Care Teams, where care duties for a ball python are assigned per pet and completed tasks are marked with a timestamp.