Issue 02 · November 2026
Issues

02 / Cover Feature

The part you can't hand off.

Tools can prepare the work, speed it up and carry parts of it forward. What still asks for someone's judgement, earns another person's trust, and leaves someone responsible for the outcome?

Ariy&Co Editorial

Scroll to read ↓
Nia on museum steps in a tailored emerald dress and nude heels.
Nia on the museum steps.

Consider a hypothetical appointment-based service. A client has booked a one-hour session for Thursday afternoon. On Wednesday evening, they ask to move it to Friday because a work shift has changed. They also ask whether moving the booking means losing the deposit.

The published policy requires 48 hours' notice. Friday is full. The booking system can establish both facts. Neither tells the owner what response would be fair.

An assistant could explain the policy, offer the next available appointment, or ask whether the client wants to hear about a cancellation. It could also prepare the request for someone authorized to make an exception. What it cannot safely do is invent a free slot or promise a deposit transfer the business has not approved.

The request has two parts: finding another time and deciding what happens to a commitment already made. The first is a scheduling task. The second asks the business to exercise judgement.

This scenario is illustrative, not an account of an Ariy customer. Its usefulness is the question it leaves open: what would the person responsible need to know before deciding?

What are we actually handing over?

A handoff can mean several different things.

It can mean preparation: gather the information, summarize the history, draft a response.

It can mean execution: send the approved message, record the decision, book the available time.

It can also mean discretion: decide which response is appropriate, when the rule applies, and when somebody else should be involved.

Those are different permissions. Giving a system one does not automatically give it the others.

A useful assistant might prepare a thoughtful reply to a disappointed customer. It might have permission to send a routine explanation. That does not necessarily give it permission to make a promise the business has never agreed to keep.

The distinction can sound fussy until the promise reaches a person who relies on it.

Then it becomes the work.

The exception is where the job becomes visible

A process tells us what should normally happen. A profession includes knowing when that process needs interpretation.

Return to the Thursday booking. The client has given less notice than the policy requires, but the owner may know more than the calendar does. Was the policy clear when the booking was made? Has the business already incurred a cost? Is there a cancellation list? Would transferring the deposit be an affordable exception, or an offer the business could not sustain for others?

Neither automatic refusal nor automatic generosity resolves that judgement.

An experienced colleague may notice that a customer is asking a different question from the one their words appear to contain. “Can I move the appointment?” might also mean “Will I lose what I already paid?” or “Do I have to explain this difficult situation again?”

Noticing that possibility does not mean guessing the answer. It may mean asking one careful question before doing anything else.

This is a more demanding standard for delegation than producing a fluent reply.

The reply has to belong to the situation.

Nia and Aletheia discussing a bronze sculpture in a sunlit gallery.
Nia and Aletheia beside the bronze.

Judgement needs somewhere to land

It is tempting to describe judgement as the mysterious quality people possess and machines lack.

That explanation does not help much when designing a working service.

People make poor decisions too. They miss context, follow habits, confuse confidence with evidence, and forget what somebody promised last week. A human approval step is not automatically a meaningful safeguard.

The more useful questions are practical.

What information does the decision require? What is uncertain? What can this person or system authorize? What would make the decision worth revisiting? Who can act if the situation changes?

Software can help with all of those questions. It can preserve context, surface a contradiction, or make the consequences of an action easier to inspect. In a bounded situation, it may be reasonable to delegate the decision itself.

But the boundary needs an owner.

Someone has to decide what counts as a bounded situation, what evidence is sufficient, and which consequences require a different level of authority.

That responsibility remains even when the individual decisions become routine.

Nia listening to Aletheia in a sculpture courtyard.
A conversation in the courtyard.

Trust is built around what happens next

From the customer's side, a handoff is rarely interesting as an organizational event.

They want to know whether their request was understood, whether the next person has the information, and whether anything is actually going to happen.

In the booking example, “We have escalated this” leaves the client unsure whether to keep Thursday free or start making other arrangements.

A useful handoff would carry the original appointment, the requested change, the policy the client accepted, and the unresolved deposit question. It would also record what the client has been told, including any promised response time. It gives the receiving person enough to act without making the customer start again.

It also needs an honest account of its own status.

A message prepared for review is not a message sent. A request recorded is not an exception granted. A proposed appointment is not a confirmed booking.

Those distinctions may look small inside an interface. To the person waiting, they are the difference between a possibility and a promise.

Warm language helps. Accurate expectations matter more.

The cost moves

Delegation can remove effort from one part of a job and create it somewhere else.

A draft may take seconds to produce and several minutes to verify. A research summary may save reading time while creating a new need to inspect its sources. A queue of suggested actions may be useful until reviewing the queue becomes another full-time responsibility.

These are possibilities to measure, not reasons to reject the tools.

The relevant question is whether the whole task becomes easier to complete well.

That includes checking, correcting, explaining, and recovering when something goes wrong. It includes the effort imposed on the customer when an internal shortcut becomes an external inconvenience.

A system that saves the business five minutes by making a customer repeat their story has moved the cost. Whether that is acceptable deserves a deliberate answer.

The same is true of responsibility. Moving an action into software does not make its consequences disappear from the business.

A person in the loop needs a real job

“Human oversight” is an incomplete description of a workflow.

Which person? Looking at what? Before which action? With enough time and authority to change it?

If every routine decision needs approval, delegation may achieve very little. If approval means clicking through a long list without understanding the exceptions, the safeguard may exist mainly on paper.

A better review asks a specific question.

This source conflicts with that one. Which should we rely on?

This request falls outside the published policy. Can we offer an exception?

This action would create a new commitment. Who is authorized to make it?

The system should do enough preparation that the person can exercise judgement. It should also make it possible to disagree, ask for more information, or stop the action.

The point is to concentrate attention where it changes the outcome.

Nia walking beside the water in a fitted emerald dress and nude heels.
What would you do with the time?

What would you do with the time?

There is another question underneath the promise of efficiency.

If the administrative work became easier, what would the business protect with the time it recovered?

More appointments? Better preparation? A slower conversation with someone who needs it? A working day that ends when it is supposed to?

There is no universal answer.

But without an answer, saved time can simply become available capacity for another demand. Faster responses become an expectation. Extra output becomes the new baseline. The tool improves and the day remains full.

A thoughtful approach to delegation includes deciding what the benefit is for.

That is a business decision, and sometimes a personal one. Software cannot settle it merely by making another task faster.

The part that stays with you

The part you cannot hand off is not necessarily a permanent list of tasks.

The list will change. Tools will improve. People will learn to trust them with more, and discover places where that trust needs limits.

What remains is the obligation to decide what good work means in this situation, who has authority to act, and what you will do when the outcome falls short.

You can ask for help with those decisions. You can distribute them across a team. You can build systems that make them easier and more consistent.

You still need somewhere for responsibility to land.

A useful test for any handoff is therefore more demanding than “Can this be automated?”

If it goes wrong, will we understand what happened? Will someone be able to put it right? Will the person affected know where to turn?

The most convincing promise of delegation is room to give those questions the attention they deserve.