End-to-end workflow evaluation
Decide whether the complete workflow reaches the intended business state
Component tests pass while users still report unfinished or incorrect work. The decision is how to decide whether the complete workflow reaches the intended business state. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to workflow owners and release engineers. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.
The release evidence relationship
- Workflow state diagrams
Establish the basis for workflow handoff.
- Terminal state
Inspect the record that defines completion.
- End-to-end evidence trail
Retain the scoped finding and its unresolved dependencies.
Decision
Frame the decision around workflow handoff
Questions and the evidence they need
- Workflow handoff
- Inspect workflow state diagrams for the relevant constraint or observation.
- Terminal state
- Inspect handoff records for the relevant constraint or observation.
- Reconciliation
- Inspect tool events for the relevant constraint or observation.
The decision is how to decide whether the complete workflow reaches the intended business state. This is relevant to workflow owners and release engineers when component tests pass while users still report unfinished or incorrect work. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.
The specific failure hypothesis is that a persuasive final answer claims success although the downstream update never occurred. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.
Mechanism
Completion belongs to the system of record
Relationships within release evidence
- Workflow handoff
- Connect approval to the downstream operation.
- Terminal state
- Inspect the record that defines completion.
- Reconciliation
- Assign inconsistent intermediate states to an owner.
What this specialty examines
Workflow evaluation needs a terminal-state definition that exists outside the conversation. A statement that a return was created is weaker evidence than the corresponding authorised record and its status. Identify which system owns that state and how the test observes it.
The review should follow cases from request through tool action, approval, persistence and final confirmation. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.
The tradeoff to make explicit
For this decision, full integration tests provide realism but make fault localization more demanding. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.
Preparation
Connect the working inputs to the boundary being examined
Evidence packet for workflow handoff
Illustrative working format
- Workflow state diagrams
- Define completion using the authoritative state beyond the conversation.
- Handoff records
- Locate transfer of responsibility, permitted authority, and unfinished-work ownership.
- Tool events
- Retain the observed conditions and distinguish gaps from contrary evidence.
- Final business-system states
- Define completion using the authoritative state beyond the conversation.
Start with workflow state diagrams, handoff records, tool events and final business-system states. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.
The scope also needs the release owner, agreed expectations for a representative task case, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which a persuasive final answer claims success although the downstream update never occurred from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.
How the work proceeds
Carry workflow handoff through to an accountable finding
From the scoped material to a decision record
- Workflow state diagrams
Separate hard constraints from graded preferences.
- Terminal state
Apply the scoped check to reconciliation.
- End-to-end evidence trail
Record the evidence, open dependencies, and the owner’s next decision.
Prepare the evaluation cases
Work with workflow owners and release engineers to assemble workflow state diagrams, handoff records, tool events and final business-system states. Select a normal task, a consequential exception and a case with insufficient information. Identify the relevant requirement and expected result for each, then mark which outcomes need human adjudication. The preparation output is a case packet that separates blocking behaviour from graded quality preferences before any comparison is run.
Run and review the comparisons
Map intermediate handoffs where partial completion can occur. An approval, a warehouse update and a customer confirmation may each succeed separately while the overall workflow remains inconsistent. Cases should expose these combinations and assign ownership of reconciliation instead of merely scoring the final response.
Choose the release or evaluation change
Use the reviewed cases to produce an end-to-end evidence trail linking intermediate actions to verified terminal states. Distinguish a product defect from a missing test, an ambiguous requirement or an unreliable measuring method. For each, name the proposed correction and the case that would check it. The release owner can then decide whether to change the implementation, improve coverage or restrict the intended use while a specific gap remains.
Indicative artefact
Make the end-to-end evidence trail usable by its owner
End-to-end evidence trail
Illustrative working format
- End-to-end evidence trail
- Link observations and counterevidence to the case, configuration, and conclusion limit.
- Intermediate actions to verified terminal states
- Name the missing evidence, responsible owner, and condition for revisiting the decision.
- Terminal state evidence
- Link observations and counterevidence to the case, configuration, and conclusion limit.
A useful decision artefact is an end-to-end evidence trail linking intermediate actions to verified terminal states. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.
Illustrative scenario
Examine reconciliation through a constructed exception
A constructed case and its decision paths
Illustrative scenario
- Workflow handoff
A return is announced before its warehouse authorisation exists.
- Terminal state
Compare the message with the warehouse record and order identifier.
- Reconciliation
Locate a failed write or premature confirmation before claiming completion.
Consider a fictional situation: a returns assistant approves a return verbally but leaves the warehouse system without a return authorisation. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.
In the returns illustration, inspect whether the authorisation exists and refers to the right order. If the assistant’s message and warehouse state disagree, pause the completion claim. The next test should distinguish a failed write from a wrong identifier or premature confirmation.
Scope and next action
Keep the conclusion within selected task cases
Confirm fit before the next commitment
- Workflow handoff
- This review is limited to selected task cases.
- Workflow state diagrams
- The relevant owner must confirm access and the intended operating conditions.
- End-to-end evidence trail
- The customer retains the release decision.
A result applies to the recorded configuration and selected cases. It does not establish universal agent competence or authorise release. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which component tests pass while users still report unfinished or incorrect work; confirm which missing observation would change the owner’s next action.
Ways to engage
Related engagement scopes
AI Agent Evaluation Evidence Diagnostic
Find the gaps between your release decision and the evidence behind it. Start with one agent workflow and a bounded set of questions.
AI Agent Evaluation Foundation
Turn scattered tests into a repeatable release discipline. Connect the behaviours that matter to datasets, evaluation criteria and evidence your team can maintain.
AI Long-Horizon Agent Evaluation
Examine what changes when an agent keeps working. Evaluate accumulated state, recovery and goal adherence across extended tasks.
Continue exploring
Related insights and resources
Engineer the harness, not just the prompt
Define the contracts around an agent's decisions: what state it trusts, which actions can execute, how interrupted work resumes, and what evidence an operator needs to recover safely.
What would justify releasing this agent?
Replace a single pass rate with a reviewable chain of requirements, cases, observations and judgements. Distinguish task quality, control failures and uncertainty before increasing an agent's exposure.
The evidence behind the go-live decision
A working paper for leaders who need to explain why an agent workflow is ready for its next release. Includes a proposed evidence-pack structure, decision table and review agenda.