What to change
Ask whether the repaired behaviour comes from shared code or a one-off page edit. Identify the entire template family and require a sample outside the original test page. A clean regeneration is important evidence when content is built automatically, because it reveals whether the correction survives normal publishing. Keep the task-specific improvement statement narrow until the supplier demonstrates that the shared source and deployed pages both carry the intended change.
A worked example
Illustrative example
Illustrative test: The original page and its siblings show the same intended implementation change. A supplier may manually optimise one reported article while other guides still use the old image treatment. The practice asks for the shared source correction, then reviews a sibling and a newly generated page. A normal rebuild preserves the change on all sampled routes. That evidence supports a family-wide improvement claim, whereas a screenshot of the original repaired article would establish only that one isolated edit worked.
What this means for your practice
An improvement on one article may come from a local edit rather than the shared design used by the rest of the library. Ask your supplier where the correction lives and which pages inherit it. Review another existing guide and a newly generated one from the same family. A normal rebuild should preserve the change without someone manually repeating it. Keep the claim narrow until that wider evidence exists: one faster page is useful, but it does not prove all similar pages improved. The practice should receive a clear account of the affected family, the maintained source and the public examples checked after publication.
How to check the result
The fix applies to the claimed page family and survives regeneration.
A mistake to avoid
A successful isolated page edit does not establish a reusable improvement.
Turn reading into a next step
Your action checklist
Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.
Record what you know, what is still missing and the answer you need from your team or supplier.
Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.
Further reading
These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.
Related guides
Need help with this?
Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.