1. Choose a short record that answers real questions
Before deciding what to write down, ask what the notes need to help your team do. A useful record supports a practical decision: who needs a check-in, which activity to adjust, or whether a concern needs follow-up. If a field does not help with one of those tasks, leave it out.
For most small programs, a simple session-level record is a good starting point. Include the date, program or group, staff present, activities offered, and a brief participation count. Add a few notes about learning and any follow-up that is genuinely needed. You do not need a narrative about every child every time.
For example, a facilitator might write: “Thursday art group; 10 attended; participants practiced mixing colors; next time, prepare a second set of shared supplies.” That gives the team something concrete to use without identifying individual children unnecessarily. If your team is exploring a more consistent operating approach, the ONWARD Playbook operations concept can be a useful place to consider how records fit into the wider program workflow.
2. Record participation without turning it into a judgment
Attendance and participation can help staff plan staffing, supplies, and outreach. Keep the record factual and separate what you observed from what you assume. “Arrived after the activity began” is an observation; “doesn’t care about the program” is an interpretation and should not be recorded as fact.
Decide in advance what counts as attendance for your program: for example, whether you record arrival and departure times or simply mark present, absent, or excused. Use the same approach across sessions so staff can interpret the record consistently. If a participant joins partway through, note that only if it matters for planning or follow-up.
Avoid collecting extra details just because they might be interesting later. Do not add sensitive family circumstances, personal identifiers, or private conversations to a routine attendance note. If the team needs to contact a caregiver, record the agreed follow-up and who will do it, not a speculative account of the family. A program’s resources can help staff build shared routines for this kind of practical documentation.
3. Make learning notes specific and modest
A learning note should describe an activity or observable skill—not assign a label to a child. Write what participants tried, practiced, created, or explained. For example: “Small groups tested three bridge designs and compared which held the most blocks” is more useful than “the group learned engineering.” It gives the next facilitator a clear picture of what happened and where the activity might go next.
You can also note a question to revisit: “Several participants asked how a longer bridge could stay balanced.” Avoid claiming that every participant mastered a skill based on one session. A brief observation is a snapshot, not a full assessment.
Choose one or two learning prompts that match the program’s purpose. For a cooking activity, you might record a technique practiced and a step to repeat. For a reading circle, you might note the text discussed and a question that prompted conversation. Keep prompts consistent enough to compare sessions, but flexible enough to reflect the actual activity. For more ideas on shaping program practices, browse ONWARD insights.
4. Treat safety notes as a separate, careful record
Routine session notes are not the place for detailed incident accounts. If something raises a safety concern, follow your organization’s established procedures and make the required record through the appropriate channel. Keep routine notes limited to what the team needs to know to run the next session, such as “follow up with program lead before next meeting.” Do not include sensitive detail in a broadly shared activity log.
When a concern must be documented, record direct observations, relevant times, actions taken, and the person responsible for follow-up. Separate what someone reported from what staff personally observed. Use neutral language, avoid guesses, and share the information only with people who need it for their role. Decide who can access these records and how long your organization keeps them; do not leave child-specific notes in open folders, group chats, or personal devices.
5. Use a five-minute closeout, then take one next action
A short closeout works best when staff know who owns it and when it is due. Set aside a few minutes after the session while details are fresh. One person can capture the shared session summary, while any necessary child-specific follow-up goes through the organization’s approved process.
**Short checklist** • Record the date, group, staff, and participation count using your agreed format. • Note one or two activities and an observable learning moment. • Add only actionable follow-up, with an owner and a due point. • Keep sensitive or safety-related information in the appropriate restricted record. • Check that the note contains no unnecessary personal details or unsupported judgments.
The next action: choose one upcoming session and try this format on a single page. Ask the staff who use it whether each field helps them make a real decision. Remove fields that do not, clarify any confusing terms, and agree on where the record belongs and who may see it. A small, dependable habit is more useful than a long form staff avoid completing.
COMMON QUESTIONS
Frequently asked questions.
GO FURTHER
