A term first.
If you have to explain carry over or probation tomorrow, start in the glossary. The sentence should be usable in a meeting, not only on a page.
The library
Guides and a plain-English glossary for the person who has to explain leave, pay or structure tomorrow, and for the person choosing whether this software fits.
From the library
Pay, leave, compliance, structure and performance, each term explained in a few honest sentences. Searchable, filterable, and written for humans.
Browse the glossaryA practical guide to org charts: why they go stale, how spans and layers actually work, and what it takes to keep a chart true for years.
Read the guideHow to design a leave policy that survives contact with reality: entitlements, carry over, approval flows, coverage, holidays and the Bradford factor.
Read the guideWhen spreadsheets stop working, what to ask vendors, why one-record architecture matters, and how to survive the data migration.
Read the guideA practical onboarding checklist from preboarding to day 90: documents, IT, manager prep, the first week, and how to measure readiness honestly.
Read the guideThe unglamorous core of HR compliance: expiry tracking, audit trails, statutory deadlines, and why the law follows where the work happens.
Read the guideWhy payroll errors really happen and the controls that stop them: validation before the run, anomaly detection, dual control and one record.
Read the guideA practical offboarding checklist: notice, handover, access removal, equipment return, final pay and the exit conversation, in the order they actually have to happen.
Read the guideWhat an HRIS actually is, how it differs from an HRMS or HCM, what belongs in the core record, and how to tell whether you need one yet.
Read the guideHow to run a probationary period that actually decides something: what to set at the start, when to review, and how to confirm, extend or end it fairly.
Read the guideHow to control overtime without losing the hours people really worked: approval before the fact, rates, records, and the gap between claimed and clocked time.
Read the guideBrowse by topic
Structure, reporting lines, span of control, and the questions a clear chart answers.
What a connected employee record looks like, and why copies of it cause quiet damage.
Statutory rules, multi entity payroll, and keeping every run defensible.
The optional intelligence layer: how it acts, recommends, drafts and surfaces when you switch it on.
How to read this library
If you have to explain carry over or probation tomorrow, start in the glossary. The sentence should be usable in a meeting, not only on a page.
Guides are for the week you are in: a chart, a leave policy, a first system. They teach the work, then point at the module that already does it.
A product claim only appears where we can show the screen. If the software cannot do it, the guide does not say it can. Honesty is the whole page.
Name the job. Say what changes for the buyer and for the person who will live in it. A page that only talks to procurement is a brochure, not a library.
Who is reading

An HR lead
You open carry over, PILON or right to work because someone asked in a corridor. The definition should be short enough to say out loud.

A manager
You need the difference between absence and leave, and who is already off, before you tap approve. A brochure will not help you on Thursday.

A joiner
Org chart, Day 1 checklist, mandatory learning. You should not need three logins to find who you report to and what is owed this week.

A buyer
You are testing whether one record can replace the spreadsheet, the folder and the second payroll file. These pages say what the software already keeps.
Keep reading
GlossaryThe words, then the screenSearch a term. Jump to a letter. Open the section that owns it. A word without a screen stays a definition.
GuideHow to build an org chartWhy a drawn chart goes stale, and what a living one is generated from. The card is the record.
GuideChoosing a first HR systemThe questions a buyer should ask before another tool copies the same person into a second file.
PlatformThe same person everywhereLeave, pay, hiring and the chart, reading one employee record. Nothing forks a second roster.No. Guides teach the work first. The product appears once, in a labelled block, and only for something the software already does.
The glossary. Search, jump by letter, or open the section. Each term is a few honest sentences.
Yes. Managers, joiners and payroll read the same pages as a buyer. The job is to make the week clearer, not to sell a stack.
No. The glossary is written by us. HARMONI AI is an optional add-on in the product, not the author of this library.
Your people, not a global demo
Import the roster. A manager should see remaining leave and named cover. An employee should open My Space and recognise their own days. Payroll should see the same person the chart already holds.
Lead with intelligence.