How Should HR Systems Handle Attendance and Pay During Adverse Weather? A Guide to Remote Work, Duty Rosters and Notifications
Updated: Aug 30
During typhoons, Black Rainstorm Warnings or “extreme conditions”, management often receives highly practical questions:
• “I cannot get to work. How will the company record my attendance?”
• “If I work from home, do I need to check in?”
• “How should transport allowances for designated duty personnel be recorded?”
• “Once the warning is cancelled, who needs to resume work, and at what time?”
• “How will Payroll know which records are normal attendance and which are temporary shift changes?”
When a company still relies mainly on WhatsApp, handwritten lists and multiple Excel files, HR, operations and Payroll can easily end up with different versions of the same information. An HR system may not make every weather-related decision for management, but it can connect decision-making, notifications, attendance, shift changes and data review to reduce confusion during unexpected events.
Using common Hong Kong SME scenarios, this article explains how adverse-weather work arrangements can be translated into an HR system, and what should be clarified before selecting or implementing one.
Who is this article for?
Hong Kong business owners, HR, administration, Payroll and operations managers with shift-based, frontline, multi-location, remote or hybrid teams—particularly SMEs considering the implementation or improvement of an HRIS / HR system.
First, understand this: an HR system is an execution tool, not an adverse-weather policy itself
The Labour Department recommends that employers consult employees as early as possible and set out work arrangements during and after adverse weather and “extreme conditions”, including reporting for work, leaving work, resumption of work and remote work where applicable. Businesses should formulate suitable arrangements according to their industry, operational needs and the urgency of their services. View the Labour Department’s adverse-weather work-arrangement guidance
In other words, a system can help execute a process, but it cannot replace the company’s need to answer these questions first:
• Which roles can work remotely?
• Which employees are designated duty personnel?
• Who can decide on early release, work resumption, shift changes or activating WFH?
• Who reviews records for transport, duty arrangements, additional working hours and pay?
• How can employees report safety or transport difficulties, and how are these escalated?
Set a clear policy before configuring the system. If a business enables numerous buttons and statuses before its rules are settled, it will only digitise the confusion.
The five types of information an HR system should handle during adverse weather
1. Employee lists and work arrangements
The system should enable the company to see clearly who belongs to the following groups:
• Remote-work / hybrid-work roles;
• General office personnel;
• Designated duty personnel;
• Shift-based or frontline personnel; and
• Personnel temporarily redeployed, on standby or working off-site.
This is not about labelling employees. It is about ensuring that notifications, attendance records and roster arrangements reach the right people. If an operations manager needs to confirm the minimum staffing level for the day within two hours, the risk is naturally higher when they need to search old Excel files or group messages.
2. Centralised notifications and acknowledgement
The biggest risk with adverse-weather notifications is that they have been “sent” but no one knows who has seen them. When integrated with company communication tools, an HR system can help to:
• Send arrangements to particular departments, locations or roles;
• Separate notifications into “information only” and “acknowledgement required”;
• Record whether employees have read, acknowledged or reported difficulties;
• Retain message versions and sending times, so records can be found if a dispute arises later; and
• Update information through one official channel, reducing the risk of managers issuing inconsistent messages.
A system notification should not simply say, “Everyone should make their own arrangements.” Clearer content should state the applicable period, intended recipients, work / remote-work / duty arrangements, reporting contact and the time of the next update.
3. Attendance, remote-work and shift-change records
On an adverse-weather day, employees may have various statuses: leaving early, being unable to arrive safely, switching to remote work, remaining on duty, working longer hours or changing shifts for service needs.
Businesses can set a limited and clear set of attendance codes in the system, for example:
Suggested status | Purpose | Who should review it? |
|---|---|---|
Normal attendance | Attending the workplace or working in the usual agreed manner | Direct supervisor / roster manager |
Temporary remote work due to adverse weather | Working from a remote location under the company’s arrangement | Direct supervisor |
Designated duty | Working on duty under the company’s arrangement during the relevant warning or extreme condition | Operations manager + HR / Payroll |
Early departure (company arrangement) | Leaving early for safety or transport reasons | Supervisor |
Unable to arrive / delayed resumption due to adverse weather | Prevented by adverse weather or other uncontrollable factors | Supervisor + HR, where needed |
Temporary shift change / standby duty | Alternative arrangement due to operational needs | Roster manager |
The key is not to create as many statuses as possible. Each status needs a definition, eligibility criteria and a reviewer. Otherwise, Payroll will still have to ask about individual cases on WhatsApp at month-end.
Pay and attendance: do not treat a “system-recorded absence” as an automatic basis for salary deduction
The Labour Department’s at-a-glance guide states that where an employee does not need to report for work, leaves the workplace early, cannot return to the workplace or cannot resume work promptly due to adverse weather, “extreme conditions” or uncontrollable environmental factors, employers should not deduct the employee’s wages, attendance bonus or allowances. Employers should also not require employees to make up the reduced working hours later, or use them to deduct annual leave, statutory holidays or rest days. View the Labour Department’s at-a-glance guide
This is an important reminder for system configuration: a missed clock-in must not be automatically converted into unpaid absence or a deduction item.
A more prudent design is to:
• Have the employee or supervisor submit the day’s status first;
• Mark it in the system as “pending review” or with the appropriate adverse-weather attendance code;
• Have the supervisor check the work arrangement and actual circumstances;
• Have HR / Payroll review exception records before payroll processing; and
• Handle duty arrangements, transport and additional working hours according to the company’s established policy.
Businesses should avoid an automated “deduct first, correct later” rule. An inaccurate wage or attendance-bonus deduction not only creates more administration; it can also affect employee trust and potentially expose the business to legal risk.
Designated duty personnel, transport and additional arrangements: systems should record exceptions, not just time
The Labour Department’s Code of Practice states that employers should notify designated personnel in advance of the arrangements and contingency measures for returning to the workplace on duty during adverse weather and “extreme conditions”. During a No. 8 or higher tropical cyclone warning, a Black Rainstorm Warning or an “extreme condition”, where public transport is suspended or operates only on a limited basis, employers should provide safe transport for employees who need to return to the workplace on duty, or provide an additional allowance.
Therefore, clock-in data alone may not be enough. The system or related process can include:
• Lists of duty personnel and backup personnel;
• Actual arrival and departure times, including whether a temporary shift change was involved;
• Records of transport arrangements or expense claims;
• Whether additional rest, meals or safe transport arrangements were provided;
• Who approved the arrangement and when; and
• Relevant attachments, such as transport receipts or approved work arrangements.
However, a company should not assume that it may require employees to report to the workplace in any weather merely because the system has a “designated duty” button. The Labour Department emphasises that employee safety should be the primary consideration and that the number of employees required to work at the workplace should be kept to a minimum. Source: Labour Department Code of Practice
A practical HR-system workflow: from weather alerts to Payroll review
This workflow does not need to be overly complicated. The key is that someone is responsible for each stage.
Step 1: Establish triggers for weather-response assessment
Management should determine in advance which weather signals or actual conditions trigger an assessment. The system should not automatically assume that every warning means company-wide WFH. Once triggered, designated decision-makers should make arrangements according to safety, transport and operational needs.
Step 2: Send arrangements by employee group
Using role, department, location or roster data, the system sends relevant notifications to different groups: remote workers, designated duty personnel, general personnel or managers. Notifications should allow employees to report safety or transport difficulties.
Step 3: Employees / managers update attendance status
Employees can confirm remote work, arrival at the workplace or actual difficulties through the system or a designated channel; managers are responsible for checking and handling exceptions. For frontline staff without system access, businesses should retain an alternative reporting method.
Step 4: Operations managers handle shift changes and minimum staffing
The system should let managers see which shifts are understaffed, who is available as backup and who has arrived safely, while retaining the shift-change decision. This helps avoid omissions caused by verbal handovers.
Step 5: HR / Payroll reviews exception records
Before the Payroll cut-off, HR / Payroll should review exceptions centrally, including inability to report for work, remote work, early departure, designated duty, transport allowances and additional working hours. The role of the system is to consolidate information; it does not remove the need for human judgement.
Step 6: Review after the event and update rules
After each event, review whether notifications were timely, whether employees could report smoothly, whether managers understood the status definitions, and whether Payroll had to manually correct a large volume of data. If the same issue arises every time, it is the process or system configuration that needs to change—not simply a reminder for employees to “be more careful next time”.
Seven questions to ask about adverse-weather functions when selecting an HR system
• Can the system send notifications by department, location, role or shift group?
• Can employees and managers acknowledge, reply to or submit exception cases?
• Can attendance statuses distinguish between WFH, designated duty, early departure and temporary shift changes?
• Can the system include a review workflow, rather than sending data directly into Payroll automatically?
• Is it easy for frontline employees or staff without company email to use?
• Can it export clear records so HR, operations and Payroll use the same version of the data?
• Will the system provider or implementation consultant first understand the company’s policies and work processes?
If a provider only demonstrates an attractive dashboard but cannot explain how your shifts, attendance exceptions, permissions and Payroll handovers will be handled, the system may not truly fit your operating model.
Four common blind spots to address before HR-system implementation
1. Treating all employees as having the same work arrangement
Office staff, frontline staff, shift workers, field staff and management all face different work constraints. System configuration should reflect the reality of each role, rather than applying one rule to everyone.
2. Only IT or the provider knows how the system works
Adverse weather is when HR, operations, Payroll and management all need to use the information. Businesses should set clear access rights and operating guidance for different roles, rather than allowing one colleague or external provider to hold the entire critical process.
3. No human-review checkpoint
Automation can improve efficiency, but it cannot replace judgement about safety, transport, employees’ actual difficulties and company policy. Appropriate review and correction processes should be retained, particularly where pay or benefits are involved.
4. No testing in normal times—the first use is when bad weather arrives
Policies, system statuses, message templates and manager permissions should be tested during normal operations. A simulated notification, test for a designated group or short manager exercise can identify problems with logins, data synchronisation or division of responsibilities.
Need Help Turning Adverse-Weather Policy into a Working HR Workflow?
If your policy is written but managers still need to handle notifications, attendance statuses, shift changes and Payroll checks manually, Get More can help map the process and identify where system support is practical.
We can help you review:
the steps from weather announcement to employee communication;
attendance, remote-work and shift-status handling;
manager permissions and Payroll handover points; and
HR system settings and implementation priorities.
Contact Get More to discuss your HR system requirements:
Let Get More become your strategic HR partner and support your company in making the right decisions.
Further Reading
Adverse-weather HR-system FAQs
1. Should the system automatically switch everyone to WFH whenever there is a Black Rainstorm Warning or a No. 8 typhoon signal?
A blanket approach is not advisable. The Labour Department recommends that employers establish suitable arrangements according to their industry, operational needs and the urgency of their services. Some work can be handled remotely, while some roles involve frontline or facility-safety needs. The system should support the business in implementing a decision already made; it should not replace management judgement. View the Labour Department’s work-arrangement guidance
2. If an employee has not clocked in, can the system automatically mark it as unpaid absence?
A missed clock-in status should not be treated as conclusive. The Labour Department’s at-a-glance guide states that employers should not deduct wages, attendance bonus or allowances where an employee cannot report for work or resume work promptly due to adverse weather, “extreme conditions” or uncontrollable environmental factors. Businesses should set a review workflow and handle matters according to the actual circumstances. View the Labour Department’s at-a-glance guide
3. Can an HR system manage transport allowances for designated duty personnel?
Many systems can record relevant information through custom fields, application workflows or Payroll integrations, but suitability depends on company policy and system capability. Businesses should first specify designated personnel, approvers, required documents and payment principles before asking the system to execute the process.
4. How can frontline employees without smartphones use the system?
The company should provide workable alternatives, such as centralised entry by supervisors, a designated telephone / SMS channel or a later record update after work has resumed. System design must not assume every employee can be online in the same way at the same time.
5. Must the system record every minute worked on a WFH day?
Not necessarily. Businesses should decide on an appropriate record-keeping method based on role, management needs, data privacy and company policy. The priority is clarity around work arrangements, attendance status, handovers and payroll data—not collecting data for its own sake.
6. If an SME does not yet have an HR system, does it need to buy a large platform immediately?
Not necessarily. First assess headcount, shift complexity, existing Payroll processes, data sources and the areas where errors occur most often. For some businesses, it is more practical to organise policies and basic information first, then select a solution that can scale gradually rather than buying a large number of features that may not be needed.
References
• Labour Department: Work Arrangements in times of Adverse Weather and “Extreme Conditions”
• Labour Department: Code of Practice in times of Adverse Weather and “Extreme Conditions”
• Labour Department: At-a-glance Guide to the Code of Practice in times of Adverse Weather and “Extreme Conditions”
• Occupational Safety and Health Ordinance (Cap. 509) and Factories and Industrial Undertakings Ordinance (Cap. 59). Refer to the Labour Department Code of Practice above for the relevant safety-responsibility guidance. Before publication, verify the latest provisions on Hong Kong e-Legislation.
• Employees’ Compensation Ordinance (Cap. 282). For compensation arrangements for work-commute accidents during adverse weather and “extreme conditions”, refer to the Labour Department Code of Practice above and the latest official information.
Disclaimer
Disclaimer: This article is for reference only and is intended to provide general legal information and HR management guidance. It does not constitute legal, employment, payroll, IT or other professional advice. Actual work, attendance and pay arrangements during adverse weather and “extreme conditions” depend on individual circumstances, including company policy, employment contracts, the nature of work, weather conditions and transport conditions on the day. For specific situations, please consult a qualified HR consultant or legal professional and refer to the latest information from the Labour Department and other relevant official bodies.
