Acceptance charter in one page
A concise structure for the promise, boundary, proof, authority, and timing of UAT.
Open the note →Field desk · Library
Library
A curated UAT inventory organised around the work: plan, design, execute, govern, prove, and decide.
Entry criteria that protect evidence
Six controls that prevent a nominal start from becoming an unreliable run.
Open the note →Cases that survive contact with reality
Move from interface steps to user intent, observable outcomes, and consequence.
Open the note →Four questions for case review
Test whether a case is recognisable, falsifiable, consequential, and self-evidencing.
Open the note →A shared vocabulary for outcomes
Keep pass, fail, blocked, and not run distinct so reporting remains credible.
Open the note →The daily UAT pulse
Report priority progress, decision blockers, evidence debt, and recovery forecast.
Open the note →Severity is not priority
Separate business consequence from delivery sequence and use both deliberately.
Open the note →The defect council
A triage rhythm that produces treatment, ownership, and visible exposure.
Open the note →Evidence without excess data
Use synthetic records, purposeful crops, source redaction, and bounded retention.
Open the note →The evidence ledger
Index decision proof and make gaps visible before the release room.
Open the note →Conditional approval with teeth
Tie every condition to a defined exposure, safeguard, owner, trigger, and limit.
Open the note →The release argument
Assemble scope, coverage, quality, operational readiness, and exposure coherently.
Open the note →