See who changed what in HR - and why.
When someone edits a shift, a leave rule, an employee record, a letter template, or payroll setup by hand, the change is written down. Leadership can ask who did it, what it was before, and the reason - without reconstructing the week from chat messages.
A record of people’s changes, kept as they happened.
This is not a report you type up later. If your company uses the area, the change is listed with the person, the time, what it was before, what it became, and why.
The person who made the change
Before and after, in plain terms
The reason captured with the change
The list matches what your company actually uses
HR can answer the question. Owners can ask it. Managers are not blamed for a setting they never touched.
Same register. Three reasons it comes up the week an auditor, a founder, or an angry employee asks “who changed this?”
Answer “who changed the shift?” without a group interrogation.
Someone updates weekend days, a leave rule, a holiday, an approval path, or a person’s details. Weeks later nobody remembers. Change Audit is the register of those hand-made changes: the person, the time, the area, what it was, what it became, and the reason. You can filter to the parts of the product your company uses - people, time, leave, letters, payroll setup, policies - and download the list when someone official asks.
- A summary plus the full list, not a pile of unrelated noise
- Search by the kind of change, the area, and the product you subscribe to
- Download for the people allowed to export
If pay or attendance rules moved, you should be able to see the hand that moved them.
A founder does not need every automatic update that happens overnight. They need the moments a person decided something: a policy, a salary setup, an exit rule, a department head, a letter that went out. The entry stays. It is not a note someone can quietly rewrite after the question is asked. That is why this sits on Professional and Enterprise.
- Before and after, so “we always did it this way” can be checked
- Covers HR, and also visitor, IT asset, and payroll changes when you use those
- You only see change types for areas your plan actually includes
A rule change should not land on the person who merely followed it.
Managers live with the result: a new shift, a new approval step, a probation decision, a time correction that was approved. When leadership asks why the rule changed, the answer should be the person who changed it - not the manager who applied it on Monday. This register is an HR insights screen, not a manager’s personal diary.
- Attendance corrections and approval decisions can be part of the same history
- The list is limited to changes in areas the company uses
- Managers are not asked to keep a parallel spreadsheet of “what HR edited”
Why “check with whoever was online” is not an audit.
Every company can tell you that someone changed a shift or a leave rule. Very few can tell you who, what it was before, and why - without opening five inboxes.
Ask in the HR WhatsApp group
The person who changed it is on leave, and the message is gone
A register with the person, the time, and the reason
Trust the last person who had admin access
Several people can edit settings. Memory picks a culprit
The entry names who actually made that change
A yearly folder of “policy PDFs”
It does not show the Tuesday edit to weekend rules
Hand-made setup changes are listed as they happen
Only attendance punch corrections are logged
The argument was about the shift rule, not one person’s punch
Corrections and the rules around them live in one register
A log so long nobody opens it
Visitor and asset noise buries the HR change you need
You only see change types for products and features you use
Someone edits the note after the dispute starts
The record becomes the story that is convenient today
Entries stay as written, and you export them
The “who touched this?” moments teams stop dreading.
Each one is a real argument that a written change record can settle.
A shift’s timings changed and payroll no longer matches what the floor remembers.
The shift create, update, or switch-off is listed with who did it and what the times were before.
Leave rules or approval steps moved, and half the company is on the old path.
Leave setup and approval-path changes are recorded with before and after.
A holiday or weekend setting was edited the week before a long weekend.
Those calendar changes are in the same register, not in someone’s inbox.
An employee record, a bulk join, or a department change has no author.
People, onboarding, and organisation-structure changes name the person who made them.
A letter template or a policy was edited and nobody can say which version went out.
Letter and policy changes are listed alongside the other hand-made edits.
Payroll setup changed and finance wants the reason, not a shrug.
Pay-setup changes are included when your company uses payroll, with the reason captured on the entry.
Someone could “clean up” history after a dispute starts.
The register is kept as written. You read it and export it. You do not edit the past entry to make the story nicer.
A company that does not use visitors or assets still sees a junk list of those changes.
The catalogue only offers change types for areas your company has switched on.
An auditor asks for three months of “who changed HR settings” and HR has a week to invent it.
Filter by area and date, then download the register you already have.
Six reasons a change list beats a memory.
If the record can be edited later to hide a mistake, it is not a record leadership can trust.
People’s changes, not every automatic job
Overnight routines are a different story. This register is for changes a person made: create, update, switch off, approve, and the like.
Before, after, and why
A timestamp alone does not settle an argument. The entry keeps what it was, what it became, and the reason.
The list matches your company
If you do not use payroll, visitor management, or assets, those change types are not offered. You are not scrolling past products you never bought.
It covers more than attendance corrections
Time corrections matter. So do shifts, leave rules, people records, organisation structure, letters, policies, probation, and pay setup.
You can take it out of the product
People allowed to export can download the filtered list when an auditor, a board, or a lawyer asks for a file.
The entry stays
This is a record of what happened. It is not a note HR rewrites after the question arrives.
What you can actually do.
Time, leave, and approvals
- Shifts created, updated, switched off, or switched back on
- Attendance rules and how those rules are assigned
- Holidays, weekends, and leave setup
- Approval paths, including when a request is cleared from the company-wide queue
- Hand-made attendance corrections, with who acted and why
People and the organisation
- Employee record changes and one-by-one joining
- Bulk joining and the setup around it
- Departments, designations, and organisation structure
- Probation decisions that a person records
- Document types employees are asked to provide
Letters, policies, and pay setup
- Letter templates and generation choices in Document Studio
- Company policy and exit-setup changes
- Payroll setup changes when payroll is part of your plan
- Platform settings a person changed on purpose
Find the change you mean
- Filter by product area: HR, visitors, IT assets, or payroll - only if you use it
- Narrow to a feature, a kind of change, or what was changed
- A summary view and the detailed register
- Download the filtered list
What each entry holds
- Who made the change, and when
- What it was before and what it became
- The reason, when one was given
- The area of the product the change belongs to
- Only the change types your company is entitled to see
Who can open it
- An HR insights screen for people allowed to view the register
- Export is a separate permission
- Professional and Enterprise
- Sits beside security and access, as the story of what people changed
Professional and Enterprise. Same change record. Honest about Starter.
Starter still runs HR. The register of who changed what by hand is a Professional and Enterprise control.
Starter
Change Audit is not on Starter - on purpose.
- Day-to-day HR still runs
- No fake “audit” tile that cannot answer who changed a shift
- Move up when leadership needs a record they can trust
Professional and Enterprise
Same change register on both plans.
- Who, when, before and after, and why
- Filters that follow the areas your company uses
- Summary, full list, and download
- The entry is kept - it is not edited away later
What makes the approach different.
Named people, not “the system”
When a human changed a rule, the register names them. That is the difference between an argument and an explanation.
You can see the old value
“It changed” is weak. “It was 9:30, it became 10:00, and this person wrote the reason” is something a manager can accept.
One place for many kinds of edits
Attendance corrections are included. So are the settings around them - shifts, leave, people, letters, and pay setup - so you are not hunting five screens.
Your catalogue, not a generic dump
Change types appear only for areas the company has. A team without visitor management does not wade through visitor entries.
Export when the question is formal
Filter first, then download. The file matches the question you were asked, not the entire history of the company.
History is not a draft
The point of the register is that it survives the awkward meeting. You read it. You do not rewrite it.
Change Audit - questions buyers actually ask.
Stop rebuilding last month’s changes from WhatsApp and memory.
Book a short walkthrough: filter to attendance or employee records, open one change, and read who did it, what moved, and the reason. That screen is usually the whole conversation.
Trusted HRMS for Modern Businesses
