Skip to main content
An Orchestration is a repeatable Sofie workflow. Use Orchestrate when work needs structured steps, reusable instructions, multiple agents, tools, inputs, or human review before continuing. For guidance on designing reusable workflows, see Use Orchestrations intelligently. For schema design and task handoff, see Structured Outputs. For detailed testing guidance, see Test Orchestrations. For detailed build instructions, see Build and edit an Orchestration. To design one from chat, see Build an Orchestration with Sofie chat.

​
When to use Orchestrate

Use Orchestrate when the same kind of work repeats with different inputs. Good candidates:
  • CAPA development.
  • CAPA effectiveness checks.
  • Deviation investigation report authoring.
  • Batch record review.
  • Tech transfer charter generation.
  • Validation protocol generation.
  • URS drafting.
  • Quality risk assessment.
  • Regulatory or pharmacopoeia research.
Use chat for one-off analysis. Use Orchestrate when you want the process itself to be reusable. Sofie onboarding screen introducing Orchestrate for repeatable workflows

​
Understand the Orchestrate page

The Orchestrate page includes:
AreaUse it for
My OrchestrationsYour owned and shared Orchestrations.
PinnedOrchestrations you return to often.
OrganizationPublished Orchestrations available through your organization.
LibraryPrebuilt workflow templates.
CreateStart a new Orchestration.
UploadImport an Orchestration file when supported.
Grid/list toggleSwitch between card browsing and table scanning.
Filter and sort controlsNarrow by draft, published, date, or name.

​
Start from the library

The Library includes prebuilt workflows that may be available to your organization. Examples include:
  • Annual Product Review (APR/PQR)
  • CAPA Development
  • CAPA Effectiveness Check
  • Complaint Investigation
  • Deviation Investigation Report Author
  • Deviation Investigation Review & Verification
  • GMP Batch Record Review Orchestration
  • Master Risk Assessment
  • Pharmacopoeia Monograph Comparative Analyzer
  • Process Validation Protocol Generator
  • Regulatory Compliance Explorer
  • Tech Transfer Charter Generator
  • User Requirements Specification Builder
  • Validation Master Plan Generator
1

Open Orchestrate

Click Orchestrate in the sidebar.
2

Open Library

Select the Library tab.
3

Search or browse

Search by workflow type, such as CAPA, deviation, URS, validation, or risk.
4

Preview the workflow

Use the view option to inspect the workflow structure before running it.
5

Run the workflow

Run the Orchestration from the Library or create your own copy when you need to customize it.

​
Build an Orchestration

An Orchestration is made from practical building blocks.
Building blockWhat to define
AgentsSpecialized roles, such as reviewer, researcher, drafter, or verifier.
TasksThe work each agent should perform.
ToolsCapabilities the workflow can use, such as search, document creation, or human input.
InputsFiles, Workspace, CoDraft, CoMeeting, CoSheet, text, dates, or options the run needs.
OutputText, structured data, a document, a table, or another artifact.
Review pointsPlaces where a human should confirm, revise, or approve before the run continues.
Build iteratively:
1

Name the workflow

Use a name that describes the repeatable job, such as CAPA effectiveness check.
2

Define inputs

List what a user must provide before the workflow can run.
3

Create the first agent and task

Start with the smallest useful workflow.
4

Add tools and review points

Add only the tools and human input steps needed for the workflow.
5

Run a test

Run it with a realistic Workspace or file set. Check whether the output is useful.
6

Refine and publish

Improve instructions, inputs, and outputs before publishing for reuse.

​
Draft, publish, and share

Keep an Orchestration as a draft while you are building and testing it. Publish when:
  • The inputs are clear.
  • The expected output is clear.
  • Review points are in the right places.
  • The workflow has been tested on realistic examples.
  • Other users can run it without needing hidden context.
Share with teammates who need to run or edit it. Pin workflows you use often.

​
Run an Orchestration

You can run an Orchestration from Orchestrate or ask Sofie from chat. When you click Run, Sofie may start a chat and ask for required inputs before the workflow begins. Inputs may include:
  • A Workspace.
  • One or more files.
  • A CoDraft.
  • A CoMeeting.
  • A CoSheet.
  • A date, text value, or selected option.
Review inputs before running. Most poor Orchestration results come from vague inputs, missing sources, or unclear output expectations.

​
Review artifacts from a run

When an Orchestration creates, opens, reviews, modifies, imports, or exports artifacts during a run, Sofie can show those items in an Artifacts section on the run result. Use this section to see what changed without hunting through the Workspace or chat history. The Artifacts section may include items such as:
  • CoDrafts created from templates or run output.
  • CoSheets created or updated during the workflow.
  • CoMeetings referenced by the workflow.
  • Orchestrations opened or modified by the run.
  • Other enabled artifact types in your organization.
Each artifact card shows the artifact type, title, and what happened during the run, such as Created or Modified. If a task name is available, Sofie shows which task touched the artifact. Open artifacts from the run result:
1

Open the run result

Open the completed Orchestration run from chat, the Orchestration run panel, or run history.
2

Find Artifacts

Scroll to Artifacts below the run output.
3

Open in the side panel

Use Open in side panel when available to inspect the artifact without leaving the run result.
4

Open in a new tab

Use Open in new tab when you want the full artifact page or when side-panel opening is not available for that artifact type.
5

Review what changed

Check the artifact content, source support, destination, and whether the run updated the right item.
Use the Artifacts section during review. It is the fastest way to confirm whether a run created a new CoDraft, updated a CoSheet, or touched the expected project artifact.
Opening an artifact from a run result helps you review the work. It does not mean the artifact is approved for controlled use. Check the content, sources, assumptions, and required review path before relying on it.

​
Use human input and approvals

Human review steps are useful when:
  • The next action requires SME judgment.
  • Sofie should not infer a missing fact.
  • The workflow needs a decision before continuing.
  • The next step would save, share, or change important content.
  • A reviewer must confirm source interpretation.
Human review inside Sofie helps control a workflow. It does not replace required approvals in your organization’s process.

​
Open results from chat

When an Orchestration runs from chat, Sofie can show progress, results, and the Artifacts section in the conversation. Open run artifacts from the result when available. Good follow-up prompts: 
Summarize the Orchestration result for a QA reviewer. Separate source-backed findings, assumptions, and open questions.

Turn the output into a CoDraft and include placeholders where SME confirmation is needed.

List every artifact touched by this run. For each one, show the artifact type, whether it was created or modified, which task touched it, and what I should review before using it.

​
Design better Orchestrations

For a deeper framework on inputs, source rules, task design, tests, publishing, and maintenance, see Use Orchestrations intelligently. For manual tests, saved-run baselines, validation methods, drift, run history, Memory checks, and parallel execution checks, see Test Orchestrations.
If users do not know what to provide, the workflow will fail in practice. Define required files, Workspace, date ranges, artifact types, and review roles first.
Ask for tables, structured sections, source references, assumptions, and open questions. Avoid asking for a final conclusion without requiring source checks.
Add human input before saving to a shared Workspace, creating a final document, or continuing after an ambiguous source interpretation.

​
Detailed build guides

Use Build an Orchestration with Sofie chat when you want Sofie to propose or create the Orchestration from a chat conversation. Use Build and edit an Orchestration when you need to configure inputs, agents, tasks, tools, output modes, review points, versions, and test runs directly. Use Test Orchestrations when you need a deeper testing workflow before publishing or changing a reusable workflow.