People
A reliable record of everyone in your organisation.
Not a directory with job titles in it. The actual record — what somebody is contracted to, who they report to, what they have taken, what you hold on file, and every change anybody has made to any of it.
The record people actually ask questions of.
“How much holiday has she got left?” “When does his passport expire?” “Who approved that pay rise?” Three questions that normally take three systems and a phone call.
Here they are one screen, and every figure on it can be traced back to the thing that produced it — the policy, the working pattern, the request somebody approved, or the opening balance a company brought with it when it moved onto GarnetOS part-way through a holiday year.
People · Employees
Priya Nair
EMP-014
Operations Manager · Operations
Started 4 March 2024 · Marlow Ltd
Annual leave · 2026
9.5
days left
- Allowance
- 28
- Carried in
- 3
- Taken
- 21.5
Documents
- PassportIn 24 days
- Employment contractNo expiry
- Right-to-work check3 Mar 2026
What it covers
Six things, one record.
Employee records
Personal details, employment terms, job history and pay history, each with the date it took effect — which is rarely the date somebody typed it in. Sensitive fields are a separate permission, so an administrator can edit a job title without seeing a passport.
Organisation
Teams, reporting lines, locations and legal entities. A company with two entities is ordinary rather than an upgrade, and moving somebody between them keeps their history.
Leave
Allowances worked out from the policy and the working pattern — pro-rated on joining and leaving, carried over within the cap, with bank holidays handled per nation. Requests are costed against the pattern in force on the day, then stored, so a later change does not silently restate leave somebody already took.
Attendance
Days derived from the working pattern, with exceptions raised where reality and the pattern disagree. Imports from an existing time system sit above the pattern and below anything a manager corrected by hand.
Onboarding and offboarding
A checklist that surfaces work rather than a process that silently performs it. A leaver produces the list of things somebody has to decide — reporting lines, open actions, access, final leave — instead of the silence that normally follows a departure.
Documents
Contracts, certificates and identity evidence against the person they belong to. Anything with an expiry is watched, and the reminder arrives as an action rather than an email somebody archives.
Joining
From first record to ongoing watch.
Onboarding is where most HR systems stop and most companies start improvising. Here it is a checklist that keeps producing work until there is none left — and then keeps watching.
Record created
Name, start date, job, legal entity.
Documents requested
The person is asked for what is missing.
Account invited
They set their own password. Nobody emails one.
Evidence reviewed
Somebody checks each document and signs it off.
They start
Leave allowance opens, pro-rated from the start date.
Still watching
Expiries, probation dates and changes keep raising actions.
Moving in
Bring your history with you.
Nobody adopts a system on 1 January. They adopt it in October, when the spreadsheet has gone wrong — and by then half the company has already taken most of its holiday.
So a balance can carry an opening position: the days brought forward, the days already taken elsewhere, and where those figures came from. Record it once and everything downstream is right from the first day you use the product, rather than over-stating what people have left until somebody notices.
The source is required, not optional. A year later, when somebody disagrees with their balance, “eleven days, from the holiday spreadsheet as at 30 September” is an answer. “Eleven” is not.
See what one system could replace.
Half an hour, the real product, and an honest answer about whether it fits how you work today.
Request a demo