Client Writing Guides — Centralized Knowledge
Overview
Inconsistent content quality and recurring factual errors traced back to a single root cause: no centralized, shared system for storing client-specific writing rules. Writers relied on informal feedback, outdated free AI models, and memory — all of which fail at scale.
The solution is a structured Client Writing Guide for each client, stored inside a shared Claude Team Project. Every guide becomes the single source of truth that governs all AI-assisted content production for that client.
See also: [1] for how these guides fit into the full 4-step workflow.
Why This Matters
Without a centralized guide, errors compound:
- Factual hallucinations — free-tier AI models fabricate details (e.g., incorrect fee structures for a reverse ATM client)
- Brand language violations — forbidden terms slip through (e.g., "peel oil" or "crushing" for Citrus America, where "squeezing" is required)
- Geographic errors — content references regions a client doesn't serve (e.g., Illinois content for a client that doesn't operate there)
- Category misclassification — describing a memory care facility as assisted living
Each of these has reached clients. The writing guide prevents recurrence by encoding corrections permanently.
Guide Structure
Each client's writing guide should contain two core documents:
1. Client Profile
Factual grounding for the AI — reduces hallucination risk.
| Field | Description |
|---|---|
| Business model | How the client makes money |
| Core product/service | What they actually sell or do |
| Primary customers | Who buys from them |
| Key competitors | Who they compete against |
| Geographic scope | Where they operate |
| Industry-specific facts | Anything a generalist AI might get wrong |
2. Writing Guidance
Brand voice and terminology rules — enforces consistency.
| Field | Description |
|---|---|
| Approved terms | Words/phrases the client prefers |
| Forbidden terms | Words/phrases never to use |
| Tone and style | Formal/casual, technical/accessible, etc. |
| Topic boundaries | Subjects to avoid or handle carefully |
| Past corrections | Specific errors flagged by the client |
Example (Citrus America):
- ❌ Never use: "peel oil," "crushing"
- ✅ Always use: "squeezing"
- ❌ Never describe as: assisted living (applies to memory care clients generally)
Where Guides Live
Guides are stored as documents inside Claude Team Projects — not personal projects.
Setup steps:
1. Log into the shared Asymmetric Claude account
2. Confirm you are on the Team plan (look for the building icon at the bottom of the sidebar)
3. Navigate to Projects → Team
4. Open or create the project for the relevant client
5. Upload the Client Profile and Writing Guidance documents
Important: Projects created under your personal workspace are not visible to teammates. Always work under the Team section.
When Claude opens a project, it reads all attached documents before responding. Starting a session with "review the files" ensures the guide is loaded before any drafting begins.
Maintenance
Writing guides are living documents. When a client flags an error or provides new guidance:
- Add the correction to the Writing Guidance document
- Re-upload the updated document to the Claude project
- Note the change so the team is aware
This transforms every client correction into a permanent guardrail rather than a one-time fix.
Current Status (as of April 2026)
| Client | Guide Status | Owner |
|---|---|---|
| Citrus America | Draft — pending Miriam's approval | Melissa |
| Scotland | In progress | Melissa |
| Didion | Not started | Melissa |
| Bluepoint | N/A — client offboarded | — |
Related
- [1]
- [2]
- [3]