A time card that includes February 29
A monthly card must use real dates, including the extra day in February 2028.
The sample record
| Field | Value |
|---|---|
| Month | February 2028, 29 days |
| Start | February 29, 2028, 22:00 |
| End | March 1, 2028, 06:00 |
| Unpaid break | March 1, 00:00–00:30 |
Check date validity before duration
February 29 is a valid date in 2028. February 30 is not. A date parser must not quietly turn an invalid February date into a March date, because that changes the record and its reporting period.
Keep the shift in its start-date period
All 07:30 belongs to February 29 and the February report under the app’s whole-shift start-date convention. March 1 remains the actual end date. The calculation is the same minute arithmetic as another overnight shift; what is distinctive here is accepting the real leap day, rejecting an impossible date and preserving the month boundary.
Use this example
Open related toolFrequently asked questions
Why is February 29 available in this example?
The selected year is 2028, which includes February 29. The actual calendar date is validated; February 29 is not accepted in a year without that date.
Does the March 1 end move this shift into March?
No. The full 07:30 net duration belongs to its February 29 start date and the February reporting month.
Sources and method
- NIST SP 330, Section 4, Table 8Time-unit definitions only; not a payroll authority or product endorsement.
- Original worked calculationSynthetic example data, explicit input rules and direct integer-minute arithmetic.
Keep going
Monthly timesheet calculator
Create a calendar-month time card with real month lengths, partial weeks, leap-day dates and explicit month-end shift handling.
Dates, clock times and durations
Read supported dates, 12- and 24-hour clock times, long durations, decimal hours and explicit fractional-minute handling.
Worked time-card examples
Browse twelve checked examples of split shifts, overnight breaks, date boundaries, decimal durations and file review.