Traffic Asked for the File. Creative Is Still in Review.

Traffic just pinged the channel: "Can you drop what you have so we can start specs?" The media planner added "latest hero is fine — we will swap later if brand moves." The designer hovered over Share. Account said "send it, keep momentum." You are the creative project manager. The file in the folder is still labeled WORKING. Nobody wrote yes on a named version. Specs are about to invent a FINAL that creative has not locked.

This is not a traffic-personality problem. Traffic is doing their job: sizes, crops, safe zones, export paths. The failure is structural. Specs on an unlocked hero create two truths at once — a trafficking track that treats the frame as final, and a creative track that is still in review. WORKING labeled as final is how Thursday becomes a surprise rebuild.

The Wrong Diagnosis Is Always Impatience

The room will tell you traffic is rushing, media is too aggressive about lead time, or the designer should just send the latest and swap later.

You ask traffic to wait politely. You promise "we'll get you something tomorrow." You tell the designer to drop v6-alt into the Specs folder "for now." You rename the file Hero_AlmostFinal so nobody panics. Specs still start. Brand still reopens the crop. Legal still softens the claim. Traffic still rebuilds every size off a ghost that everyone treated as locked, because impatience was never the constraint.

Traffic is not the villain for asking early. Early specs are rational when platforms need lead time. The error is answering "what you have" with an unlocked file, then letting it behave like FINAL downstream. "Swap later" is not a version-control plan. It is permission to build the wrong tree twice.

More courtesy will not fix this. This post is what to do when traffic or media asks for the file while creative is still in review — and how WORKING stays WORKING until freeze.

Specs on Unlocked Files Create Two Truths

That is the structural problem.

Most creative teams treat trafficking as a courtesy that can start whenever someone needs a file. Drop a link. Start crops. Label the lane Finals because the folder is empty and the calendar is loud. Useful intent. Incomplete system. The missing object is the lock that authorizes leaving WORKING: a named version, a written approver yes, and a freeze rule for what may still change after specs begin.

Without that lock, you run two finals. Traffic's final is the hero they are cropping into 1:1, 9:16, and publisher templates. Creative's final is still in Figma with open comments, an unlocked claim, and a brand manager who has not closed direction. Both sides believe they are helping. Both are right about effort. Only one path can be true when the freeze date arrives. The second truth is the rebuild.

This sits next to five posts you may already know. The Media Buy Is Booked. The Creative Still Isn't Approved. is the hard-date collision when freeze and approval share a calendar. Your Status Is Green. Concept Is Still Open. is when the board reports tasks while locks stay open. Approved With Comments Is Not a Lock is the soft yes that reopens the job while claiming to close it. "Two Rounds" Is Not a Decision Plan is why counting passes is not exit criteria. What to Say When a Client Asks for One More Thing is Friday inventing a cutdown as collaboration. This post is the midstream ask: traffic wants the file before creative has a named lock, and "the latest" tries to pass for FINAL.

WORKING vs FINAL: Rules Before Anyone Specs

Do not ban early trafficking prep. Ban treating an unlocked hero as FINAL. Write these rules into the channel before Share goes out.

1. Named version or no specs

"What you have," "the latest," and "current hero" are not version names. Specs start only against a named frame, export, or file (for example Hero_v7_LOCK_CANDIDATE or Hero_v7_APPROVED). If the designer is still in a branch, traffic does not get a FINAL lane. They get a HOLD note and a ping when the name exists.

2. WORKING stays WORKING until freeze language is written

A file can be shared for awareness. Awareness is not authorization. If concept, claim, or layout hierarchy can still move, the label stays WORKING. Do not rename it AlmostFinal, SoftFinal, or ForSpecsOnlyFinal. Soft labels are how two truths get filing cabinets.

3. Freeze means what may still change

When a named version is locked for specs, write the allowed residual list in the same thread: platform crop, safe-zone nudge, typo, required legal line that does not change the claim, export naming. Write what may not change without a named reopen: concept, primary claim, hero hierarchy, end-card story, offer, audience. Specs after that list are production. Specs before that list are gambling.

4. Who may authorize the handoff

The CPM owns the trafficking sentence and the folder language. The named approver owns whether the version is locked. The designer owns whether the file in the link matches that name. Account owns the client-facing conversation when media pressure tries to skip the lock. Traffic owns refusing to build sizes off an unclassified WORKING file. Align privately if needed. Put one authorization in the shared channel.

