Planning shift schedules

Making Shift Changes Less Messy

When employees swap or change shifts informally, attendance and pay suffer. Record shifts and change requests so the DTR counts them correctly.

In many workplaces the schedule changes during the week. Someone swaps with a colleague, another moves to an earlier start, a third covers a late shift. If none of this is recorded, the attendance system sees only people who appear late or absent.

Why informal shift changes cause trouble

Attendance is computed against a schedule. If the schedule on record is not the one the employee actually worked, the result is wrong: a person who worked a different shift is marked late, or an absent mark appears for someone who was simply somewhere else on the roster. HR then has to correct these by hand, one at a time.

Shifts and change requests in the DTR

easyHR keeps shift information together with attendance:

  • Shift defines the working schedule against which attendance is computed.
  • Change Shift requests let an employee ask for a different shift through the system. Once approved, the change is reflected in the DTR computation, so late, undertime and absent are computed against the shift actually worked.
  • Rostering is available for companies that want it. It is optional, so companies with fixed schedules do not need it.

What each user sees or can do, including rostering, may depend on settings and user rights.

Fewer manual corrections

Because the request and the DTR are connected, there is no need to remember to adjust the record later. The approval is the adjustment. HR spends less time explaining marks that were never real problems.

An illustrative scenario

Imagine a team where two employees agree to swap shifts for a week. They tell their supervisor in passing, and nothing is recorded. At cutoff the DTR shows one of them as late every day and the other as having left early, and HR spends an afternoon working out what happened.

If the swap is filed as a Change Shift request and approved, the DTR is computed against the new shifts. There are no false marks to explain, and payroll is based on the attendance that really took place.

Habits for tidy shifts

  • File changes in advance. A request made before the shift gives the approver time to respond.
  • Approve before the cutoff. Late approvals mean late corrections.
  • Keep base shifts accurate. Change requests only help if the underlying schedule is right.
  • Use rostering only if it fits. If your schedules rarely change, a simple setup may be enough.
  • Review exceptions in the DTR. A quick check before payroll catches shift mismatches.

Easy to start

easyHR is cloud-based, with nothing to install. Employees and approvers use it from a browser, and the company always works on the latest version.

Frequently asked questions

Do approved shift changes affect attendance? Yes. They are reflected in the DTR computation.

Is rostering required? No. Rostering is optional.

Can everyone file or approve shift changes? That depends on settings and user rights.

Want to see it in action? Message us for a free demo at humedit.ph/easyhr, or contact Sales: +63 917 628 0355 / hiisales@humedit.ph.

AI Chat