Skip to content
VeraFrame Docs

Correcting findings

The trust report is not a gatekeeper. You are the decision-maker. For every claim the validator flagged, VeraFrame gives you three options that let you move the output toward a publishable state while keeping a record of the decisions you made.

The three actions

Approve

Use when the flagged claim is actually correct, but the validator could not find a direct match in the source material — for example, because the claim is a valid synthesis of multiple source passages, or because it refers to general knowledge that was not in the uploaded sources.

Approving a claim does not change the output. It records your decision and removes the flag. In compliance-ready deployments, approvals are captured in the audit trail together with the user who approved them.

Override

Use when the validator reported a mismatch, but you know the source is wrong, out-of-date, or incomplete. Overriding takes the position that the output is correct and the source should be updated.

An override requires a note explaining the reason. The note becomes part of the audit trail. In high-risk compliance profiles, override notes are mandatory — the workflow cannot proceed without them.

Edit

Use when the output itself is what needs to change. Rewrite the relevant passage in the editor, then click Revalidate.

A revalidation runs the verification pipeline again on the edited output. This is the only action that changes the content. Edits are also recorded in the audit trail so that reviewers can reconstruct what the original output was and what was changed.

Revalidation

After any edit you must revalidate. VeraFrame re-runs:

  • Claim-by-claim source validation against the same source material.
  • Math checks on any numeric content.
  • Completeness checks against the schema or template.
  • Source conflict detection.

The trust report updates in place. If your edit resolved the mismatch, the finding disappears. If a different claim now has a problem, a new finding appears.

The iterative loop

For complex documents it is normal to go through two or three cycles of edit → revalidate → edit → revalidate before the trust report is where you want it. Each cycle is fast — VeraFrame only re-verifies claims that could be affected by the edit — and every step is logged.

When corrections are required

Depending on your tenant’s workflow and compliance settings, some decisions may be enforced by the system:

  • If workflow is disabled, the trust report remains informational. VeraFrame stays in “create and forget” mode even when findings say needs review.
  • If workflow is enabled, policy rules and optionally validation findings can create a review case in pending_review.
  • In high_risk_ready, final output can be blocked from export or downstream integration until a reviewer decision has been made. Rejections and edits both require a written note.

See Compliance profiles for how this is configured.

What gets recorded

For every correction action, VeraFrame stores:

  • Which claim the action applied to.
  • The user who performed the action.
  • The timestamp.
  • The note (for overrides, rejects, and edits in restricted profiles).
  • The previous output text (for edits).

This record is the mechanism that lets you answer the question “who approved this, and on what basis?” months later, in an audit.