5. Reopen has a cost before rebuild starts

If brand, legal, or creative reopens an object after specs begin, name the cost before traffic rebuilds every size: date slip, dropped unit, overtime, freeze risk, or a scoped delta pass. "Swap later" without cost is how the second final becomes free labor.

Put those five answers next to the traffic ask. A private "sure, send it" to the designer is how the Specs folder fills with fiction.

The Sentences That Keep WORKING From Becoming Fake FINAL

A folder rule nobody defends is decoration. These are the lines to send when traffic or media asks for the file while creative is still in review.

1. Traffic asks for "what you have"

They say: "Can you drop what you have so we can start specs?"

Do not send: "Sure — here's the latest. We'll swap if anything changes."

Send:

"Not yet for FINAL specs. Current file is still WORKING — no named-version lock from [approver]. Specs off this hero create a second final the moment brand reopens crop or claim. I will ping the named lock and allowed residual list the minute they exist. Until then Specs stays empty on purpose. Awareness link only if you need layout context, labeled WORKING."

Why it works: you respected traffic's lead time without authorizing a ghost FINAL.

2. Media planner wants to "start crops now and swap later"

They say: "Latest is fine. We will swap later if creative moves."

Do not send: "Works for me — designer will share."

Send:

"'Swap later' is not a lock. If we crop now, we are building FINAL off WORKING. Options: (A) [approver] locks a named version today with a residual list, then specs start, or (B) traffic waits and we protect the freeze by not inventing two trees. Which does media need in writing before we spend the day?"

Why it works: you forced a binary before labor splits into two truths.

3. Account pushes momentum over lock

They say: "Just send it. Keep momentum. Brand is basically there."

Do not send: "Okay, sharing now."

Send:

"'Basically there' is not a named yes. I will not authorize FINAL specs on an unlocked hero. If account needs momentum, get [approver] to lock [VersionName] for concept/claim/layout with residuals limited to [list]. Then traffic starts. Momentum that builds the wrong sizes is rework with a smile."

Why it works: you protected the relationship and refused to launder soft progress into trafficking.

4. Designer offers to "just send the latest so they can work"

They say: "I can drop v6 so traffic isn't blocked."

Do not send: "Yes please, thank you."

Send:

"Pause on FINAL handoff. v6 is still WORKING. If you share, label it WORKING / not for specs, and I will tell traffic the same in-thread. Finals handoff waits for named lock + residual list. I will not let helpfulness create a second final you have to rebuild Thursday."

Why it works: you protected the designer from unpaid rebuild dressed as team play.

5. Brand manager is still commenting while specs are requested

They say: "Traffic can start — I'm just leaving a few notes on the hero."

Do not send: "Perfect, notes and specs in parallel."

Send:

"Notes and FINAL specs cannot share an unlocked hero. Confirm: are the notes residual polish on a locked [VersionName], or do they still change concept/claim/layout? If they can change those, creative is still in review and specs wait. If locked, write the yes and the allowed list, then traffic starts once."

Why it works: you reused the soft-yes split without turning the thread into a different post.

6. Someone renames the file AlmostFinal to unblock traffic

They say: "Call it AlmostFinal_v3 and put it in Specs."

Do not send: "Done."

Send:

"AlmostFinal is still WORKING with better manners. Folder names do not create locks. I need a named version, written approver yes, and freeze residuals before Specs gets a FINAL file. Until then the file stays in Working and traffic gets a HOLD. Soft labels are how two truths get shelves."

Why it works: you blocked the labeling trick that invents approval without deciding.

7. Leadership asks why trafficking slipped after "we sent the file"

They say: "I thought traffic had the creative. Why are sizes late?"

Do not send, in the leadership thread: "Traffic jumped the gun." or "Creative was slow."

Send, privately to account or your lead first, then one clean line upstairs:

"Traffic asked for the file while creative was still WORKING — no named-version lock. We correctly held FINAL specs so we would not build two trees. Lock landed [date/time]. Specs are in flight against [VersionName]. The delay was refusing a second final, not missing a handoff."

Why it works: you refused the blame story and reported the missing decision object.

What Changes When Named-Version Lock Comes First

