Use a Claude Project to Separate Launch Facts from Assumptions

For: product, marketing, and operations teams preparing a launch from incomplete notes.

You will create: an assumption register with claim, source support, classification, owner question, and decision needed.

Evidence label: Documentation-based guide. The output below is illustrative. No Claude run is claimed.

What you need

Use Claude on the web with Projects available. Anthropic’s help documentation says Projects can hold chats and a knowledge base. It also says you can upload documents to project knowledge and set project instructions. The exact interface and plan limits can change, so use the controls visible in your account.

Use a fictional or approved launch note. Do not add private customer, employee, or unreleased company information unless your workspace permits it.

Sample input

Create a file called launch-notes.txt with this content:

Launch notes for the Northstar invoice reminder feature

The feature sends a reminder when an invoice is seven days late.

Marketing wants to announce it to small business customers in November.

The product note says reminders can be paused by an account administrator.

The launch meeting did not confirm whether reminders are on by default, which customer plans receive the feature, or who handles support questions.

The team expects fewer overdue invoices, but no baseline or target was recorded.

Steps

1. Open Claude and create a new Project. If your account shows a different project flow, follow the current in-product labels.
2. Add launch-notes.txt to the project’s knowledge base.
3. Add the project instruction below. Keep it narrow so the project does not turn guesses into facts.
4. Start a chat in the Project and request the register using the second prompt.
5. Compare each row with the source file. Ask the relevant owner to resolve open questions before using the register for a launch decision.

Project instruction

Use only the files added to this project as factual source material.
Separate direct facts, stated plans, assumptions, and missing information.
Never turn an expectation into a result.
When a statement is not supported by the source, label it "Not supported by source".
Use short source quotes for supported claims.

Copyable prompt

Read the launch note in this project and create an assumption register with these columns:

- Claim or assumption
- Type: fact, stated plan, assumption, or missing information
- Short source quote, or "No source quote"
- What must be confirmed
- Owner question
- Decision needed before launch

Rules:
- Keep one row per distinct claim or uncertainty.
- Do not add a date, owner, plan entitlement, default setting, support process, target, or customer result unless the note states it.
- Treat "expects" as an assumption, not evidence of an outcome.
- Put missing information in the register instead of filling the gap.
- Finish with the three questions that would block a responsible launch review.

Illustrative output

Claim or assumption	Type	Source quote	What must be confirmed	Decision needed
The feature sends a reminder when an invoice is seven days late	Fact	“sends a reminder when an invoice is seven days late”	Confirm the trigger in the product specification	Is the trigger ready for launch review?
Marketing plans a November announcement	Stated plan	“announce it … in November”	Confirm the date and audience	Should the announcement date be approved?
An account administrator can pause reminders	Fact	“can be paused by an account administrator”	Confirm where the setting is documented	Is the control ready for customer support?
Reminders are on by default	Missing information	No source quote	Confirm the default setting	Should the default be approved?
The feature is available to small business customers	Missing information	No source quote	Confirm eligible plans	Which plans are in scope?
The team expects fewer overdue invoices	Assumption	“expects fewer overdue invoices”	Define a baseline and target	Is there a measurement plan?

This is a desired example, not a model-generated result. Check every row against the source.

Acceptance checks

The register passes when:

• It includes the seven-day trigger and pause control as source-supported facts.
• It does not claim a November launch date, plan eligibility, a default setting, or a reduction in overdue invoices as established facts.
• Every supported row has a quote that appears in the source note.
• Missing decisions remain visible.
• A named owner can answer the blocking questions before launch approval.

If the result goes wrong

• The output sounds too certain: ask for a source quote beside every fact and delete unsupported rows that are not labeled as assumptions or missing information.
• Claude cannot find the note: check that the file appears in the Project knowledge area, then start a new Project chat after the upload finishes.
• The project remembers an old answer: inspect the knowledge files and project instructions, then ask Claude to use only the current file and show its source quote.

Limits and privacy

A Project can organize context, but it does not verify a product specification or approve a launch. Check changing Project availability, file limits, and sharing permissions in your account. Keep access narrow and review the register with the accountable team.

For a related source-linked customer artifact, see Use a Claude Project to turn approved product notes into a source-linked FAQ. If you want one practical work lesson each week, join the updates.

Sources

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