Poor creative request processes kill productivity. Incomplete briefs, unclear requirements, and lost requests create frustration and delays. A well-designed request system ensures creative teams get what they need to produce effective work efficiently.
Here's how to build an internal creative request system that works.
Creative Request Challenges
What goes wrong without good systems:
- Incomplete information: Back-and-forth for clarification
- Lost requests: Work falling through cracks
- Unclear priorities: Everything is "urgent"
- Missed deadlines: No visibility into workload
- Rework: Misunderstood requirements
System Components
Request Intake
Structured form for submitting requests:
- Requester information
- Client/account context
- Creative type needed
- Required specifications
- Deadline and priority
- Supporting materials
Brief Template
Essential information for creative production:
- Objective: What should this creative accomplish?
- Audience: Who is this for?
- Message: What's the key communication?
- Tone: How should it feel?
- Format: What specifications?
- Assets: What materials are available?
- Examples: What should it look like?
Workflow Stages
- Submitted: Request received
- In Review: Brief being clarified
- Assigned: Designer/creator assigned
- In Progress: Work underway
- Review: Awaiting feedback
- Revision: Changes being made
- Approved: Ready for use
Tracking and Visibility
- Dashboard showing all requests
- Status updates at each stage
- Workload visibility for capacity planning
- Historical data for process improvement
Building the System
Tool Options
- Project management tools (Asana, Monday, Notion)
- Form builders (Google Forms, Typeform)
- Creative workflow tools (Wrike, Frame.io)
- Custom solutions (spreadsheets, internal tools)
Implementation Steps
- Document current process and pain points
- Design brief template with team input
- Build request form and workflow
- Train team on new process
- Iterate based on feedback
Best Practices
For Requesters
- Complete the brief fully—incomplete requests get sent back
- Provide realistic deadlines
- Include all necessary assets upfront
- Give clear, actionable feedback
For Creative Teams
- Ask clarifying questions before starting
- Update status regularly
- Flag capacity issues early
- Document recurring request patterns
How ROASPIG Helps
ROASPIG complements creative request systems:
- Organized storage for delivered creative
- Performance tracking to inform future briefs
- Clear workflow from request to deployment
- Historical reference for past creative
- Easy iteration on approved concepts
Request System Mistakes
- Over-complicated: Too complex and people bypass it
- No enforcement: Accepting incomplete requests
- Missing capacity view: Can't plan without workload visibility
- No iteration: Systems need continuous improvement
- Siloed tools: Request system disconnected from production
Related reading: scaling creative, QA processes, and agency workflows.
Frequently Asked Questions About Creative Request System
Objective, audience, key message, tone, format specifications, available assets, deadline, and reference examples. Enough information that creative team can work without back-and-forth.
Define what 'urgent' means and limit who can designate urgency. Have a fast-track process but require trade-offs (other work delayed). Don't let everything become urgent.
Depends on your team. Asana and Monday work well for most. The best tool is one your team will actually use. Start simple and add complexity as needed.
Involve team in design, explain the problems it solves, make it genuinely easier than current process, and enforce consistently. Buy-in comes from experiencing the benefits.
Have a process for exceptions but make it slightly harder than standard. Review exceptions regularly—if same type recurs, update the form to accommodate it.