# Verify a form from raw source through to the label

Keep transient trials, independent form examples and whole-workflow proof separate.

Source: https://help.smartfact.ai/manuals/labels/form-workflow-proof

Review edition: 25 October 2026

Roles: author, reviewer

A form can accept an answer correctly while producing the wrong corrected input or label. Author prepares the definition and independent expectations; Reviewer checks the exact frozen candidate before publication. A trial, a form-only example and a complete source-to-label verification provide different evidence.

## Save the complete form definition

Open **Operator forms** and the intended draft. Check every field's identifier, label, type, required status, choices and visibility conditions. Review **Permitted corrections**, including the required reason and exact fields the form may correct. Keep hidden/required combinations consistent with the intended source data.

Save the changed definition and confirm the current saved revision. Resolve a stale-save refusal before using a proof. A form is draft work until the appropriate candidate is frozen, verified and published.

## Use trials for immediate feedback

Under **Try saved revision**, enter representative sample answers and choose **Validate sample answers**. Review whether they pass or are held and inspect any proposed corrections. Check missing answers, conditional visibility and invalid types as well as a successful answer.

The trial creates no label or print intent, and its answers are not saved. Use it to investigate the saved definition, not as retained independent verification or permission for production acceptance.

## Retain independent expectations

Open **Review form examples** for form-only expected behaviour. Enter the intended outcomes from the actual requirement rather than copying the form's latest output. Save and verify the examples for the exact revision.

For the combined source workflow, open its source-review workspace. Read **Frozen workflow** so that the inherited source mapping, form, rules and layout are clear. Each source example must specify the raw source and form answers, the expected corrected input and expected label. For a blocked form, both expected corrected input and expected label must be JSON null. Do not invent successful downstream values.

The combined review accepts three to five complete entries. Include the required challenge conditions and explain **Source of expected outcomes**. Only acknowledge review after checking the whole set and the inherited workflow. Saving an expectation is different from verifying that the implementation matches it.

## Verify and inspect every result

Use **Verify saved source review** for the current saved set. Inspect expected versus actual corrected input, rule outcomes and label results. Open each offered preview/PDF proof and check the content, barcode and geometry against the independent expectation. A syntactically valid answer or passing form-only case does not prove downstream label correctness.

If the source review, draft or inherited workflow changes, obtain current evidence rather than reusing an earlier run. Keep an uncertain request's original identity and inspect retained runs before starting another verification.

## Freeze and publish the exact reviewed candidate

Use **Freeze combined release candidate** only when the workspace permits it. Review the form, source outcomes and inherited workflow, add the useful note and confirm **Freeze form candidate**. Open the resulting retained candidate and follow [verification and publication](/manuals/labels/examples-and-releases).

The candidate's independent proofs and the site's additional approval controls still apply. A frozen form candidate is not automatically live and does not qualify the printer. Operators subsequently complete the published form through [ordinary label preparation](/manuals/labels/operator-forms).