Attendance is collected by hand
Registers and sheets are typed in at month end, and the corrections arrive after the numbers have already been used.
HR
Employees, attendance, leave and shifts sit in the Core OS next to the branches, warehouses and roles they belong to. Who is on shift, who is on leave and who approved it are records, not a rota on a wall and a leave sheet in someone’s inbox.
The problem
None of it is complicated. It is just done by hand, in several places, by people who have other jobs.
Registers and sheets are typed in at month end, and the corrections arrive after the numbers have already been used.
Balances are disputed because nobody can see the same figure, and an approval sent from a phone is easy to lose.
The warehouse finds out it is two people short when the shift starts, not the afternoon before.
When someone moves branch or leaves, their system access is a separate task, so it is the one that gets missed.
Capabilities
Five groups, held next to the branches, departments and roles already in the Core OS.
One record per person, from joining to exit.
Who was in, recorded once.
Balances that are worked out, not argued about.
Cover planned before the shift starts.
Joining, claims and leaving, with the access that goes with them.
Workflow
The request, the balance, the approval and the cover are one record, so nobody has to ask where it got to.
A leave request moves through six stages: application, balance check, manager approval, shift cover, attendance and the monthly summary.
01 Request
LV-2026-0057
Applied
02 Balance
LV-2026-0057
Available
03 Manager
LV-2026-0057
Approved
04 Shift cover
LV-2026-0057
Covered
05 Attendance
LV-2026-0057
Marked
06 Summary
LV-2026-0057
Included
Use cases
Shift assignments per warehouse, so the supervisor can see tomorrow’s cover today and fill a gap before anyone is waiting at the dock.
Each branch manager approves leave and attendance for their own people, and HR reviews every branch in one place.
Claims raised with the receipt attached, approved by the manager, and posted to the ledger through Finance rather than re-entered.
Works with
These read and write the same Core OS records, so a handover between them passes a reference rather than a retyped copy.
Invoicing, receivables, payables and one double-entry ledger.
Planning, picking, loading and proof of what actually left.
Trips, carriers and freight cost landing on the right consignment.
Bills of material, work orders and quality checks.
FAQ
This page covers employee records, attendance, leave, shifts and claims. Payroll depends on your country’s statutory rules, so talk to us about it directly — we would rather tell you exactly what is covered for you than promise a checkbox.
Yes. An employee with a login applies against their own balance, the request goes to their approver, and the balance changes when it is approved. Nobody keeps a second copy.
Marked daily by a supervisor or recorded from employee check-ins. A correction is raised as an attendance request and approved, rather than edited without a trace.
Access follows Core OS roles. A branch manager sees their own team; HR sees everyone; nobody else sees personal records unless a role gives them that.
Have a different question? Talk to us.
Bring a month of attendance sheets and this week’s rota. We will show what they look like as records the whole business can read.