Define usefulness in a small set of tasks.

We start with the actions people need to complete and the decisions a maintainer needs to make. Together we identify a useful first boundary, then review a working prototype using representative records and awkward cases.

The delivery plan covers implementation, editing, access, deployment and recovery. Language approval and specialist advice have named owners. At handover, someone other than the builder should be able to carry out a routine change using the notes. Remaining gaps and untested devices stay visible in the completion record.