Clone Support

knowledge-plan-worksheet.md

Plan what each clone should know before you upload: knowledge levels, a document inventory, which clone gets what, document hygiene, a 15–20 question test set and owners. Fill it in; no Google account needed.

Version 1 · updated Nov 15, 2026

# Knowledge plan worksheet: [COMPANY NAME]

> How to use this template: fill it in before you upload documents to Knowledge. It decides what each clone should know, where each document lives, and who can see it. Blank answers are fine; a rough plan beats none. Keep it as a working file; don't upload this worksheet itself.

## How knowledge levels work

| Level | Who can use it | Best for |
|---|---|---|
| Clone | Only that clone | Role-specific documents (e.g. the support clone's FAQ) |
| User | Any clone, but only when that user is the one using it | Personal notes, drafts, your own preferences |
| Organization (Team knowledge) | All clones and users (can be limited by department) | Brand and style guide, company policies, anything everyone needs |

**Golden rule:** anything a public-facing clone can read, a member of the public could learn. Keep sensitive internal data (payments, personal records, contracts) on a separate internal clone, and give public-facing clones only approved, customer-safe content.

## Step 1: Inventory your documents
One row per document. The first row is an example.

| Document | Owner | Format | Language | Internal or public | Sensitivity (low / medium / high) | Which clone(s) | Level | Last reviewed | Ready to upload? |
|---|---|---|---|---|---|---|---|---|---|
| [Customer FAQ] | [Support] | [PDF] | [English] | [Public] | [Low] | [Support clone] | [Clone] | [date] | [Yes] |
| | | | | | | | | | |
| | | | | | | | | | |

## Step 2: Decide your clones

| Clone | Audience | Purpose | Knowledge it can use | Integrations (website, phone, Teams, email...) |
|---|---|---|---|---|
| [Customer support clone] | [Customers, public] | [Answer questions, hand off when needed] | [Approved FAQs and policies only] | [Website embed, phone] |
| [Internal operations clone] | [Staff] | [Reports, internal questions] | [Internal procedures] | [Teams, email] |
| | | | | |

## Step 3: Document hygiene
- One topic per document where possible, with a clear title
- Keep one current version; remove outdated copies
- Use CSV or plain text for data tables
- Remove personal or sensitive data the clone doesn't need
- Note each document's language, and test questions in that language
- Give every document an owner who keeps it current

## Step 4: Test set
Collect 15 to 20 real questions people have asked, with the ideal answer for each. After uploading, ask your clone each one and compare. Fix gaps by improving the documents, not the questions.

| # | Real question | Language | Ideal answer | Source document | Answered correctly? (Y/N) |
|---|---|---|---|---|---|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |

## Step 5: Owners and review rhythm
- Knowledge owner: [name]
- Review cadence: [monthly / quarterly]
- Who approves new documents before upload: [name]

Was this useful?