Capture the moment, not a reconstruction
A program report is often written months after the work it describes. By then, a team may know how many sessions happened but struggle to explain what changed, which activities were adapted, or why attendance fell in a particular week. Those details are easiest to preserve while the work is still fresh.
Decide what each activity needs to leave behind. For a workshop, that might be an attendance count, a short facilitator note, and one observation about what participants needed. Keep the record short enough that staff can complete it as part of closing the session, rather than as a separate reporting project.
Give each record a purpose
Not everything that can be collected should be collected. Start with the question the program needs to answer: who was reached, what was delivered, what changed, or what the team learned. Then choose the smallest useful record for that question.
A count may show reach, while a consented participant reflection may help explain experience. Label the source and reporting period, and keep access appropriate to the sensitivity of the information. This makes the evidence more useful without turning program delivery into paperwork.
Review while there is still time to respond
Build a short evidence check into the regular program rhythm. Ask which activities have records, which measures are missing, and whether the current evidence still answers the questions the team agreed to track.
When a gap appears, give it an owner and a date. Sometimes the right response is to recover a missing record; sometimes it is to explain honestly that the information was not captured. Either is better than finding the gap for the first time when a funder report is due.