Try the everyday work. Not just the demo.
A six-point checklist for testing a shift notes app before putting real client information into it.
Published 8 September 2026. General workflow guidance, not clinical, legal or compliance advice. Follow your organisation's policies and the requirements that apply to your work.
1. Write a note on the device you actually use
Use a fictional shift. Check that the fields are readable, the keyboard does not hide the save action, and the app tells you whether the note saved. Ask what happens when the connection drops rather than assuming an app works offline.
2. Find it again
Try finding the record by person, date and worker. Ask a colleague to locate the same fictional note. A record that is easy to create but hard to find can still create work later.
3. Test different roles
With the vendor's permission and test accounts, check what a worker and an administrator can access. Ask how staff access is removed when someone leaves. Do not test with someone else's account or real participant records.
4. Make a correction
Find out whether edits record who changed the note and when, how earlier versions are handled, and what the organisation can export. Ask the supplier for written information; a polished screen alone does not establish the security of a system.
5. Follow an incident and a handover
Check how a routine note differs from an incident report. Test where follow-up appears and who receives it. If notifications are important, confirm they actually arrive and that they do not disclose more than the recipient needs.
6. Check the whole cost and the exit
Ask about staff limits, storage, exports, integrations, messaging charges, onboarding and cancellation. Confirm how you can retrieve records if you leave. Compare the total for the team you expect to have, not just the first account.
Have a correction or a question? Contact the publisher. Please do not send client or health information.
More from the reading list