Tracker delivery notes
Designed example · synthetic data. This is a model delivery note, not a working demo or recorded interaction test.
Reviewable version
Expected fields: text task ID, title, owner, due date, status and notes. Expected actions: add, edit, filter and save/reopen. The sample includes a blocker and an unassigned owner so both remain visible.
Storage and access
Assumed prototype route: browser-local storage. Edits would be saved only in that browser profile; another browser or teammate would not automatically see them. Shared persistence and visitor permissions remain to be configured and checked. No deployment or access grant is represented by this example.
Check record to complete during an actual build
| Action | Required observation | Example status |
|---|---|---|
| Add | P04 appears without losing P01–P03 | Not run |
| Edit | P03 owner and due date update | Not run |
| Filter | Blocked shows P02; clearing filter restores all tasks | Not run |
| Save/reopen | Edited values survive the stated save method | Not run |
| Sharing | Another authorized browser/person sees the expected data | Not configured |
Next decision
Inspect a built version before choosing shared storage, audience access and deployment. A saved Sites version is for review; a deployment URL is production.