Home/Process library/From template to signed employment contract
Process library · HRFrom template to signed employment contract
HR fills in the contract data once. The contract is generated in the right template and language, approved by HR, signed electronically and then followed until it ends. Almost every step in between runs by itself.
See the flow Map your own flow
In short
In this blueprint an HR team creates every employment contract in M-Files. A template per contract type and language generates the document: employees, students, interns, freelancers and other types each have their own. Dutch contracts go straight to approval; English and French contracts wait until the translated version is added. HR approves, the contract goes out for electronic signature, and the signing status comes back by itself. After signing, the employee record is updated and a new hire is created in the planning system. From then on, the dates drive the contract: valid from the start date, flagged before the end date, expired on the end date. SoftAdvice designed and documented the process.
A contract touches HR, the new colleague and every system after it
A new colleague starts on Monday. The contract is still somewhere between Word, HR and a signature.
An organisation hires employees, students, interns and freelancers, in three languages. Every contract type has its own wording, and every contract has to be checked, signed and stored before the first working day.
By hand, someone copies last month’s contract in Word, changes the names, mails it around for approval and chases the signature. Nobody sees which contracts are still waiting, and nobody is reminded when a fixed-term contract is about to end.
- A template per contract type and language
- Approval by HR before anything is sent
- Electronic signature with status feedback
- Start and end dates followed by themselves
What happens from the first draft to the last day
A contract has two rhythms: a fast one until it is signed, and a slow one that follows the dates.
Before the start
Generate and approve
The contract is generated from its template, translated when needed and approved by HR.
On signing
Sign and process
The signed contract comes back by itself, the employee record is updated and a new hire reaches the planning system.
On the start date
Valid
The contract becomes valid and the employee active.
Before the end date
About to expire
About two weeks before the end, the contract is flagged, so HR can decide on an extension in time.
On the end date
Expired
The contract expires and stays in the file, with its full history.
From contract data to signed contract, step by step
Two steps need a person: adding a translation and approving. M-Files does the rest and records every step.
Generate
HR enters the contract data. dox42 generates the contract from the template that matches the contract type and language.
Translate
A Dutch contract goes straight on. For an English or French contract, HR adds the translated version; the contract waits until it is there.
Approve
HR receives a task to review and approve the contract, with a deadline. Nothing is sent before that.
Sign
The contract goes out for electronic signature. Waiting, signed, refused or failed: the status comes back and moves the contract by itself. A refused contract returns to approval.
Process after signing
After signing, the employee record is updated. For a new hire, the employee is also created in the planning system.
Follow up
The dates take over: valid from the start date, flagged before the end date, expired on the end date.
One contract, one route, from draft to expired
Every state is visible, so HR sees at a glance which contracts are out for signature and which are about to end.
Employment contract
From copying contracts to checking them
HR spends its time on the content of the contract, not on templates, reminders and chasing signatures.
Before
- Last month’s contract copied and edited
- Approval by e-mail
- Signatures chased by phone
- End dates in someone’s agenda
Now
- The right template per type and language
- An approval task with a deadline
- Signing status comes back by itself
- Contracts flagged before they end
M-Files with document generation and e-signature
Standard building blocks, configured and documented by SoftAdvice.
Electronic signature with Nitro Sign
The contract is sent from the workflow; the signing status moves it on by itself.
Workflow on dates
Start and end dates move the contract by themselves, and every step is recorded in its history.
Questions about this blueprint
Which contract types can this handle?
Every type you define gets its own template per language. In this blueprint: employees, students, interns, freelancers and a few other types, in Dutch, English and French.
What happens when someone refuses to sign?
The refusal comes back as a status. The contract returns to HR for approval, so it can be corrected and sent again.
Can we use another e-signature provider?
Yes. This blueprint uses Nitro Sign; the same route works with the other signature services we connect to M-Files.
Is the translation made automatically?
No. HR adds the translated version to the contract. The workflow recognises it and only then sends the contract to approval, so no contract leaves in one language only.
How does a contract reach signature today?
In a one-hour demo we show the contract route in M-Files, from template to signature. Want to map your own HR process first? Discovery is the next step.
