Handling Ad Hoc Marketing Requests Without Losing the Week
Handling ad hoc marketing requests well starts with one move: do not answer the request, answer the missing information. "Something for LinkedIn by Friday" has no budget, no audience, no definition of done and no stated trade-off. Before you say yes or no, ask four questions: what should happen as a result, who it is for, what it can spend, and what it replaces. Most vague requests either become a small, scoped job or quietly go away once those answers are needed. The ones that survive are usually worth doing.
This is written for the marketer inside a company, often a team of one or two, who answers to a manager and fields requests from sales, leadership and product. It is not a project management system. It is a way to have the conversation.
The limitation first: you cannot process your way out of this
Most advice on ad hoc requests comes from project management software companies, and it tends to end at "use an intake form." Intake forms help a team of eight. They help much less when the person asking is the head of sales, the request arrives in a hallway, and your manager wants you to "be helpful."
A form does not change the underlying problem, which is that nobody has decided what the request is worth. That decision is a conversation, and it is usually one you have to start, because the person asking has not thought about it. They have a feeling ("we should be on LinkedIn more") and a date ("the trade show is Friday").
So the goal here is not to block requests. It is to make the cost visible early enough that someone with authority can decide.
Why "no budget, no deadline" is the dangerous kind
A request with a real budget and a real deadline is easy to plan. A request with neither is where time disappears, for three reasons:
- No budget usually means "your time is free." The requester assumes the work costs nothing because no invoice appears. Your hours are the budget, and they come out of planned work.
- No deadline means it floats. It sits on your list, gets mentioned in a meeting, and then becomes urgent without warning.
- No stated outcome means it cannot be finished. Without a definition of done, "something for LinkedIn" can absorb any amount of revision.
When the ask involves paid media, "no budget" hides a second problem. Someone will eventually say "just put a little money behind it," and a little money with no objective produces numbers nobody can interpret.
The four questions that turn a request into a job
Ask these in the same order every time, in writing where you can. They are short enough to send in a chat reply.
1. What should be different after this runs?
Not "what do you want made," but what outcome the person is after. More demo requests? Booth visitors at the trade show? A post the CEO can share? Each of these is a different job. If the answer is "awareness," ask how they would know it worked. If nobody can say, you have learned something important about the request.
2. Who is it for?
Existing customers, prospects in a named industry, the sales team's own network, job candidates? The audience decides the channel. "Something for LinkedIn" aimed at existing customers might be better as an email that sales sends personally.
3. What can it spend, in money and in your hours?
Ask for both. If the answer is "no money," the job is organic only, and it should be scoped to what organic can do. If the answer involves ad spend, get a number and a period. Platforms think in daily and monthly terms, not "a bit." Google's help page about average daily budgets (checked on 2026-09-27) explains that, for most campaigns, spend on a single day can reach up to two times the average daily budget, while monthly spend is capped at 30.4 times that daily figure. Explaining that to a requester is a quick way to show that "a little money" still needs a real monthly number someone signs off on.
If the request is for paid social with a very small amount, it is worth being honest about what that amount can and cannot learn. Our piece on running Meta ads on a small budget covers the limits that general advice leaves out, and many of the same limits apply to other social ad platforms.
4. What does this replace?
This is the question that matters most and the one people skip. Your week is already full of planned work. Taking on the request means something moves. Say what, specifically: "I can do this by Friday if the October report moves to next Tuesday. Is that the right trade?"
That sentence changes the conversation. It is no longer you refusing; it is a scheduling decision, and the person with authority to make it can make it.
Sorting what comes back
Once you have answers, most requests fall into one of four types. Knowing which one you are in tells you what to do next.
| Type | What it looks like | What to do |
|---|---|---|
| Real and urgent | Clear outcome, fixed date, owner agrees to the trade | Do it, and log what moved |
| Real but not urgent | Clear outcome, no real date | Put it into the next planning cycle with a date |
| Unclear | Nobody can say what should change | Ask for the outcome in writing, then pause |
| Not marketing's job | Sales enablement, a personal favor, IT work | Point to the right owner politely |
The "unclear" row is where most "something for LinkedIn" requests land. Asking for the outcome in writing is not obstruction. It is often the first time anyone has had to state it.
How to say no without sounding like you are saying no
A flat "no" to a senior colleague rarely goes well, even when it is the right answer. A few phrasings that tend to hold up because they put the trade on the table rather than refusing:
- "Yes, and here is what moves to make room. Can you confirm with my manager that this is the priority?"
- "I can do a smaller version by Friday: one post and one image. The full campaign would take until the end of the month."
- "Before I build this, can you tell me what you would want to see happen afterward? That changes what I would make."
- "This looks like it needs ad spend to work. Who approves that, and how much?"
None of these are clever. They work because each ends with a decision the requester or your manager has to make, instead of you absorbing the cost silently.
Handling ad hoc marketing requests over time: make the cost visible
The strongest protection against a steady stream of unscoped requests is a record. Keep a simple log for a few weeks: date, who asked, what for, hours spent, and what was pushed back as a result. You do not need software. A shared spreadsheet is enough.
After a month, the pattern usually speaks for itself. When you bring it to your manager, bring it as a question rather than a complaint: "This much of my time went to unplanned requests last month, and these planned items slipped. Is that the split you want?" Use the numbers from your own log, not an industry average. Your manager may decide the requests are worth it. That is a legitimate answer. What matters is that it is now a decision someone made, not an accident.
If some of those requests produce real leads, it also helps to know roughly what a lead is worth to the business. Our guide on how to calculate lead value walks through that, and it gives you a way to compare an unplanned request against the planned work it displaced.
If you do the work, make it measurable
When a request survives the four questions and you take it on, set it up so you can answer "did it work?" later. That means tracking links on anything that points to your website, a one-line note of what the goal was, and a date to look back.
Consistent tagging is the part people drop first under time pressure. A short, shared UTM naming convention means the Friday rush job still shows up correctly in analytics next month, instead of landing in a bucket nobody can explain.
Then close the loop. A two-line note to the requester a few weeks later ("here is what happened, here is what I would change") does more to shape the next request than any process document.
Reduce the repeat requests
Some ad hoc requests come back every month: a resized banner, a post for an event, a one-page sales sheet with updated numbers. These are good candidates for templates or a short self-service guide, so the request becomes "fill in this template" rather than "please make me something."
Be selective. A template for a job you do twice a year is overhead. A template for a job you do every week pays for itself quickly.
FAQ
How do I handle ad hoc marketing requests from senior leaders?
Treat the request as a trade, not a yes or no. Confirm the outcome they want, then state what planned work would move to make room, and ask them or your manager to confirm the priority. That keeps the decision with someone who has the authority to make it.
Should every marketing request go through an intake form?
A form helps when several people are submitting requests to a team. For a team of one or two, a consistent set of questions asked in chat or email usually works just as well, as long as the answers are written down.
What if a request has no clear goal?
Ask the requester to state, in a sentence, what should be different after it runs. If they cannot, pause the work until they can. A request without an outcome cannot be finished or measured.
How much time should I reserve for unplanned requests?
There is no universal figure. Track your own unplanned work for a few weeks, then agree a working allowance with your manager based on that record, and revisit it when the pattern changes.
What if the request needs ad spend but nobody has approved a budget?
Do not launch paid activity on an informal "just spend a little." Ask who approves the spend, get a specific amount and period in writing, and set a clear objective before anything goes live.