Ask an office manager what they would change about their week and they rarely say "more free time". They say something closer to "I would like the week to be mine". The Monday reminder emails, the mid-month payment run, the quarterly renewals chase: these are not hard tasks, but they set the rhythm. The calendar is organised around what the office needs doing, and the person is slotted into it.
That is a different thing from being busy. A person can be busy with work they chose and feel entirely in charge. A person can also have a quiet week and feel as if every hour has been spoken for in advance. Autonomy is about who decides the shape of the day, and routine administration is one of the places where that decision tends to be quietly taken away.
Routine as a schedule someone else wrote
Recurring work has a particular property: it does not wait. Supplier statements arrive on the same day each month. Staff leave requests pile up. Insurance, licences and subscriptions renew on dates set long ago. If a person is the only mechanism that notices these things, then the person is also bound to the dates. Skipping Friday afternoon is not really an option when Friday afternoon is when the debtors list has to go out.
The UK Health and Safety Executive's Management Standards on work-related stress treat control as how much say people have in how they do their work. The practices it lists include people being able to set their own pace where feasible, being consulted about their schedules, and having a say over when they take breaks. Those are not grand freedoms. They are the small ones that decide whether a working day feels chosen. A calendar crowded with recurring, memory-dependent duties limits every one of them.
It is worth noticing what the standard does not claim. It says nothing about how much work is acceptable, and it does not suggest that fewer tasks always means more control. It is about say, not volume. That distinction matters for what follows: the aim is not to remove work for its own sake, but to loosen the grip that fixed, personal routines have on when and how a person works.
What it means to let a system hold the routine
The idea is simple. A recurring task that follows a predictable pattern can be handed to a system that runs it on schedule, so that a person is no longer the thing that remembers. Microsoft's documentation for Power Automate describes this in plain terms: cloud flows can be triggered by an event, such as an email arriving, or run on a schedule, and it gives the example of a daily data upload. Its overview notes that predictable tasks can be automated once, with no need to create a flow for every run. Its approvals guidance describes how a request can be sent to a named approver, who can respond from their email inbox or an approvals centre, with the decision recorded and passed back to the requester.
These are descriptions of a tool, not claims about outcomes. What matters for this article is what such a tool changes in the shape of someone's week. The reminder goes out whether or not the office manager is in. The request waits for an answer instead of waiting for a person to remember it. The deadline is held by something that does not have a bad day.
An illustrative example
Consider an illustrative case, not a real one: a property management firm in Cape Town with a small administrative team. Every month, the office administrator sends rent statements, chases tenants who have not paid, and reminds owners about outstanding maintenance approvals. She has done this for years and is good at it. She also cannot easily take a long weekend in the first week of the month, because everything sits in her head and in a handful of manual steps.
Suppose the firm moves the predictable parts onto scheduled processes. Statements are generated and sent on a set date. Reminders go out at agreed intervals after the due date. Maintenance approvals are sent to owners with a clear deadline and a recorded answer. The administrator is no longer the clock. She reviews exceptions: the tenant who has called to say a payment is delayed, the owner who has not answered after two attempts.
What changes is not only the hours she works. It is that she can choose where to put them. She might spend the freed time on the difficult owner conversations that she used to postpone. She might simply leave on time on the first Friday of the month. Either choice is hers. Mellorca's reading is that the second kind of choice is as legitimate as the first.
What could realistically change
- List the recurring tasks and their dates. Many offices have never written down the routines that govern their calendar. A single list, with who does each task and how often, is usually revealing. Mellorca has written about routines that outlast their reasons in the daily routine nobody remembers the reason for.
- Separate the predictable from the judgemental. A reminder that always reads the same is a candidate for scheduling. A message to a tenant in difficulty is not.
- Let the person who does the work design the change. Someone who understands the routine will know which steps are mechanical and which carry hidden judgement.
- Keep the exception path visible. A scheduled process should tell a person when something has not worked, not fail silently.
- Review approvals as well as reminders. A request that waits in an inbox is another form of routine memory. Mellorca explores why in why approval processes become bottlenecks.
What changes first, and the business outcome
The first change is that dates stop depending on a single person's presence. Statements go out when they are meant to. That tends to make cash collection more regular, and it reduces the number of items that slip when someone is ill or on leave. These are plausible effects and will differ widely between businesses; Mellorca does not claim a measured figure.
A second change is less visible: the person stops carrying a mental calendar of other people's deadlines. Mellorca has described the cost of that carrying in the slow leak of time through manual reminders.
The human dividend
The dividend is autonomy first, with time as a companion. It is the ability to decide when to work on what, to take a day without arranging a rota of favours, and to put attention where a person's judgement matters. It is deliberately not a prescription. Some people will use the room to learn something new. Others will use it for family, rest or simply a shorter day. A business that decides on their behalf what the freed hours are "for" has missed the point.
The trade-offs
Handing routine to a system can reduce a person's sense of control if they no longer understand what the system is doing. A process that runs without anyone able to explain it is a dependency, not a freedom. Mellorca's impact material on automation understood by one employee describes how the dependence can simply move from a routine to a person who maintains it.
Some routine is useful. Reading through a monthly statement run can be the moment a person notices a pattern. Taking every such moment out of the week can remove the contact with the work that built expertise in the first place.
Freed time can also be absorbed. A business that sees spare capacity may fill it with new tasks, and the autonomy never arrives. That is a management choice, and it is worth making consciously.
Finally, automation shifts some risk. A wrong date or address, repeated on schedule, can reach many people before anyone notices. Testing, checking the first few runs and having a clear owner reduce this, but do not remove it.
Why it matters
Administrative routine looks like a small matter next to strategy and growth. Yet it is often where the daily experience of work is decided. The World Health Organization lists lack of control over job design and workload among the risks to mental health at work, and notes that involving workers in decisions is one recommended way to build an enabling environment. Mellorca treats that as general background, not proof about any one office.
The narrower hypothesis offered here is that when predictable work is held by systems that are understood and owned, some people regain the ability to arrange their own weeks. The measure of success is not how many tasks have been automated. It is whether the person who used to be the clock can now decide what time it is for them.
Sources and further reading
- Management Standards - Control - HSE (last verified 10 October 2026)
- Overview of cloud flows - Power Automate (last verified 10 October 2026)
- Create and test an approval workflow with Power Automate - Power Automate (last verified 10 October 2026)
- Mental health at work (last verified 10 October 2026)
Related Mellorca reading
- The Manager Who Finally Owns Their Budget View
- What Changes When People Can See Their Own Numbers
- When Your Calendar Belongs to Other People's Systems