Task statement 5.4 · Configuration and knowledge management

5.4 · Maintaining Configurations

In Wrenfield Housing, the course example, the communications team drafts tenant replies in its shared Tenant comms Project, which holds the tenant handbook and the style guide (3.1). When a new handbook changed the notice to end a tenancy, nobody was responsible for the Project, so Claude kept quoting the old rule for three weeks.

Why it's tested

The tempting view is that a Project, once set up, looks after itself, because every chat uses its knowledge and instructions. Claude cannot know that a document it holds has been replaced somewhere else, so it answers confidently from the old one. The opposite habit fails too. When anyone who spots a problem edits the Project, several changes land at once and nobody is told, so no one knows which change fixed or broke a reply, and colleagues keep checking drafts against old rules.

KnowledgeWhat keeps a shared Project correct

A Project's configuration is everything that shapes Claude's replies inside it: the project knowledge (the files it holds), the project instructions (the standing directions it follows), and who it is shared with. Claude uses the knowledge and instructions in every chat in the Project, so one out-of-date file gives out-of-date replies to everyone who works there. On a Team or Enterprise plan, only Can edit members of a shared Project can change its knowledge and instructions (5.1). The help articles describe an email when a Project is shared with you, but none when its knowledge or instructions change. Keeping a Project correct therefore needs a person, a routine and a habit of telling people, which rules out treating a Project as finished once it is set up.

The routine has five steps, starting before anything goes wrong:

  1. Name an owner: one person, plus a deputy, holds Can edit and answers for the Project; other members get Can view.
  2. Watch the triggers: the owner acts when a listed event happens, and reviews the Project on a fixed date for changes nobody reported.
  3. Change one thing: replace one file or edit one instruction, never several at once.
  4. Re-test: re-run a few saved real requests in a new chat and check each reply against its source.
  5. Log and inform: add a line to the change log, then tell the people who use the Project what changed and why.

Interactive · what Claude drafts after each maintenance step

Four stages of the Tenant comms Project in April, from top to bottom. On the left is what happened to the Project; on the right is what Claude’s replies or the saved test requests show. With no owner, the Project kept the February handbook and replies quoted four weeks, which is wrong. Replacing the handbook makes 4 of 5 saved requests pass. Removing an old instruction line makes 5 of 5 pass. Logging the change and telling the team means officers check replies for one month. A step not yet taken is dashed and labelled not done yet. WHAT HAPPENED TO THE PROJECT WHAT THE REPLIES SHOW 1–21 April · no owner New handbook from 1 April; the Project keeps the February file PRODUCES WRONG · “four weeks’ notice” 17 replies sent to tenants CAUGHT IN A CHECK, 22 APRIL Update the knowledge Owner uploads the new handbook and removes the February file NOT DONE YET RETEST 4 of 5 saved requests pass request 1 still: four weeks NOT YET: A SECOND SOURCE NO RETEST YET Update the instructions Owner deletes the old line “Notice to end a tenancy: four weeks” NOT DONE YET RETEST 5 of 5 saved requests pass “one month”, as the handbook says NO RETEST YET Inform Change log entry, and a message to everyone who uses the Project NOT DONE YET TELLS Officers know what changed and check replies for one month NOBODY TOLD YET One change, then a retest: each result traces to one step.

Step through April in Tenant comms, one maintenance step at a time.

No owner: the Project still held the February handbook, so for three weeks replies said four weeks' notice.

The owner swaps in the new handbook and re-tests. Four requests pass; the notice request still says four weeks.

The owner deletes the old rule from the instructions. The retest passes 5 of 5.

The owner logs both changes and tells the team, so for one month the officers check every reply for the new rule.

Dashed and labelled NOT DONE YET: a step still to come. Each retest box says how many saved requests pass.

Steps 3 and 4 reuse two habits from earlier: change one thing per round, so each difference traces to one change (1.3), and check each output against its source for accuracy and completeness (2.1). A test set is a short list of saved real requests, each with the answer its source gives. Anthropic's guidance on evaluations asks for tests that mirror real tasks, so save the requests people send most, without personal data; five suit a small Project. Run them in a new chat, so earlier drafts cannot sway the result.

KnowledgeInform, maintain and update: three jobs

The objective names three jobs, each at a different moment. To maintain a Project is to keep it correct between changes, through the owner, the regular review and the test set. To update a Project is to change its knowledge or instructions after a trigger, meaning a listed event that should make the owner check it. A new model belongs on the list, because Anthropic's prompting guide notes that a model can follow the same instructions differently, for example more literally. To inform is to pass news both ways: anyone who notices a trigger tells the owner, and the owner tells the Project's users what changed. Wrenfield's version of each job:

Maintain

