Ball Python Feeding and Shed Log: Record Events Without Guessing the Cause

A ball python feeding and shed log is most useful when it records events without guessing their cause. Keep what was offered, when it was offered, what you observed afterward, and the date and character of each shed. Creatures supports animal records and care plans so future tasks and completed events can stay separate.

This page is about documentation. It does not set feeding intervals, prey sizes, enclosure conditions, or treatment. Use the ball python care guide, the species page, and your reptile veterinarian for those decisions.

AI-generated illustration.

Record one event, not an assumed pattern

For a feeding event, record the actual date and time, the food item and amount, and the observed outcome. “Offered” does not automatically mean “eaten.” The Feeding form requires an outcome: Eaten, Partly eaten or Refused, with Eaten selected initially. If the outcome is still unknown, wait to check before saving that feeding result. Keep a separate factual note if you need to preserve an observation in the meantime.

Keep the terminology consistent enough to compare entries. A free-text amount should still include its unit or a clear description, such as the number and weight of frozen-thawed prey offered. Name the prey item and preparation actually used; do not copy an example as a feeding recommendation. Avoid writing “usual” when a different caregiver would not know what that means. Do not convert an approximate quantity into a precise weight afterward.

The entry can include relevant context you actually know, such as a recent move or a recorded shed stage. It should not assert that the context caused a refusal. Several events appearing near each other in a timeline do not establish cause.

Add Feeding directly or complete a scheduled task

Open Add Record, then Care & growth, and choose Feeding. Enter the feed item, amount, actual date and time, and check the outcome before saving. Feeding is a standard Add Record choice.

Where Quick capture or Describe what happened is offered, write a factual note and choose the record-draft action. Review the proposed animal, record type, date, feeding item, amount, and outcome before saving. The draft is editable and does not save itself.

For a scheduled feeding, Done now on Today’s care saves an Eaten outcome. Choose Add details to record Partly eaten or Refused and the actual completion time. Do not use Done now for an unobserved outcome.

AI-generated illustration.

Keep shed stage and completion separate

For a reptile, Shed / Molt records let you distinguish an in-blue observation from a shed event. Enter the date you observed the stage, and use completeness only when you have evidence for it. A pre-shed observation is not proof that shedding later finished.

Use notes for what you could see. If the result is uncertain, keep that uncertainty instead of selecting Complete because a calendar interval has elapsed. Note visible retained shed around an eye cap or tail tip and contact a reptile veterinarian about a concern. Do not pull retained skin from the log’s description. The Assisted field records what happened; it is not an instruction to intervene.

• Food offered. Record the observation: Item, amount, and actual time. Do not infer: That it was eaten.
• Food refused. Record the observation: Observed outcome and context. Do not infer: A diagnosis from one entry.
• In-blue appearance. Record the observation: Date and description. Do not infer: The eventual shed date.
• Shed found. Record the observation: Date found and observed condition. Do not infer: Unseen details about the animal.
• Veterinary advice. Record the observation: Who advised what and when. Do not infer: A new treatment plan from the log.

Compare dates without turning the chart into a diagnosis

Use the animal records tab to search the history and narrow by record type and date. Read the notes behind the dates. Two refusals separated by missing records are different evidence from a complete series of observed events.

Record body weight in grams using a consistent scale and routine, so a run of refusals can be read alongside comparable weights. Retain the measurement method and unit. The measurement workflow distinguishes a measured value from an estimate. The same comparability principles appear in the reptile growth-log guide.

Bring the timeline and original veterinary instructions to your reptile veterinarian when you have a concern. Do not wait to finish the log before seeking needed help, and do not let a reassuring-looking chart override the animal in front of you.

Make the log usable by a second keeper

At handoff, identify the snake unambiguously and show the other person where to find the most recent event. Explain which future tasks are scheduled and how to record a refusal or uncertainty. Review reminders if a one-off check is more appropriate than an ongoing routine.

AI-generated illustration.

An illustrative observation note might read: “Food offered in the evening; outcome not yet checked.” This is a note, not a completed Feeding outcome. After checking, save the supported outcome with its actual time and preserve any relevant uncertainty in Notes.

Before sharing a packet, review private notes and attachments. Keep the enclosure photographs dated and described as observations, not as proof that every environmental condition was correct. A good log is a faithful account, including its gaps.

Use the ball python care guide for the broader enclosure and feeding context, and the ball python lifespan guide for long-term planning. A dated event log supports those conversations without turning one refusal or shed into a diagnosis.

Do this next on Creatures

Start with the information and responsibility you already have. Choose the action that fits your role today.

• Keep an animal’s history together: Add your ball python with the identity details you know. You can start while signed out and complete the free account steps in the flow.
• Record a real event: Add a record, choose the correct animal and check visibility. The form opens for visitors; a free account is needed to save.
• Follow availability: Save a ball python listing alert. Visitors can enter an email and complete signup; an alert does not guarantee a match.
• Represent your work: If you manage a reptile breeding organization, create its organization profile. Guest signup is available in that flow.
• Compare current listings: Browse ball pythons on the marketplace, then confirm the individual animal’s identity, history and suitability with the seller.
• Find organizations to contact: Explore the breeder directory and discuss records and ongoing support directly with the relevant organization.