Blog

Clock time and elapsed time are different questions

Dates make a shift unambiguous across midnight; offsets answer a different question.

What a wall-clock record contains

A simple time card records the date and clock reading at the beginning and end of a shift. From those fields, a tool can subtract entered calendar minutes and deduct unpaid breaks. That is the model used by MinuteFolio. It is useful because the inputs are easy to read and the arithmetic can be checked directly.

What those fields do not say

A date and clock time do not identify a timezone offset. They do not tell the calculator whether the clock was moved, whether the person traveled between zones, or which occurrence of a repeated clock reading was intended. Adding a later calendar date solves the ordinary midnight boundary; it does not supply those missing facts.

A simple overnight example

22:00 on one date to 06:00 on the next gives an eight-hour wall-clock span. A 30-minute unpaid break produces 07:30. This result follows from the entered dates and readings. If the clock changed during that interval, the relationship to actual elapsed time requires additional information that is not represented in those inputs.

Reporting date is another separate choice

MinuteFolio assigns the complete shift to its start date and the period containing it. This decides where the result appears in a report; it does not change the duration formula or manufacture timezone information. Keep date attribution, break treatment and elapsed-time interpretation as separate questions when checking an unusual record.

How to handle a record outside this model

Keep the original dates and readings rather than altering them to force a preferred answer. Note the missing offset or clock-change context in your own records and use an appropriate timezone-aware method when actual elapsed time is the question. Do not treat a wall-clock total as proof that such a calculation has already happened.

For ordinary records that remain within the intended model, enter both dates explicitly, use dated break intervals and review the displayed limitation. The purpose of that limitation is to make the result understandable, not to conceal a default adjustment.

Keep going