Attendance & operations
Attendance Management for Retail and Restaurants in the Philippines
By ElevenOS ··5 min read
For a Philippine shop, café or restaurant, attendance management starts before anyone clocks in. The opening crew needs a published shift, the closing crew needs a clear end date, and the supervisor needs a way to explain changes before payroll cutoff. A time record becomes useful when it connects the employee, expected schedule, actual punches and reviewed exceptions. This guide gives SME owners and HR managers a practical workflow for busy service teams, whether you operate one location or are evaluating a wider branch setup.
Published by ElevenOS. Product scope and quotes can change; confirm your requirements with each provider.
In this guide
7 sections
1. Publish a roster employees can follow
Start with the hours your business needs covered, then assign people to those shifts. Separate opening, peak-service and closing responsibilities. Give every employee an identifiable workday and rest-day arrangement under your company policy. A roster in a supervisor's chat is difficult to reconcile if the attendance system still expects a different shift.
Choose who can publish and revise schedules. When a server swaps a shift or a cashier covers an absent colleague, record the approved change in the schedule workflow. Tell both employees which assignment now applies. Before the week begins, ask a sample employee to find their next shift; this checks that the roster is usable beyond the administrator's screen.
2. Explain clocking at the real workplace
Show employees when and where to record attendance, which device permissions are needed and whom to contact when a punch fails. Test at the locations people actually use, such as a mall entrance, restaurant kitchen or loading area. A demonstration beside the office window does not establish how a phone will behave inside your store.
ElevenOS Starter includes attendance with GPS clocking and workplace geofencing. The outcome of a boundary exception depends on your configured policy and the available location reading. Accuracy and permissions can affect the result. Agree a reviewable fallback for unavailable readings and explain that a location captured during clock-in is separate from ongoing location sharing.
3. Check dates on late closing and overnight work
Consider a fictional restaurant employee whose scheduled shift starts at 6 p.m. on Friday and ends at 1 a.m. on Saturday. Review the shift as a connected work period, with the correct dates on both punches. Searching only Friday's calendar events can hide the Saturday clock-out and make the record appear incomplete.
An actual closing time may also differ from the published schedule. Ask the responsible supervisor to explain the difference and complete any required overtime decision under the company policy. The employee staying later and the company approving the resulting pay treatment are separate facts. Keep both understandable for the attendance reviewer and payroll owner.
4. Resolve missing punches without creating duplicates
Review exceptions during the week while the employee and supervisor can still explain them. For each case, check the expected shift, original clock events and relevant leave or schedule changes. If a punch exists but its time is wrong, use the correction workflow. If an event is genuinely absent, use the supported missing-punch or manual-entry process.
In ElevenOS, Correct recorded time addresses an existing punch; manual attendance supports missing events. Preserve the original history and provide a reason that identifies the problem and evidence checked. After the required approval, review the resulting open attendance totals. Adding a second event without checking the first can leave an overlapping session instead of resolving the exception.
5. Give branch review a clear owner
At several locations, a local supervisor may know why a shift changed while central HR prepares the cutoff. Maintain consistent branch names and employee assignments. Name the reviewer for each location, the person covering their absence and the owner of cross-branch cases. For an employee supporting another store, check the schedule and approved workplace as well as their usual organizational assignment.
ElevenOS Business includes multi-branch operations. During evaluation, test what a branch supervisor can see and approve using their actual role, rather than an administrator account. Confirm any separate employer or legal-entity requirements with the implementation team. A branch structure alone does not establish the setup for several distinct employing companies.
6. Hand payroll a reviewed attendance cutoff
Set a branch review deadline early enough for central HR to resolve questions before payroll preparation. The handoff should identify the attendance date range, reviewed employees, approved corrections and any unresolved item with an owner. Check new hires, departures, approved leave and transfers that apply to only part of the period.
After changes, refresh and review the affected open totals, then complete the required attendance review steps. Payroll preparation still needs its own calculation and approval checks. ElevenOS Growth adds timesheets, Philippine payroll and payslips; Starter covers core HR, attendance, schedules and leave. Payroll preparation, payslip publication, payment and agency filing remain separate responsibilities.
7. Pilot the process through a service week
Choose a small group covering an opening shift, a late close and a supervisor's approval work. Use anonymized examples for a shift swap, missing clock-out and approved leave. Ask each person to perform their own step. Keep a short issue list showing the scenario, expected result, actual result and person responsible for resolving the difference.
Bring the pilot results, employee count and location structure to an ElevenOS walkthrough. Review the retail or restaurant workflow and choose the plan by the work you need covered. Expand after employees can find their schedules, supervisors can resolve exceptions and the payroll owner understands the handoff. Keep the same named owners when adding the next location.
Frequently asked questions
4 answers
