In consumer packaged goods, one request is almost never one request.
“Refresh the packaging for the spring line” arrives as a single row in a queue. What it actually contains is fourteen SKUs, each in three pack sizes, each needing a bilingual variant for Canada, each with a different retailer’s dieline, two of which carry a Proposition 65 warning and one of which is a supplement with mandatory disclaimer language. The creative team finds this out in week two.
That gap between what was requested and what was actually asked for is where CPG intake breaks. And it is not a form design problem. It is a structural mismatch between how CPG work is scoped and how most intake forms are built.
What a Marketing Request Intake Process Actually Is
A marketing request intake process is the structured path a work request travels from submission to accepted project, capturing the information a team needs to scope, schedule, route, and approve the work before any production begins. In CPG, it also has to capture the variant count, the regulatory scope, and the retailer specifications, because those three determine the true size of the request.
That last part is what separates a CPG intake process from a generic one. A form that asks “what do you need and when” will produce a project estimate that is wrong by an order of magnitude, because the requester is thinking in campaigns and the team has to deliver in SKUs.
Why CPG Intake Breaks Differently
Three failure patterns show up consistently, and none of them are solved by adding more fields to the form.
One Request Is Really Forty
Most intake forms are built around a single deliverable. CPG work is built around a matrix: SKU by size by language by retailer by region. When the form captures the campaign but not the matrix, the estimate is built on the wrong denominator, and the schedule fails before anyone opens a design file.
The fix is asking for the variant count at intake and letting it drive the project structure automatically, so one request generates the correct number of tracked deliverables rather than one line item that quietly expands.
The Compliance Question Arrives Last
Packaging carries a regulatory load that digital campaigns do not. Food labeling falls under FDA nutrition and ingredient disclosure requirements (21 CFR 101). Supplements require specific disclaimer language on structure and function claims. Meat and poultry labels need USDA approval (9 CFR 412), alcohol requires a federal certificate of label approval (27 CFR 13), and Proposition 65 adds warning obligations that ripple across national artwork.
When the intake form does not ask which of these apply, legal and regulatory review discovers it at the proofing stage. At that point the layout is finished and the warning panel has nowhere to go.
Retailer Specs Live Outside the Form
Dielines, print specs, and retailer-specific requirements typically sit in a shared drive, an email thread, or a brand manager’s head. If intake does not require them at submission, the designer starts on an assumption and rebuilds later. This is the single most avoidable source of rework in packaging production.
International Vitamin Corp saw the cost of this directly. Before restructuring their intake process, staff were spending 20 to 30 percent of the working day searching email and folders for responses and assets, and maintaining a physical paper trail purely so the company could survive an audit. The information existed. It just was not attached to the work. Moving intake and approval into one system removed that overhead and strengthened their FDA compliance position.
Seven Best Practices for CPG Marketing Request Intake
- Ask for the variant matrix, not the deliverable. SKU count, pack sizes, languages, and retailers, captured as structured fields rather than free text. This is the number that determines schedule and capacity.
- Make the form conditional on project type. A packaging request asks about regulatory scope and dielines. A social campaign does not. Requesters should only see the fields that apply to what they are asking for.
- Gate regulatory scope at submission. A required field asking which claims, warnings, or approvals apply routes the project correctly from day one and tells legal what is coming before it arrives. It also lets you forecast regulatory workload, which most CPG teams cannot currently do.
- Require specs as attachments, not references. If the dieline is not attached, the request is not complete. Treating this as a hard gate rather than a nice-to-have removes an entire class of rework.
- Close every other intake door. Email, chat, and hallway requests are not intake. They are untracked work that competes with tracked work for the same hours, and they make capacity reporting meaningless. Enforcing this needs leadership backing, because the people most likely to bypass the form are usually the most senior.
- Let the request build the project. A completed request form should trigger a project template that lays in the tasks, the schedule, and the staged reviews automatically, rather than creating a ticket someone then has to configure by hand. Lehigh Valley Health Network runs 55 templates for exactly this reason: a poster, a flyer, and a table tent share a workflow, so none of them get rebuilt from scratch.
- Report on intake quality, not just volume. Track how often requests come back for missing information. That number, more than any throughput metric, tells you whether your form is working.
A Diagnostic: Is Your Intake Actually Working?
- Can you tell, from the request alone, exactly how many finished assets a project will produce?
- Does the form ask about regulatory scope, or does compliance discover it during review?
- How often does a project stall in its first week waiting on information that intake should have captured?
- What percentage of work arrives through the form rather than around it?
- Can a requester submit without attaching specs, and how often do they?
- Do you know your most common reason for a request being sent back?
If most of your problems cluster in the first week of a project rather than at review, the fix is at intake and nowhere else.
What Good Looks Like
Maui Jim implemented structured intake to protect brand standards across a global footprint and eliminated more than 200 meetings a year while saving over 200 hours in request processing alone. Those meetings existed to clarify requests. Better intake removed the reason for them.
Lifetime Brands went further, scaling from 1,000 to 7,000 projects per month while cutting average project duration from 45 days to 15. That is not a throughput story about working faster. It is a scoping story: work that arrives correctly specified moves without stopping.
AAA Washington named incomplete intake explicitly as the core issue when a rebrand pushed their team of 12 into new formats. Their production lead noted that something as small as an unflagged display ad size change could significantly affect the final product, and there was no process to catch it early enough. That is an intake problem wearing a production costume.
The pattern across all three is the same. None of these teams fixed their queue by working faster or adding headcount. They fixed it by changing what a request had to contain before it was allowed to become a project.
Frequently Asked Questions
What is a marketing request intake process? It is the structured path a work request travels from submission to accepted project, capturing what a team needs to scope, schedule, route, and approve work before production begins. In CPG it must also capture variant count, regulatory scope, and retailer specifications.
What should a CPG creative request form include? At minimum: project type, SKU and variant matrix, pack sizes, languages and markets, retailer requirements with dielines attached, regulatory scope, launch or shelf date, and the requesting brand or business unit. Fields should appear conditionally so requesters only see what applies.
How do you stop people submitting requests by email? By closing the alternative and making the form faster than the workaround. Teams that succeed do two things at once: they mandate a single intake path with leadership backing, and they make the form short enough through conditional logic that using it is genuinely easier than sending an email.
How many fields should an intake form have? Fewer than you think, shown conditionally. The goal is not a comprehensive form, it is a complete request. A packaging request may need fifteen fields while an internal announcement needs four, and requesters should never see the fields that do not apply to them.
How do you measure whether intake is working? Track the rate of requests returned for missing information, the time between submission and work starting, and the percentage of total work arriving through the form. Volume alone tells you nothing about quality.
Should compliance review happen at intake? Not the review itself, but the scoping question should. Capturing which claims, warnings, or approvals apply at submission lets the system route the project through the right stages automatically and gives regulatory teams advance visibility rather than a surprise at proofing.
Where to Start
Do not redesign the form first. Pull your last twenty projects and find where each one stalled. If the delays cluster in week one, intake is your constraint, and the variant matrix is almost always the field that is missing.
RoboHead’s project request forms use conditional logic to capture complete requests without overwhelming requesters, and generate the project structure and review routing automatically on submission. See how it applies to consumer goods teams, or take the Creative Workflow Maturity Assessment to benchmark where your intake is losing time.