Traffic stops rebuilding every size because the "latest" mutated mid-crop. Designers stop sharing WORKING files into Finals out of guilt. Account stops selling momentum as a freeze path. Media planners get honest lead-time math: lock date first, then specs duration — not specs hope plus swap fiction. Status can say In Specs without lying that creative closed.

In-house, there may be no agency traffic desk. There is still a producer, a brand manager, and a channel asking for "the file for the site team." Same rule. If the page team crops an unlocked hero, you still have two finals. WORKING stays WORKING until the named lock exists.

In production environments, picture lock is already native. Steal the sentence. "Is this locked for trafficking, or still in review?" belongs in Slack the same way it belongs on a slate. If still in review, do not open Specs.

None of this requires a new DAM. It requires refusing to let "what you have" authorize FINAL while the decision is still open.

Frequently Asked Questions

Why shouldn't traffic start specs on the latest creative file?

Because "latest" is not a lock. Specs treat the frame as final across sizes and templates. If concept, claim, or hierarchy can still move, you are building a second final that will be rebuilt when creative closes for real. Named-version lock first. WORKING stays WORKING until freeze language is written.

What is the difference between sharing WORKING and authorizing FINAL?

Sharing WORKING is awareness: traffic can see layout context, estimate effort, and plan capacity. Authorizing FINAL is permission to build the size tree against a named locked version with an allowed residual list. Awareness without authorization is fine. Authorization without a lock creates two truths.

Who decides when creative is ready for trafficking — CPM, traffic, or the designer?

The CPM owns the handoff sentence and folder language. The named approver owns whether the version is locked. The designer confirms the file matches that name. Traffic owns refusing to spec an unclassified WORKING file. Account owns the client conversation when pressure tries to skip the lock. One authorization in the shared channel beats five private "sure" replies.

How is this different from a booked media buy with creative still unapproved?

Media Buy is the hard-date / freeze-calendar collision: the buy is booked and approval has not closed. This post is the midstream file ask: traffic or media wants "what you have" before a named lock exists, even when the crisis is not yet a calendar emergency. Same family of decision failure. Different trigger. Use both when the room only sees one.

What should you put in the thread before specs start?

Named version, written approver yes on concept/claim/layout hierarchy, allowed residual list, reopen cost if something crosses that list, and a clear label: WORKING vs FINAL. Without those, hold Specs empty on purpose.

Do I need a certification to hold FINAL specs until lock?

No. You need the habit of refusing "the latest" as a trafficking authority. A creative-specific credential helps if you want brief discipline, single-approver routing, and decision closure taught as one system. It is not required to keep WORKING out of the Specs folder.

Closing

If traffic keeps asking for the file while creative is still in review, and your team keeps sending "the latest" with a promise to swap later, the problem is probably not that traffic is impatient. It is that specs were allowed to invent a FINAL on an unlocked hero, and WORKING never stayed WORKING long enough for a named freeze.

You do not need a softer reply. You need named-version lock before FINAL specs: a version name, a written yes, a residual list, and a cost when reopen arrives after the size tree is already built.

The default path is the Bundle: Level I ($147), Level II ($197), the Creative PM AI Kit ($97), and the Resume Kit ($57). $297 one-time. Bought separately those are $498, so you save $201. Self-paced. Unlimited exam retakes. Digital certificates emailed when you finish. They never expire. 5-day full refund if it is not the right fit. Enroll in the Bundle.

If you only want the foundation, Level I is the alternative at $147. Eight self-paced modules, typically 10 to 15 hours, 70% to pass, unlimited retakes. The credential is a Certificate of Completion, emailed when the requirements are met. It never expires. Start with Level I.

Not ready yet? Start with the free eBook, The Essentials of Creative Project Management.

Who should skip this: if your team already refuses FINAL specs until a named version is locked, WORKING cannot enter Specs dressed as AlmostFinal, and "swap later" is never a trafficking plan, you do not need this post. Keep the lock first. Come back when the channel asks for "what you have" again.

The Only Certification Built for Creative Project Managers

CPMA is the only certification built exclusively for creative project managers, developed with veterans from Disney, Google, Snap Inc., Red Bull, Sony Pictures, Accenture, and Paramount Pictures. The Bundle is $297. Level I is $147 if you want the foundation only. Or start with the free eBook.