In short: Start onboarding from an authorised HR record, not an applicant email. Give each team tasks they can finish, keep identity documents away from the task board, and cancel or review access when the start date changes or the offer is withdrawn.
Employee onboarding automation works when it is a handoff between HR, the hiring manager and IT. A confirmed start date creates tasks. Each team records completion against those tasks. A changed or cancelled start date updates the plan. Identity documents and salary information should not travel on a general task board that every assignee can open.
This page is the joiner path only. Removing access when someone leaves is the offboarding guide. It is not a payroll guide and it does not score employees.
The trigger is an HR record
Do not start from an unverified applicant email. The authoritative event is an HR record with an identifier, the employing entity, the manager, the start date, the workplace and the role. Contractors need a different template from employees, because the access and the documents are different. A rehire who shares a name with a former employee must attach to a new identifier or a deliberately reopened one. Matching on name is how the old mailbox comes back.
Write down which system wins when dates disagree. If a manager’s spreadsheet says Monday and HR says the following Monday, the workflow follows HR and tells the manager. IT should not keep a third date in a ticket.
Checklists follow the role, not a neighbour’s access
Split the work so each team sees its own list:
| Workstream | Typical tasks | Evidence of done |
|---|---|---|
| HR | Required forms received, right to the role confirmed by HR | A completion flag, not the file itself, on the manager’s view |
| Manager | Role template confirmed, first-week work assigned | Named confirmation |
| IT | Accounts prepared from the role template, then activated | Account id and the template version used |
| Workplace | Equipment issued or a remote-work setup confirmed | Asset id and who received it |
Copying another employee’s permissions feels fast and leaves unexplained access. The role template is the request. Exceptions are an extra approval, with a reason and an expiry if the extra access is temporary.
Microsoft’s Entra offboarding tutorial is about leavers, and it states that lifecycle workflows of that kind require Microsoft Entra ID Governance or Microsoft Entra Suite licences. It is relevant here only as a warning: joiner and leaver features are licensed product capabilities, not something every Microsoft 365 tenant already contains, and they do not configure every local account in a third-party app. Confirm the joiner events your HR and identity tools actually emit before you buy a scenario that assumes them.
What the manager is allowed to see
A manager often needs to know that documents were checked. The manager does not, by default, need the identity file or the salary offer. Store those in the HR system. Put a status on the task. Test this with a real permission review: sign in as the manager and try to open the document. The PDPC’s Advisory Guidelines on Key Concepts (17 May 2022) describe a duty to make reasonable security arrangements for personal data in the organisation’s possession or control. A shared task board with attachments is a common way that duty gets missed. Business contact details are not automatically outside the PDPA; the guidelines explain that the Data Protection Provisions generally do not apply to business contact information, but the classification depends on purpose and context. Employee records are a different category.
Outsourcing the workflow to a vendor does not remove the company’s responsibilities for that data.
Dates move, offers die, people return
Design these as first-class events, not as a human remembering to cancel a ticket:
- Start date moves after tasks exist. Incomplete tasks shift. Anything already activated is reviewed. Equipment delivery dates change with the record.
- Offer withdrawn. Pending tasks cancel. Created access goes to a revocation queue the same day. The offboarding pattern is the right shape for that queue even though the person never started.
- Contractor versus employee. Different checklist, different data, different end date.
- Rehire. New or explicitly reopened identity. Do not turn the former employee’s old account back on because the display name matched.
Employment records, with their actual scope
MOM’s employment records page says employers must keep records for employees covered by the Employment Act. The records may be soft or hard copy. For current employees, the latest two years. For employees who have left, the last two years of records, kept for one year after they leave. The page lists the employee and salary fields it expects.
That duty is not permission to delete every onboarding file on the anniversary, and it is not a rule for people the Act does not cover. Tax, work-pass, dispute and contract needs can point the other way. Decide with HR. The automation design only needs a place where those decisions can be applied. More on separating logs from employment records is in the retention guide.
What to ask before you buy
Ask which HR event is authoritative, whether access can be approved and left disabled until activation, and how abandoned files are retained or removed. Ask for a demonstration with the three tests: a moved start date, a rehire who shares a name, and a manager account that cannot open restricted documents. Do not accept a promise that the template “handles MOM”.
Illustrative scenario, not a client engagement: a professional-services firm lets HR confirm the joiner. IT prepares access from the role group the manager signs off. Equipment receipt is a separate task with an asset number. When the start date is withdrawn, pending tasks cancel and any account already created is queued for review before anyone treats onboarding as finished.
This is an operational design guide. It is not employment-law advice, and FYAdvisers is not a law firm. To map your HR, IT and manager handoff, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
Which HR event should start the workflow?
An authorised record in the HR system: employee or contractor id, employing entity, manager, start date, workplace and role. A forwarded CV or a personal email saying “I accept” is a prompt for HR, not a trigger for account creation.
Can IT create the account before the person may sign in?
Yes, if the design separates provisioning from activation. The account can exist, disabled, until the start date is still true and the manager has confirmed the role template. Activation on the day, with a check that the offer was not withdrawn, is the safer pattern.
What happens to records if onboarding is abandoned?
Pending tasks close. Any account that was created is queued for review, not left enabled. Retention of the documents depends on why they were collected. MOM’s employment-record periods are not a universal deletion date, and they apply to employees covered by the Employment Act.
Does an onboarding template make the company employment-law compliant?
No. A checklist can show that a step was completed. It does not decide Employment Act coverage, work-pass conditions or what must be kept. Those questions need the company’s own HR and, where needed, qualified advice.

