Staff rostering systems: from availability and shift changes to timesheet export
An employee needs cover for Friday, and two colleagues volunteer. A rostering system can connect availability, branch and skill requirements, published schedules, confirmed replacements and actual hours, giving employees, roster coordinators and payroll clerks a clear next step.
A fictional retailer has branches in Mong Kok and Quarry Bay and is planning the week of 19–25 October 2026. Each branch needs checkout and opening or closing coverage. Ching is scheduled at Mong Kok on Friday, 14:00–22:00, but needs a replacement after publication. Who can cover, when responsibility changes and whose hours reach payroll all need clear answers.
A Hong Kong public-sector rostering brief, last reviewed on 19 June 2025, describes manual re-entry from Excel into an online calendar and limited staff visibility. Microsoft Shifts also documents separate scheduled and worked hours. These point to work beyond publishing a weekly grid, including staff responses, reassignment and payroll checks. The proposed workflow has three users: employees, roster coordinators and payroll clerks.
Smart Government Innovation LAB — Rostering tools need N-0313 (last reviewed 19 June 2025) · Microsoft Shifts — Export the time-sheet report
Employees enter availability; leave has its own decision
A “My availability” screen can hold recurring hours, dated exceptions and branch preferences. Ching is usually available in the afternoons but is available only for a morning shift on 21 October. Distinguish available, unavailable and preferred periods rather than treating a preference as a confirmed assignment. An availability change after publication highlights affected shifts for the coordinator instead of silently deleting them.
Leave requests have pending, accepted, declined and withdrawn states with decision history. The roster shows confirmed unavailable periods; colleagues need not see the reason or attachment. Part-time availability submissions and fixed rotations can use different input methods while retaining one employee record. Workstem’s availability documentation provides an existing example of employees submitting their own available periods.
Check branch, skill and headcount coverage together
The coordinator’s week view groups shifts by branch and date, showing start, end, breaks, duties and required headcount. Friday evening at Mong Kok needs two people, including one authorised to close. Assigning a replenishment-only employee still leaves a closing-skill gap even if headcount is filled. Keep usable branches, confirmed skills and any validity dates in the staff record.
Flag overlapping branch assignments, accepted leave, insufficient transfer time and conflicts with the company’s rest rules. Explain which shifts conflict so the coordinator can change the person or time. A draft can retain an open slot while suitable staff are contacted. Suggestions propose candidates; they should not commit an employee to work or rewrite the company’s rules.
Make the published schedule and its changes visible
Publication checks open slots and conflicts, then records the week, version and publisher. “My shifts” shows the branch, hours, duties, breaks and current version, with only permitted colleague details. Drafts remain separate. A later change preserves the prior version and states what changed and when it applies. Track sent notices separately from employee acknowledgements, and leave delivery failures for follow-up.
Separate a shift offer from a two-way swap
Ching selects “Find cover” on Friday’s shift and sends its time, branch and skill requirements to eligible colleagues. Chun volunteers without asking Ching to work another shift: this is an offer. In this proposed approval-based workflow, acceptance creates a pending reassignment. Ching remains the scheduled employee until approval, and both people see that the transfer is unfinished.
A mutual swap selects both Ching’s Wednesday morning and Chun’s Tuesday evening shifts. The colleague confirms the pair, then the system checks each person’s resulting hours, skills and locations. If either side fails, neither transfers. Microsoft documents coworker acceptance followed by approval; Deputy documents direct transfer when an ordinary offer is claimed. Configure the actual policy rather than assuming one rule across products.
Microsoft Shifts — Request, swap or offer shifts · Deputy — Swap or offer a shift to a coworker
Confirm one reassignment when two people volunteer
Chun and Yan accept Friday’s offer simultaneously. Checking current state retains one active acceptance awaiting approval and tells the other employee it has already been accepted. The coordinator sees the original employee, proposed replacement, current roster version and checks. Approval rechecks new leave, other branch shifts and skills. A changed situation returns the request for resolution instead of relying on an earlier eligibility result.
Approval updates the assigned employee, request outcome and roster version together, records who decided and why, and notifies both people. Repeating approval must not create another transfer; a swap changes both shifts together. Declines, withdrawals, expiry and edits to the original shift need explicit outcomes. If cover fails after a sick call, open absence and coverage work rather than assuming the original employee will attend.
Record actual attendance alongside the scheduled shift
On Friday, Chun records arrival, breaks and departure. Incomplete records stay unresolved instead of taking scheduled hours as actual work. A review screen shows 14:00–22:00 beside the attendance record and preserves original clock events and their source. A missed departure allows a correction request with time and reason; an authorised reviewer stores the confirmed correction separately from the original.
An overnight shift needs full dates: 22:00 on 24 October to 06:00 on 25 October, not just two clock values. Hong Kong branch screens use Asia/Hong_Kong. For overseas payroll or another time zone, agree the reporting date, time conversion and export rules. Keep attendance intervals, breaks, reviewed hours and the final pay calculation distinct rather than deriving a fixed number from “night shift.”
Review hours before exporting a payroll batch
The payroll period screen separates missing events, pending corrections, unreviewed and reviewed records by employee and branch. Microsoft’s export documents scheduled versus worked time and original versus edited data. A custom review can follow that distinction: Chun’s confirmed hours enter the period, without also recording those same worked hours against Ching simply because an old schedule named her. Resolve adjustments under the company’s pay procedures.
Preview payroll IDs, period, fields and totals, then create a numbered export batch. Repeated downloads return that batch; transfer retries reuse its identity to avoid duplicate payroll entries. Downloaded does not mean accepted by payroll software: track submission and acceptance or failure separately. A later approved correction creates a linked revision, handled through the receiving system’s replacement or adjustment process rather than silently overwriting processed data.
Adapt disruption handling, access and integrations
A sick call records absence, then the coordinator opens coverage for missing duties and tracks contacted and confirmed replacements. A typhoon-related closure or changed opening time updates affected shifts, notices and responses under the company’s agreed arrangements. Attendance and pay still receive separate review. The system should not decide attendance or deductions from a weather signal alone; show differing branch arrangements explicitly.
Employees see their shifts and hours; coordinators see availability, skills and gaps; payroll clerks see reviewed hours and necessary payroll identifiers. Restrict medical attachments, private contacts and pay data to people who need them, keeping them out of shared rosters and notification previews. An outage can use a versioned schedule and manual entries, reconciled to the employee and original shift after recovery.
Before connecting a time clock or payroll tool, map employees, branches and payroll IDs, and agree which system confirms hours and calculates pay. Deputy’s integration guidance also discusses the source of truth for hours and costs. Verify account access, APIs or import formats instead of inferring access from a documented field. Check a small anonymous batch, retry and revision against the receiving records.
Deputy — Integration guidance for employee and timesheet data
Before payment, walk through Friday cover after publication
ProApp provides a Demo before payment. For a rostering system, we can agree a walkthrough around your employee, coordination and payroll roles using this fictional two-branch week. Bring an anonymous roster, availability examples and payroll import fields. Check that each person finds outstanding work and that the employee screen and payroll export reflect the confirmed replacement.
- Enter availability and one leave request for 19–25 October. Create a shift with sufficient headcount but no closing coverage, resolve it, publish, and check the employee’s version and notice.
- Offer Ching’s Friday shift and accept simultaneously from two accounts. Add a conflicting branch shift before approval, resolve reassignment and repeat approval. Test a mutual swap with one ineligible side.
- Record Chun’s hours and a missed-clock correction, add an overnight shift, then test sick-call coverage and changed branch hours. Check the original schedule, changes and attendance separately.
- Review and export a batch, repeat the download and simulate a transfer retry. Approve a later correction, inspect its link to the original batch and find entries not accepted by payroll.