The communications lead owns Tenant comms, with one deputy, and re-runs the five saved requests on the first working day of each month.

Wrong choiceEveryone holds Can edit, so the Project belongs to nobody.

Update

Triggers: a policy, figure or contact changes in a source document; a new model appears in the model selector; the same error is reported twice.

Wrong choiceWaiting for the monthly review after a known change.

Inform

A dated line in the change log, a shared document beside the handbook, and a short message to the team: what changed, why, and what to check.

Wrong choiceChanging the Project quietly and trusting people to notice.

SkillWorked example: the notice period nobody updated

Wrenfield's tenant handbook used to require four weeks' written notice to end a tenancy. A new version, in force from 1 April, requires one month. Tenant comms holds an uploaded copy, which does not change when the Drive original does (5.2), and nobody owned the Project to replace it. From 1 to 21 April Claude drafted replies with the old rule, and the officers checking them had not heard of the new handbook either. On 22 April the communications lead caught the error in a check, after 17 replies had gone out:

# before: Tenant comms, 1–21 April, no owner
Knowledge: tenant handbook, February edition
Instructions: … Notice to end a tenancy: four weeks.
→ 17 replies quote four weeks; the handbook now says one month
# after: the owner's change log, 23 April
1. Uploaded the 1 April handbook, removed the old file. Test: 4 of 5 pass.
2. Deleted the notice line from the instructions. Test: 5 of 5 pass.
Message to the team: notice is now one month (new handbook). Check it in replies.
→ replies quote one month; the checkers know what to look for

The cause was a missing owner, not a weak model: the old file and an old instruction line both told Claude four weeks. The lead became the owner and swapped the handbook as one change, then re-ran the test set. Request 1, "How much notice do I give to end my tenancy?", still said four weeks, and because that change was tested on its own, the lead knew a second source was left. The lead deleted the copied line, re-tested, logged both changes and messaged the team. The 17 tenants received a correction letter, checked by the lead under Wrenfield's AI policy.

Keep each fact in one place. The old rule survived because someone had copied it into the instructions. A fact kept in two places needs two updates, and people miss the second. Keep facts in the knowledge files, and keep the instructions for how Claude writes (5.3).

Ask one question: could you name who updates this shared Project, how a change gets tested, and how its users hear about it? Yes → act on each trigger as it comes. No → name an owner, write the trigger list and the test set, and agree where changes are logged and announced.
Takeaway
  • A Project's replies are only as current as its knowledge and instructions, and nothing updates or announces them by itself.
  • Update one thing at a time and re-run the same saved requests after each change, so every result traces to one change.
  • Inform runs both ways: colleagues report triggers to the owner, who tells users what changed, why, and what to check.

check yourself

0 / 3 answered

A sales team shares a Project that holds the price list as knowledge and drafts customer quotes. Prices change each quarter, and last week a rep sent a quote with old prices because nobody had replaced the file. Six people hold Can edit. The sales manager wants the fix at the source, without adding work to every quote.What is the most effective change?

Select one.

A legal team's shared Project drafts contract summaries. Yesterday its owner replaced the clause library file and also rewrote the instructions to add a risk rating. Today the summaries no longer include the governing-law line they always had. The owner cannot tell which change caused it and wants the same confusion avoided next time.Which TWO steps would most directly find the cause and prevent a repeat?

Select two.

A facilities team's owner replaced the building guide in its shared Project a month ago and announced the new visitor sign-in rule. The owner's five saved requests, re-run in the Project yesterday, all give the new rule. A receptionist reports that Claude gave the old rule today, in a chat outside the Project where the receptionist had attached a saved copy of the guide.What is the most likely root cause?

Select one.

sources

  1. Claude Help Center, "Manage project visibility and sharing": sharing on Team and Enterprise plans; Can view members see project contents, knowledge and instructions and chat in the Project but cannot edit it; Can edit members can modify project instructions and knowledge; an email when a Project is shared with you. Checked 2026-10-15.
  2. Claude Help Center, "How can I create and manage projects?": uploaded content is used across all chats in the Project; Claude uses the project instructions for all chats in the Project. Checked 2026-10-15.
  3. Claude Help Center, "Use Google Workspace connectors": the Google Drive option for project files is available only in private Projects and is disabled for shared Projects. Checked 2026-10-15.
  4. Claude Platform Docs, "Define success criteria and build evaluations": design tests that mirror your real-world task distribution, including edge cases. Checked 2026-10-15.
  5. Claude Platform Docs, "Prompting best practices": model-specific guidance on where a single model behaves differently and what to change in a prompt, including literal instruction following. Checked 2026-10-15.
  6. Wrenfield's April handbook change, the 17 replies, the owner's routine, the test set and the change log are this course's example.