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

# Handoff and review from notifications

> Use notifications to return to paused work, review generated outputs, and continue Sofie workflows safely.

Sofie may surface work through notifications when something needs attention. The notification is the signal. The review usually happens in the related chat, artifact, Workspace, Orchestration, Sequence, or settings page.

This guide explains how to handle those handoffs without losing context.

## Common handoff patterns

| Notification says                     | Open                      | What to check                                                                                        |
| ------------------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------- |
| A chat was shared with you            | Chat                      | What the sender wants, source context, and whether you should continue the thread.                   |
| A CoDraft has a comment or suggestion | CoDraft                   | The selected text, proposed change, surrounding section, and source support.                         |
| An Orchestration completed            | Orchestration run or chat | Inputs, outputs, sources, warnings, and the **Artifacts** section for created or modified artifacts. |
| A workflow needs review               | Chat or workflow run      | The question, current output, source support, and whether to continue.                               |
| A Sequence started or finished        | Sequence or run details   | Schedule, inputs, output destination, and errors if present.                                         |
| A Workspace invitation arrived        | Workspace                 | Workspace purpose, members, files, and what you are expected to do.                                  |
| A meeting was shared                  | CoMeeting                 | Transcript, summary, notes, action items, and follow-up context.                                     |
| A security alert appeared             | Account or security page  | Whether the activity is expected and whether you need admin help.                                    |

## Respond to a paused workflow

<Steps>
  <Step title="Open the notification">
    Click the notification that needs action.
  </Step>

  <Step title="Review where it sends you">
    Confirm whether you are in chat, an artifact, a Workspace, an Orchestration, a Sequence, or account settings.
  </Step>

  <Step title="Read the current state">
    Identify what Sofie already did, what it is asking for, and what will happen next.
  </Step>

  <Step title="Check the source set">
    Review selected files, Workspace search results, CoMeeting content, CoSheet data, or citations before approving next steps.
  </Step>

  <Step title="Reply with a decision">
    Continue, revise, stop, ask for more evidence, or move the work to the right artifact.
  </Step>
</Steps>

Example responses:

```text theme={null}
Continue, but add a source-gap column before drafting the conclusion.
```

```text theme={null}
Do not save this yet. Show the CoDraft outline and destination first.
```

```text theme={null}
Stop this run. It used the wrong Workspace. Restart with the PPQ Workspace only.
```

## Review before continuing

Before you let Sofie continue, check:

* Source files and search modes.
* Workspace or artifact destination.
* Artifacts created or modified during the run.
* Whether public web sources were used.
* Whether assumptions are labeled.
* Whether calculations or formulas need review.
* Whether conclusions rely on missing evidence.
* Whether the next action will create, edit, save, send, publish, or share content.

<Tip>
  If you are not sure what Sofie will do next, ask: `Before continuing, state the next action, source set, destination, and what will be visible to others.`
</Tip>

## Use handoff prompts

Use these prompts when a notification sends you back into active work.

```text theme={null}
Summarize the current state of this workflow. Include completed steps, pending decisions, source material used, open issues, and the next action you are waiting on.
```

```text theme={null}
Before continuing, show what will be created or changed and who can access it.
```

```text theme={null}
Show me every artifact this run created or modified. Include the artifact title, type, action taken, task that touched it, and what I should review.
```

```text theme={null}
List all assumptions in the current result and mark which ones need SME review.
```

```text theme={null}
Create a CoDraft only after I approve the title, Workspace, outline, and source set.
```

## Handling failed or stale work

If a notification reports a failed run or stale work:

* Open the related item.
* Check whether inputs are missing or outdated.
* Confirm that the Workspace, files, and connected apps are still accessible.
* Check whether a Sequence schedule should be paused.
* Rerun only after you know what changed.

For recurring work, compare the failed run with the last successful run:

```text theme={null}
Compare this failed Sequence run with the last successful run. Identify changed inputs, missing access, source issues, and what I should fix before rerunning.
```

## Notifications and controlled work

Notifications help you return to the right place. They do not decide whether an output is acceptable.

Use Sofie notifications to:

* Find the item that needs attention.
* Continue a paused workflow.
* Review generated output.
* Route work to a CoDraft, CoSheet, Workspace, or Orchestration.
* Notice when a scheduled process fails.

Do not use notifications alone to:

* Approve technical conclusions.
* Accept calculations without checking formulas.
* Release a document.
* Bypass your organization’s required review process.

<Warning>
  Treat notification-driven handoffs as workflow control inside Sofie. Your organization’s formal review, approval, validation, or release process remains separate unless your team has explicitly configured and documented otherwise.
</Warning>