Why logging meals and outcomes helps next time
How keeping a simple log of foods, carbs, insulin and what happened after helps families of kids with type 1 diabetes spot patterns and feel less alone.
Tyler
ยท 3 min read

A useful diabetes log answers a practical question: what do we actually know about this meal and what happened afterward? It does not need to document every detail of family life. A few accurate observations, with clear times and honest gaps, are more useful than a complete-looking record built from guesses. Start with information that helps another caregiver understand the event without needing to reconstruct it from text messages.
Record the meal and its context
- Food, portion and estimated carbohydrate amount, including whether the child finished it.
- First-bite time separately from the time you entered the note.
- Glucose at first bite if available, its measurement time and whether it came from a meter or CGM.
- Insulin actually administered, including amount, type, delivery method and actual administration time.
- Relevant activity, illness, low treatment, another snack or suspected device problem.
These fields describe different events. The time someone types a note is the logged time, not necessarily when insulin was given. If a caregiver documents lunch later, preserve both times. If the administration time is uncertain, mark it approximate or unknown rather than making the entry appear exact.
Keep calculated, given and unknown separate
A calculated or suggested insulin amount is not evidence of administration. Record it separately from a confirmed dose. A missing entry also does not establish that no insulin was given. Use clear descriptions such as calculated, administration confirmed or administration unknown. Verify uncertainty with the responsible caregiver or available delivery record.
Unknown is not zero. Zero carbohydrate and zero insulin are positive statements about what happened; a blank field means information is missing unless your system explicitly defines it otherwise. Preserve this distinction when reviewing records. Do not invent a value or give another dose based only on an empty log. Pump delivery should be identified as pump delivery rather than assumed to be an injection.
Anchor readings to real times
A glucose value measured later cannot be relabeled as first-bite glucose. If there was no meal-start reading, say it is unavailable and retain the later reading with its timestamp. CGMs estimate glucose in fluid between cells; meter and CGM readings are different sources and should be identified accordingly.
For follow-up observations, use the timing recommended by your care team and retain actual measurement times. Note intervening food, activity, insulin or low treatment. For example, a later rise after lunch has a different context if another snack occurred before that reading. Without that detail, two meals can look more comparable than they really were.
Look for questions, not proof
Repeated observations may suggest an association worth discussing, but they do not prove a food caused a rise or exercise caused a low. Portion estimates, insulin timing, illness, activity and delivery problems can overlap. Bring several dated examples and their uncertainties to your team rather than labeling a meal as always causing a spike.
Make shared records easy to clarify
Agree on who confirms administration and how corrections are recorded. Carolyn supports chat and voice entry and shared family records, offering ways to capture observations without a long journal entry. These features do not verify treatment occurred or guarantee errors are prevented. Review captured details, correct inaccuracies and communicate directly when a handoff or uncertain dose needs clarification.
Sources

About Tyler
Founder of Carolyn, parent of a child with type 1 diabetes. He built Carolyn to ease the daily mental load of T1D for his family.
Remember every meal, together
Carolyn keeps your family's carbs, doses and outcomes in one shared place.
Join the Carolyn waitlist