What to change
Capture the smallest useful account of what happened without including patient information. Ask the reporter for the exact public route, the action attempted, the observed result and whether the problem repeats. Include browser or device context when it helps explain the difference. A screenshot can supplement that record, but redact unnecessary details and avoid using it as a substitute for the route. This gives the supplier a concrete starting point for diagnosis.
A worked example
Illustrative example
Illustrative test: A colleague reproduces the fictional fault using only the issue record.
How to check the result
The ticket supports an independent diagnostic attempt without a live patient example.
A mistake to avoid
Collecting excessive personal context does not make a technical report more useful.
Your action checklist
Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.
Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.
Further reading
These primary sources provide additional context for the project decisions above.
Related decisions
Turn the brief into a working service
Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.