Key takeaways
- Keep planned shifts separate from actual time records.
- Show breaks, leave, workplace and overnight work clearly.
- Preserve a trace when the plan changes.
- Review planned versus actual hours every week.
1. Separate the schedule from the timesheet
The schedule is forward-looking: it contains dates, expected start and finish times, workplace and planned breaks. The timesheet contains real clock-in, clock-out, breaks, leave and corrections. Automatically treating every scheduled shift as worked creates false records.
Keep both layers and display them differently in one calendar. A late finish, missed shift or swap can then be understood without rewriting the original plan.
2. Gather the scheduling inputs
Define the period, workplace, fixed or rotating pattern, known leave and exceptions. If you work for more than one workplace, make travel time and potential overlaps visible before accepting the plan.
An employer creating a staffing rota also needs to consider coverage, roles, qualifications and applicable rest or working-time rules. A personal tracker should not pretend to approve those organisational decisions; it should accurately capture the schedule the user receives.
- Date range and rotation pattern
- Start and finish times
- Expected breaks
- Leave and unavailable days
- Workplace or branch
- Shifts crossing midnight
3. Model fixed, rotating and irregular patterns
A fixed schedule repeats the same days and times. A rotating schedule moves through defined day, evening or night blocks. An irregular rota requires individual entries and more frequent confirmation. Choose a repeat rule that reflects reality instead of hiding exceptions.
Bulk creation saves time, but it needs a preview of affected dates, excluded days, times and breaks. Existing records or overlaps should be reported rather than silently overwritten.
4. Make the schedule readable on every screen
A calendar should let a user distinguish the date, shift type and workplace at a glance. Do not rely on colour alone; include a text label such as “Night”, “Leave” or a workplace abbreviation.
On a small screen, show the selected day in a clear detail panel rather than squeezing every field into a month cell. PDF or spreadsheet exports should include date, planned start and finish, break, workplace and notes.
5. Record swaps and schedule changes
When a plan changes, preserve the fact that it was changed along with a timestamp and short reason. This answers whether a difference at period end came from the original schedule or from the work event.
A swap can alter the date, workplace or role. Notifications and reminders should follow the current version, while the previous plan must not appear as an actual worked shift.
6. Compare planned and actual hours
Run a short weekly review for missing shifts, unexpected extra hours, overlaps and changed breaks. Correcting the record while the week is fresh is easier than reconstructing an entire payroll period.
The ILO guide to balanced working-time arrangements describes a systematic approach to work schedules for workers and organisations. HourTally supports the personal side of that workflow by keeping the plan visible next to the shift record.
FREQUENTLY ASKED
Questions you may still have
Is a shift schedule the same as a timesheet?+
No. A schedule shows planned work; a timesheet records actual work and non-working events.
Are repeating shifts safe to add in bulk?+
Yes when the app previews every affected date and reports conflicts or skipped entries instead of overwriting them.
Should an old schedule be deleted after a change?+
Keep a trace of the change and clearly mark the current version so the history remains understandable.
PRIMARY SOURCES