Streamline Creative Asset Requests: A One-Page Intake System

The fastest way to stop overloading a creative team is to make every request arrive complete, in one place, with one named approver. Designers rarely drown in design. They drown in clarification: "which size?", "is the copy final?", "who signs this off?". A one-page intake form, three triage lanes and a written turnaround rule remove most of that.

TLDR: Replace chat and email requests with one form that has seven required fields. Sort what comes in into three lanes (template, adapt, new), give each lane a turnaround, and cap revisions at two. Requests that skip the form wait.

The seven fields every request must carry

A request is complete when the designer can start without asking a single question. Make these fields required, not optional:

1. Goal. One sentence: what should this post make people do or understand?
2. Platform and format. "Instagram carousel, 1080 x 1350, 6 slides", not "the Instagram post".
3. Final copy. Headline, caption and any legal line, already approved.
4. Reference files. Logo version, brand colours, one example you like.
5. Deadline. A date and a time, plus the publish slot it is aiming for.
6. Approver. One name. Not "the team".
7. Where it lives afterwards. The brand, campaign and folder it gets filed under.

Most teams already know these fields. What they lack is a gate. Put the gate in the form, not in the designer's patience. If a field is empty, the form does not submit.

Sort every request into one of three lanes

Not every request deserves a designer's afternoon. Triage on arrival, ideally by the same person every day:

Lane	What it is	Who does it	Typical turnaround
Template	A known layout with new text or a new photo (quote card, event date, product tile)	The requester, from a locked template	Same day, no designer
Adapt	An existing asset resized, translated or recut for another platform	Junior designer or the automation	1 to 2 working days
New	A new concept, illustration or video	Senior designer	3 to 5 working days, booked in advance

Treat the turnarounds as your starting numbers and adjust after a month of real data. The point is that the requester can see the lane and the wait before they submit. Rush requests stop being invisible when the lane has a visible cost.

If most of your queue lands in "template" and "adapt", you have a tooling problem, not a staffing problem. Our guide on automating repetitive social media edits covers how to take those two lanes off the designers entirely.

Cap revisions and name the approver

Endless revisions are the second source of overload. Two rules fix most of it:

• Two rounds, then it is a new request. Round one is for content feedback, round two for small fixes. Write it on the form so nobody feels punished when it is enforced.
• One approver, one place for comments. Feedback scattered across email, chat and screenshots means the designer has to merge it. Keep comments on the post itself. In Mydrop, approvals and comments sit next to the post preview, and the client or manager can approve without logging in through the client portal.

For turnaround targets you can put in an agency or freelancer contract, see agency creative turnaround SLAs.

Publish a weekly capacity number

Designers feel overloaded because demand is invisible until it lands. Fix that by publishing one number every Monday: how many "new" slots are open this week. When the slots are full, the next request goes to next week, or the requester trades one out.

A simple weekly board needs only four columns: Requested, In progress, In review, Delivered. Review the oldest item in "In review" every day, because stuck approvals are what make a creative team look slow when it is actually waiting.

File finished work where the next request will find it

A surprising share of requests are for something that already exists. Before a request is accepted, the form should ask: "Did you check the library?" Finished assets should be filed by brand and campaign so the next request can start from them. If you are building that library now, how to centralize social media assets without the mess is the follow-up. Mydrop keeps assets in a shared media library per brand, with Canva and Google Drive connected, so approved files sit next to the calendar they will be scheduled on.

A 30-minute setup for this week

1. Write the seven fields into a form (any form tool works).
2. Define your three lanes and a turnaround for each.
3. Announce the two-round revision rule and the weekly slot count.
4. For one week, do not accept any request that arrives outside the form.

Next step: pull the last ten requests your designers received and count how many would have passed the seven-field test. That number is the share of your team's time you can get back. If you run several brands, start free with Mydrop and keep requests, approvals and assets in one workspace.