Rosters fail on information HR already holds
Operating teams get dependable roster and headcount visibility when HR passes approved leave, start and end dates, transfers and qualification status to the supervisors who build schedules, using availability statuses both teams read the same way. Most rostering gaps come from information HR already has but operations never receives.
On the floor, the problem looks like a supervisor short-handed on a busy shift. Behind it sits a chain of small misses: leave approved by a department manager but invisible to the shift lead, a new joiner rostered before finishing safety induction, a resignation known to HR but not to the planner who still counts that person next month.
What a supervisor needs to know about each person
Supervisors do not need the personnel file. They need to know, for each person on the team, whether that person can be rostered and for which duties.
That comes down to approved leave dates, the start date and any induction or training outstanding, the last working day for leavers, transfers in and out of the team, and changes to contracted hours. For roles that need a licence, certificate or medical clearance, operations needs to know whether it is current and when it lapses, without seeing any underlying medical detail.
Contractors and agency staff often sit outside HR's records entirely. Decide who tracks their availability. If HR does not hold them, operations must, and the headcount view should show both groups clearly labelled.
Transfers between sites need care of their own. A worker moving from one plant to another may need a fresh site induction even if fully trained in the role, so their status at the new site should start as in training until the local supervisor clears them.
Availability statuses HR sets and operations reads
HR sets the status from its records and operations reads it. If a supervisor thinks a status is wrong, they raise it with HR rather than overriding it on the roster.
- Available: can be rostered for all duties in the role
- Restricted: can be rostered with limits, such as light duties or no night shifts, with no reason shown
- In training: employed but not yet cleared for independent work
- On leave: approved absence, with a return date
- Pending leave: applied for but not approved, visible to the approver and the roster planner only
- Leaving: serving notice, with the last working day
- Not available: transferred out, suspended or otherwise unable to be rostered
Timing updates so the roster can still react
A status change helps only if it arrives before the roster is published. Agree with each operating team when its roster is built, and make sure HR's updates reach the planner beforehand. Late leave approvals should come with a direct note to the supervisor, not merely a record change.
Sick days and emergencies cannot be planned. For these, the employee or their manager tells the supervisor directly and HR records it afterwards. The status should then reflect the absence, so the roster history is accurate when someone reviews it later.
Leave approval itself works better with input from the people who know the roster. Where HR approves leave centrally, supervisors should at least be consulted for periods of high demand.
Public holidays add another wrinkle for teams spread across states, since a holiday at one site may be a normal working day at another. HR should keep each person's work location accurate, so the planner sees the holidays that actually apply to the people on that roster.
Headcount visibility above the individual roster
Operations managers need a wider view than any single roster: how many people are in each role and site, how many are in training, how many are leaving and how many roles are open. That view shows where overtime will grow or where a site needs a hiring request. Bring overtime and agency spend into the same discussion where you can, since rising overtime is often the earliest sign of a headcount gap.
Review it with HR at a regular operations meeting. HR explains open roles and expected start dates; operations explains where cover is thin. The output is a short list of hiring priorities and temporary cover arrangements that both sides have agreed.
Keeping people status and operating work in their own systems
People records, leave approvals and onboarding sit in BukuHR. Work tracking, exceptions and handoffs between teams sit in BukuOP. Whether availability statuses should appear alongside rosters or task assignments is a question to scope with Fasttrade, because rostering practice varies widely between sites and shift patterns.
Frequently asked questions
Should supervisors see why an employee is on restricted duties?
No. Supervisors need to know what the person can and cannot do so they can roster safely. The medical or personal reason stays with HR and, where relevant, the occupational health adviser. Showing the restriction without the reason keeps the roster workable while protecting sensitive information, in line with PDPA principles you should confirm with your adviser.
Who should track contractors and agency workers on the roster?
Whoever manages the contract, usually operations or procurement, unless HR has agreed to hold them. The headcount view should show employees and contractors separately so managers know who is on the payroll and who is supplied. Track contractor availability, training and site clearance with the same status set, even if the records sit elsewhere.
How do we stop people being rostered before their induction is complete?
Use an in-training status that HR sets from the start date and clears only when induction and required training are recorded. Planners should not roster anyone for independent duties while that status applies. The supervisor and trainer confirm completion to HR, which then changes the status to available and the person joins the normal roster.
Next step
Explore BukuHR or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.