1. Form Builder Platform
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Make the review decision inspectable.

OverviewRevision review inbox
Form Builder Platform · Review and evidence

Revision review inbox

Approval conditions

New
SourceSource revisionDecisionReviewerEvidence reference
FD-10870880PendingER-695
FD-40046360PendingER-660
FD-41284940PendingER-522
FD-31766710PendingER-609
FD-30083680PendingER-996
6 of 6 records
ER-695Review decisions · RD-18995
Pending
SourceFD-10870
Source revision880
Example screen with sample data

What you can do

Make the review decision inspectable

Review Decisions record a reviewer, source revision, decision, date, reason and evidence reference against a Form Definition. Evidence Documents provide a title, attachment, document date, external reference, verification value and verifier. A reviewer can see unverified documents beside pending or rejected submitted lines on Form Submissions Review. This keeps the decision close to the exact form version and supporting material.

A review decision names the reviewer and source revision. The evidence document names a source form, attachment and verifier. Their references help a later reviewer distinguish a decision on the current schema from an earlier one and inspect the material used at that time.

How the work is organized

  • Collect the document. Link its attachment and external reference to the correct form definition.
  • Verify the source. The Evidence Verifier records the verification value and remains named on the document.
  • Decide the revision. The Independent Reviewer records Approved, Returned or Rejected with a reason and source revision.

What to agree during setup

The Independent Reviewer decides what evidence is needed for the form and when a returned revision can be reviewed again. The Evidence Verifier checks the attachment and records verification against the right source form. A verification value should reflect an actual check, not merely the presence of a file. The reviewer should record a reason for a return or rejection so the owner knows what to correct.

Agree what makes a document verified and who may see its attachment. A decision must state which revision was reviewed. If the revision changes, the earlier approval stays with the earlier version and a new decision is required.

Check the handoff on an actual case

Take one validated form revision and its supporting attachment. Ask the verifier to confirm the document and the reviewer to record a decision against that revision. Then change the draft into a successor revision and compare both decisions. An earlier approval should remain attached to the earlier source revision; it should not silently cover the new schema.

Reopen the decision after creating the successor Draft. Confirm that its source revision still names the earlier form and that the new revision awaits its own decision. Check that the document source and verifier are visible to the next reviewer.

What your team sees

  • Revision review inbox — Find Pending decisions with their source revision and reviewer.
  • Evidence to verify — Check documents marked No and identify the source form.

Follow the work through

See definition and publication and submission review for the decisions that connect this module to the next one.

What it keeps track of

Data model
Review decisions
Independent review decisions recorded against an exact source revision.
Evidence documents
Source evidence supporting submitted and reviewed form data.
Form definitions
Versioned published form schemas with conditional logic and validation rules.
People
Form owners, operators, reviewers and verifiers.

Who uses it

Permissions
Independent Reviewer
Owns the decision; Evidence Verifier checks documents.
Form Owner
Corrects returned definitions; Admin manages access.

Set up Form Builder Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started