Home
Build the weekly roster, let employees confirm and swap shifts in the app, and check their attendance against the shift. Leave, labour cost and a payroll hours file, in the same system.
From the weekly roster to the payroll hours file
Build the weekly roster on a board, drag a shift to another employee and publish the week in one click. The system blocks assigning one employee to overlapping shifts and flags an employee with approved leave.
Employees confirm or decline a shift in the app and get an in-app reminder 24 hours, 4 hours and 1 hour before the answer is due. Swap requests and requests to take an open shift go to a manager for approval.
Each employee marks when they can work each week and adds dates when they are unavailable. The manager sees the whole team's availability and the clashes with shifts already assigned.
Employees clock in and out from the app, the browser or by scanning a QR code. The business can require a geofence, the office IP address or a photo at clock-in. The manager sees who is at work and is alerted to no-shows, late arrivals, early leaves and forgotten clock-outs.
Employees request one of 7 leave types - vacation, sick, reserve duty, maternity, bereavement, personal and other - with a document attached when needed. The manager approves or rejects, and the employee's balance updates.
Actual labour cost by week, site or department, against a target the manager sets. Hours beyond 8 in a shift count as overtime, and at month end the manager approves, locks the month and exports an hours file for the payroll software.
Tasks with a photo as proof of completion, report forms employees fill in on their phone, a notice board with read confirmations and an onboarding checklist for new hires.
The system flags exceptions; it does not certify that the business complies with the law. The binding pay calculation is done in the payroll software.
Every hour beyond 8 in a shift counts as overtime. The system's cost estimate prices each overtime hour at 125%.
A missing break or one shorter than 45 minutes on a day over 6 hours, under 8 hours of rest between work days, no 36-hour weekly rest, more than 12 hours a day or 42 a week.
A shift that starts or ends between 22:00 and 06:00 is marked as night hours, and Friday and Saturday hours are marked separately in the report.
Every hours correction is recorded: who changed it, what changed and when.
Managers on a computer or phone, employees in the app
Managers schedule, approve and run reports from a computer or phone. Employees see their shifts, clock in, request leave and complete tasks in the app.
Experience a powerful interface designed for productivity on any screen
For businesses whose employees work shifts, across several sites or in the field, not only fixed hours.
The roster lives in the system, not in a spreadsheet sent as a picture. Each employee sees their own shifts, confirms them and asks for swaps, and the manager sees who has confirmed and who has not.
See it in a demo →Each clock-in is checked against the shift: late arrivals, early leaves and no-shows are flagged automatically. The clock-in methods, geofence and offline clock-in are on the time tracking page.
To time tracking →Approved hours go out as a file for your payroll software, or on to payslips in the Lynxbe payroll module.
To payroll and payslips →Related modules: HR and employee files · Time tracking and attendance · Payroll and payslips · Field sales teams
The common ways businesses run shifts and attendance are an Excel sheet sent to a WhatsApp group, a dedicated shift-scheduling app, an attendance system (such as Synerion or Meckano), and an international workforce management (WFM) suite for large organisations. The comparison is by tool type, not a specific product; where it says "depends on the tool", check with the vendor.
| Topic | Excel and a WhatsApp group | Shift-scheduling app | Attendance system (Synerion, Meckano) | International WFM suite | Lynxbe |
|---|---|---|---|---|---|
| Building the roster | Manual, in a spreadsheet | The core of the tool | Depends on the tool | In most tools | Weekly board with drag and drop, templates and week publishing |
| Shift confirmations and swaps | Messages in the group | In most tools | Depends on the tool | In most tools | Confirm, swap and open shifts, with manager approval |
| Reminders to employees | Manual | Depends on the tool | Depends on the tool | Depends on the tool | In-app reminder before the answer is due; not by WhatsApp or SMS |
| Attendance against the shift | Manual record | Depends on the tool | The core of the tool | In most tools | App, browser or QR, with a geofence, IP or photo |
| Leave and balances | A separate sheet | Depends on the tool | In most tools | In most tools | 7 leave types, manager approval and balances |
| Export to payroll software | Retyping | Depends on the tool | In most tools | Depends on the tool | Files for Hilan, Michpal, Shiklulit, Oketz and Excel |
| Automatic demand forecasting | None | Depends on the tool | Depends on the tool | In some tools | None. There is a weekly cost target against actual cost |
| CRM, WhatsApp and invoicing in the same system | No | No | No | Depends on the tool | Yes, on the same platform |
Everything you need to know about this module
Book a demo and we will show you shift scheduling, confirmations and swaps, attendance against the shift and the payroll hours file.
Get the Lynxbe app
Review access, privacy, encryption, retention, and audit controls against your organisation's requirements. Certification or legal compliance is confirmed only with current independent evidence and legal review.
Define roles, permissions, sensitive-data scope, and approval paths, then verify them in a test environment before production access is granted.
Map access, correction, export, deletion, consent, and retention workflows to the legal requirements that apply to your organisation. Regulatory compliance depends on configuration and operating processes and requires legal review.
Confirm transport encryption, storage protection, backup handling, and secret management for the selected services during the security review.
Review account scoping, role boundaries, administrator access, and integration permissions against your security requirements before launch.
Review which user and configuration events are recorded, how long logs are retained, and which exports are available for the modules you select.
Define access, export, retention, and deletion requirements during implementation and verify the workflow for the modules and jurisdictions you use.
For more information, please review our App Privacy Policy, Privacy Choices, and Terms of Service.
