Onboarding That Depends on a Manager's Memory Produces Uneven Starts

The new starter with no laptop password and no desk

A logistics firm in Kempton Park hires a dispatcher who starts on a Monday. The hiring manager had meant to ask IT for a login, tell payroll the bank details, book the safety induction and introduce the new starter to the operations team. He remembered to order the uniform. On Monday morning, the dispatcher sits at a borrowed desk for two hours before anyone finds a working computer. The safety induction is only booked for the following week. Payroll does not have a tax number until the second month, and the new starter's first payslip is wrong.

None of this is difficult work. Each task is small and familiar. The problem is that the process depends on a manager remembering a long list of small things, usually while also running a team. When the manager is busy, one or two things are forgotten. The new employee's first impression of the company is formed by those gaps.

This article is about onboarding that relies on checklists and memory, and the cost of inconsistent starts. It complements the equipment-focused view in new employees without equipment and the customer-side view in manual customer onboarding by looking at the manager's memory as the weak link.

Why a checklist is not enough

Many companies do have a checklist. It sits in a Word file or on a shared drive, and the manager is expected to find it and work through it. That helps, but it still leaves several weaknesses:

Nobody triggers it. The checklist is used only if the manager remembers to open it, which is the exact thing that tends to be forgotten.
Tasks belong to different people. Equipment is IT's, contracts are HR's, payroll set-up is finance's, and the manager has to chase each of them.
Timing matters. A laptop ordered on Friday is useless on Monday. A checklist does not show that some items need a week's notice.
Nobody can see what is done. HR cannot tell which items are outstanding without asking the manager.
The list drifts. New requirements, such as a policy acknowledgement or a system access request, are added to one copy and not another.

What inconsistent starts look like

One new starter receives a thorough welcome and another, hired by a busier manager, is left to find their own way.
Employees who start without system access and spend their first days watching others work.
Missing contracts, unsigned policies or incomplete tax and banking details that surface only at the first pay run.
Compulsory safety, compliance or product training that is booked late or not at all.
New staff who do not know who to ask, or what is expected of them in the first month.
Early resignations from people who felt unwelcome or unsupported.

The compliance side

Some of the forgotten steps carry real consequences. An employer has to register and pay over employees' tax correctly, and the SARS page on Pay-As-You-Earn describes the employer's role in deducting and paying over employees' tax. Missing information at the start tends to turn into corrections later. The right information at the start of employment is cheaper to collect than to repair at the first reconciliation. Safety and other statutory training obligations depend on the nature of the work, so a business should confirm its own requirements with its advisers. Whatever those requirements are, they should be on a list that does not depend on a manager's memory.

How the pain becomes money

Unproductive paid days. An employee who cannot log in or does not know what to do still earns a salary.
Manager time spent fixing. Rushed requests to IT, HR and payroll cost more than a planned request.
Payroll corrections. Wrong first payslips need adjustments, explanations and sometimes apologies.
Slower ramp-up. Employees who are not shown how things are done reach full productivity later.
Early turnover. Replacing someone who leaves in the first months means repeating recruitment, advertising and onboarding costs. The same connection between handover quality and continuity appears in catching up after absence.
Uneven culture. Different managers give different starts, so some teams become attractive and others do not.

An illustrative cost model

These figures are illustrative assumptions for a hypothetical Cape Town services business with 80 employees that hires 16 people a year.

Assumption	Value
New starters per year	16
Starts with at least one missed task	50%
Productive days lost per affected start	2.5
Daily loaded cost of a new starter	R1,400
Manager, HR and payroll time fixing the gaps, per affected start	4 hours at R350
Extra early leavers per year because of a poor start	1, replacement cost R60,000

Lost productive days: 8 × 2.5 × R1,400 = R28,000
Fixing time: 8 × 4 × R350 = R11,200
Early leaver: R60,000
Illustrative total: about R99,000 a year

The early-leaver line is a judgement and may be zero in some years and larger in others. Even without it, the lost days and fixing time are a recurring cost for something that a better process removes.

Why it is tolerated

Hiring is infrequent from the manager's point of view, so there is no routine to build habit. HR may be one person who cannot chase every task. Managers see onboarding as an interruption to their real job, and they rely on goodwill and improvisation. Because the person who suffers the gap is new and unlikely to complain, the failure never reaches the owner.

What better looks like

The idea is to move the memory out of the manager and into the process, so that hiring someone sets off the right tasks automatically.

Start the process from the hire decision. A signed offer or an approved start date should create the onboarding tasks, not a manager's good intentions. The principles in designing workflows that survive staff changes apply to the hiring manager as well.
Assign each task to a named owner with a due date. Equipment to IT, contract to HR, payroll set-up to finance, workstation to facilities, welcome to the manager. Due dates should be counted back from the start date.
Make progress visible. HR and the manager should see what is done and what is outstanding in one view.
Use a shared task tool rather than a document. Request and task systems such as Jira Service Management show how requests can be routed to teams and tracked to completion, and any task tool with owners and due dates can play the same role.
Define ownership at each stage. The approach in how to make ownership clear at every stage removes the question of whose job a task is.
Check the first week and the first month. A brief review with the new starter shows what was missed and feeds back into the template.

When it becomes urgent

hiring is increasing and the manager-by-manager approach is breaking down;
a new starter left in the first three months and cited a poor start;
the first payslip of a new starter has been wrong more than once;
the same task, such as system access, is regularly late.

Practical next actions

Ask the last three new starters what was missing in their first week.
List every task that must happen before and after day one, with an owner and a lead time for each.
Turn the list into a template that is created automatically when an offer is accepted.
Choose one person to review outstanding onboarding tasks weekly.
Measure days to first productive work for the next five hires.

Bottom line

A new employee's first week should not depend on whether their manager had a quiet month. When onboarding relies on memory and a document nobody opens, starts become uneven, small errors reach payroll and good people feel unwelcome. A shared list with named owners, lead times and visible progress produces consistent starts at very little cost.

Sources and further reading

Pay As You Earn - South African Revenue Service (last verified 10 October 2026)
What is Jira Service Management? - Jira Service Management Cloud - Atlassian Support
RACI Chart: What is it & How to Use - The Workstream (last verified 10 October 2026)