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

# Fill templates progressively

> Use Sofie and the fill-progress rail to complete reusable templates over multiple sessions.

Progressive template filling lets you turn a template into a live draft, fill what is known now, leave the rest open, and return later without losing field status.

Use it for work that develops over time, such as deviation investigations, CAPA plans, validation protocols, audit responses, meeting follow-up packets, and technical transfer summaries.

<Note>
  A progressive template draft is still a draft. Review Sofie's suggestions, confirm values, and complete required process review before using the document in controlled work.
</Note>

## Start a progressive draft

<Steps>
  <Step title="Open Templates">
    Go to **Create** and choose **Templates**.
  </Step>

  <Step title="Find the right template">
    Use **All Templates**, **My Templates**, **Pinned**, **Organization**, category filters, search, grid view, or list view.
  </Step>

  <Step title="Choose Use Template">
    Sofie starts a fill conversation and opens a draft CoDraft from the template.
  </Step>

  <Step title="Add source context">
    Add the Workspace, files, CoMeeting, CoSheet, or existing CoDraft that Sofie should use.
  </Step>

  <Step title="Let Sofie fill what is supported">
    Sofie can draft values from the context you provide. Missing or uncertain fields stay open for review.
  </Step>
</Steps>

Sofie may ask for one section at a time instead of asking for every field at once. That is useful when different teammates, files, or lab results become available at different stages.

## Use the fill-progress rail

In a progressive draft, the CoDraft editor shows a **Fill progress** rail.

The rail helps you see:

| Area             | What it shows                                           |
| ---------------- | ------------------------------------------------------- |
| Required fields  | Fields that must be filled before finalizing.           |
| Optional fields  | Fields that can improve the draft but are not required. |
| Progress count   | How many required fields are filled.                    |
| Suggested values | Values Sofie drafted and you still need to confirm.     |
| Missing fields   | Fields that still need input or a source-backed answer. |

Sofie-drafted values appear as suggestions. Review them in the rail and in the document before you confirm them.

<Tip>
  Use **Confirm all** only after you have reviewed the suggested values. For life sciences work, confirm values against source records, SME input, or your team's required review process.
</Tip>

## Fill fields yourself

Some fields can be filled directly in the rail.

Use direct fill for:

* Text values, such as a deviation ID or product name.
* Numbers, such as batch count or target quantity.
* Dates and date-time values.
* Yes or no fields.
* Choice fields.

Click the field, enter the value, and click **Save**.

For richer fields, the rail may show **Fill via Sofie in chat**. Use chat when the field needs structured content, repeated rows, references, long narrative text, or source synthesis.

## Continue with Sofie

Use **Continue with Sofie** when you want Sofie to keep filling the draft.

Good follow-up prompts:

```text theme={null}
Continue filling this template. Use the Workspace and only fill fields that are supported by the attached records. Ask for the next missing section before drafting conclusions.
```

```text theme={null}
Review the remaining required fields. For each one, tell me whether you can fill it from the sources, need SME input, or need a missing record.
```

```text theme={null}
Fill the evidence reviewed section from the batch record and CoMeeting. Keep unsupported impact and root cause language as open questions.
```

When Sofie suggests values, review the rail, confirm the values you accept, and revise anything that is incomplete or unsupported.

## Resume later

Progressive drafts can span multiple sessions.

To resume:

<Steps>
  <Step title="Open Templates">
    Go to **Create** and choose **Templates**.
  </Step>

  <Step title="Find Drafts in progress">
    Use the **Drafts in progress** section to see active template drafts.
  </Step>

  <Step title="Click Continue">
    Sofie opens the related fill conversation when one exists. Otherwise, Sofie opens the draft document.
  </Step>

  <Step title="Refresh status if needed">
    Use the refresh control in **Fill progress** if another teammate changed fields while you were away.
  </Step>
</Steps>

Before asking Sofie to continue, name any new context that arrived since the last session.

```text theme={null}
Resume this template draft. Since the last session, we added the updated LIMS export and QA triage notes. Recheck field status, then fill only the next source-supported section.
```

## Finalize the draft

Finalize when all active required fields are filled and Sofie-drafted suggestions are confirmed.

You can finalize from:

* **Drafts in progress** on the Templates page.
* **Finalize document** in the **Fill progress** rail.
* Chat, after Sofie confirms the draft is ready.

Finalizing collapses the fillable fields into the finished CoDraft content. The document keeps the same CoDraft location.

<Warning>
  Do not finalize to bypass review. If a required field is missing, a suggested value is unconfirmed, or an unsupported conclusion remains, keep the draft open.
</Warning>

## Reopen a finalized draft

If you finalize too early, open the CoDraft and use **Reopen draft** in the template lineage banner.

Reopening restores the pre-finalize fillable draft state so you can update fields, confirm values, and finalize again.

Use reopen for correction work, not for routine editing. If the document is already complete and only needs wording changes, edit the CoDraft normally.

## What to ask Sofie

<Accordion title="Ask Sofie to fill conservatively">
  ```text theme={null}
  Fill this template progressively. Use only source-supported values. Mark AI-filled values for my review. Do not infer root cause, product impact, approval status, or effectiveness conclusions without explicit support.
  ```
</Accordion>

<Accordion title="Ask Sofie for missing inputs">
  ```text theme={null}
  Review the remaining required fields and ask for the next logical section only. Include the likely source record or SME owner for each missing value.
  ```
</Accordion>

<Accordion title="Ask Sofie to prepare for finalization">
  ```text theme={null}
  Before finalizing, list every required field, whether it is confirmed, the source support used, and any fields that still need SME or QA review.
  ```
</Accordion>

## Related guides

<Columns cols={2}>
  <Card title="Templates" icon="layout-template" href="/templates/templates">
    Find, use, duplicate, pin, share, publish, and maintain templates.
  </Card>

  <Card title="Templates and placeholders" icon="file-text" href="/codraft/templates-and-placeholders">
    Design CoDraft templates with clear fields, instructions, and review habits.
  </Card>
</Columns>