Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Request Intake

The single route through which every request reaches the marketing team, usually a short form, so work is triaged and checked before it starts.
StrategyprocessUpdated

Definition

Request intake is the single entry point for work the marketing team is asked to do, together with the rule that nothing else counts as a request. The guide to prioritising work and capacity states the rule bluntly: work not submitted through the front door does not exist. The route can be a form, a ticket queue or a shared board; the tool matters less than the rule.

Intake is the first stage of a longer route, not the whole of it. The campaign workflow from intake to launch describes it as the stage that does most to protect everything after it, because each piece of missing information at intake becomes a question asked later at greater cost.

What a good intake asks

Two pressures pull against each other. Every missing field causes a delay later; every extra field pushes requesters back to email. The workflow guide's test resolves it: keep a field only if its absence has delayed work before. What survives is usually short: what is being asked for, the objective it serves, the audience, the deadline and the reason for it, and who will approve it.

The other fields that earn their place are review triggers. The guide to approvals and compliance reviews has the intake form ask whether the work contains a new claim, a price or promotion, a testimonial or a regulated product, so that a yes routes the work to the right reviewer before build rather than after. The same pattern applies to personal data and to anything else that brings in a specialist.

Different kinds of request can have their own front doors with their own questions. The analytics request process asks for the decision behind a question rather than the chart wanted, and the guide to handling requests for new tools asks what the tool is for, what the business already owns and what data it would touch.

In practice: weekly triage and service levels

Intake on its own is a queue. Triage turns it into decisions: accept, decline, park until a later window, or send to a fast lane for low-risk repeatable work, each with a reason the requester can see. Triage happens on a fixed rhythm, usually weekly in the prioritising guide, with someone who has the authority to say no.

Once requests arrive in one shape, the team can promise how long each kind takes. The tutorial on setting service levels for marketing requests treats an intake route as a prerequisite and publishes its service catalogue at the front door, because without one there is nowhere to publish the levels and nothing to measure them against.

Illustrative example — not a real result

A museum's marketing team closes the side doors

Prailtabe Museum's marketing team of 3 took requests from curators, the shop, learning and fundraising by email, chat and conversations in the corridor. At one count it had 46 requests in progress, nobody could say which mattered most, and an exhibition poster had gone to print with a claim the director had never seen. The team set up an intake form with 6 required fields, one of them asking whether the piece described an object's history or significance in a new way, and a 30-minute triage every Monday. Requests sent any other way got a polite link to the form. Within 2 months the open list was down to 17, and every new exhibition claim reached the curator for review before design started.

A SLA is the promise a team makes about turnaround once requests come through intake. The Approval Matrix maps each kind of risk to a reviewer, and the intake form is where it is applied first. A Claims Library holds approved claims with their evidence, so an intake answer of "uses only library claims" can shorten review. A Creative Brief follows accepted intake and turns a request into instructions for the people making the work.

Common confusions

  • Intake is the brief. Intake decides whether work happens and what reviews it needs; the brief, written once the request is accepted, tells the makers what to make.
  • A longer form gives better requests. Long forms drive requesters back to email. Keep only the fields whose absence has caused delays.
  • Intake means every request is accepted. Triage exists to decline and park as well as accept, with reasons.
  • Urgent requests can skip the front door. A request sent another way is not accepted until it is in the intake. A fast lane handles genuinely routine work through the same door with fewer steps.

More terms to look up

Where this term is used

Related