Guide

How to Keep a Client's Claude Project, Custom GPT or Gemini Gem Up to Date

Published Nov 9, 2026 · Last updated Nov 9, 2026 · By Stéphane Guérin

To keep a client's AI workspace up to date, maintain one master client brief, re-check the facts that change every week, and replace the file in every tool when it changes. It doesn't matter whether the workspace is a Claude Project, a ChatGPT custom GPT or Project, or a Gemini Gem. The method is the same, and it takes about 15 minutes per client per week.

Why client AI workspaces go stale

A client workspace is accurate on the day it is set up and starts drifting the next day. The client keeps changing prices, offers and messaging, and the workspace keeps answering with what it was told. Four habits make it worse:

• Set and forget. Agencies put real effort into setting up one Claude Project or custom GPT per client. Almost none plan who updates it, or when.
• Uploaded copies. A file uploaded to a workspace is a snapshot. When the original changes, the uploaded copy doesn't.
• Copies everywhere. The same client lives in a Claude Project, a custom GPT, a teammate's Gem and a freelancer's folder. Each copy goes stale on its own schedule.
• Fixes that stay in the chat. Someone corrects the AI ("they dropped that offer in September"), the draft improves, and the correction is lost when the chat ends.

The result is what we call context drift: a growing gap between what the AI believes about a client and what is true today. Nobody notices until the client spots an outdated price in a deliverable.

One master brief, many copies

The fix starts with structure: one master brief per client, and every workspace fed from it. Where a tool can link to a live document, the workspace stays current on its own. Everywhere else, it holds a copy that someone must replace.

The fewer copies you have, the less there is to maintain. Count the dashed lines for one of your clients: that's your weekly replacement list.

The weekly routine: 15 minutes per client

Pick one owner per client and give them a fixed weekly slot. Monday morning works well: the week's work starts from fresh facts.

1. Open the master brief. One file per client, ideally in the client.md format, with a source and a "verified" date on every fact.
2. Re-check the facts that move. Open the client's pricing, offer and product pages and compare them with the brief. Update anything that changed, with today's date.
3. Log last week's decisions. Scan meeting notes, emails and chat threads. Add one line per decision: date, what was decided, who decided.
4. Turn repeated corrections into rules. Ask the team: "What did you have to fix twice this week?" Each answer becomes a line in the Rules or Voice section.
5. Answer one open question. Pick a gap from the Open questions list and fill it, asking the client if needed.
6. Update the version and the date. Bump the version number and the "last verified" date at the top of the brief.
7. Replace the brief in every workspace. Delete the old file and add the new one in each tool (details below). Never leave two versions side by side.
8. Run the freshness test if anything important changed (see below).

Most weeks, steps 2 to 5 find nothing new, and the routine takes five minutes. That is the point: you know the workspace is current instead of hoping it is.

Tool by tool: Claude, ChatGPT and Gemini

The method is the same in every tool. The one difference that matters is whether the brief is a live link or an uploaded copy. A live link updates itself; a copy has to be replaced by hand.

Gems are becoming skills. Google is replacing Gems with skills: on personal Google accounts, Gems become read-only on November 17, 2026 and are removed on December 17, 2026; Workspace business accounts follow in March 2027, and education accounts in June 2027. Existing Gems convert automatically. Skills can't add files from Google Drive yet (Google says it's coming), so until then a skill holds an uploaded copy of the brief: replace it whenever the brief changes (Google).

Two tips that apply everywhere

• Keep the master brief as a Google Doc when you can. Private Claude Projects and Gemini Gems then read the latest version automatically, and only the remaining tools need a manual replacement.
• Put the rules in the instructions, the facts in the brief. Instructions ("Use the client brief as the source of truth; if a fact is missing, ask") rarely change. Facts change weekly, so they belong in the file you maintain.

Assistant memory is a hidden copy too. If a chat taught the assistant an old fact, for example through ChatGPT's or Claude's memory features, correct or delete that memory as well.

The five-question freshness test

Ask the workspace five questions you can verify in under a minute. Any wrong or hesitant answer points to the part of the brief that drifted.

Run it after every brief update and whenever someone new joins the account. It takes two minutes, and it's the fastest way to show a team why the routine matters.

Once a quarter: review the brief with the client

The weekly routine catches what is public. The quarterly review catches what only the client knows. Send the brief to your client contact with three questions:

1. Is anything here no longer true?
2. What is coming in the next three months: new offers, price changes, launches, people?
3. Is there anything we should never say, or always say?

Clients rarely mind. It shows the agency cares about getting their facts right, and it often surfaces changes they forgot to mention. At the same time, prune the brief: remove retired offers, merge duplicate rules, and archive decisions older than a year.

FAQ

How often should I update a client's Claude Project or custom GPT?

Check the fast-moving facts (pricing, offers, decisions) every week, and review the whole brief with the client once a quarter.

Do Claude Projects update automatically when a document changes?

Google Docs added from Google Drive to a private Claude Project sync to the latest version. Uploaded files don't, and Drive linking isn't available in shared projects, so those files must be replaced by hand.

Do Gemini Gems update automatically?

Yes for files added from Google Drive: the Gem uses the most recent version. Files uploaded from your computer need to be re-uploaded after changes.

Do custom GPT knowledge files update automatically?

No. Uploaded knowledge files are copies. Remove the old file, upload the new one and save the GPT.

Who should maintain a client's AI workspace?

One named owner per client, usually the account manager. Everyone else reports errors to the owner instead of fixing them in their own chat.

How do I know if a client workspace is out of date?

Run the five-question freshness test: price, current offer, audience, a sentence in the client's voice, and the latest decision. A wrong answer means something drifted.

Should I add a new file or replace the old one?

Always replace. Two versions side by side make the AI pick between conflicting facts, and it may pick the old one.

Let Joe do the weekly check

The routine above works by hand. SagaJoe automates the part that takes the most discipline: it re-checks each client's website every week and sends one note listing only what changed, for you to approve, so the brief behind every workspace stays current. See how it works.

Keep learning

• Context engineering for agencies: the complete guide
• Client brief template for AI (client.md)
• How to set up one AI workspace per client (Claude Project, custom GPT or Gemini Gem)
• All guides

Sources

• Use Google Workspace connectors, Claude Help Center (Google Docs sync in projects; private projects only)
• Use Gems in Gemini Apps, Google Gemini Help (Drive files use the most recent version)
• Upload Google Docs and other file types to Gems, Google Workspace Updates (uploaded files need re-uploading)
• About the transition from Gems to skills, Google Gemini Help (timeline by account type; Drive files not yet in skills)