No Microsoft subscription required
People, positions, reporting lines, teams and calendars use our keys. Teams and Entra are optional add-ons. Your workforce record works without either.
HRMS - workforce system of record
Your workforce record.
Not your vendor’s.
People, positions, rotas, attendance, leave, hiring and growth, all in one place and keyed by us. Teams and Entra are optional add-ons, so nothing breaks when a subscription lapses.
Hire to retire
One record, from first interview to last day.
Most teams run hiring in one tool, time in another and the employee list in a third, then join it all up by hand. This keeps it together.
Architecture
Job families and grades
Your job families, grades, profiles, salary bands, skills and headcount plans. Each one dated, so last year still reads correctly.
Hire
Recruitment to offer
Open a role, work the candidates, screen resumes, plan and book interviews, then make the offer.
Core HR
Employee master and org
Who works here, in what position, reporting to whom, on which team. Keyed by us, linked to your sign-in.
Time
Shifts, attendance and leave
Published rotas, attendance checked against the right calendar, and leave that somebody else has to approve.
Grow
Goals, reviews and learning
Goals, reviews, learning records, pay and benefits enrolment.
Exit
Cases and separation
Employee cases, leavers, and the laptop-and-access tasks that joining or leaving kicks off.
Provider-neutral by design
Optional add-ons. Never a dependency.
If your HR system keys its employees to a chat tool, that vendor now owns your workforce record. We do it differently. We keep our own keys, link to your sign-in instead of copying it, and treat every outside system as a source of facts rather than the source of truth.
Identity links, never copies
An employee links to a permanent ID, not to a username someone can change. Outside accounts are stored separately, so renaming one breaks nothing.
Providers are authorities, not owners
An outside system is only right about what it created, like a rota or a clock-in. You can keep that here instead. The maths is the same either way.
HRMS calls no provider directly
Outside data comes in through Connectors, which holds the credentials and the consent. No provider password ever sits in your HR system.
The leave lifecycle
Nobody approves their own time off.
Every step says who is allowed to take it. You draft, submit and can withdraw. Someone else approves or rejects. Leave only counts as taken once the last shift has ended, and only closes when attendance agrees. If your calendar or allowance changed after you submitted, you submit again.
01
Draft
Owner edits, versioned
02
Submitted
Plan must still match
03
Approved
A separate authorized human
04
Taken
Only after every shift ends
05
Closed
Needs calculated On leave
Suggested actions
Agents suggest. People decide.
HR is the wrong place for software acting on its own. Arin reads what is already saved and prepares a suggestion. A named person with the right authority makes every change.
Time off imported from a calendar is not an approval. It tells you someone said they were away. It does not decide that they can be.
It shows its work
Each suggestion names the person, the change, the reason, the record behind it and what happened before. The technical detail stays tucked away.
Reading changes nothing
Opening or refreshing a suggestion changes nothing. Nothing in HR approves itself.
It infers no identity
Arin reads the same saved records your own screens read. It adds no outside calls, no credentials, and no guesses about who someone is.
Attendance you can defend
Reconciled against a policy you reviewed.
Attendance is more than a clock-in log. We compare what was recorded against the right calendar, using the lateness and early-leaving allowances your HR team set and signed off. We assume no policy on your behalf.
- An assigned shift overrides the usual pattern from the day it starts
- Finished clock-ins count time worked, minus unpaid breaks
- Missing calendars and bad dates get flagged for review, never guessed
- Entries typed here and data imported run through the same maths
Hiring with evidence
A shortlist that shows its reasoning.
Assisted screening reads a saved application's PDF or DOCX and extracts skills, experience, titles, employers, education, certificates and location - identified by file checksum, parser version and skill-library snapshot. A reviewer corrects what it got wrong, and re-extracting the same source preserves those corrections.
- The shortlist shows its reasoning against your skill records, not a hidden score
- It never moves, rejects or hires anyone on its own
- Needs no Microsoft or Teams account at all
Job architecture
Structure that remembers last year.
Job families, grades, profiles, salary bands, skills and headcount plans are yours. We seed nothing underneath them. Each one is dated, and the same code can have several periods, so a grade that changed in April still reads correctly for March.
It will not let itself contradict itself either. A profile needs one active family, grade and skill set covering its whole period, and you have to close an open period before starting a new one.
The workforce dashboard
Who is on shift, present, late, absent, on leave.
The overview reads your saved records. Attendance as it stands, absences as approved, leave as it is now. It calls nothing outside and works nothing out on the fly.
Dates mean the work date that was saved. A shift that ran on Tuesday still reads as Tuesday, whichever timezone you open it from.
HRMS in the workforce stack
Who owns the employment record.
HRMS owns the employment record. Payroll postings, sign-in and issued laptops stay with the systems that already own them.
HRMS walkthrough
See the workforce record, end to end.
Tell us where your people data lives today. Directory here, rotas there, spreadsheets in between. We will show you what it looks like in one place.