Use a Claude Project to Turn Approved Product Notes into a Source-Linked FAQ

A product FAQ is easy to draft badly. The wording sounds confident, but one invented limit or missing condition can create a support problem.

This guide shows how to use a Claude Project as a bounded workspace for approved product notes. It creates a draft FAQ and a source map for human review. It is documentation-based and illustrative. I am not claiming to have run this workflow in Claude.

Anthropic describes Projects as self-contained workspaces with their own chat histories and knowledge bases. Uploaded material in a project’s knowledge base can be used across chats in that project. The exact interface and plan access can change, so check your account before following the steps.

What you will create

A customer-facing FAQ draft plus a claim table that points each answer back to a fictional source note.

You need Claude with Projects available, the web version, product notes you are permitted to upload, and no secrets, private customer records, or unapproved pricing promises.

Fictional source pack

Create two plain-text files.

product-notes.txt

Product: Northstar Desk
Release status: Pilot for invited teams only.
Supported input: CSV files with a header row. Maximum file size is not specified in this note.
Exports: The pilot can produce a PDF summary. This note does not confirm other export formats.
Access: An administrator invites team members. This note does not describe guest access.
Data handling: Use only approved workspace data. Retention and deletion terms are not included here.
Support: Pilot questions go to the named internal pilot owner. No public response-time promise is approved.

faq-boundary.txt

Write for an operations manager evaluating a pilot.
Never invent a limit, price, date, retention period, security certification, or response-time promise.
If the source pack does not answer a question, label it "Needs product owner confirmation."
Keep each answer under 80 words.

The missing facts are deliberate. A useful FAQ makes gaps visible instead of smoothing them over.

Steps

1. Open Claude and create a new Project. Use a name such as Northstar Desk FAQ review.
2. Add both files to the project’s knowledge base. Keep the originals unchanged outside Claude.
3. Add this project instruction:

Use only the files in this project's knowledge base for product claims. Every answer must include a source label using the exact filename. If the files do not answer a question, write "Needs product owner confirmation." Do not invent prices, dates, limits, certifications, retention terms, or support promises. Draft only. Do not send or publish anything.

4. Start a project chat with:

Using only the project knowledge, draft a customer FAQ for an operations manager considering the Northstar Desk pilot.

Return two sections:
1. FAQ draft: 8 questions with short answers.
2. Claim review table: question, answer claim, source filename and exact supporting sentence, or "not found".

Use plain English. Separate confirmed facts from missing information. Do not turn pilot access into general availability. Do not imply that an unspecified file size, export format, retention period, price, or support response time exists.

5. Check the claim review table before editing the FAQ. It is the review artifact, not decorative citation furniture.
6. Keep every not found row as a question for the product owner. Do not fill a gap from memory.
7. Ask for a second pass:

Audit the FAQ against the source files. List every sentence that adds a detail not stated in the files. For each one, quote the sentence, explain the problem, and propose either a source-grounded rewrite or "Needs product owner confirmation." Do not rewrite silently.

8. Copy the FAQ and audit into a separate document. A human product owner should approve the wording before publication or sending.

Example artifact

This is an editor-written illustration, not Claude output:

Question	Draft answer	Source check
Who can use Northstar Desk?	The pilot is available to invited teams.	product-notes.txt, “Pilot for invited teams only.”
What file format can it accept?	The pilot supports CSV files with a header row.	product-notes.txt, “Supported input…”
What is the maximum CSV size?	Needs product owner confirmation.	Not found in the source pack.
Can it export a PowerPoint file?	Needs product owner confirmation.	Not found in the source pack.

The point is not to make every answer sound complete. It is to make unsupported certainty hard to miss.

Acceptance check

The workflow passes when every factual answer has a source filename and matching sentence, missing facts remain marked for confirmation, pilot access is not rewritten as general availability, the FAQ contains no invented price, date, limit, certification, retention term, or support promise, and a product owner can review the claim table without reopening the Project.

If something goes wrong

Claude answers from general knowledge. Restate the source-only instruction and ask for a claim audit. Remove any answer whose source cannot be found.

The files do not appear. Confirm that they were added to the Project knowledge base, not merely mentioned in a different chat. The interface can vary by account.

A source claim changes silently. Compare the claim table with the original files line by line.

Someone asks you to publish immediately. Stop at the draft. This workflow prepares a review artifact and does not authorize publication or product commitments.

Limits and privacy

A Project knowledge base is not a substitute for an approved source repository or document-control process. Upload only material your workspace permits. Review sharing and visibility settings before adding internal notes. Keep customer data and credentials out of the practice pack.

For a similar source-checking habit applied to project updates, see Use a Claude Project to Turn Approved Updates into a Weekly Status Brief. For a no-code document reply workflow, see Use ChatGPT to Turn Product Documentation into a Customer Reply Draft.

Want one practical workflow each week? Join The Weekly Verdict.

Sources

• What are Projects?
• How can I create and manage Projects?

Evidence label: Documentation-based guide with an illustrative example. No personal test, reproduced demo, measured result, or client result is claimed.