How to Eliminate "Where Is That File?" from Your Marketing Team's Vocabulary

"Where is that file?" is the question that never should need to be asked. In a well-organised team, every document has a home — one obvious, predictable place where it lives — and finding it is a matter of knowing the system, not knowing which person to ask.

Most marketing teams haven't built that system. Here's how to build it.

Why Files Get Lost

Files get lost for one of three reasons:

Inconsistent storage. Some files live in Google Drive, some in email attachments, some in Dropbox, some in local storage. There's no single canonical location.

Unpredictable naming. Files are named by whoever created them, using whatever naming convention felt right at the time. There's no standard, so there's no predictable place to look.

No portal layer. Even with organised storage, if clients receive individual links to files rather than accessing a structured portal, the internal organisation doesn't map to anything the client (or the team on a bad day) can navigate.

The Two-Layer Solution

The most effective file organisation for a marketing agency has exactly two layers:

Layer 1: Internal storage (Google Drive)

• One top-level folder per client
• Inside each client folder: one folder per engagement
• Inside each engagement folder: defined subfolders (Strategy, Deliverables, Assets, Admin)
• Strict naming convention: [Date]-[DocumentType]-[Version] (e.g., 2025-06-01-Q2-Strategy-v1)

Layer 2: External delivery (Client Portal)

• One portal per engagement
• Portal reflects the client-visible subset of the engagement folder
• Client always accesses through portal link, never through raw Drive link

The portal layer is what makes the internal structure robust. Because clients access through a portal, you can reorganise internal folders without breaking their access. And because the portal is organised by what makes sense to the client (not your internal taxonomy), they can find things too.

Enforcing the Standard

A naming convention that no one follows is useless. The two mechanisms that actually make standards stick:

Template everything. When a new engagement starts, duplicate a standard template folder (with all the subfolders already created and named). The team fills it in; they don't build it from scratch.

Make the portal the canonical delivery channel. If everything goes through the portal, the team is incentivised to keep the internal structure correct — because if it's wrong, the portal breaks.

The question "where is that file?" should always have the same answer: "in the engagement folder, in the appropriate subfolder, labelled by date and type." If it doesn't, the system needs another round of enforcement.

---

Frequently Asked Questions

What is the best folder structure for a marketing agency?

A clean three-level structure works for most agencies: Client → Engagement → Document Type. Within document type, use a consistent naming convention: date, document type, version. Apply it as a template so every new engagement starts with the structure already in place.

How do you get an entire marketing team to follow a consistent naming convention?

Template enforcement is more reliable than policy enforcement. If every engagement folder is created from a template that already has the naming convention baked in, team members follow it by default rather than by discipline. Pair this with a brief onboarding session for new team members and periodic folder audits.

How does a client portal help with internal document organisation?

A client portal creates a forcing function: if the internal folder structure isn't organised and correctly labelled, the portal either breaks or delivers a poor client experience. This makes good internal organisation a client-experience requirement rather than just an internal preference — which gives it much more organisational priority.