How should I explain decision-making authority when I hand off a task?

Make the boundary explicit in the handoff, rather than relying on phrases like “use your judgment” or “keep me posted.” Those can mean different things to different people. Separate decisions into three levels:

1. Decide independently: choices the assignee can make and communicate afterward.
2. Consult before deciding: choices the assignee can recommend or explore, but should discuss with you before committing.
3. Reserved for you: choices you will make, even if the assignee gathers information or prepares options.

For each level, name decisions that could actually arise in this task. For instance, in an assumed task of preparing a draft presentation, the assignee might independently organize sections, consult before changing the agreed audience or scope, and leave any change to the delivery date with the manager. Those are examples to adapt, not universal rules.

Also distinguish consultation from approval: say plainly whether they may proceed while you are being consulted. If you need to agree first, say “pause this decision until we’ve discussed it.”

Anchor the boundaries to the task’s agreed goal, scope, and constraints. You do not need to anticipate every detail. Name a few representative choices and describe a rule for similar choices.

A compact handoff could say:

“Outcome: [what the work should achieve]. You can decide: [routine choices within the agreed goal and constraints]. Talk with me before deciding: [choices that could change scope, affect another person’s work, or create a commitment]. I will decide: [named decisions retained by me]. If unsure: [pause, gather options, and contact me through agreed channel].”

Then test it with one or two realistic examples: “If you find that option A won’t work, what would you do?” If the answer reveals a different interpretation, revise the wording together. The purpose is not to remove judgment; it is to make the limits of delegated judgment visible.

Give them a simple default for the unknown case. For example: “If a decision might change the agreed outcome, scope, timing, or commitments to others, don’t commit on my behalf. Send me the issue, your recommended option, and what happens if we wait. For a reversible, low-impact choice within the agreed boundaries, use your judgment and note what you decided.”

Adjust that rule to fit the work. The key is to tell the person what to do while waiting: continue with unaffected parts, collect information, or pause the affected part. Set a practical contact method and response expectation, such as [team channel] and [agreed response window]. Don’t promise availability you can’t provide. If a decision is time-sensitive and you cannot be reached, agree beforehand who else can decide or what safe, non-committing fallback to use.

Here is a worked example using an assumed task: preparing a first draft of a team update. Replace the details and boundaries with your own:

“Please prepare a first draft of the team update by [date]. The goal is to summarize [agreed topics] for [audience]. You can choose the order of sections, wording, and layout, and correct routine errors. Before adding a new topic, changing the audience, or requesting work from another team, discuss it with me first; wait for my agreement before committing. I’ll decide whether to change the deadline or the agreed purpose. If you discover an issue outside these examples, send me the issue, your suggested options, and any timing impact in [team channel]. Continue with unaffected sections while we resolve it. If you can’t reach me and a choice could change the scope or create a commitment, don’t make that commitment; use [agreed fallback] and flag it in your handoff.”

Before sending it, check that the assignee can tell what they may decide, which decisions require prior discussion, and which decisions remain yours. Ask them to reflect back any boundary that feels unclear. Revisit the agreement if the task’s scope or constraints change.