A workplace conversation about hours can be easier when a worker can describe what they remember, but memory alone is a fragile organizer. A shift blurs into the next one: the same station, the same handoff, the same end-of-day routine. A manager may be willing to look into it, but “I think that happened last week” gives both people little to work with.

Make a small note while it is fresh

Consider a delivery worker whose route ends later than expected. The schedule, the clock-out and the worker’s memory may not line up neatly, especially if the end of the day includes returning equipment or completing a handoff. A note made shortly after the shift can capture the event without making a judgment: date, approximate time, what remained to be done, and what the time card later showed. The point is to make a later question concrete, not to decide what the record must say.
That small note can reduce the burden on memory, but it has limits. A person can misread a clock, forget a break or write down the wrong date. A record should be treated as a prompt for checking, not as unquestionable proof. Comparing it with the workplace record and asking how the entry was created is more informative than assuming either source tells the whole story.

Use the note to invite a check

When the worker raises the issue, the note can shape a modest request: “I wrote down that I was finishing the return after this shift. Could we check what time was entered?” That wording shares the relevant detail and gives the manager room to explain. Maybe the clock-out happened before the task, maybe the worker’s note refers to another day, or maybe the recorded time deserves a closer look. Each is a possibility, not a conclusion.
Some people worry that keeping notes signals distrust. Others think not keeping them means accepting a system they did not create. There is a middle position: a personal record can be ordinary organization, just as someone keeps a schedule or a list of shifts. It need not be hidden or confrontational. Its value is that a question can be specific when it is finally asked.

Preserve context, not just totals

A weekly total can alert someone that the numbers feel unexpected, but it rarely explains which shift is behind the feeling. Shift-level context—what happened, what the system shows and what was clarified—makes follow-up easier. If an entry is later changed, retaining the original and the reason for the change helps the worker understand the sequence rather than seeing only a new number.
Documentation should make a conversation more accurate, not more combative. A worker can hold onto their recollection while acknowledging that a record or memory may need context. The manager can check the system without being presumed dishonest. What is the smallest note you would actually keep after a busy shift?
iOS: https://apps.apple.com/us/app/everyhour-overtime-tracker/id6820807660 Android: https://play.google.com/store/apps/details?id=com.everyhour.overtime.tracker