MELLORCATalk to Mellorca
Patterns

People Operations & Internal Service

When a New Employee's First Months Run on Emails and Memory

Onboarding does not end on day one. Training, introductions, policy sign-offs, check-ins and probation reviews often depend on a manager remembering, so they happen late, unevenly or not at all.

Mellorca Patterns2026-10-07

Observable condition

The first day goes reasonably well. The laptop works, the contract is signed and the new employee has a desk. Then the structure fades. The manager means to arrange product training but a big order comes in. The introduction to the finance team happens three weeks later, by chance, at the coffee machine. Nobody is sure whether the new person has read the leave policy or the safety rules. The thirty-day check-in becomes a quick chat in the corridor. The end of probation arrives and HR only notices when payroll asks whether the person is now permanent.

Nothing was refused or neglected on purpose. Every step was intended. But each depended on someone remembering to start it, usually by email, while doing their actual job.

An illustrative example: a Bloemfontein medical supplies distributor with around eighty staff hires sales representatives and warehouse staff several times a year. Its HR officer has a good pre-start checklist, but after day one onboarding is left to line managers. Some managers run a thorough first month; others hand over a product catalogue and a vehicle. Two representatives who left within their first few months said in exit conversations that they had never been properly trained on the product range.

Realisation

Many businesses have improved what happens before a new person arrives: contracts, equipment and system access. The weeks after the start date are where onboarding most often falls back on memory, because they involve many small steps spread across time and across people. Training sessions, introductions, shadowing, policy sign-offs, safety induction, the first check-in, the probation review: each is due on a different date and owned, informally, by a different person.

That is exactly the kind of work memory handles badly. It is easy to remember to do something today. It is hard to remember, among everything else, that a review is due in six weeks for someone who joined in a busy month.

Some of these steps carry obligations, not just good intentions. The Basic Conditions of Employment Act requires an employer to supply written particulars of employment when the employee starts, and to revise them and give the employee a copy when any of those particulars change. If a role, hours or pay is adjusted at the end of probation by an informal conversation, that obligation is easy to miss. And the employee information gathered during onboarding is personal information that POPIA requires to be protected with appropriate, reasonable safeguards, not scattered across emails.

Realisation prompt: for the last person you hired, could you show on which date each part of their first three months was completed, and who did it?

Identification

This is a people-operations workflow problem. The visible symptom is inconsistent onboarding quality, late reviews and new employees who take longer than expected to become productive. The common assumption is that some managers are better at onboarding than others. The structural cause is that onboarding after day one is not designed as a scheduled journey with tasks, owners, dates and a record of completion, so it depends on individual memory and email.

It continues where an existing Pattern stops. Why does hiring someone create so much internal admin covers the work up to the first day, and the Discovery article why new employees wait for system access covers one specific day-one failure. This Pattern covers the following weeks and months, when the employee is present but the process that should support them has gone quiet.

Diagnosis

  • No defined journey. Nobody has written down what should happen in week one, month one and month three for each type of role.
  • Dates are not anchored to the start date. Check-ins and reviews are scheduled, if at all, by someone creating a calendar entry by hand.
  • Ownership is assumed. HR assumes the manager is training; the manager assumes HR is arranging introductions and policy sign-off.
  • No record of completion. Policy acknowledgements and training attendance are confirmed by email or not at all, a gap described in why policy acknowledgements need a reliable system record.
  • Changes are not captured. When probation ends or terms change, the update to the employee's written particulars and records depends on someone remembering.
  • Managers are overloaded. Line managers carry onboarding on top of full workloads, so it slips whenever operations are busy.

Commercial impact

The commercial value at stake is time to productivity, employee retention, management capacity, compliance and consistency.

Time to productivity lengthens when training and introductions happen late, so the business pays a full salary for partial output for longer than necessary. Retention suffers because the early months shape whether a new person feels supported and competent; a business that loses people early repeats the cost of recruitment and the admin of hiring. Management capacity is spent improvising onboarding each time instead of following a prepared plan. Compliance risk arises when written particulars are not updated, safety rules are not demonstrably communicated or personal information is held in uncontrolled places. Consistency suffers because each new person's experience depends on which manager they report to. The experience of joining without time or structure to learn is captured in the employee who never has time to learn.

Common misidentification

A longer induction day is a common response. It front-loads information the new person cannot yet absorb and does nothing for weeks two to twelve.

Another is to buy an HR system and assume onboarding is solved. Many HR and identity platforms can schedule tasks relative to a start date, but only if the business has first defined what those tasks are and who owns them.

Possibility

In a better state, each common role has a written onboarding journey covering the first three months: what training happens when, who the new person should meet, which policies they must acknowledge, and when check-ins and the probation review take place. When an employee's start date is recorded, the tasks are created automatically, each with an owner and a due date, and reminders go to managers before they are due. Identity platforms already work this way for access, with joiner workflows that run tasks a set number of days before or after the hire date and keep a history for audit. Completion is recorded, so HR can see who is on track. When probation ends or terms change, updating the written particulars is a task in the same journey.

For the medical supplies distributor, that might mean separate twelve-week journeys for sales and warehouse roles, product training scheduled in the first fortnight, and probation reviews that appear in managers' task lists two weeks before they are due.

Intervention

  1. Interview recent hires. Ask people who joined in the last year what happened in their first three months, what was missing and what came too late.
  2. Define journeys by role. For your most common roles, list the steps for week one, month one and month three, with an owner for each.
  3. Anchor to the start date. Schedule every step relative to the start date so it can be generated, not remembered.
  4. Record completion. Capture training, policy acknowledgements and reviews in one controlled employee record rather than in emails.
  5. Include contract changes. Make updating written particulars part of the probation review and any change of role, hours or pay.
  6. Automate reminders and review. Use your HR system, workflow tool or even shared task lists to issue tasks and reminders, and review completion monthly, applying the principles in how to design a handoff that cannot depend on memory.

Diagnostic questions

  • Is there a written plan for a new employee's first three months, by role?
  • Who owns each onboarding step after day one, and do they know it?
  • How are probation review dates tracked?
  • Can you show that each new employee acknowledged key policies and safety rules?
  • Were written particulars updated the last time someone's terms changed after probation?

Bottom line

When a new employee's first months run on emails and memory, onboarding quality depends on which manager they report to and how busy that manager is. The steps are known; they are simply not scheduled, owned or recorded. Defining a journey for each role, anchoring it to the start date and tracking completion turns good intentions into a consistent process that shortens time to productivity and gives new people a reason to stay.

Sources and further reading

Related Mellorca reading

Article summaryOnboarding does not end on day one. Training, introductions, policy sign-offs, check-ins and probation reviews often depend on a manager remembering, so they happen late, unevenly or not at all.
Explore our solutionsStart a conversation