Desk by Desk Automation MEL

Catalogue / HR & onboarding

HR and onboarding automations: new starters, access and leavers

Getting someone started properly, and finished properly, involves a dozen small steps across HR, payroll and IT. These four entries are where automation helps most.

HR-01

New starter paperwork pack

Every new employee needs the same set of documents and forms, and missing one is easy when onboarding happens a few times a year.

Before

  1. Find the last starter’s welcome email and edit it
  2. Attach the contract, policies and forms you remember
  3. Chase the tax file number declaration and super choice form
  4. Re-key details into payroll

After

  1. Enter (or forward) the starter’s name, role, start date and employment type
  2. A pack is assembled for that role: contract for signature, the Fair Work Information Statement, the Casual Employment Information Statement for casual staff, the TFN declaration and super choice form, and your policies
  3. A welcome email is drafted with first-day details
  4. Returned forms are collected, checked for completeness and filed
  5. Payroll details are drafted for entry
A person still approves: the contract terms and pay rate before anything is sent, and the payroll entry.

The Fair Work Ombudsman sets out what new employees must be given. Check fairwork.gov.au for the current requirements rather than relying on a template from years ago.

HR-02

Accounts and access for new staff

In a Microsoft 365 business, a new starter needs an account, a licence, the right groups and Teams, shared mailboxes and sometimes a phone number. Done piecemeal, something is always missed.

Before

  1. Email IT or the office manager with the details
  2. Account created; licence assigned, sometimes the wrong one
  3. Groups and Teams added from memory
  4. Starter arrives and asks for access to things one at a time

After

  1. From the starter’s role, a standard access set is drafted: account, licence type, groups, Teams, shared mailboxes
  2. The draft is checked against licences you already have spare, to avoid buying another one
  3. Once approved, the account is created and the starter’s manager gets the sign-in details for day one
A person still approves: the access set for each new starter, any admin rights, and any spending on new licences.

This entry touches security, so it is usually a second-round automation, after your team is comfortable approving automated steps.

HR-03

Offboarding a leaver

Late offboarding is a security risk and a cost: former staff with live sign-ins, and licences paid for months after someone leaves.

Before

  1. Someone remembers to tell IT, eventually
  2. Account disabled, maybe
  3. Mailbox and files left in limbo
  4. Licence keeps billing

After

  1. The last working day triggers a checklist
  2. At the agreed time, sign-in is blocked and sessions are revoked
  3. Mail forwarding or an auto-reply is set; the mailbox is converted or shared with the manager
  4. Files are handed over to the manager
  5. The licence is freed, and a confirmation goes to HR
A person still approves: the leaving date and time, who receives the mailbox and files, and final pay. For a sudden departure, a person triggers it manually.
HR-04

Staff policy questions

Office managers answer the same questions every week: leave, expenses, uniform, parking, who to call for IT.

Before

  1. A staff member asks the office manager
  2. The office manager looks it up or answers from memory
  3. Answers vary depending on who is asked

After

  1. Staff ask in Teams or by email
  2. The answer comes from your own policy documents, quoting the section
  3. If the policies don’t cover it, the question goes to a person and the gap is noted
A person still approves: anything personal, such as an individual’s leave balance, pay or performance, and any question the policies don’t answer.

Is one of these your bottleneck?

Book 15 minutes and bring the code. We’ll tell you how it would work with your systems.

Book a call