Generate reviewed document batches from a master

Why use this

1. A team generating similar documents for many rows can make a single mapping error that spreads across the whole batch. Missing values are especially risky when an apparently finished document hides a blank or borrows data from another record.

2. This job could make variable mappings explicit before any draft files are produced. A visible exception report and row-to-file traceability give reviewers a practical way to detect omissions and cross-record mistakes before documents are used.

Why an agent / simpler alternative

Useful judgment

Identify variable fields, distinguish repeated static text and flag ambiguous spreadsheet-to-template mappings.

Simpler alternative

Use ordinary mail merge when the template and column mapping are already reliable.

Unsuitable when

The workflow would send, sign or publish documents or apply an unconfirmed mapping to consequential content.

Proposed inputs

1. Name

   Master document

   Owner

   Document owner

   Minimum scope

   Approved Word/Excel template copy

   Quality check

   Identify protected text and formatting

2. Name

   Row data

   Owner

   Authorized owner

   Minimum scope

   Required columns with stable row IDs

   Quality check

   Check blanks, duplicates and field types

Access and setup — proposed or unknown

Proposed minimum

1. Inspect copied templates and synthetic rows; no batch generation until a mapping is explicitly confirmed.

Compatibility unknowns

1. Current document-library behavior, formatting fidelity and exact runtime compatibility are unknown.

External actions requiring approval

1. Confirm variable mapping before generation; external uploads, document sharing, sending and signing require separate approval.

Expected deliverable and review checks

Proposed artifact

Proposed mapping, row-to-output manifest and missing-value report; future generated files remain drafts.

Critical checks

1. Preserve static clauses; verify row identity and field types; show missing values rather than guessing; prevent accidental file overwrite.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Two columns could fill the same token

   Why it matters

   A plausible match can put the wrong data everywhere

   Proposed response

   Present alternatives and request mapping confirmation.

2. Signal

   A blank carries forward the previous row's value

   Why it matters

   One person's data leaks into another document

   Proposed response

   Require independent row binding and flag empty fields.

Effort and cost — unknown

Setup work

1. Mark variables and resolve mapping ambiguity.

Ongoing review

1. Review batch exceptions and representative formatting before use.

Unknowns

1. Template complexity, output volume, formatting repair and tool costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent a template with three variables and three rows, including a missing value and two similar address columns; propose the mapping only.

Acceptance checks

1. Surface ambiguity; list missing data; preserve row IDs; generate no files before confirmation.

Stop conditions

1. Stop if the mapping is unapproved or a missing field would require invented content.

Limits

1. Successful template filling cannot establish the accuracy, legal effect or suitability of the resulting documents.