.jpg){kind=link}
- Published
- Updated
A diary reminder may help at the right moment and create avoidable burden at the wrong one. Consider how a participant receives notifications alongside their understanding of the daily task. Sending more messages does not automatically produce better data or a better experience.
Define the workflow
Distinguish protocol recording times from permitted reminder options. Discuss notification frequency, channel and privacy preferences through the appropriate process. Reminder wording should not influence the response or encourage someone to reconstruct past entries through guesses about what they might have reported.
Worked example
For example, a working participant receives three evening messages about the same task. Staff discover overlapping device notifications and coordinator messages. They review a single clear support route within approved arrangements, without arbitrarily changing the permitted recording window.
Practical checks
- Map reminders from different systems and staff together to identify unnecessary duplication.
- Consider notification timing alongside daily life and the permitted recording interval.
- Review wording to confirm that it neither suggests answers nor encourages guessing historical information.
Decision and boundaries
A good arrangement helps the person understand the task and support pathway. Unanswered reminders should not be labelled disinterest; investigate technical access and actual burden. Document the authority and scope of setting changes. Handle missing entries through the appropriate data process and refer clinical concerns separately to the investigator.
Frequently asked questions
- Will increasing the number of reminders solve the problem?
- Understand the cause first. Overlapping messages can increase burden, and a missing entry does not by itself prove forgetfulness.
- Can a coordinator help with the content of an answer?
- Explaining how to complete a task differs from suggesting the participant’s response. Support should avoid leading the answer.