How to Delegate a Project to a Direct Report in English

Delegating well is not about handing off less work with more words. It's about handing off the right amount of context so the other person can act without you — and without guessing.

Too little:

"Can you take the vendor migration? Let me know if you have questions."

Too much control:

"Take the vendor migration, but check with me before every decision, even small ones."

More useful:

"I want you to own the vendor migration end to end. Here's what's included and what isn't. Anything under $10k or inside the current timeline, decide it yourself — I've got you covered if a stakeholder pushes back. Let's touch base every Friday."

That version names the scope, sets the decision boundary, offers protection, and sets a rhythm for checking in — all before the work starts.

Spell out the scope, not just the task

"Spell out" means stating something in full, itemized detail — what's included, what isn't, and where the edges are — instead of leaving the other person to infer it.

Vague handoff:

"Can you take the vendor migration?"

Spelled out:

"Own the vendor migration: the contract renegotiation, the data cutover, and the rollback plan. Not included: the vendor's onboarding training — that's staying with me for now."

Useful phrases:

• "Let me spell out exactly what's included and what isn't."
• "Here's what you own: [list]. Here's what stays with me: [list]."
• "If something comes up that isn't on this list, come to me — don't assume it's included."

A task handed off without its edges spelled out gets reinterpreted differently by every person who receives it. Spelling it out once, at the start, prevents most of the mid-project "wait, was that included?" conversations.

For the difference between this and simply explaining something, see Spell Out vs Explain: What's the Difference?.

Set guardrails, not a leash

"Guardrails" are the boundaries within which someone can decide and act freely — not a list of steps they must follow, and not permission you grant one decision at a time.

Sounds like a leash:

"Check with me before you make any changes to the timeline."

Sounds like guardrails:

"Anything under $10k or inside the current timeline, decide it yourself. Anything that touches the external launch date, loop me in first."

Useful phrases:

• "Here are the guardrails: inside [boundary], it's your call. Outside it, come to me first."
• "You don't need approval for [category] — you do need it for [category]."
• "These guardrails exist so you can move fast on most of this without waiting on me."

Guardrails answer a different question than scope does. Scope says what the work includes. Guardrails say how much of the decision-making the direct report owns inside that work. Skipping this step is what turns "I delegated it" into "I'm still approving everything."

For the distinction from a stricter boundary, see Guardrails vs Boundaries: What's the Difference? and How to Use 'Guardrails' at Work.

Give air cover, not just a task

"Give someone air cover" means using your own standing or authority to protect a person's ability to do the work — absorbing outside pressure or pushback so they can focus on execution, not just wishing them well.

Encouragement, not protection:

"Good luck with it — I'm sure it'll go fine."

Actual air cover:

"If the vendor's account team pushes back on the new terms, tell them to talk to me directly. You don't need to win that argument yourself."

Useful phrases:

• "If [source] pushes back, send them to me — I'll handle it."
• "I'll give you air cover on this with [stakeholder group]; you focus on the work."
• "You have my backing on [decision area] — I'll support the call if anyone questions it."

Air cover is what makes real ownership possible. Without it, a direct report with full scope and real guardrails can still end up fighting battles above their level on every difficult call.

Set a cadence, don't disappear or hover

"Cadence" is a deliberately recurring pattern for checking in — a rhythm, agreed in advance, rather than either constant interruption or no contact at all.

Hovering:

"Just send me an update whenever something happens, and I'll probably check in most days."

A set cadence:

"Let's touch base every Friday for 15 minutes. Between those, only reach out if something needs a same-day decision."

Useful phrases:

• "Let's set a cadence: [frequency], for [purpose]."
• "Outside our regular check-in, only come to me for [specific trigger]."
• "This cadence is a starting point — we can adjust it once you're further in."

A named cadence tells the direct report exactly when they'll have your attention, which reduces the pressure to ping you constantly — and reduces the temptation for you to check in more than the work actually needs.

For the difference between a fixed cadence and an informal habit, see Cadence vs Schedule: What's the Difference?.

A practical delegation structure

Combine the four parts into one handoff conversation:

"I want you to own [project]. Here's what's included: [scope], and what isn't: [exclusions]. Inside [guardrail], it's your call — outside it, loop me in. If [stakeholder] pushes back, send them to me. Let's touch base [cadence]."

Example:

"I want you to own the vendor migration end to end — the contract renegotiation, the data cutover, and the rollback plan. The onboarding training stays with me for now. Anything under $10k or inside the current timeline, decide it yourself. Anything touching the external launch date, loop me in first. If the vendor's account team pushes back on the new terms, send them to me. Let's touch base every Friday for 15 minutes."

A realistic handoff dialogue

Manager: I want you to own the vendor migration end to end.

Direct report: The whole thing? Including the contract terms?

Manager: Yes — the contract renegotiation, the data cutover, and the rollback plan. The onboarding training stays with me for now, since legal already has a version in review.

Direct report: Got it. What do I need to check with you on versus just decide?

Manager: Anything under $10k or inside the current timeline, that's your call. If it touches the external launch date, loop me in first.

Direct report: And if the vendor pushes back on the new payment terms?

Manager: Send them to me directly — you don't need to win that fight yourself. Let's touch base every Friday to see where things stand.

The direct report leaves knowing exactly what they own, what they can decide alone, and where the manager still has their back.

Common mistakes

Mistake 1: Delegating the task but not the scope

Incomplete:

"Can you take the vendor migration?"

Complete:

"Own the vendor migration: contract, cutover, and rollback plan. Onboarding training isn't included."

Without a spelled-out scope, "delegating" a project quietly becomes checking every assumption the direct report made.

Mistake 2: Calling it delegation while approving every decision

Sounds delegated, isn't:

"It's yours — just run every change by me first."

Actually delegated:

"Inside the current budget and timeline, it's your call. Outside that, loop me in."

If nothing falls inside the guardrails, the work hasn't really been delegated — it's been assigned with an approval step attached.

Mistake 3: Skipping the cadence and leaving contact ambiguous

Ambiguous:

"Just keep me posted."

Set in advance:

"Let's touch base every Friday, and reach out outside that only for a same-day decision."

Without a stated cadence, both people default to different assumptions — one expects daily updates, the other expects to be left alone until the deadline.

Practice scenarios

Practice delegating a project in situations like:

• handing off a project you've owned for months to someone new to it
• delegating to someone more senior, where the guardrails need to feel like trust, not oversight
• a direct report who keeps checking in more than the work requires
• a handoff where external stakeholders will test the boundary you just set

Useful practice phrases:

• "Here's what's included, and here's what isn't."
• "Inside [guardrail], it's your call — outside it, loop me in."
• "If [stakeholder] pushes back, send them to me."
• "Let's set a cadence: [frequency], for [purpose]."

Lyra Practice gives managers realistic delegation scenarios, with feedback on whether the handoff actually transfers ownership — not just a task.

Delegating well is not about saying less. It's about naming the scope, the decision boundary, the backing, and the rhythm clearly enough that the other person can move without you.

Return to English for Managers for more language on delegation, feedback, priorities, and execution.

Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.