> ## Documentation Index
> Fetch the complete documentation index at: https://sofiedocs.usetransfer.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run work from chat

> Use Sofie chat to move from a request to source search, artifact creation, workflow execution, and review.

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:

```text theme={null}
Task:
Source:
Output:
Constraints:
Review point:
```

Example:

```text theme={null}
Task: Review the attached deviation summary for investigation gaps.
Source: Attached deviation summary and the fill-finish investigation Workspace.
Output: Table with known facts, missing evidence, likely source documents, and SME questions.
Constraints: Do not conclude root cause.
Review point: Show the table before creating a CoDraft.
```

## Run a source-backed review

<Steps>
  <Step title="Add the right context">
    Attach one-time files or add the Workspace that contains the shared source set.
  </Step>

  <Step title="Choose search settings">
    Turn on **Workspace search** for Workspace files. Turn on **Web search** or **Deep research** only when public sources are needed.
  </Step>

  <Step title="Ask for source separation">
    Tell Sofie to separate facts, assumptions, source gaps, and review questions.
  </Step>

  <Step title="Review the answer">
    Check source names, citations when provided, and whether the answer used the source set you expected.
  </Step>

  <Step title="Move the result">
    Ask Sofie to create a CoDraft, CoSheet, Workspace item, or Orchestration output after you review the structure.
  </Step>
</Steps>

Good prompt:

```text theme={null}
Use Workspace search to review the validation package. Return a table with source, evidence, gap, risk, and reviewer question. Do not draft final conclusions.
```

## Create a CoDraft from chat

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

<Steps>
  <Step title="Ask for an outline first">
    Request headings, source set, assumptions, and intended audience before creating the document.
  </Step>

  <Step title="Confirm the destination">
    Name the Workspace and folder where the CoDraft should live.
  </Step>

  <Step title="Create the CoDraft">
    Ask Sofie to create the document after you approve the outline.
  </Step>

  <Step title="Continue editing in context">
    Open the CoDraft and use Sofie Everywhere or chat context to revise sections, add comments, or prepare suggestions.
  </Step>
</Steps>

Example:

```text theme={null}
Create a CoDraft CAPA effectiveness check memo from this table. Use sections for objective, source evidence, criteria, findings, limitations, and open questions. Show the outline before creating it.
```

## Create or analyze a CoSheet from chat

Use CoSheet when data should remain editable.

<Steps>
  <Step title="Attach data or select an existing CoSheet">
    Use XLSX, CSV, or an existing CoSheet as the source.
  </Step>

  <Step title="State the data task">
    Ask Sofie to profile columns, identify missing values, suggest formulas, create a chart, or build a pivot table.
  </Step>

  <Step title="Ask for formula review">
    For calculated fields, ask Sofie to show the formula and explain the assumptions before applying it broadly.
  </Step>

  <Step title="Export when ready">
    Export back to Excel or keep the CoSheet in a Workspace for team review.
  </Step>
</Steps>

Example:

```text theme={null}
Import this CSV into a CoSheet. Profile missing values, flag outliers, suggest formulas for cycle time and yield, and show me the formulas before filling the column.
```

## Run an Orchestration from chat

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

<Steps>
  <Step title="Find the workflow">
    Ask Sofie to find an Orchestration by name, use case, or library category.
  </Step>

  <Step title="Provide required inputs">
    Add the Workspace, files, date range, product, process, or other required fields.
  </Step>

  <Step title="Set review rules">
    Tell Sofie where to pause before conclusions, artifact creation, or shared saves.
  </Step>

  <Step title="Run and inspect">
    Review intermediate outputs, citations, structured results, and the **Artifacts** section for items the run created or modified.
  </Step>
</Steps>

Example:

```text theme={null}
Run the CAPA effectiveness Orchestration with this Workspace. Use only Workspace search. Pause before drafting the final effectiveness conclusion.
```

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:

```text theme={null}
List the artifacts touched by this run. For each one, tell me whether it was created or modified, which task touched it, and what I should review before using it.
```

## Build an Orchestration from chat

When you are designing a workflow, ask Sofie to draft the workflow first.

```text theme={null}
Help me design an Orchestration for batch record review triage. Include required inputs, agents, tasks, source rules, Structured Outputs, human review points, and test cases. Do not publish it.
```

After Sofie drafts the design, move to the Orchestrate editor to refine details. Use [Build Orchestrations with chat](/orchestrate/build-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.

<Steps>
  <Step title="Choose a template">
    Use **Templates** or ask Sofie to help find a relevant template.
  </Step>

  <Step title="Start a fill conversation">
    Ask Sofie to help fill the template. Sofie can ask follow-up questions for required fields.
  </Step>

  <Step title="Provide sources">
    Add the Workspace, attachments, meeting notes, or CoSheet that should supply content.
  </Step>

  <Step title="Review before creating the final document">
    Check field values, assumptions, missing evidence, and destination.
  </Step>
</Steps>

Example:

```text theme={null}
Help me fill the deviation report template. Use this Workspace and ask one question at a time for missing fields. Keep assumptions in a separate section.
```

## 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:

```text theme={null}
Create a Sequence that runs the weekly Workspace summary Orchestration every Friday at 9:00 AM Pacific. Keep it paused until I review the schedule and inputs.
```

## 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.

<Warning>
  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.
</Warning>