MELLORCATalk to Mellorca
Patterns

Workflow, Process & Handoff Design

The Hidden Cost of Repeating HR Administration for Every New Hire

When every new starter triggers the same forms, emails and re-typed details, HR time disappears into repetition. Here is why it happens and how to build the routine once.

Mellorca Patterns2026-10-08

Observable condition

A new hire is confirmed on a Thursday, and the machinery starts. Someone in HR sends the offer paperwork as email attachments. The employee prints, signs, scans and returns it, usually from a phone, usually crooked. The details are then typed into the payroll system, typed again into the leave register, typed a third time into the access request for IT, and pasted into a welcome email for the line manager. A checklist, kept in a Word document that was last edited two hiring rounds ago, tells the HR officer what comes next.

None of the individual steps is difficult. The problem is that they are identical every time, and every time they are done by hand. The HR officer knows the sequence by heart, which is exactly why nobody has questioned it. When two people start in the same week, the work doubles. When the officer is on leave, the process stalls, because the real instructions are in their head rather than in a system.

An illustrative example: a Durban-based distribution company with about ninety staff hires roughly three people a month, more in the festive season. One HR administrator handles all of it. She estimates that each hire consumes close to half a working day of re-keying and chasing, and she has stopped counting how often a start date passes before the laptop, the payroll profile or the building access card is ready.

Realisation

Onboarding is usually described as a people process, and the welcome and the first week certainly are. But a large share of what happens between acceptance and day one is plain administration: collecting the same set of facts, and handing those facts to the same set of places. Repeating that for every hire does not make the business more careful. It makes it slower and more error-prone, because every manual copy is a fresh chance for an ID number, bank detail or start date to be wrong.

The cost is rarely visible, because it is spread across many small tasks and several people. Nobody owns the total, so nobody sees it.

Realisation prompt: if you timed everything that happens between a signed offer and a new starter's first productive day, how much of it is new thinking, and how much is the same steps repeated?

Identification

This is a pattern of repeated administration around a predictable event. The visible symptom is an HR team that is always busy but rarely able to improve anything. The common assumption is that HR needs another person, or that new starters are simply late with their documents. The structural cause is that the facts about a new employee are captured once but then re-entered by hand into every place that needs them, and the sequence of tasks is held in a document and in memory instead of in a defined workflow.

The published Pattern when a new employee's first months run on emails and memory looks at what happens after day one. The Impact page on collecting employee information every pay period covers the same duplication on the payroll side. This article concentrates on the pre-start routine and why it is rebuilt for every hire.

Diagnosis

  • The same details are typed more than once. Name, identity number, tax reference, bank account, emergency contact and start date are each re-keyed into payroll, leave, access and communication tools.
  • The checklist is a document, not a workflow. It cannot remind anyone, cannot show what is outstanding, and is copied and edited by hand each time.
  • Handoffs depend on email. IT, finance and the line manager learn about a hire when someone remembers to tell them, not when a record changes.
  • Approvals travel as attachments. A manager's sign-off on a salary or a role sits in a forwarded message that must be found later.
  • Knowledge sits with one person. The order of steps, and the exceptions, are known by the officer who has done it forty times.

Commercial impact

The commercial value at stake is administrative productivity, error reduction, employee experience and scalability. The direct cost is HR time: even a modest three hours of avoidable re-keying per hire, across thirty-six hires a year, is more than a hundred hours that could have gone into recruitment quality, retention or training.

The indirect costs are larger. A new employee who starts without equipment or system access is paid but unproductive, and forms their first impression of the company from the delay; the Impact page on new employees without equipment explores that cost. Payroll errors caused by mistyped details are found later, usually by the employee, and they take longer to correct than to prevent. SARS expects employers to submit accurate employee information and valid tax reference numbers when reconciling PAYE, so a transposed digit entered at onboarding can resurface months later during a filing period.

It also limits growth: the Impact page on high-value employees doing low-value admin describes how skilled people get absorbed by routine.

Common misidentification

One response is to add an HR assistant. This can relieve the pressure for a while, but it multiplies the number of people who know a slightly different version of the routine, and it leaves the re-keying in place.

Another is to buy a full HR suite and expect it to fix onboarding. If forms still arrive by email and are retyped, the software becomes a fourth place to type the same data. The Insight why copying data between systems is more expensive than it looks explains why the copy step, not the destination, is the expense.

Possibility

In a better state, a new hire's details are captured once, by the employee, through a structured form that checks for missing fields. That single record becomes the source for payroll set-up, leave entitlement, access requests and the manager's welcome notice. A workflow created on confirmation of the offer assigns tasks to HR, IT, finance and the line manager with due dates relative to the start date, and shows at a glance what is still outstanding.

Standard business tools already support this shape. Microsoft's Power Automate documentation describes approvals that send sign-off requests to the right people, notify them, and record the decision, with sign-off of documents and expense reports among its own examples. Its documentation for model-driven apps names the onboarding of new employees as a typical process well suited to that kind of application. The technology is not the hard part. Agreeing what a complete hire record contains, and who owns each step, is.

For the distribution company, that would mean the half-day of re-keying shrinks to a review of an already-complete record, the laptop request goes out automatically when the offer is accepted, and the administrator is no longer the only person who knows the sequence.

Intervention

  1. Trace the last three hires. List every place each person's details were typed and every message sent. Count the repeats. This is the baseline.
  2. Define the complete hire record. Agree the fields every department needs, mark which are legally required, and drop the ones nobody uses.
  3. Capture once, at the source. Replace emailed attachments with one structured form completed by the new employee, with validation for identity and bank number formats. Take POPIA into account: collect only what is needed, and restrict who can see it. The Information Regulator's guidance on the role of the information officer is a sensible starting point for who should own that decision.
  4. Turn the checklist into a workflow. Assign each task to a role, with a due date counted back from the start date, and send an automatic reminder if it slips.
  5. Route approvals through the workflow. Salary, role and equipment approvals should be recorded where the hire record lives, not in a forwarded email.
  6. Measure and review. Track time from signed offer to a fully set-up starter, and the number of corrections made in the first two payroll runs. Review after three hires.

Diagnostic questions

  • How many times is a new hire's identity number typed by different people?
  • Could someone other than the HR officer run the onboarding routine from written steps alone?
  • When does IT find out that someone is starting, and how?
  • How many payroll corrections in the last year trace back to a mistyped onboarding detail?

Bottom line

Repeating HR administration for every hire is not diligence; it is a routine that was never built into the business. Capturing the facts once, sharing them automatically and turning the checklist into a workflow returns HR time to work that needs judgement, protects the accuracy of payroll and tax records, and gives every new starter a first week that works. The saving grows with every hire.

Sources and further reading

Related Mellorca reading

Article summaryWhen every new starter triggers the same forms, emails and re-typed details, HR time disappears into repetition. Here is why it happens and how to build the routine once.
Explore our solutionsStart a conversation