A request can be ready while some decisions are still open
A producer needs enough information to scope the work, ask the next useful question, and decide what happens next. The concept can still be open. The objective, deliverables, timing, and other facts that shape the assignment need to be visible.
Use this checklist before a request enters the queue. It is shorter than a full creative brief because it answers a different question: is there enough here for a producer to take ownership without reconstructing the request?
Eight things to check
Each item below needs an answer, a clear unknown, or an owner who can resolve it. A blank leaves the team guessing.
- Objective: What should this work help accomplish?
- Audience: Who should see it, and what do they already know?
- Deliverables: Which assets, for which channels, and how many?
- Message and action: What must the audience understand or do?
- Source material: Which copy, photography, claims, or references are approved?
- Production requirements: Which dimensions, formats, placements, or versions apply?
- Decision path: Who reviews the work, and who makes the final call?
- Timing: When is the first review, final delivery, and launch?
The distinctions that prevent the most chasing
Label each date. “Live Friday” is usually a launch date, not the first review or final delivery.
Make the scope countable. Replace “social assets” with the channel, asset type, quantity, and required versions.
Tell the team what a reference is for. “Use slides 8 through 11 for approved photography” is useful. “See deck” is not.
What can stay open
The concept, headline options, visual direction, and creative solution usually belong to the work itself. A request does not need to dictate them before a producer can accept it.
Some operational questions can also remain open when they are visible. Mark the missing answer, name the owner, and state when it must be resolved. The producer can then judge whether the team can start around it.
Use the checklist as a conversation
A checklist should expose the next useful question. It should not force a requester to pretend they know production language they have never used.
Sage Brief lets a requester speak, chat, add files, or enter details directly. Sage organizes that starting material and asks about missing information that affects the brief. A producer still reviews the request and decides whether the team is ready to move.