Docs
Shifts, breaks and labels
Keep each interval clear enough to check on its own.
Add separate work sessions
Use another shift row for another session on the same date. Each shift carries its own start and end date, times, labels and notes. The gap between separate shifts is outside their spans; it must not also be deducted as a break from one of them.
Add and label breaks
Each break has explicit start and end dates and times. Use those dates when the interval occurs after midnight. Paid breaks stay in the shift’s counted span. Unpaid breaks reduce it. The label is your input, not an automatic determination of legal break treatment.
Resolve conflicts
| Issue | What to review |
|---|---|
| End before start | Check the end date and clock time |
| Break outside shift | Keep both break boundaries inside the shift |
| Two breaks overlap | Edit or explicitly remove the mistaken interval |
| Two shifts overlap | Check whether a session was duplicated or mistimed |
Keep unaffected entries
Reviewing a conflict should not clear your other rows. The affected shift cannot provide a final valid duration until the issue is resolved. A separately labeled completed subtotal may remain useful, but it is not the final period total. Do not hide an overlapping row simply to make a warning disappear.
Labels and notes
Use a stable project label for repeated work and notes for one-off context. Text is retained as data, including Unicode characters, commas and quotes. Avoid including private details the record does not need. Review whether notes should appear in the PDF or printed copy you plan to share.
Removing a record
Use the explicit remove action for the intended shift or break and check the new result. Deleting a named saved card is a separate operation in Saved cards. A local deletion does not delete files already downloaded or sent elsewhere.