How do you prioritize creative requests when everything is “urgent”?

01

What should be checked before scoring a request?

Score valid requests, not incomplete ideas. Intake and prioritization solve different problems: intake establishes what is being requested, while prioritization decides which accepted request deserves capacity first.

Before scoring, confirm that the request identifies its objective, audience, deliverables, specifications, owner, approver, desired date, and required inputs. Asana describes centralized creative production as collecting request details before work is reviewed, prioritized, and resourced in a shared project (source).

If your queue still contains requests such as “need some ads by Friday,” return them for clarification. Use a consistent intake process first, then apply this checklist only to requests that can be compared. See the ecommerce creative request intake workflow in the related guides.

02

How does the 100-point creative priority worksheet work?

Give each criterion a 0–5 rating. Calculate its contribution as: rating ÷ 5 × weight. Add all seven contributions to produce a score out of 100. Weighted models help teams compare work using consistent benefit and cost criteria rather than intuition alone (Atlassian).

Use these weights: business or customer impact, 25 points; deadline reality, 20; dependencies and blocked work, 15; brief readiness, 15; reuse potential, 10; lack of an acceptable substitute, 10; and effort efficiency, 5.

Example: a deadline rating of 4 contributes 16 points because 4 ÷ 5 × 20 = 16. Do not change weights to favor individual requests. Review the model periodically as a team if the criteria no longer reflect the brand’s actual constraints.

1. Business/customer impact — 25: A 5 means the asset directly supports a major launch, customer decision, revenue path, or material business risk.
2. Deadline reality — 20: A 5 means there is a fixed external date and a documented consequence for missing it.
3. Dependencies and blocked work — 15: A 5 means several approved activities cannot proceed without the asset.
4. Brief readiness — 15: A 5 means the objective, audience, offer, copy, specifications, inputs, owner, and approver are ready.
5. Reuse potential — 10: A 5 means the source asset can support several placements, formats, markets, or iterations.
6. Lack of substitute — 10: A 5 means no approved asset, crop, template, recut, or temporary version can perform the immediate job.
7. Effort efficiency — 5: A 5 means meaningful value can be delivered quickly with known resources and limited production complexity.

03

How do you verify impact and deadline reality?

Ask what customer decision, launch, revenue event, or business risk depends on the asset—and what specifically happens if it arrives late. Unsupported statements such as “this should perform better” do not establish impact.

Customer-facing product media may have direct purchase-decision relevance because Shopify says product images, video, and 3D media can help customers understand product function and size and gain confidence in product quality (Shopify). That does not mean every product-media request automatically ranks first; the requester must still identify the affected product, event, audience, and consequence.

Test every due date by asking what event created it. A scheduled launch, booked media start, marketplace cutoff, inventory arrival, expiring promotion, contractual commitment, or required claims review can create a real constraint. “Leadership wants it Friday” is a preference until the requester documents what becomes impossible or materially riskier after Friday.

1. Record the event behind the requested date.
2. Document the consequence of missing it.
3. Identify whether the date is fixed, movable, or internally chosen.
4. Lower the urgency rating when no concrete consequence can be shown.

04

How should blocked work and readiness affect the ranking?

Raise the score when an asset releases multiple downstream activities. Keep the request out of committed production when essential inputs are missing, even if its potential impact is high.

Ask: “If this is one week late, what else stops?” Dependencies might include a product-page build, retailer submission, approved media launch, lifecycle campaign, localization, or derivative production. Work that blocks several committed activities generally deserves more weight than work that can proceed independently.

Readiness protects capacity. A useful brief defines the objective, audience, message, deliverables, stakeholders, timeline, distribution, and success measures (Asana). As an operating rule, requests below 3/5 for readiness should remain in a “readying” state rather than becoming committed work, except when a documented compliance or emergency risk requires immediate action.

05

Can existing assets or reusable masters reduce the queue?

Before approving net-new production, check whether an existing asset can satisfy the immediate need and whether one adaptable source asset could replace several isolated requests.

Consider recutting footage, cropping approved photography, refreshing copy in an existing template, using current product media temporarily, or producing one master designed for derivatives. Google’s Demand Gen guidance recommends using available image and video formats and notes that advertisers can reuse existing imagery when developing creative (Google Ads Help).

Score reuse and substitutes separately. High reuse raises a request because it can serve more work. A viable substitute lowers a request because the immediate need can already be covered. Do not let a quick task outrank a major launch dependency merely because it is easy; effort receives only five points for that reason.

06

What rules should govern the published queue?

Rank requests by total score, expose the supporting evidence, and make every expedite identify the work it displaces. A visible queue turns prioritization into an operating rule rather than a private negotiation.

Use total score first. Break ties by the earliest irreversible deadline, then by the amount of downstream work unblocked, and finally by lower effort. Re-score when the launch date, inventory status, brief, media plan, business objective, or available substitute changes.

An executive override is allowed, but it should state the reason, which queued item moves down, and that item’s revised delivery expectation. Compliance work can also bypass ordinary scoring when creative must be corrected: the FTC states that advertising must be truthful and non-deceptive and that advertisers need evidence for their claims (FTC).

1. Publish each request’s score, evidence, owner, status, and override reason.
2. Review the top of the queue at a fixed cadence and whenever material facts change.
3. Limit active work instead of marking every ranked request as in production.
4. Record why completed work was prioritized so future decisions can reuse the learning.

07

How can ATIYO support this prioritization process?

ATIYO can preserve the roadmap, briefs, brand context, assets, iterations, and reusable learnings around prioritized creative work. Apply the worksheet to accepted requests, then use the roadmap and queue to keep sequencing and context visible.

ATIYO does not connect to ad accounts, buy media, calculate ROAS, or independently know performance. Media performance remains in the ad platform, while ATIYO preserves creative context and learnings. If performance should inform later prioritization, a user must record the relevant result and context.

The practical next step is not to automate judgment. It is to establish one scoring rule, use it across stakeholder groups, and maintain a visible queue whose order can be explained.