01 / Section
A gap is part of the evidence
A workflow record is shaped by what was collected and what was not. If a batch begins after intake, ends before approval, or contains only some of the related activity, the description should say so. The gap is not a minor footnote; it limits the claim you can responsibly make.
For example, “the captured work shows information being copied from an intake record into a review document” is stronger than “the intake process is manual.” The first statement stays close to the recorded evidence. The second may be true, but the collection does not establish whether other paths, tools, or exceptions exist.
- Name the captured start and end points.
- State which systems, records, or stages were absent.
- Avoid using an incomplete sequence as the full workflow.
02 / Section
Use batches to compare attempts, not to fill in blanks
A single captured batch can show one attempt at a business outcome. Comparing distinct batches can reveal recurring workflow patterns, such as repeated handoffs, similar document preparation, or the same kind of review step. That comparison can make a description more useful without pretending that every instance was collected.
Describe the pattern at the level the batches support. If several attempts include a handoff from one record to another, say that the handoff recurs in the captured attempts. Do not add an unrecorded approval, exception, or business rule simply because it would make the process diagram look complete.
- Use “in the captured attempts” when the collection is partial.
- Treat recurring steps as patterns in the evidence, not proof of universal practice.
- Keep unusual or one-off steps visible rather than smoothing them into a standard path.
03 / Section
Keep discovery signals separate from workflow proof
App and site sequences can help identify where to investigate. A repeated sequence may point to a likely research, preparation, or coordination activity. It does not by itself prove the purpose of each action or establish that the sequence belongs to the same business outcome.
Use these sequences as discovery signals alongside the stronger evidence in captured batches. A citation shows where a statement came from; it does not make the statement certain. When the meaning is inferred, label it as an interpretation and preserve the underlying sequence for review.
- Call a sequence a discovery signal when its business purpose is not recorded.
- Link interpretations to the relevant evidence without presenting them as confirmed facts.
- Do not convert navigation or app usage into a claim about time, effort, or performance.
04 / Section
Write the next version with explicit assumptions
A useful workflow description can include a planning view, but planning assumptions must remain distinct from recorded evidence. For instance, an operations team may plan to inspect the missing approval stage, collect a complete example, or ask process owners whether an exception path exists. Those are sensible next steps, not facts about what already happened.
This discipline makes descriptions easier to revise. When new material arrives, the team can update the evidence, retain or reject the interpretation, and change the plan without having to untangle conclusions that were presented as certain. The result is a workflow account that is specific enough to guide investigation and careful enough to support responsible decisions.
- Label each statement as recorded evidence, interpretation, or planning assumption.
- Use collection gaps to define the next investigation step.
- Revise the workflow description when new evidence changes its boundaries.