First, find the record that is already there
Check the selected child, then look for a running timer or the saved feed or sleep. Do not add a replacement before checking: two entries can make the day harder to understand.
If a caregiver may still be timing the same event, confirm what happened with them. A phone that has been offline may not yet show their latest changes. Bring the shared record up to date before deciding that an entry is missing.
In Cocoon, the latest saved feed or sleep can be opened from its activity card. Older entries are available in the recent history and Journal. Open the event you mean to correct, rather than starting another timer.
Change the finish, then check the duration
If the timer is still running but the event has finished, end it and open its saved record. Correct the end to the time you remember. If the record is already saved, edit that entry directly.
These examples use made-up times to explain the arithmetic:
| What happened | What to correct |
|---|---|
| A left-side feed ran from 09:10 to 09:25; you noticed at 09:50 | Finish 09:25; left-side feeding time 15 minutes |
| Baby slept from 13:00 to 13:40; you noticed at 14:10 | Wake time 13:40; sleep duration 40 minutes |
| Sleep started Monday at 23:50 and ended Tuesday at 00:30 | Keep both dates; duration 40 minutes |
For a breastfeed, the outer start/end window and the minutes on each side are different details. Check both. A feed from 09:10 to 09:35 with a five-minute break has a 25-minute window but 20 minutes of feeding. Do not turn the break into time on a breast simply to make the numbers match.
The time-between-feeds guide explains these different clocks with another worked example.
If you forgot to start it instead
If the feed or sleep is still happening, use the earlier start you remember. In Cocoon, Started earlier / enter minutes on the Feed card opens the feeding options; the sleep logger also accepts an earlier start. An active timer has a start-time editor.
If the event has already finished, use a past entry rather than leaving a new timer running. For a breastfeed, enter the minutes you know for each side. For sleep, enter the sleep and wake times. Check the calendar date if either time was before midnight.
An approximate start is still approximate after it is typed into an app. Add a note such as “started around 09:10” so a later reader can see the uncertainty.
A paused timer is not always an awake gap
Timer controls describe how the app records time; they cannot observe whether your baby was feeding or sleeping.
In Cocoon, pausing a breastfeed excludes that break from feeding minutes. Resuming the same sleep restores its full time window, including the paused period. If baby was actually awake, keep that waking visible in the record; separate sleep stretches can be clearer than one continuous sleep.
If baby stayed asleep and you paused the timer by mistake, resuming is different from inventing a new sleep start. If they woke and later slept again, preserve both observed times. The overnight sleep examples show how to keep an awake period separate.
Finish with a small check
After saving, reopen the entry and confirm the child, dates, start, finish and duration. For a breastfeed, check the sides too. If the app reports a save failure, check whether the change appears before creating another entry; keep your correction handy while resolving the error.
If the original wake time was 13:40 and it is now 14:10, the example baby has been awake for 30 minutes, regardless of when you repaired the log. A correction should describe the event, not the editing session.
When you cannot remember a finish, say so. Ask the other caregiver or keep a note of the gap; do not use a typical nap length or yesterday’s feed to manufacture an exact time. A partial record is more useful when its limits stay visible.
