Here is a question that sounds trivial and is not: what was this person's job title in March?
In a spreadsheet the question has no answer. The cell holds their current title. When they were promoted somebody typed over the old one, and the old one stopped existing at that moment. Not archived. Gone.
In an HR system the question has an answer, because a promotion is not an edit.
Effective dating
Every job fact on this platform carries the date it became true. Job title, department, manager, salary, employment type, working pattern, location.
Changing one does not overwrite the previous value. It adds a new record that takes effect on a date, and the previous one keeps the period during which it applied. The record becomes a sequence rather than a snapshot.
That is the whole mechanism, and this is what it makes possible.
What you can answer that you otherwise cannot
A reference letter that is actually correct. Somebody asks what a former employee's role was between 2024 and 2025. The record knows, including the change halfway through.
A payroll recalculation for a month that has closed. If a backdated change is agreed in June effective from March, the system can compute what should have been paid in each of those months, because it knows what was true in each of them.
An organisation chart as it stood before the reorganisation. Useful for exactly the conversation where somebody says the old structure worked better and nobody can remember what it was.
An audit that asks who approved something and what authority they held at the time. Not what authority they hold now, which is the question a snapshot system accidentally answers.
A leaver's full history. Including the two internal moves everybody has forgotten about.
Future dating, which is the same mechanism pointed forward
Because a fact carries a date, that date can be in the future.
A promotion agreed in March and effective in June is entered in March. The system keeps reporting the old title until June, and then changes by itself. Payroll picks it up in the right month. The organisation chart redraws itself on the right day.
Nobody has to remember, and that is the real benefit. The most common failure in HR administration is not a wrong entry. It is a correct entry that nobody made, because the person who agreed the change in a meeting is not the person who maintains the records, and the note never travelled.
What it costs, honestly
This makes some screens more complicated than they would otherwise be. A field that could have been a text box is a text box plus a date, and every change asks a question that a spreadsheet does not ask.
It also means corrections and changes are different operations. Fixing a typo in a title is a correction to an existing record. Changing somebody's title is a new record. The system has to ask which one you mean, because it cannot tell, and being asked is mildly annoying on the day.
We think that is the right trade. The alternative is a system that is easier to type into and cannot answer a question a payroll auditor will certainly ask.
Where you actually see it
Anywhere a job fact changes, the form asks when it takes effect and offers today as the default.
The employee record shows the history rather than only the current value, so you can read the sequence of changes and see who made each one. Reports that cover a period use what was true during that period rather than what is true now, which is why a headcount report for last quarter does not change when somebody is promoted this quarter.
The one habit worth forming
Enter changes when they are agreed, with the date they take effect, rather than waiting until they are due.
The mechanism is built for that. Using it that way turns HR administration from a monthly scramble into something that has already happened.