Why delegated work keeps coming back, and how to hand it off so it stays gone.

1. You handed off the task, but kept the decision. If every judgment call still needs your approval, you did not delegate the work. You delegated the typing. The person has to come back to you whenever something is not exactly like last time, and in a real business, almost nothing is exactly like last time.
2. The steps only exist in your head. You have done this task so many times that you no longer notice the small calls you make along the way: which folder, which tone, which client gets a phone call instead of an email. None of that transfers unless it is written down, and “just watch me do it once” rarely captures it.
3. Nobody defined done, or what to do when something breaks. Without a clear finish line, a careful person checks in to be safe. Without a rule for exceptions, they stop and wait. Both look like the task coming back to you.

Before you hand anything off, write four short answers. They fit on half a page, and they do most of the work.

1. The outcome. What does done look like? “Send the invoices” is a task. “Every client invoiced by the 3rd, with the PDF saved to their folder and the send logged” is an outcome someone can check their own work against.
2. The boundaries. Which decisions can they make alone? Be specific: refunds under a set amount, rescheduling without asking, anything involving a particular client comes to you. Clear limits make it safer to act, not riskier.
3. The steps. Record yourself doing the task once, talking through each choice as you make it. That recording becomes the first draft of a written process, and the person refines it the first few times they run it.
4. The return format. When something does need you, agree on how it comes back. The one we use is 1-3-1: one clearly defined problem, three possible solutions, one recommendation. You stop answering open questions and start approving decisions.

This is where AI earns its place in delegation. It can turn your recorded walkthrough into a written first draft of the process. It can send the reminder before a deadline, fill in the recurring fields, and flag when something does not match the usual pattern.

What it cannot do is decide that this particular client needs a phone call instead of an email, or notice that a polite request is really a complaint. That is the part a person carries: the context, the relationships, and the calls that depend on knowing your business.

So a good handoff has two receivers. Repeatable steps go into a system. Judgment goes to someone you trust, who oversees that system and brings you recommendations instead of questions. That is how Kalinaw works: AI handles what should be automated, and people handle what needs judgment and care.

A good handoff does not mean zero questions on day one. Early questions are how the process gets finished: each one reveals a step you forgot to write down. Add the answer to the process, and that question does not come back.

The sign it is working is not silence. It is questions getting fewer and better, until what reaches you is a recommendation rather than a request for permission. Honesty about what someone does not know yet is part of that. One of our clients put it this way:

You can read more from our clients on the testimonials page.

1. Pick one task you do at least weekly and would happily never do again. Not the most important one. The most repeatable one.
2. Record yourself doing it once, narrating every choice as you make it.
3. Write the four answers: outcome, boundaries, steps, and return format.
4. Review it together after the first three runs, and fold every question into the written process.

When that task stops coming back, pick the next one.