Skip to main content
Use chat as the starting point for most Sofie work. A good chat request names the task, source material, output, and review boundary.

​
Start with a complete request

Use this structure when the task matters:
Example:

​
Run a source-backed review

1

Add the right context

Attach one-time files or add the Workspace that contains the shared source set.
2

Choose search settings

Turn on Workspace search for Workspace files. Turn on Web search or Deep research only when public sources are needed.
3

Ask for source separation

Tell Sofie to separate facts, assumptions, source gaps, and review questions.
4

Review the answer

Check source names, citations when provided, and whether the answer used the source set you expected.
5

Move the result

Ask Sofie to create a CoDraft, CoSheet, Workspace item, or Orchestration output after you review the structure.
Good prompt:

​
Create a CoDraft from chat

Use this when a chat answer needs to become a document.
1

Ask for an outline first

Request headings, source set, assumptions, and intended audience before creating the document.
2

Confirm the destination

Name the Workspace and folder where the CoDraft should live.
3

Create the CoDraft

Ask Sofie to create the document after you approve the outline.
4

Continue editing in context

Open the CoDraft and use Sofie Everywhere or chat context to revise sections, add comments, or prepare suggestions.
Example:

​
Create or analyze a CoSheet from chat

Use CoSheet when data should remain editable.
1

Attach data or select an existing CoSheet

Use XLSX, CSV, or an existing CoSheet as the source.
2

State the data task

Ask Sofie to profile columns, identify missing values, suggest formulas, create a chart, or build a pivot table.
3

Ask for formula review

For calculated fields, ask Sofie to show the formula and explain the assumptions before applying it broadly.
4

Export when ready

Export back to Excel or keep the CoSheet in a Workspace for team review.
Example:

​
Run an Orchestration from chat

Use an Orchestration when the work has repeatable steps, defined inputs, and review points.
1

Find the workflow

Ask Sofie to find an Orchestration by name, use case, or library category.
2

Provide required inputs

Add the Workspace, files, date range, product, process, or other required fields.
3

Set review rules

Tell Sofie where to pause before conclusions, artifact creation, or shared saves.
4

Run and inspect

Review intermediate outputs, citations, structured results, and the Artifacts section for items the run created or modified.
Example:
After the run completes, open artifacts from the run result when available. Use Open in side panel for quick review or Open in new tab for the full artifact page. Good follow-up:

​
Build an Orchestration from chat

When you are designing a workflow, ask Sofie to draft the workflow first.
After Sofie drafts the design, move to the Orchestrate editor to refine details. Use Build Orchestrations with chat for the full workflow.

​
Use a Template from chat

Templates are reusable CoDraft structures. They work well when the document format is known but source details change.
1

Choose a template

Use Templates or ask Sofie to help find a relevant template.
2

Start a fill conversation

Ask Sofie to help fill the template. Sofie can ask follow-up questions for required fields.
3

Provide sources

Add the Workspace, attachments, meeting notes, or CoSheet that should supply content.
4

Review before creating the final document

Check field values, assumptions, missing evidence, and destination.
Example:

​
Use a Sequence from chat

If Sequence is enabled for your organization, use it when an Orchestration should run later or on a recurring schedule. Good uses:
  • Weekly Workspace summary.
  • Daily open item triage.
  • Recurring meeting follow-up digest.
  • Scheduled monitoring of workflow inputs.
Example:

​
Keep work reviewable

Use these habits when chat actions create durable work:
  • Ask for an outline before document creation.
  • Ask for formulas before filling a CoSheet.
  • Ask for source lists before conclusions.
  • Ask for a preview before connected app actions.
  • Ask Sofie to pause before shared saves.
  • Keep project source material in a Workspace instead of reattaching it in every chat.
Do not use a generated answer as final technical judgment. Review sources, calculations, assumptions, and destination before using work in regulated, quality, clinical, or controlled processes.