How to say "that's not my job" professionally

The professional version of "that's not my job" is a redirect: you name the person who owns the work, do the one small piece you can do right now, and hand it over in writing. The phrase itself never has to be typed.

It is usually true, which is exactly what makes it tempting. Being right about ownership does nothing for the person staring at a broken thing, and they will remember your tone long after they have forgotten who was technically correct.

A good redirect moves the work to its owner and leaves you out of the story.

What people hear when you say it

People hear "I do not care whether this gets done", which is almost never what you meant.

The person asking usually has no idea how the work is divided. They asked you because you were visible, or because you helped last time, or because your name sits at the top of a document nobody has touched since. Their picture of your job is a guess.

So a scope refusal answers a question nobody asked. They wanted the thing fixed. You handed them an org chart.

Correct, and useless.

The cost arrives later and quietly. People start routing around whoever bounces things, including on the days when the work really is yours, and nobody announces that this has happened. You notice you are being looped in later than you used to be.

Ask who owns it, not whether it is yours

Before you reply, work out who the owner is, because a redirect without a name is a bounce with better manners.

Four questions get you there fast:

• Who has the access or the approval this needs?
• Who fixed it the last time it broke?
• Who answers for it if it stays broken?
• Is there an owner at all, or has this fallen into a gap?

If you cannot answer any of them, say so. "I am not the owner and I am not sure who is, give me until the end of the day and I will find out" beats a clean decline by a mile, and costs about the same effort.

Slow down on the last one. Plenty of "not my job" moments are ownership gaps, and in a gap there is nobody correct to point at, so a refusal lands as abandonment.

The four parts of a clean redirect

A clean redirect names a person, gives one reason, includes the smallest piece you can do yourself, and says what happens next.

• Name a person rather than a team, because teams do not read messages.
• Give one reason, and make it about access or ownership instead of how busy you are.
• Do the small piece yourself: forward the thread with the id attached, or paste the link to the form.
• Say what happens next and who is doing it, so the thread has an ending.

Assembled, that is three sentences. "Approvals for this go through the ops lead, so they can push it through today. I have forwarded your message with the invoice number attached. If you have not heard back by Thursday, tell me and I will chase it."

Nothing in there says no. The work moved, the requester has a name and a date, and you spent under a minute.

The forward matters more than it looks. It carries the context the requester would otherwise retype from memory, badly, and it means the owner receives a task instead of a rumor.

The words that turn a redirect territorial

Redirects usually fail on the wording, not on the plan behind them.

• "That is handled by the platform team" sends someone hunting, while a name saves them a day.
• "I am not the right person" leaves them exactly where they started unless you say who is.
• "That is above my pay grade" is a joke out loud and bitterness in text.
• "You will need to raise a ticket" is fine, and it is kinder with the link to the form sitting in the same sentence.
• "As I mentioned" is a scolding in a cardigan, and everyone can hear it.

Writing has no face attached. In a room, telling someone that a colleague handles this comes with a shrug and a wave toward their desk. In a message it arrives flat, and flat reads as annoyed.

These come out colder than I mean them whenever I draft them fast, which is usually when the request has landed on top of something I was concentrating on. That is the moment the wording gets fixed or does not, so I let Unvent cover the gap: the name and the date stay exactly where I typed them, and the sentence around them stops sounding like I resented being asked.

When it actually is your job

If the same task has landed on you three times, it is your job now, whatever the chart says.

Ownership on paper and ownership in practice drift apart constantly. The chart was drawn before the work existed. Nobody updates it, because updating it is nobody's job either.

Here is the part that is less fun to read: scope is a hiding place at least as often as it is a defense. Boring work triggers the refusal reflex much faster than hard work does, and your job description is a respectable excuse that is always within reach.

The test I use on myself is one question. If the task were interesting, would I still be checking whose job it is? When the answer is no, the scope argument is decoration.

Absorbing everything handed to you is a different mistake with a worse ending. The deciding question is whether the work should happen and who is best placed to do it, and the job description is one input into that, not the verdict.

When the same work keeps arriving

Work that keeps misrouting is a plumbing problem, and you fix plumbing in one conversation instead of in twelve polite redirects.

Count them first. Twice is coincidence. A handful in a month is a pattern with a cause, and the cause is usually mundane: a stale document, or a form link buried three clicks deep.

Take the pattern, with two examples, to whoever can change the plumbing, and bring the fix with you. "Export requests keep coming to me because my name is at the top of the doc. Can we put the real owner in the header? I will make the edit." That conversation removes a recurring tax on your week.

Sending the twelfth polite redirect is the passive version of complaining, and it costs you more than raising it once would. If the fix means telling your manager the current setup is wrong, that message has a shape of its own.

The people who get treated as reliable are rarely the ones with the tightest boundaries. They are the ones whose replies tell you where to go next, even when the answer is somewhere else entirely. It costs a sentence. I still forget to write it about once a week.