1. Business Process Modeler
  2. Features
  3. Evidence and Corrections
Feature · Evidence and Corrections

Evidence and Corrections

Verify receipts, assign follow-ups and preserve superseded execution.

OverviewEvidence to verify
Business Process Modeler · Evidence and Corrections

Evidence to verify

Evidence documents

New
IdSourceTitleAttachmentDocument dateVerified
IDD-599PM-80417No ed-653ATT-64125 OctNo
IDD-580PM-35605No ed-301ATT-23507 OctNo
IDD-886PM-42821No ed-707ATT-19110 OctNo
IDD-320PM-34660No ed-930ATT-58011 OctNo
IDD-812PM-36496No ed-394ATT-39506 OctNo
6 of 6 records
IDD-599Evidence documents · ED-36305
No
SourcePM-80417
TitleNo ed-653
AttachmentATT-641
Document date25 Oct
Example screen with sample data

What you can do

Preserve what happened before a correction

An executed model may need correction after an external effect or a review of the result. The correction workflow retains the prior revision and records a correction run with a compensating step. It creates a successor revision and an explicit compensating output, raises a verification follow-up and appends correction history. The earlier execution stays available for inspection.

For example, a simulation may have sent an output to an external service using an assumption that was later revised. The team should not silently replace the old result. The Process Owner identifies the affected revision, the Simulation Operator records the compensating action and the Evidence Steward verifies its receipt. The successor model carries the corrected path forward.

How the work is organized

  • Evidence. Documents link to a model and identify the person who verified them.
  • Follow-up. Assigned actions have a due date, status, resolution and completion date.
  • History. State transitions preserve actor, source revision, operation key and reason.

What to agree during setup

Define which receipts need an attachment and which can be verified through an external reference. Agree who can mark evidence verified and who will own follow-ups. Set a practical due-date policy for unresolved verification work. A follow-up marked Completed should include a resolution that tells the reviewer what was checked, especially when an external compensating output was involved.

Decide how a successor revision is named and linked to the prior one. The correction should explain both the original result and the compensating effect. If the external action’s outcome is uncertain, investigate it before starting another attempt. The organization should also agree when a corrected model needs fresh validation and review before it is published as the working reference.

Check the handoff on an actual case

Take a completed intake simulation whose specialist response needs correction. Locate the model revision, run, step and external receipt. Record the correction run and compensating step, then create the successor revision. Assign the verification follow-up to a named person and attach the evidence used to confirm the compensating effect.

Ask the Independent Reviewer to inspect both the original and correction traces. They should be able to find the old decision and explain why the successor differs. Complete the follow-up with a resolution after verifying the external effect. Check the state history for the reason, actor and revision. The outcome should be a usable current model and an intact account of the earlier execution.

What your team sees

  • Open verification follow-ups — Track unresolved actions, assignees and due dates.
  • My verification follow-ups — Work through actions assigned to you.
  • Evidence to verify — Find documents awaiting a recorded verification.

Follow the work through

Use correction and follow-up for the full trace and roles to rehearse the separation of duties.

What it keeps track of

Data model
Evidence documents
Source evidence documents supporting validation and execution.
Follow up actions
Assigned follow-up work raised from an automation definition.
State history
Immutable status transition history for each automation definition.
Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Operation runs
Workflow-maintained durable run records with frozen revision and input hash.
Operation steps
Numbered step trace with persisted input and output references.
Review decisions
Independent reviewer decisions recorded against an exact source revision.

Who uses it

Permissions
Evidence Steward
, Process Owner, Simulation Operator, Independent Reviewer, Admin.

Set up Business Process Modeler your way.

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

How to get started