A consultant at a management consultancy is running a six-week process review for a client and works in a Claude Project her team shares for that client. Each working session produces decisions on scope and recommendations, and a colleague will take over the engagement for its final fortnight. How should she make sure the agreed decisions carry forward?
- AKeep the whole engagement in one ongoing chat so her colleague can scroll back through it
- BRely on Memory to carry the decisions forward so they are recalled in her colleague's chats
- CEnd each session by saving an updated, reviewed summary of all decisions so far to project knowledge, replacing the last Correct
- DUpload every session's full chat transcript to project knowledge as a separate new file
Why A is wrong: A single thread seems to keep everything in one place. Over six weeks it becomes very long, earlier decisions blur with discarded options, and the colleague would have to reconstruct what was finally agreed.
Why B is wrong: Memory does carry context between chats, which makes it sound suitable. It is tied to the person using Claude rather than being a shared, reviewable record, and engagement decisions are reference material that belongs in project knowledge.
Why C is correct: A checked summary of every decision to date, held in the shared Project's knowledge, is available to every chat in the Project, including the colleague's, and replacing the previous version keeps one authoritative record instead of conflicting copies.
Why D is wrong: Saving everything feels thorough. Raw transcripts mix rejected options with final decisions and pile up as separate, sometimes contradictory files, so Claude and the colleague cannot tell which position is current.