Home/Process library/From newcomer to leaver
Process library · HRFrom newcomer to leaver
The employee file follows the dates. Two weeks before the start, the newcomer is announced. When the contract runs, they are active. On the last day, access to the planning system is closed. HR only steps in for the exceptions.
See the flow Map your own flow
In short
In this blueprint every employee has a file in M-Files that moves through the employment on its own. A new employee starts as a newcomer and appears in the newcomers view two weeks before the start date. Once the contract is active, the employee becomes active. On the last working day the employee is operationally out of service; on the end date of the contract, contractually out of service. The linked records, such as personal data, address and emergency contact, follow each step, and so does the employee record in the planning system, whose access is closed when the contract ends. A re-hire is one manual step back to active. SoftAdvice designed and documented the process.
Who works here today?
Nobody knows exactly who starts next week, and someone who left last month still has access.
An organisation with a steady flow of new and leaving colleagues needs one simple answer: who works here, who is about to start and who has left. Everything else depends on it, from planning to access to personal data.
When HR updates statuses by hand, a leaver keeps access for weeks and a newcomer is missing from the planning on day one.
- Newcomers announced before they start
- Status driven by the contract and its dates
- Linked data follows the employee
- Access closed when the contract ends
What happens from before day one to after the last day
The dates in the file set the rhythm. Nobody has to remember to change a status.
On hiring
Newcomer
HR creates the employee with a start date, or imports a batch from Excel.
Two weeks before the start
Starting soon
The newcomer appears in the newcomers view.
When the contract runs
Active
The employee becomes active, and so do the linked records.
On the last working day
Operationally out
No longer working, while the contract still runs.
On the end date
Contractually out
Access to the planning system is closed and the clean-up of personal data begins.
From newcomer to leaver, step by step
HR records the start and handles the exceptions. The dates and the contract move the file; every step is recorded in its history.
Record the newcomer
HR creates the employee with a start date, or imports several at once from an Excel file.
Announce
Two weeks before the start date, the employee moves to starting soon and shows up in the newcomers view.
Activate
As soon as the contract is active, the employee becomes active. The linked records follow.
Operationally out
On the last working day, the employee is operationally out of service. The record in the planning system follows.
Contractually out
On the end date, the employee is contractually out of service. Access to the planning system is closed and the linked personal data starts its clean-up.
Re-hire
When someone comes back, HR moves the employee back to active. The linked records come back with them.
One employee, two systems, always in step
The employee file in M-Files leads. The record in the planning system follows every change, so both always tell the same story.
Employee file
Planning system
From updating statuses to trusting them
HR no longer keeps a list of who starts and who leaves. The file knows, and the systems around it follow.
Before
- Starters announced by e-mail, or not at all
- Statuses changed by hand
- Leavers keep access for weeks
- Two systems that disagree
Now
- Newcomers visible two weeks ahead
- Status follows the contract and its dates
- Access closed on the end date
- Planning system always in step
M-Files with the Compliance Kit and PowerPack
Standard building blocks, configured and documented by SoftAdvice.
Workflow on dates
Start date, last working day and end date move the employee by themselves.
Linked records that follow
The Compliance Kit moves personal data, address, emergency contact and the planning-system record along with the employee.
Excel import
PowerPack imports employees, departments and functions from Excel, and keeps the planning-system records up to date.
Questions about this blueprint
Why two out-of-service states?
Because the last working day and the end of the contract are often not the same day. Planning needs to know when someone stops working; the clean-up of personal data starts when the contract ends.
What if someone comes back?
HR moves the employee back to active in one step. The linked records come back too, as long as they have not been cleaned up yet.
Does this replace our payroll or planning software?
No. M-Files keeps the file and the status; the other systems keep doing their job and receive the changes they need.
Who works here today, according to your systems?
In Discovery we map your HR process from hiring to leaving and show where the dates can do the work.
