Published

A maintenance technician returns after 14 months, this time at a different plant. HR already has a signed offer, a training certificate and a policy acknowledgement from the earlier employment period. The new supervisor needs to know whether onboarding is complete. Copying the entire old file into the new assignment would mix earlier terms, potentially outdated evidence and records the supervisor should not see.
Connect the employee’s history and review what the new assignment can use. Keep the earlier employment context, collect the documents required for the return, and record why any prior evidence is accepted. A returning person’s identity provides continuity; each document still needs the right purpose, audience and review.
Match the authoritative employee identity and the new employment period without relying on a name or email alone.
Check the document’s scope, version and validity against the current assignment’s requirements.
Collect missing documents and record the review outcome while keeping restricted history protected.
Agree the evidence rules with the HR owner for the applicable role and location. The examples below describe document handling decisions, rather than universal employment requirements. An old document can remain a valid historical record without satisfying a new onboarding requirement.
| Earlier record | Treatment for the return | Evidence to retain |
|---|---|---|
| Signed offer | Preserve the earlier terms with their employment period. Collect the new offer required for this assignment. | Separate document references, effective dates and the current onboarding review. |
| Training certificate | Review issuer, scope, expiry and whether the new equipment or location is covered. | The exact certificate, reviewer, acceptance reason and next review date where applicable. |
| Policy acknowledgement | Check which policy version and audience it covered. Obtain a new response where current requirements call for one. | The earlier response and its version, plus the current policy and response when required. |
| Restricted HR case notes | Keep the existing restricted audience unless an authorised decision changes it. | The applicable purpose and access decision, without exposing the notes through an onboarding summary. |
Use the HRIS’s authoritative person reference and its employment or assignment reference. Some systems issue a new employee number on return or permit concurrent assignments; map those relationships explicitly. A name match, reused email address or old account is insufficient grounds to attach confidential history. Route uncertain matches to HR before linking records.
The continuing employee file can connect both periods while preserving their separate offers, dates and decisions. Record a source event reference so a retried integration message does not create a second onboarding review. The HR document management and ATS guide explains the wider division of responsibility between recruiting, HR systems and governed documents.
This fictional continuation of HR-1042 brings EMP-1042 back after 14 months. The HRIS confirms a new assignment, A-771. Under this organisation’s rules, the new plant needs a new offer, a current training review and acknowledgement of workplace-conduct policy version 4. The earlier file contains a version 3 response.
HR confirms the source identity and effective date. The configured integration associates A-771 with EMP-1042 and the continuing employee file. The earlier separation remains recorded; it is not overwritten by the return.
The HR reviewer confirms that the retained certificate is current and covers the new plant’s equipment. The onboarding review links the exact certificate and records that decision. If its scope were unclear, the training item would stay outstanding until resolved.
The coordinator adds the new offer and the employee’s version 4 acknowledgement. The earlier offer and version 3 response remain associated with the earlier period. The application’s checklist shows which current requirements are still missing.
The new supervisor receives the agreed completion information and permitted documents. HR tests that restricted case notes cannot be found or opened through that supervisor’s search, document links or onboarding view. Connecting the file does not grant access to every record in it.
The FormKiQ review workflow records the HR decision and any comments against the submitted summary and linked evidence. The application reflects the outcome in onboarding status. Any update to the HRIS or identity provider follows the agreed integration; document acceptance does not itself activate an account or authorise employment.
Decide what the employee, supervisor and specialist HR staff may see for their current responsibilities. Test metadata, previews and search results as well as file downloads. A completion indicator should not reveal a sensitive record’s contents or reason for restriction.
Rehire should trigger a review of relevant retention rules, rather than a blanket reset of every record’s clock. Preserve earlier separation dates and existing holds. Confirm which trigger applies to each document class under the organisation’s policy. Do not recreate documents already lawfully disposed of or infer that an absent historical record was never collected.
A useful rehire record shows what the team reused, what it collected again and who accepted the current onboarding file. Preserve that decision alongside the employee’s earlier records, with access and retention applied to the documents themselves.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.