The Roster Is the Contract, Attendance Is the Evidence

A roster states what was supposed to happen. Attendance records what did. Most companies treat these as separate exercises — the schedule lives in a spreadsheet, attendance lives in a system — which means the most useful number in workforce management, the gap between planned and actual, is never calculated automatically.

When roster and attendance share a system, that gap becomes visible daily. Scheduled twelve, clocked in nine, two late, one absent. That single line is what a shift supervisor actually needs at the start of a shift, and it cannot be produced when the plan and the record live apart.

It also fixes something subtler. If the shift definition carries the verification rules, then assigning someone to a shift automatically applies the right geo-fence, the right grace period, and the right requirement for face verification. Nobody configures attendance rules per employee, because the rules belong to the shift and follow the assignment.

• Scheduled versus actual is the most useful daily number and requires one system
• Supervisors need the gap at shift start, not in a monthly report
• Verification rules live on the shift and follow every assignment
• Nobody should configure attendance rules per employee

Define Shifts Once, Not Every Week

The most common reason roster software gets abandoned is that it made scheduling slower. If assigning next week means clicking through every employee individually, a spreadsheet genuinely is faster, and people will go back to it.

The mechanism that avoids this is defining the pattern rather than the instance. In Attend Mitra you create shift templates that carry timings, break rules, location, and verification requirements, then apply recurring patterns so a rotating day-night cycle is defined once instead of re-entered every week. Rosters can be saved as presets, so a standard staffing shape for a site or a peak week is reapplied rather than rebuilt.

Shift templates are also where the operational detail belongs. Break rules, grace periods before a mark counts as late, and whether the shift requires face verification, a geo-fence, an approved network, or permits offline marking. A night shift at a remote site and a head-office day shift need different answers to all of these, which is precisely why the settings sit on the shift rather than on the company.

• If assigning a week takes longer than a spreadsheet, the tool will be abandoned
• Shift templates carry timings, breaks, location, and verification rules
• Recurring patterns define rotating cycles once instead of weekly
• Reusable presets reapply standard staffing shapes for sites or peak weeks
• Grace periods and late rules belong per shift, not per company

Draft, Rearrange, Then Publish Once

Rosters are not written once. They are drafted, adjusted for a leave request, adjusted again when someone swaps, and adjusted a third time when a new requirement appears. A system that pushes every intermediate state to employees' phones teaches everyone to ignore roster notifications, which defeats the purpose entirely.

Attend Mitra keeps the weekly schedule in draft while you work on it and publishes the complete week as a single action. Employees see a stable schedule, and you retain the freedom to rearrange without generating noise. You can also copy a previous week as a starting point rather than beginning from an empty grid.

The leave conflict warning during assignment is the check that earns its place. Assigning someone who already has approved leave is a mistake that only reveals itself when the shift starts and the post is empty. Surfacing it during scheduling turns a Sunday-night incident into a Thursday-afternoon adjustment, and it only works because leave and scheduling are in the same system.

• Keep the week in draft while it changes; publish once when it is final
• Copy a previous week rather than starting from an empty grid
• Leave conflict warnings during assignment prevent unmanned shifts
• Publishing intermediate states trains employees to ignore notifications

Holidays, Week-Offs, and the Payroll Consequence

A roster is not only about who works — it also defines who legitimately does not. Rostered week-offs are paid non-working days, and if the payroll system cannot see them it will treat them as absence. This is one of the most common sources of incorrect deductions when scheduling sits outside the platform.

Public holidays and declared office closures belong in a company calendar rather than being handled per employee, so a declared closure applies everywhere at once. In Attend Mitra the calendar covers holidays, closures, and company events, and setting the full year in January removes a question that otherwise recurs every month.

Together, roster and calendar produce the paid-days figure that payroll needs: days worked with verified attendance, plus approved paid leave, plus holidays and closures, plus rostered week-offs. Whatever remains is unapproved absence and becomes loss of pay. The roster is not a scheduling convenience at that point — it is a payroll input.

• Rostered week-offs are paid non-working days and must be visible to payroll
• Holidays and closures belong in a company calendar, not per employee
• Set the full-year calendar once instead of answering the question monthly
• Paid days = worked + approved leave + holidays + rostered week-offs
• The remainder becomes loss of pay without manual calculation

Publishing to People Who Are Not at a Desk

A roster nobody can see is a roster nobody follows. For shift workers, field staff, and guards, the schedule has to reach a phone, because they are not opening a shared drive or checking a noticeboard at head office.

Employees see their assigned shifts in the app alongside their leave balances, so they can plan around the schedule rather than around a photographed printout in a group chat. Managers publish and adjust the week from the manager app, which means a supervisor at a site can react without going back to a laptop.

This is also what makes the scheduled-versus-actual comparison meaningful. Once staff know their assignment and marked attendance against it, the daily gap is real information rather than a data-quality artefact. That is the point at which a roster stops being an administrative document and becomes an operational control.

• Schedules must reach a phone for shift, field, and site-based staff
• Employees see assigned shifts alongside leave balances in the app
• Managers publish and adjust the week from the manager app on site
• A known schedule makes scheduled-versus-actual real information