← All articles

Workflow evidence

Collection Gaps Should Narrow the Workflow Claim

When a captured batch leaves steps unseen, describe what the evidence supports—not a complete process. Treat missing coverage as a limit on the claim, not proof that work did or did not happen.

Text-free Shadow evidence-map composition with separated evidence paths and open gaps, in ink black, warm cream, mustard gold, and muted sage.

A gap changes what you can say

A workflow description is only as strong as the evidence behind it. If a captured batch shows someone preparing information and later recording an outcome, but not the intervening steps, describe those observed parts. Do not fill the gap with a plausible sequence and present it as fact.

Missing evidence is not evidence that a step was skipped, unnecessary, or completed elsewhere. It means the available record does not establish what happened in that interval.

Separate the record from the interpretation

Start with the recorded evidence: the captured actions, their order, and the outcome they are linked to. Then state your interpretation separately—for example, that the actions may form part of a recurring handoff. Make clear when that interpretation depends on incomplete coverage.

A citation lets a reviewer trace a statement back to its source. It establishes provenance, not certainty. A cited action can be clear while its purpose, significance, or place in the wider workflow remains uncertain.

Use distinct attempts to test a pattern

One attempt can show what happened in that attempt. It cannot, by itself, establish a standard workflow. Compare separate attempts linked to business outcomes and look for steps that recur, steps that differ, and gaps that appear in the evidence.

If attempts show a similar sequence, describe it as a recurring pattern in the captured evidence—not as a universal procedure. If the records differ, preserve the differences rather than forcing them into one tidy path.

Keep discovery signals in their lane

App and site sequences can help identify where to investigate further. They are discovery signals, not proof of a business task or its purpose. A sequence of visits alone does not establish that someone completed a particular workflow.

Keep those signals separate from evidence-linked attempts. If a proposed process map uses them to suggest a missing step, label that step as a question to verify, not a recorded fact.

Make the next description useful and honest

When coverage is incomplete, write the narrowest useful account: what is directly recorded, what pattern appears across distinct attempts, and what remains unknown. Then identify the specific missing evidence that would resolve the question.

Planning assumptions can still help teams decide what to examine next, but label them as assumptions. This lets operations leaders plan without confusing a possible workflow with one the evidence has established.