Create, edit, share, promote, and reuse Saved prompts for repeatable Sofie chat requests.
A Saved prompt is reusable prompt text plus optional chat setup. Use Saved prompts for instructions you send often, such as document review patterns, meeting follow-up requests, deviation investigation tables, CAPA traceability checks, CoSheet analysis prompts, or Sofie Guide help prompts.Saved prompts do not make Sofie remember facts. They insert reusable instructions into chat so you can adapt them for the current task.
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.
Web search, Deep research, Workspace search, Plan Mode, and Sofie Guide toggle state.
Added context, such as a CoDraft, CoSheet, CoMeeting, Workspace, Orchestration, plan, or selected content.
Attachments.
References inserted with [[.
Be careful when saving prompts with context or attachments. Anyone you share the prompt with may be able to see or use the saved prompt setup according to their access and the prompt permissions.
Enter a clear Title. Use the outcome, not only the topic.
4
Write the prompt
Enter the reusable text in Prompt.
5
Add optional setup
Choose a model, add context, attach files, or turn on search settings such as Workspace search, Plan Mode, or Sofie Guide when they should be part of the prompt.
Promote a prompt when it should be available as an organization prompt. This is useful for approved team patterns, onboarding prompts, or standard source-review formats.You can promote a prompt when:
Your account has permission to publish prompts.
You own the prompt or have editor access.
The prompt is not already an organization prompt.
1
Open the prompt menu
Find the prompt on the Prompts page.
2
Choose Promote to Organization
Click Promote to Organization.
3
Review the prompt
Confirm the text, context, attachments, and search settings are appropriate for organization use.
Users with permission to manage organization prompts can remove a prompt from the organization.
Do not promote prompts that contain project-specific confidential context, temporary assumptions, uncontrolled attachments, or instructions that should not become a team standard.
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.When a prompt includes context or attachments, keep them stable and reusable. For example, an onboarding Workspace or organization training document may belong in a shared prompt. A one-off deviation file usually belongs in the chat message instead.
Saved prompts can include references created with [[. Use references when the prompt should point to specific saved context or attachments.Example:
Use [[Review checklist]] to evaluate [[Draft protocol]]. Return a table with section, checklist item, source support, gap, impact, and SME question. Do not infer acceptance criteria.
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.
CAPA traceability
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.
Meeting follow-up
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.
CoSheet data review
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.
Sofie Guide help
Use Sofie Guide. Answer with citations to Sofie documentation. Explain the workflow, when to use it, when not to use it, and what the user should review before using the output in controlled work.
