Skip to main content
A Saved prompt is reusable prompt text. Use Saved prompts for instructions you send often, such as document review patterns, meeting follow-up requests, deviation investigation tables, CAPA traceability checks, or CoSheet analysis prompts. Saved prompts do not make Sofie remember facts. They insert text into chat so you can reuse and adapt it.
Use Memory for durable facts or preferences. Use Directives for standing rules Sofie should follow. Use an Orchestration when the work needs repeatable steps, tools, review points, or structured outputs.

​
Open Prompts

Open Prompts from the main sidebar. The Prompts page lets you:
  • Create a Saved prompt.
  • Search your prompts.
  • Sort by Recently updated, Recently created, or Title.
  • Use a prompt to start a new chat.
  • Edit prompt title or content.
  • Delete prompts you no longer need.

​
Create a Saved prompt

1

Open Prompts

Click Prompts in the sidebar.
2

Click Create

Click Create.
3

Name the prompt

Enter a clear Title. Use the outcome, not only the topic.
4

Write the prompt

Enter the reusable text in Prompt.
5

Save

Click Save.
Good titles:
  • Deviation gap table
  • CAPA traceability review
  • Meeting follow-up summary
  • Protocol acceptance criteria check
  • CoSheet data quality profile

​
Save a prompt from chat

When you write a prompt in chat that you expect to reuse, save it instead of rebuilding it later. Good candidates:
  • A prompt that creates the same output format every week.
  • A source review checklist you use across projects.
  • A meeting follow-up format your team expects.
  • A table structure for deviations, CAPA, URS, validation, or batch record review.
Keep the reusable part in the Saved prompt. Add project-specific details in chat each time.

​
Use a Saved prompt

There are two common ways to use a Saved prompt.

​
Start from Prompts

1

Open Prompts

Click Prompts in the sidebar.
2

Find the prompt

Search or sort until you find the prompt.
3

Select it

Click the prompt card. Sofie starts a new chat with the prompt text ready to use.
4

Add context

Add a Workspace, CoDraft, CoSheet, CoMeeting, file attachment, or search setting.
5

Edit before sending

Add project-specific details before you send.

​
Insert from chat

1

Click plus

In chat, click +.
2

Choose Prompts

Open Prompts.
3

Search prompts

Search for the Saved prompt you want.
4

Insert and edit

Select the prompt, then edit the inserted text for the current task.

​
Edit or delete a prompt

1

Open Prompts

Click Prompts in the sidebar.
2

Find the prompt

Search by title or prompt content.
3

Open the menu

Hover over the prompt and open the action menu.
4

Choose Edit or Delete

Use Edit to update the title or prompt. Use Delete when the prompt is stale or duplicated.
Deleting a Saved prompt removes the reusable prompt. It does not delete chats where you used the prompt.

​
Write prompts that stay reusable

A Saved prompt should define the repeatable pattern without locking in temporary project facts. Use this structure: 
Task:
Sources to use:
Output format:
Review rules:
What to flag:
What not to assume:
Good Saved prompt: 
Review the provided source material for deviation investigation gaps. Return a table with known fact, source, missing evidence, follow-up question, likely owner, and whether the issue affects root cause, CAPA, or batch impact. Do not infer root cause unless the source supports it.
Less reusable: 
Review yesterday's filling line deviation and explain why the stopper issue happened.
The less reusable version bakes in time and unsupported conclusion language. Keep that context in the chat message, not the Saved prompt.

​
Life sciences Saved prompt patterns

Review the selected deviation materials. Return a table with known facts, source support, missing evidence, follow-up questions, owner or SME, and whether each item affects impact, root cause, CAPA, or closure rationale. Separate assumptions from facts.

Evaluate this CAPA plan for traceability. For each action, list the linked cause or contributing factor, source support, owner, due date, effectiveness measure, evidence needed, and open risk. Flag any action that does not map to a source-supported cause.

Create a meeting follow-up summary with decisions, action items, owners, due dates, unresolved questions, risks, and source transcript references where available. Keep recommendations separate from confirmed decisions.

Analyze this CoSheet for missing values, outliers, duplicate records, inconsistent units, and trends that need review. Return a table with issue, affected rows or columns, possible cause, recommended check, and whether a formula, chart, or pivot would help.

​
Saved prompt versus other reuse tools

NeedBetter tool
Reuse text in chatSaved prompt
Sofie should remember a stable fact or preferenceMemory
Sofie should follow a standing ruleDirective
Run a repeatable multi-step processOrchestration
Reuse document structureTemplate
Keep project sources available to a teamWorkspace