Skip to main content
Populate takes a template with blanks in it, such as a purchase deed, a power of attorney or an engagement letter, and fills the blanks from the documents already in the project. For each value it shows you where the value came from, whether the source supports it, and whether other sources disagree. Nothing is written until you have reviewed the values.

​
Prepare a template

A template is a Word document (.docx) or an editor document that marks its blanks in any of these ways: You can mix styles in the same document. Placeholders are found in body text, tables, headers and footers, and they are still recognised when Word has split one across differently formatted runs of text. Numbered citation markers like [1] are ignored.
Descriptive placeholders give better results than bare underscores. [NIE del vendedor] tells the agent what belongs there; ________ makes it work that out from the surrounding sentence.Do you have a finished document rather than a template? Anonymize turns one into the other.

​
Run it

1

Put the sources in the project

Populate reads the documents in the project: files in the project’s vault, editor documents, and documents filed from email. A run uses up to 200 sources.
2

Start Populate

Choose Workflows → Populate in the composer, or the Populate quick action on a matter, and name the template to fill.
3

Watch the stages

The workflow card shows Populating and moves through its stages.

​
Review the values

At Needs your input the card shows a running count, for example “18 of 24 filled · 2 conflicts · 4 unresolved”, and a table with a row per field: Field, Value, Source, Verification and Status.

​
Status

​
Verification

Verification is a second, independent check of each value against the passage it was taken from. Difficult cases are escalated to a stronger model. Each source shows its document and, where known, the page, so you can open it and check. You can answer up to 100 fields in one go. When you are satisfied, choose Populate to apply, or Cancel to stop without writing anything.

​
What you get

  • From a Word template: a new .docx in the project’s vault. The template itself is never modified. Each filled value carries a Word comment citing its source, and the filled document is saved as a second version on top of a copy of the template, so the version history shows exactly what Populate changed.
  • From an editor template: the values are written into the editor document, where each carries a reference to its source.
Open the result from the card with Open document or Open file.

​
Populate from email

A verified member of your organization can also ask for a populate by emailing the agent. Because nobody is watching the run, it behaves differently:
  • It does not pause for review. If the values are clean, it applies them and the agent replies with the result.
  • It stops rather than guesses. If more than a handful of fields conflict, or too much of the source material has not been indexed yet, the run is Blocked and the agent asks a member to continue from the dashboard.
  • Only verified members can start one. External senders are never given this ability. See Sender rules.

​
Troubleshooting

New uploads are parsed and indexed before they can be searched. Large scans take longest. The run continues by itself when indexing finishes. If a document cannot be indexed, upload it again or remove it from the project and start a new run.
The value is probably not in the project. Check that the relevant documents are in this project’s vault rather than in your private vault or another project. Scanned documents of poor quality are a common cause.
The template changed after it was scanned, or the run met a condition it would not guess through. Start a new run.
The person who started it and organization admins, and only if they still have access to the project. Run details are kept for seven days.