On this page
Treat confidence as a review priority
High confidence can help prioritize review but does not prove correctness. Similar values can still map to the wrong field.
Inspect low-confidence and required fields first, then confirm high-confidence suggestions in context.
Compare each suggestion with its source
Use the displayed source label to trace why a value was proposed and compare it with the authoritative record.
If evidence is missing or ambiguous, mark the field unresolved rather than confirming it.
Respect field type and allowed options
Dropdowns and radio groups accept only defined options. Checkboxes represent a choice, not arbitrary text.
Do not force a near match into an option whose meaning differs from the source.
Use the human approval gate
Edit incorrect suggestions and explicitly confirm reviewed values. Required blanks should stop export.
Optional unresolved fields may remain unchanged when no authoritative value exists.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Smart Fill PDFFrequently asked questions
Clear answers before you merge
Is 100% confidence always correct?
No. Confidence is a model signal, not a factual guarantee.
Can I change a suggestion?
Yes. Editing a value marks it confirmed.
Can unresolved fields be exported?
Optional unresolved fields stay unchanged; required ones block export.
Are dropdown values validated?
Yes. The final write uses the options defined by the PDF field.
