The argument
Stop Making the Assessor Excavate the Control
Evidence should emerge from the normal operation and review of a control with its meaning attached, not be reconstructed from fragments when the assessment request arrives.
The field pattern
The control ran, the team says. A ticket contains the result but not the population. A screenshot shows a green state but not the date. A chat message explains the exception but not who approved it. Three people can reconstruct the story if they are all available at the same time.
Why it matters
Evidence Archaeology creates avoidable cost and fragile assurance. A true event may be impossible to verify later, while an incomplete artifact may appear stronger than it is because the missing context lives only in memory.
Designing evidence into the workflow improves both operations and assessment. The retained record should explain what ran, against what population, when, by whom, with which exceptions, under whose review, and where remediation concluded.
Questions that expose the Wack
- What facts would a reviewer need if everyone who operated this control were unavailable?
- Does the retained artifact identify the intended and observed population?
- Where are exceptions, approvals, remediation, and retest linked to the result?
- Which evidence fields can the workflow capture automatically at execution time?