A three-day role is not a five-day job compressed

The first draft of the three-day role at Hantam Service Cooperative, a fictional shared-services cooperative in the Northern Cape, took HR about ten minutes. They copied the cloud financial operations analyst's job description, changed "Monday to Friday" to "Tuesday to Thursday" and adjusted the salary line. Every responsibility stayed. So did every meeting invitation, the expectation of same-day answers to members and the analyst's name on the cost-alert distribution list.

The platform engineer who read it summed it up: "This is the same job with longer Wednesdays." He was right. The draft did not describe a three-day role. It described a five-day job compressed into three days, and the person in it would have been the one paying for the difference.

Part 1 showed how Hantam measured a real reduction in the analyst's workload and decided, with her agreement, to put part of that gain into a three-day role for a six-month pilot. This article is about the design work that has to happen before day one, so that the role is genuinely smaller and not just shorter.

Compression is a different idea, and a legal term

South African law already has a name for fitting the same hours into fewer days. Section 11 of the Basic Conditions of Employment Act deals with a "compressed working week": a written agreement may require or permit an employee to work up to twelve hours a day, including meal intervals, without overtime pay, as long as the arrangement does not exceed 45 ordinary hours or ten hours' overtime in a week, or more than five days a week. Section 9 sets the usual limits of 45 ordinary hours a week and nine hours a day for someone working five days or fewer.

A compressed week keeps the hours and changes their shape. It can suit some people and some work. It is not what Hantam set out to do, and it is not what a reduced-time role is. A three-day role reduces the work. That only happens if someone decides which work leaves the role and where it goes.

The informal version of compression is worse than the formal one, because nobody agrees to it. The responsibilities stay, the hours drift up on working days, messages arrive on non-working days, and the employee absorbs the gap to avoid looking as though the arrangement is failing.

Start from accepted outcomes, not the job description

Job descriptions list activities. A reduced-time role has to be designed from outcomes, because outcomes are what tell you whether the smaller role still works. The approach is the same one CloudNala uses for engineering roles in Engineering roles are defined by outcomes, not tools, applied here to time instead of tools, and it borrows the discipline of defining the outcome and baseline before changing anything.

For the analyst role, Hantam wrote down four things:

• Accepted outcomes. Cost allocated accurately to all 40 member organisations each month; member cost reports published with commentary members can act on; anomalies above an agreed threshold investigated and explained; commitment and rightsizing recommendations made each quarter with their evidence. These follow the cooperative's own cloud cost governance policy.
• Service levels. Reports on the fifth working day. Member queries answered within two working days. Cost anomalies acknowledged on the day they are raised, by someone.
• Non-negotiables. The analyst signs off the monthly allocation. Nobody else does, and it is not delegated to the AI assistant.
• What the role is not. It is not the first responder for every member question, the owner of the onboarding project, or the person who attends every platform meeting "for visibility".

The last item is the one most redesigns skip. It is also the one that stops the role refilling.

The scope ledger: keep, move, drop, cover

With outcomes defined, Hantam went through every recurring activity in the analyst's measured week and put it in one of four columns. One activity was split between two of them.

The kept work adds up to about 19.5 hours a week against a contracted 24. That leaves around 4.5 hours, close to 20%, of slack. Slack is not waste. It is what absorbs a difficult month-end, an audit request or a member's unexpected bill without pushing work into the non-working days. A redesign that fits the role exactly into its contracted hours has no capacity for an ordinary bad week.

Two checks keep the ledger honest. First, every "move" needs a named receiver who has agreed to take the work and has the time to do it. Moving work to a colleague who is already full is not redesign; it is transferring the cost of the reduced role to someone else. Second, every "drop" needs the person who received the output to agree they can do without it. The fortnightly cost note replaced two meetings only after the platform lead said it would do. Replacing a standing meeting with a short written record is a decision-system change as much as a time saving, a point made in Small teams need better decision systems, not more tools.

Continuous coverage and concentrated expertise

Some responsibilities need someone available every working day. Others need deep expertise applied at particular points. A three-day role can hold the second kind comfortably. It cannot hold the first kind alone.

At Hantam, anomaly acknowledgement needs continuous coverage, so it moved to the rota. The monthly allocation needs concentrated expertise on fixed days, so the role's days are set around it. Her regular days are Monday to Wednesday. In close week she works the first three working days of the month instead, dropping other days, as agreed in writing. Flexibility runs both ways and has a ceiling. "Available if needed" on non-working days is not a coverage model.

The coverage design, including handovers, decision records and escalation for non-working days, is the subject of Part 4.

