Diary design and participant recording form
Part 1 is for team design; distribute Part 2 onward to participants, digitally if needed.
Diary design and participant recording form
Part 1: diary design for evaluators
Design diary specifications
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- Evaluation question to answer
- What opportunities and barriers affect plan use?
- Recording start and end dates
- July 1–14, 2026 (fictional)
- Frequency: daily / 3 times weekly, etc.
- End of workdays
- Structured / unstructured / mixed format
- Mixed behavioral options and brief text
- Time per entry, based on pilot and burden
- About 3 minutes, checked in pilot
- Collection: post / email / dedicated form
- Restricted-access form
Reason for this entry: Time is a planning guide, not an outcome measured by length.
Writing tips and explanation for this section
About this section
Design diary specifications
Time is a planning guide, not an outcome measured by length.
View the method explanationWriting tips
Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.
Read the full fictional examplePart 2: participant daily template
Adapt prompts to questions and distribute
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- Recording date: year / month / day
- July 1, 2026 (fictional)
- Today's tasks and activities
- Discussed draft indicators with supervisor
- Insights and learning
- Noticed target definitions need alignment
- Difficulties and what did not work
- Attendance and report numbers differed
- Today's satisfaction or feelings on a 1–5 scale
- 4 on this diary's fictional scale
- Any other notes
- Ask about missing-data treatment at the next meeting
Reason for this entry: Distinguish actions from personal meaning.
Writing tips and explanation for this section
About this section
Adapt prompts to questions and distribute
Distinguish actions from personal meaning.
View the method explanationWriting tips
Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.
Read the full fictional exampleParticipant orientation checklist
Explain and confirm before distribution
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- ☑ Checked: Explained purpose and use
- ☑ Checked: Explained evaluation-only use and no identifiable publication
- ☑ Checked: Explained no right/wrong answers and welcomed honesty
- ☐ Not checked: Obtained written consent
- ☑ Checked: Confirmed reminders by email, social media, etc.
Reason for this entry: Explanations and contact modes prepared; actual consent not yet obtained.
Writing tips and explanation for this section
About this section
Explain and confirm before distribution
Explanations and contact modes prepared; actual consent not yet obtained.
View the method explanationWriting tips
Read each item and check those you have confirmed. Do not use the fictional example’s checkbox states as findings about your own program.
Read the full fictional exampleRecording-period monitoring notes for team
Review weekly and record people needing follow-up
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
Scroll horizontally to view the table
| Participant code | Completion: ○ / △ / × | Follow-up | Notes |
|---|---|---|---|
| P01 | △: entries for 8 of 10 workdays (fictional) | Voluntarily check reasons for unrecorded days | Do not convert 2 missing days to no activity |
Reason for this entry: Check reminder burden during operation.
Scroll horizontally to view the table
| Participant code | Completion: ○ / △ / × | Follow-up | Notes |
|---|---|---|---|
Writing tips and explanation for this section
About this section
Review weekly and record people needing follow-up
Check reminder burden during operation.
View the method explanationWriting tips
Keep the information in each row aligned. Scroll wide tables horizontally to see every column.
Read the full fictional exampleBefore writing, check when to use the worksheet and what completion involves
Diary design and participant recording form is a worksheet for applying Diary Method in meetings or individual work. For the overall duration of the method, use “Illustrative planning durations, not common standards: recording over days to months by purpose; design 1–2 weeks, analysis 2–4 weeks” as a reference, adjusting for scale and resources. Fill in what you know provisionally and leave unresolved matters as questions to check next.
When this worksheet is useful
- Record learning, growth and behavior-change processes over time
- Track everyday experiences, habits and changes missed by one-off studies
- Evaluate reflection in training, coaching or support
Participants and preparation
Evaluators coordinating recording/support and recorders with relevant experiences. Set numbers and duration from analytical resources and burden.
Bring the materials used for decisions, existing data, and differing stakeholder views to help complete the worksheet.
Suggested order
- 1. Part 1: diary design for evaluatorsDesign diary specifications
- 2. Part 2: participant daily templateAdapt prompts to questions and distribute
- 3. Participant orientation checklistExplain and confirm before distribution
- 4. Recording-period monitoring notes for teamReview weekly and record people needing follow-up
Signs the worksheet is ready for review
- Diary records by participant and day
- Aggregation and time-series report
- Thematic findings for open responses
Cautions for review
- Avoid excessive items. Focus on necessary information and adjust time and psychological burden through pilots and interim checks.
- Overemphasizing accuracy can make participants guarded. Keep an invitation to freely describe feelings and insights.
- Do not merely store collected diaries. Set who analyzes when and how beforehand.
Read a completed fictional example (your entries will not change)
A fictional illustration: staff briefly record plan-related actions and difficulties for 2 weeks.
Part 1: diary design for evaluators
- Evaluation question to answer
- What opportunities and barriers affect plan use?
- Recording start and end dates
- July 1–14, 2026 (fictional)
- Frequency: daily / 3 times weekly, etc.
- End of workdays
- Structured / unstructured / mixed format
- Mixed behavioral options and brief text
- Time per entry, based on pilot and burden
- About 3 minutes, checked in pilot
- Collection: post / email / dedicated form
- Restricted-access form
Reason for this entry: Time is a planning guide, not an outcome measured by length.
Part 2: participant daily template
- Recording date: year / month / day
- July 1, 2026 (fictional)
- Today's tasks and activities
- Discussed draft indicators with supervisor
- Insights and learning
- Noticed target definitions need alignment
- Difficulties and what did not work
- Attendance and report numbers differed
- Today's satisfaction or feelings on a 1–5 scale
- 4 on this diary's fictional scale
- Any other notes
- Ask about missing-data treatment at the next meeting
Reason for this entry: Distinguish actions from personal meaning.
Participant orientation checklist
- ☑ Checked: Explained purpose and use
- ☑ Checked: Explained evaluation-only use and no identifiable publication
- ☑ Checked: Explained no right/wrong answers and welcomed honesty
- ☐ Not checked: Obtained written consent
- ☑ Checked: Confirmed reminders by email, social media, etc.
Reason for this entry: Explanations and contact modes prepared; actual consent not yet obtained.
Recording-period monitoring notes for team
Scroll horizontally to view the table
| Participant code | Completion: ○ / △ / × | Follow-up | Notes |
|---|---|---|---|
| P01 | △: entries for 8 of 10 workdays (fictional) | Voluntarily check reasons for unrecorded days | Do not convert 2 missing days to no activity |
Reason for this entry: Check reminder burden during operation.
Common errors in judgment
Average blanks as satisfaction 0
How to revise: Separate unrecorded entries as missing
Reason: Non-response differs from the lowest scale value.
Require long daily open accounts
How to revise: Use brief necessary items and optional text
Reason: Burden makes sustained participation difficult.
References and checked sections
- Journals and logsBetterEvaluation
- Section consulted
- Journals and logs opening definition
- How it relates to the text
- Diaries and logs record activities and changing conditions over time.
How to cite this page
Change history
- — Checked sources for definitions and conditions and added fictional examples, judgment rationales and completed entries for every field. Revised unsupported historical or uptake claims. Reviewed procedures and cautions, adjusting fixed counts, thresholds and institutional generalizations. Preserved field positions, types and counts while revising fixed conditions and thresholds.


