When Parental Leave Means Handing Over an Undocumented Job

Few life events are as planned for, and as unpredictable, as the arrival of a child.

There are weeks of preparation, appointments and conversations. And at work, for many people, there is a quieter task running alongside: trying to write down a job that has never been written down, so that someone else can do it for a few months.

This is the situation this piece examines. Not parenthood itself, which Mellorca has no business advising on, but the operational question underneath it. What happens to work that only lives in one person's head, when that person needs to be somewhere else?

A change in who takes leave

In South Africa the question has recently become broader. On 3 October 2025 the Constitutional Court handed down judgment in Van Wyk and Others v Minister of Employment and Labour. As summarised by Polity and by BDO South Africa, the Court found the maternity and parental leave provisions of the Basic Conditions of Employment Act unconstitutional and ordered an interim position: parents, whether biological, adoptive or commissioning, are collectively entitled to four months and ten days of parental leave, shared as they agree, or as equally as possible if they cannot agree. A single employed parent receives the full period.

BDO's guidance notes that employees must give written notice, generally at least four weeks in advance for a birth, and that HR and payroll systems built around separate maternity and paternity categories may need to be redesigned. Parliament has until October 2028 to amend the legislation, but the interim arrangement applies now.

The legal detail belongs with employment lawyers. The operational consequence is simpler to state. Extended parental leave is no longer something many businesses can plan for in only one kind of role or one kind of employee. A senior estimator, a lead developer, a sales manager or the person who runs the month-end may now be the one going on leave for a substantial period.

Some of those roles have never been designed to be covered.

The handover that is really a reconstruction

When a role is well documented, a handover is mostly a transfer: here are the processes, the open items, the contacts and the decisions you may need to make.

When it is not, the handover becomes something else. The person leaving has to reconstruct their own job from memory, under time pressure, at exactly the moment their attention is most needed elsewhere. Small but critical knowledge is easy to miss: which client must be called before an invoice is sent, which supplier needs a purchase order number in a particular format, which report has a manual adjustment every quarter.

The record behind this story names two human taxes: presence and confidence. They are hypotheses, not findings, but they follow logically from the mechanism.

Presence, because if the job cannot run without its holder, the holder is likely to be contacted during leave, or to feel they ought to check in.
Confidence, on both sides. The person on leave cannot be confident the work is safe; the colleague covering cannot be confident they have understood it.

We should be careful here. People respond to leave in very different ways. Some will want to stay lightly in touch, and that is a legitimate choice. The concern is not contact itself. It is contact that happens because the system leaves no alternative.

An illustrative handover

Consider an illustrative example: a Durban logistics broker with around twenty-five staff. The operations coordinator, who has been with the business for six years, is about to take three months of parental leave.

Customer-specific rules for documentation and billing live in the coordinator's email history and memory.
Exceptions are handled through phone calls and WhatsApp messages with carriers the coordinator knows personally.
There is no written process; there is a person.

In this scenario, the final four weeks before leave are spent producing a long handover document late in the day, after normal work. The colleague covering reads it but cannot test it until situations arise. During the leave, there are calls. Not many, but enough that the coordinator never fully stops carrying the job.

Nothing in this example involves bad intent. It is simply what happens when a role grows faster than the system around it, a dynamic explored in Mellorca's work on key-person dependency as a systems problem.

What could realistically change

The interventions are mostly ordinary good practice, done earlier rather than in a rush.

Document continuously, not at departure. Short, living process notes written as work happens are far easier than a reconstruction under pressure. Mellorca has written about which processes need documentation first.
Move work out of private channels. Customer rules and exceptions recorded in a shared system, rather than in one inbox or phone, are available to whoever is covering.
Cross-train before it is needed. A colleague who has done the work a few times while the role holder is present will cover far better than one reading a document for the first time.
Agree contact rules explicitly. What, if anything, would justify contacting someone on leave, and through whom? Writing this down protects both sides.
Design for absence generally. Workflows that survive staff changes also survive leave, illness and resignation.

Technology helps where it makes knowledge shared by default: a ticketing or job system instead of personal email, a shared customer record instead of private notes. But the decisive step is organisational. Someone has to decide that roles should be coverable, and allocate time for it.

The first consequence, and the business outcome

The immediate change is that a handover becomes shorter and less fraught, because most of what needs handing over already exists in shared form. The colleague covering has done some of the work before.

The business outcome is continuity. Customers experience fewer gaps. The business is less exposed when any individual is away, for any reason. And compliance with new leave rules becomes an operational matter, not a crisis each time someone gives notice.

The human dividend

The dividend is presence: a greater ability for the person on leave to be fully where they are, for as much of that time as they choose. Alongside it sits predictability: the reasonable expectation that the work will continue, and that there will be a job to return to that has not quietly fallen apart.

For the colleague covering, there is a dividend too. Covering a documented role is a manageable stretch. Covering an undocumented one can be an exposed and anxious few months.

The trade-offs

Documentation takes time that busy small teams rarely feel they have, and its value is only visible later.
Making work shareable can feel like making people replaceable. Some employees value being the person who knows; that concern deserves an honest conversation rather than dismissal.
Cover is still a cost. A colleague absorbing extra work for three or four months may carry their own human tax unless workload is genuinely redistributed.
Some people want to stay involved. Good systems should make contact optional, not forbidden.

Why it matters

Parental leave is meant to be time given to something that matters more than the job. If the way work is organised means that time is partly spent carrying the job anyway, the leave exists on paper but is diminished in practice.

Mellorca's interpretation is that this is a design question, not a question of individual commitment. A role that cannot be covered is a fragility in the business. Fixing it is useful at any time. At the point of a life transition, it is the difference between leave that is taken and leave that is truly available.

Sources and further reading

Constitutional Court Redefines Parental Leave: Key Implications for Employers and Professionals (last verified 10 October 2026)
SA Shift from Maternity Leave to a Unified Parental Leave System What Every Employer Must Know - BDO (last verified 10 October 2026)