Safeguards against intensification

The main risk of a reduced-time role is not that the work fails. It is that it succeeds at the employee's expense. The UK four-day-week pilot report is useful here because it looked for this. Across the trial, 36% of employees reported an increase in work intensity and 31% a decrease, and interviews in one larger company that had not prepared much found staff describing their work as a battle to get through long to-do lists, with second-hand accounts of colleagues regularly working into the evenings (full report, February 2023).

Hantam agreed four signals it would watch from the start, and told the analyst what they were:

1. Hours logged against hours contracted, weekly, with a conversation if logged hours run above contract for two weeks in a row.
2. Activity on non-working days: messages sent, reports edited, alerts acknowledged. A little is normal. A pattern is a design failure.
3. Rework and corrections in the monthly allocation, as a quality signal that the role is too tight.
4. The load on the people who received moved work, measured the same way, so that the role's success is not borrowed from colleagues.

These are measures of the design, not of the person. If they turn red, the scope ledger is reopened. The analyst is not asked to try harder.

Terms, in outline

Reduced-time roles have legal consequences that HR and employment-law advisers must review. The points below are general information, not legal advice, and were checked against the legislation on 5 November 2026.

• Part-time employees earning below the threshold. Section 198C of the Labour Relations Act, inserted in 2014, requires an employer to treat a part-time employee, taking their working hours into account, on the whole not less favourably than a comparable full-time employee doing the same or similar work unless there is a justifiable reason, and to give comparable access to training and skills development and the same access to opportunities to apply for vacancies. It does not apply to employees earning above the threshold set under section 6(3) of the Basic Conditions of Employment Act, to some small employers, to employees who ordinarily work less than 24 hours a month, or during the first three months of employment. Because the threshold is an earnings figure, a reduced salary may bring someone who was above it below it, so ask your advisers where the new pay falls.
• Annual leave. The default is 21 consecutive days of leave a cycle, which is three calendar weeks: for someone who works three days a week, that is nine working days. By agreement, the Basic Conditions of Employment Act also allows one day of leave for every 17 days worked, or one hour for every 17 hours worked.
• Sick leave. The entitlement in each 36-month cycle equals the number of days the employee would normally work in six weeks, so it scales with the working pattern.
• Family responsibility leave. Section 27 applies only to employees who have worked for the employer for longer than four months and who work at least four days a week for that employer. A three-day employee has no statutory entitlement to it, which is a gap an employer can close by policy. Hantam did.

Changing an existing employee's working time and pay is a change to their terms, which generally needs the employee's agreement; take advice before changing terms. Hantam recorded the pilot in a written agreement with a review date and a right for the analyst to return to full-time work at the end of it.

Before day one: a checklist

• Accepted outcomes, service levels and non-negotiables are written down.
• The role states what it is not responsible for.
• Every recurring activity is in the scope ledger, and every "move" and "drop" has a named, agreeing receiver.
• Kept work fits the contracted hours with roughly 15 to 20% slack.
• Continuous-coverage duties are not held by the reduced-time role alone.
• Working days are fixed, with any swap rule agreed and capped.
• Intensification signals are agreed and shared with the employee.
• Pay, leave, benefits and the return-to-full-time right have been reviewed by HR and employment-law advisers and recorded in writing.

Key points

• A three-day role reduces the work. A compressed week keeps the work and changes its shape, and in South Africa "compressed working week" has its own legal meaning.
• Design from accepted outcomes, service levels and non-negotiables, and say what the role is not.
• Use a scope ledger: keep, move, drop and cover. Moved work needs a receiver with capacity; dropped work needs the recipient's agreement.
• Leave real slack. A role designed to exactly fill its hours cannot absorb an ordinary bad week.
• Watch for intensification from the start, and treat the signals as design faults, not personal failings.

Next: Part 3, Hire the outcome, not the attendance pattern. All parts are on the series page.

How CloudNala can help

CloudNala helps teams redesign roles when AI and process change reduce workload. We build the scope ledger from measured work, test whether kept work fits the hours with sensible slack, design coverage for continuous duties and set up the intensification signals that tell you early if the role is too tight. We work with your HR and employment-law advisers on terms, and with your managers on making the change stick.

Work with CloudNala

CloudNala helps organisations move from technology ambition to practical execution across cloud, AI, data, platform engineering and digital services.

Whether you are exploring AI, modernising your cloud environment, building a public-sector digital service, or turning an idea into a working MVP, we can help you shape the roadmap and deliver the next step.

Talk to us about AI and work design or write to us at consult@cloudnala.co.za