Fill Sections from Source Documents

Starts the fill for a package's sections in one call, each section reading only the source documents mapped to it.

Overview

By the time this runs, the package already knows which forms it contains — that was settled in the previous step. What it does not have is values in the fields. This step hands each section the documents it should read, along with which of your typed notes apply to it, and starts the fill.

What comes back is confirmation that each fill has been started, not the filled result. Each section's fill carries on in the background afterwards, so the sections finish independently of each other and independently of the call. Both workflows that have this tool are told the same thing about it: start the fills, then stop — do not wait, do not poll, do not check.

The per-section pairing of documents to forms is the part that matters for accuracy. A section is given only the sources mapped to it, and the appraisal workflow's own instructions are blunt about why: pass every attachment to every section and the model gets confused and accuracy drops.

What It Does

When the Agent Chooses This Tool

Available in the appraisal-report and pre-bid workflows. The coating QA workflow does not have it.

In the pre-bid workflow there is nothing to work out. The instructions spell the call out in full: the one section, the invitation file as its source, every run whose typed text should feed it, and ordinary filling. It happens once, after the section is created.

In the appraisal workflow the instructions leave the agent three decisions:

• Which sections go in the call. A section is included when at least one of the source files mapped to it is among the uploads. On a repeat run, only sections this run brings something new to — a newly uploaded file that maps to them, new typed text, or an explicit request to rerun. A section whose inputs have not changed is deliberately left out and its previous fill stands. Sections that exist only to carry a source page through to the deliverable are left out too; there is nothing on them to fill.
• Which sources each section sees. The minimum mapped set, never everything.
• Which mode each section needs. Ordinary filling; or, when a package you already completed was taken apart into per-section sources on this run, a mode that writes only the fields designated to carry over from it; or, when that carry-over already happened on an earlier run, a mode that writes everything except those fields, so the carry-over is not overwritten. Taking a completed package apart is Split a Filled Package.

Then it stops waiting. In the appraisal workflow the agent goes straight on to placing images while the fills are still running.

Inputs and Outputs

Takes: one entry per section — the section, the source documents it should read, which of your typed notes should feed it, and the fill mode.

Returns: one result per section confirming the fill was started, with the mode used and the number of sources handed to it. No field values: those are written afterwards.

Example

An appraisal package. The uploads are the subject property's tax record, three comparable tax records, an MLS listing PDF, a mapped-comps PDF and a notes file. The sections were created a step earlier.

One call starts all of them, each with only its mapped sources:

• The main report form gets the widest set — the subject tax record, the three comparable records, the MLS listings, the map and the notes file.
• The invoice and the cover page get the notes file and the subject tax record.
• The pages that only carry a source page through into the deliverable are not in the call at all. There is nothing on them to fill; a page of the source document gets placed on them instead.

The call returns straight away. The agent moves on to placing images, and the sections finish in the background.

Limits

• The call returns when the fills have been started, not when they have finished. Values appear section by section afterwards, and nothing in the result tells you when a section is done.
• The number of sources reported back for a section can be lower than the number you selected. A source that cannot be copied for the fill is dropped, and the section is still reported as started.
• Each section's fill counts as a fill against your plan's allowance, so an N-section package uses N of them. If the allowance runs out partway through, the sections that did not get one come back as failed — the call itself had already returned successfully.
• A refill will not revisit a field a person edited by hand. Corrections are safe, but you cannot get the AI's own answer back for that field by filling again.
• Accuracy depends on the mapping being right. Sources are paired to sections by the workflow's own instructions, so a document nobody mapped to a form is never read for that form.

FAQ