Eight Completeness Gates in the Hiring Process
November 2, 2026
Features
A missing item discovered just before a new employee's start date can stop a contract, signature or HR system handover. In the documented AMODIT workflow, completeness is checked at eight points while the person responsible for each item can still act. These checks span the entire hiring process; the electronic personnel file is the final gate, not the whole story.
Rules check the process; people own the decisions
The source materials describe configured workflow rules, required fields, document presence and status checks. They do not assign AI the task of deciding whether hiring data is complete or interpreting health-related documents.
AMODIT can flag a missing item, stop a transition where the implementation requires it and route work to the right role. People verify data, sign documents and decide how to handle exceptions. Where AI supports another part of an AMODIT solution, it recommends or prepares an output for a person to review and approve. Existing models are configured for the use case; models are not trained for this workflow.
The eight gates in the documented workflow
The following sequence translates the eight gate names and conditions stated in the Polish product materials. In this documented configuration, a case cannot continue until the relevant stage meets its condition.
- Candidate form — Required fields, a valid Polish national identification number (PESEL) and postal code, and documents for foreign nationals.
- Employment terms — The limit of three fixed-term contracts and 33 months, a working day, and the person being replaced.
- Medical examinations — A signed referral, a scheduled date and a scan of the medical certificate.
- Contract — No required fields missing before the contract is sent for signature.
- Employer representative's signature — The signature is checked in the contract file.
- Document package — Sending is blocked when the contract is missing from the package.
- Candidate's signature — Status from AMODIT Trust Center: signed, rejected or overdue.
- Electronic personnel file and HR system — A separate stage verifies the documents and the integration.
What each gate protects
1. Candidate form
The candidate completes required information through temporary access to their own stage. AMODIT checks the PESEL format and postal code and can switch the form to a path for a foreign national. Information entered earlier by the recruiter cannot be changed by the candidate.
Format and presence checks are automated, while the recruiter remains responsible for reviewing the data before approving employment terms.
2. Employment terms
The recruiter completes the contract type and duration, working time, compensation and other agreed conditions. The documented process checks the fixed-term contract limits, whether the start date is a working day and, for a replacement contract, whether the person being replaced has been identified.
Approval launches downstream tasks, so the recruiter remains accountable for this review.
3. Medical examinations
Before the process continues, the case is expected to contain a signed referral, the appointment date and a scan of the medical certificate. The health and safety coordinator reviews role requirements and signs the referral. The candidate arranges the examination and uploads the certificate; HR reviews it and records the result.
AMODIT checks that the required items are present. It does not interpret the medical content or decide whether a person is fit for work.
4. Contract
HR generates the contract from previously reviewed case data and a template approved by the organization. The gate prevents the contract from being routed for signature while required information is missing.
The organization remains responsible for the template and its compliance with applicable law. AMODIT fills the template; it does not provide a legal assessment of its content.
5. Employer representative's signature
The prepared contract is routed to a group of authorized employer representatives. A representative reviews the documents and applies a qualified electronic signature in AMODIT. The system checks for the signature in the file and records its date.
If a correction is needed, a person returns the case to HR. Approval and signature remain human responsibilities.
6. Document package
AMODIT assembles the package for the candidate and blocks sending when the contract is absent. The check prevents an incomplete set from reaching the candidate's signature stage.
7. Candidate's signature
The candidate signs the package in AMODIT Trust Center. The workflow reads one of the three states listed in the source: signed, rejected or overdue. A refusal or missed deadline is not treated as an automated HR decision; it starts an exception path owned by the assigned people.
8. Electronic personnel file and HR system
The final gate is a separate verification stage for both documents and integration. HR completes the process by transferring documents to the electronic personnel file, while hiring data is sent to the payroll or HR system in the scope agreed during implementation.
This is broader than an electronic filing check. It also verifies that the configured system handover has completed correctly.
Not every missing item should block the workflow
The source gives a practical design rule: block progress only where the missing item genuinely stops the process. Other issues can be shown as guidance next to a field.
Each organization defines required data, documents, roles, permissions and transition conditions during implementation. The gates therefore reflect its operating model rather than impose one rigid workflow on every company.
Every exception needs an owner
Eight standard gates are useful only when the workflow also assigns responsibility for non-standard situations. The documented examples include:
- no PESEL: the documented configuration has no separate route, so the recruiter takes ownership;
- an SMS code does not arrive: the candidate can request it again, while the recruiter corrects an invalid number and reopens access;
- the start date changes: the recruiter or HR coordinator updates the data that also controls candidate-link validity;
- an error is found before signature: the case returns with a comment to the person responsible for that stage;
- the candidate refuses to sign: HR manages a contract correction, reopens the questionnaire or cancels the process;
- the signature deadline passes: the package expires and HR and recruitment determine the next action;
- a correction is needed after both parties have signed: the source treats this as outside the documented workflow and assigns it to HR;
- the HR system integration fails: HR and IT take ownership in the verification stage;
- the candidate withdraws: recruitment closes the hiring case, linked onboarding cases are cancelled, and actions completed outside AMODIT need separate reversal.
Each exception should have an owner and a response deadline. If it cannot be handled inside the workflow, the organization defines who decides and where that decision is recorded.
Candidate and health data require an implementation-specific design
This workflow handles candidate and employee data, employment documents and health-related information. The product materials confirm role-based tasks and access to the case within assigned permissions. They are not a legal or data-protection assessment for a particular organization.
The sources do not specify the legal basis for processing, retention periods, encryption design or the complete access matrix. HR, health and safety, legal, data protection and IT stakeholders need to define these elements for the organization's implementation.
Explore the wider AMODIT HR process area, the electronic personnel file and the detailed occupational health referral workflow.
Frequently asked questions
Are the eight gates only about the electronic personnel file?
No. The electronic personnel file and HR system form the eighth gate. Earlier checks cover candidate data, employment terms, medical examinations, the contract and signatures.
Does AMODIT decide that the information is substantively correct?
AMODIT checks configured conditions such as required fields, formats, document presence and signature status. People in the assigned roles perform substantive reviews and make decisions.
Does every gate have to block progress?
No. The source recommends blocking only when a missing item genuinely stops the process. Other issues can be shown as guidance. The organization defines the specific rules during implementation.
What happens when a candidate refuses to sign?
The case goes to HR. The documented process allows HR to manage a contract correction, reopen the questionnaire or cancel the hiring process. A person decides which route to take.
Do these gates guarantee compliance with data protection or employment law?
No. Completeness checks support a configured workflow, but they do not replace legal analysis, a lawful-basis assessment, retention rules, access design or the organization's data-protection controls.
Do the completeness gates use AI?
The source materials describe rules-based automation at these gates and do not confirm an AI role in completeness assessment. Where AI supports another part of the solution, a person reviews and approves its output.
