Client delivery folder structure for marketing assets (copy this tree)

Clients do not want your creative process—they want a package that makes them look competent in their Monday meeting.

Your folder tree is part of that competence cosplay—in a good way.

Last reviewed: April 2026. Delivery packages should follow contractual confidentiality rules—avoid sharing internal strategy docs unless explicitly included.

Copy this tree (baseline)

DELIVERY__Client__2026-04-22__v1.3/
00_README.pdf (or .md)
01_ChangeLog.md
02_Claims/
claims_sheet_v4.pdf
approved_copy_v4.docx
03_Finals/
meta/
tiktok/
youtube/
04_Source_Package/ (optional contract)
projectfile/
fonts/
music/
05_Licenses/
06_Archive__superseded/

README contents (minimum)

1. What this delivery contains (one paragraph)
2. What changed since last version (bullets)
3. What is not included (scope clarity prevents drama)
4. Contact + escalation path
5. Link to live preview URLs (if relevant)

Changelog discipline (adults only)

Each version entry:

• date
• author
• what changed
• why

If you cannot explain why, you should not bump version.

Claims folder: treat it like hazardous materials

If claims live only in Slack, you do not have claims—you have lore.

Internal links

• Client delivery automation
• Drive organization
• Creative QA

Appendix: client acceptance checklist (optional attachment)

• finals open on standard machines
• captions readable
• music present as expected
• CTA matches LP modules
• naming matches media tracker

E-E-A-T: delivery is part of product quality

A messy handoff is indistinguishable from a messy product experience—especially for agencies selling professionalism.

Key takeaways

• README + changelog are part of the deliverable.
• Separate finals vs sources by contract.
• Licenses live with delivery, not in someone’s inbox.

People also ask

What folder structure should I use for client delivery?

README, changelog, claims, finals by platform, licenses, archive.

What should a client README include?

What shipped, what changed, what is excluded, contacts.

Should PSDs be included?

Only if contracted—otherwise define source package rules.

FAQ

How do I version deliveries?

Dated folders or semver + changelog.

How does Pinnacle AdForge help?

Delivery framework—signup.

---

If your delivery is a zip without a README, it is not a handoff—it is a guess with compression.

Bonus: the "one zip per version" rule

Never reuse the same zip name for a new version—humans will open the wrong zip until the heat death of the universe.

"Redlines" folder (optional but saves marriages)

07_Redlines/ for:

• annotated PDFs
• timestamped feedback
• agreed decisions

If feedback only lives in email, you will relive the same argument with more CCs.

Security: what not to put in client zips

• internal cost sheets
• competitor teardowns with sensitive notes
• raw customer PII exports

If it would embarrass you in discovery, it does not belong in DELIVERY__.

Handoff meeting agenda (15 minutes)

1. Walkthrough README
2. confirm acceptance checklist
3. confirm media launch window
4. confirm moderation plan for UGC
5. assign owners for post-launch monitoring

Meetings should reduce Slack, not become Slack.

Multi-market delivery (duplicate tree or subfolders)

Pick one:

• 03_Finals__US/ and 03_Finals__EU/
• or separate top-level deliveries per market

Do not mix markets in one finals folder unless your naming convention is military-grade and your team is actually disciplined.

Retention policy (one paragraph in README)

State how long you keep:

• finals
• sources
• licenses

Clients appreciate clarity—and legal appreciates it even more.

"Done" definition (write it)

Define done as:

• uploaded OR
• delivered zip + README acknowledged OR
• live in accounts with naming verified

Otherwise "done" means different things to creative and media, which is how friendships end.