Home
Neural Draft

Keeping each client's website and socials separate

Agency and freelance workflow

Keeping each client's website and socials separate

The caption is written, the post is queued, and your cursor is hovering over "Schedule." Then you reread it and something feels off. The tone is breezy and full of puns, but this client sells careful, serious financial advice. The caption belongs to a different brand entirely.

That near-miss isn't carelessness. It happens when brand notes, logins, drafts and calendars all sit in one shared pile, so every file sits right next to the wrong file.

The simple idea is that separate containers prevent this kind of confusion: one tidy space per client, built the same way every time.

Below, you'll find a folder structure for each client, a weekly rhythm, sign-off before anything goes out, and a clear way to hand things over.

Why client work gets muddled, and the simple fix

Mixed-up work rarely comes from a single big mistake. It builds up from small overlaps: a shared drive where every client's files look alike, one calendar holding everyone's posts, a handful of logins saved in the same place.

The fix is to give every client their own container, with the same shape every time.

Give every client their own brand file, logins and calendar

Start with a one-page brand file. Here's a template you can paste and fill in:

  • Tone of voice: ___, ___, ___ (three or four plain words, like "warm, direct, no jargon")
  • Words to use: ___
  • Words to avoid: ___
  • Colours and fonts: ___
  • Opening hours and prices: ___
  • Who approves what: ___

Next, logins. Wherever possible, the client should own their website, bookings and social accounts, with you added as a helper rather than the owner. That way, if you part ways, nothing gets held hostage. Keep credentials in a password manager with one shared folder per client. And check each platform's current rules on managing accounts for others, since they change and differ from site to site.

Then calendars. Make one per client, never a single mixed one. Label or colour-code by client name so a glance shows whose week it is.

Here's how it looks in practice. A small agency with several clients and a freelance web designer with a few site-care clients can use the exact same folder layout for everyone:

  • Brand
  • Access
  • Calendar
  • Approved posts
  • Handover notes

Same structure every time. That means you (or anyone covering for you) always know where to look. It also means you can paste a client's brand file straight into Claude or ChatGPT before drafting, so the output sounds like them.

Before you move on, check each client against this list:

  • Brand file written
  • Access recorded
  • Calendar created
  • Approver named

With each client's kit in place, you can give your week a shape that moves through all of them calmly.

A weekly rhythm that works for several clients at once

Juggling several clients works best when the week has a shape. Here's a simple pattern to start from. Adjust it to fit your own clients and your own energy.

  • Monday: Review last week and collect each client's news.
  • Tuesday and Wednesday: Draft social posts, blog updates and website tweaks.
  • Thursday: Send everything for client sign-off.
  • Friday: Schedule approved posts and run a final check.

Think of it as a starting point, not a promise of results. If a client always replies on Tuesdays, move sign-off. If your best writing happens in the morning, protect those hours.

Batch by task where it helps. Writing all your captions in one sitting saves you from constantly switching gears. But keep each client's brand file open while you write for them. That's how a bakery's warm, plain voice doesn't leak into a law firm's careful one.

A web designer can run the same rhythm for site care. Monday, check what needs changing. Midweek, make the edits. Friday, confirm everything looks right on the live site (not just in the editor).

When you ask Claude or ChatGPT for help, work for one client at a time. Here's wording you can copy:

Use only the brand notes below for [client]. Draft three Instagram captions for next week about our new autumn menu, in a warm, plain tone. Prices are £4.50 and £6. Do not mention any other client.

One tip makes this far safer. Start every assistant conversation by pasting in that client's brand file, and keep one conversation per client. Never mix them. It keeps each voice, price and detail where it belongs.

A rhythm only holds if nothing slips out between Thursday and Friday, which is where sign-off comes in.

Get sign-off before anything goes out

Here's the rule. Nothing goes live until the named approver says yes in writing. That covers social posts, blog drafts and website changes, with no exceptions.

It protects you and your client equally. They get the final word on what carries their name. You get proof that the work was signed off, so a "that's not what I wanted" three weeks later doesn't land on you.

Send this before every batch:

Hi, here are next week's posts for review. Please reply with APPROVED, or tell me what to change, by Thursday. Nothing goes out until I hear from you.

And plan for silence, because it happens. Add this line to your process:

If I haven't heard by Thursday, I'll hold the posts and publish nothing until you confirm.

Silence never counts as a yes. It just means the posts wait.

Then keep a record. Save the client's reply in an "Approved posts" folder, with the date in the file name. If your scheduling tool lets you hold a week of posts for approval before publishing, use that setting. And make sure every website edit is easy to undo, so a change that slips through can be reversed.

Your checklist:

  • Named approver
  • Deadline day
  • Written yes
  • Saved copy

Approvals keep the work safe while it's live, and the same tidy habits make the eventual goodbye easy.

Hand over clearly when the work ends or changes hands

Most freelancers skip this step. The project ends, the invoice goes out, and everyone drifts off. But a clean handover is simply good practice, and it protects your client and your reputation. (Rules on data, accounts and contracts differ from country to country, so check what applies where you work.)

A solid handover pack covers:

  • Where the site and accounts live, and who owns each one
  • The brand file
  • The approved-post history
  • The weekly routine
  • A list of recurring tasks
  • Who to contact for each service

Then send a short note. Copy this one: "Here is everything you need to carry on without me: where each account lives, how we approved posts each week, and what needs checking monthly. I've removed my access as agreed on [date]."

One order of operations matters. Confirm the client can log in first. Then remove your own access.

And if you kept each client's folders tidy from day one, this becomes much simpler. You're just handing over what's already there.

Start with one client this week

You don't need to rebuild everything at once. Four habits carry the whole system: a separate brand file, a weekly rhythm, written sign-off, and a clear handover.

If you'd like a hand, paste your draft brand file into Claude or ChatGPT and ask it to tidy the notes into a clean one-page version.