Wrivio
Get Wrivio
5 min readBy Wrivio Team

How to Write a Request to Another Team That Has Its Own Priorities

Some of the hardest messages at work go to people you have no authority over. You need a design review from another team, an API change from platform engineering, or a contract check from legal. They have their own queue, their own manager, and no obvious reason to put your work first.

Most cross-team requests fail in the same way. They describe your problem at length and never say what the other team should actually do, by when, or what happens if they cannot. The reader files it under “later” and later never arrives.

Lead With The Ask, Not The Backstory

The reader is triaging. If the first paragraph is about your project’s history, they will not reach the request. Put the ask and the date first, then the reason. The same principle sits behind plain language guidance for writing to an audience: the reader should know what you want from them before they read why.

Before:

Hi team, so as you may know we have been working on the new onboarding flow for a few months and there have been a lot of changes, and one thing that came up is that we might need some help with the notification service at some point.

After:

Hi Dana, could your team add a “welcome_sent” event to the notification service by 21 November? Our onboarding launch on 5 December depends on it. The change is roughly one new event type; details below.

The second version names a person, a deliverable, a date, and the consequence. It can be accepted, declined, or negotiated in one reply.

Size The Request Honestly

Other teams decide fast when they can see the cost. Say how big the work is in your best estimate, and say what you have already done so they are not starting from zero. If you are guessing, say so. Overpromising “it’s tiny” burns trust the first time it is wrong; see how to give a time estimate in writing without overpromising.

Explain Why It Matters To Them

You do not control their priorities, but you can connect the request to something they already care about. A shared customer commitment, a dependency on their own roadmap, or a quarterly goal both teams own are legitimate reasons. Flattery and vague urgency are not. If there is no honest connection, say so and ask whether their manager should weigh in.

Offer Options Instead Of A Deadline Ultimatum

“We need this by Friday” invites a flat no. Give them a way to say a partial yes:

  • A smaller version that unblocks you now.
  • A later date, with the consequence for you stated plainly.
  • A pointer to someone else who could do it.
  • A short call instead of a long thread.

Ask for a reply by a specific day, even if the answer is no. A clear no lets you re-plan, which beats silence.

A Wrivio Context for cross-team requests could say:

Rewrite this as a request to a colleague on another team who does not report to me. Put the specific ask and the date in the first two sentences, then the reason, then the estimated size of the work. Offer one lighter alternative. Keep every name, date, system name, and commitment exactly as written. Do not add urgency, flattery, or apologies that are not in the draft.

Press Ctrl+Shift+Space, paste the draft, and check the diff to confirm the date and the deliverable survived unchanged.

Make The Escalation Path Visible Without Using It

If the request stalls, you will need a next step. Mention it early and gently: “If it is easier, I am happy to raise the priority question with both our managers together.” That tells the reader you are not going around them. When a reply does not come, follow up once with a shorter version of the original ask; see how to write a nudge email without sounding pushy. If the delay puts your work at risk, report it as a project blocker update to your own manager rather than complaining sideways.

Close The Loop Afterward

When the work lands, thank the person specifically and tell their manager if the work was meaningful. Teams remember who made their work visible, and the next request becomes easier. For general asks that are less formal, how to ask for help at work in writing covers the one-to-one version.

Common Questions

How do I ask another team for help when they are overloaded?

Make the request small and specific, state the real cost and deadline, and offer a lighter alternative they can accept instead. Overloaded teams say yes to clear, bounded asks far more often than to open-ended ones.

Should I copy their manager on the first message?

Usually not. Copying a manager on a first request reads as pressure and can damage the relationship. Ask the person directly first, and involve managers together if the priority question genuinely needs resolving.

How long should I wait before following up?

Give a reasonable window based on the date you asked for a reply, commonly a couple of working days for a small request. Follow up once with a shorter message restating the ask and the date.

What if they say no?

Treat it as useful information. Ask whether a smaller version, a later date, or another owner is possible, then re-plan and tell your own manager if the schedule is affected.

Download Wrivio for Windows to turn a rambling cross-team request into one with the ask, the date, and the alternative up front.