Free Calculator

How Long to Hand This Task to Someone Else?

Delegating a report, covering for a leave, or getting a system out of one person's head. Here is a realistic estimate of how many weeks until someone else can do it independently, and the two milestones worth planning for.

SimpleModerateVery complex

Steps, judgment calls, edge cases involved

NoneSomeVery strong
In one headPartialFull runbook
1h3h10h

Pairing, answering questions, reviewing

Weeks to fully independent

0

Can do it with supervision

Week 0

first clean run, watched

Independent by

–

if you start today

Owner time to invest

0 h

total, one-time cost

Documentation gain

0 wk

faster with a full runbook

Your Setup vs a Documented One

Documentation is the one lever with a second payoff: it speeds up this transfer and every future one. Here is your estimate against the same transfer with a full runbook in place.

Your setup

0 weeks

to independent

With a full runbook

0 weeks

and reusable next time

What This Number Means for You

Plan for independent, not for the first success.

This is delegation with a stopwatch on it.

Every task stuck in one person's head is a bottleneck and a single point of failure. The transfer is a one-time cost that buys back permanent capacity. The delegation guide covers the how, and the delegation ROI calculator shows when the payback lands.

Write the runbook once, benefit forever.

Documentation is the only input here that pays off twice: it speeds this transfer and removes the next one almost entirely. If the knowledge lives in one head, the highest-leverage first step is getting it onto a page, ideally by having the trainee write it as they learn.

About the numbers: Base weeks are set by task complexity (1 to 8), then adjusted by the trainee's related experience (up to ±30%), documentation quality (up to ±25%), and the owner's weekly help (up to ±15%). "With supervision" ≈ 35% of the full transfer. Owner time = weeks × the weekly help hours. The documented comparison recomputes with a full runbook. Judgment-heavy tasks resist documentation and lean on real reps, so treat those estimates as a floor. Planning estimates, not a training plan.

Frequently Asked Questions

How is this different from the onboarding timeline calculator?
Scope. The onboarding timeline calculator covers a whole new hire learning an entire role over months. This one covers a single task or responsibility being handed from one person to another: a report you want to delegate, a system only one person knows, a duty you need covered before someone goes on leave. Same idea, much smaller unit, and the number that matters is weeks to independent, not months to fully ramped.
Why does documentation matter so much?
Because undocumented knowledge transfers one interruption at a time. If the process lives only in someone's head, every question is a tap on the shoulder, and the transfer stretches out for as long as questions keep arising. A written runbook converts most of those interruptions into a fifteen-minute read, which is why the documentation slider moves the estimate as much as the trainee's experience does. Writing it down once also means the next person learns it without the first person again.
What does "fully independent" actually mean here?
It means the person can handle the task, including the non-obvious cases and the occasional thing going wrong, without checking with the original owner. That is later than "did it once successfully." The first clean run is the "with supervision" milestone; independence is when you would be comfortable being unreachable while they do it. Plan for the second date, not the first, or you will hand over too early and quietly take it back.
Can I go faster by just documenting everything up front?
Documentation helps enormously, but it has a ceiling: some knowledge is judgment, not procedure, and judgment transfers by doing the task with feedback, not by reading. The fastest realistic transfer is a written runbook plus a few real reps with the owner available to react. Docs alone leave the trainee confident right up until the first unusual case; reps alone leave them re-asking things a doc could have answered.
Is this time worth it? It is faster to just keep doing it myself.
This week, yes. Over any longer horizon, no. Keeping a task because transferring it is slower right now is the exact trap that keeps managers as bottlenecks and single points of failure. The transfer is a one-time cost that buys permanent capacity back, plus resilience for when the current owner is sick, busy, or gone. The delegation guide covers the mindset; this calculator just prices the one-time cost honestly so you stop deferring it.
What if the only person who knows it is leaving soon?
Then this is urgent, and the estimate is your countdown. If the weeks-to-independent number is longer than the time until they leave, you have a knowledge-loss risk on your hands, and the response is to compress: prioritize documentation immediately, schedule concentrated pairing time, and accept "independent on the common cases" as the realistic goal, with the rare cases captured in writing for later. A partial transfer with a runbook beats a clean transfer that does not finish in time.

A Task in One Head Is a Risk. Transfer It.

Budget the weeks, plan for independent rather than the first success, and have the trainee write the runbook as they learn.

Guide: How to Delegate → Calculator: Delegation ROI →

Related: Onboarding Timeline → Related: Team Capacity →

← All Calculators