What does it mean to monitor your progress? Monitoring means regularly collecting and reviewing information about your initiative's activities, progress, and emerging outcomes. It helps you compare what is happening with your plans and community priorities. Monitoring can identify implementation challenges and changes that need further investigation, although it does not by itself establish what caused an outcome. A useful monitoring system can help you: Understand how the initiative operates and who it reaches Make informed decisions about activities, resources, and improvements Communicate accomplishments, challenges, and lessons learned Build community participation and support Inform funding decisions and account for the use of resources Monitoring is already part of many everyday activities. Teachers review students' work to understand learning progress. A household might compare utility use across several months. A community organization might track attendance and ask participants about their experiences. For a community initiative, monitoring provides a consistent way to document activities, accomplishments, challenges, and changes over time. The monitoring approach described here has three key parts: Clearly defined process and outcome measures A system for observing and documenting activities and changes Regular feedback and discussion to inform action This section explains process and outcome measures and how to organize an observational monitoring system. Later sections discuss ways to share feedback with coalition members and the wider community. Plan for that use from the beginning by agreeing on who needs the information and which decisions it will inform. Process measures Process measures describe how an initiative is implemented, including its activities, participation, reach, and quality of delivery. Teams may track these alongside inputs, such as funding, and outputs, such as workshops delivered or plans completed. Keeping these distinctions clear helps you avoid treating activity counts as evidence of improved community outcomes. Implementation monitoring can cover many aspects of your initiative, such as: Participation: The number of people involved, frequency of attendance, new and continuing participation, and barriers to involvement. Example: Seventeen people attended the most recent coalition meeting. Ten had attended previously, and seven were participating for the first time. Planning products: Agreed objectives, action plans, bylaws, and other documents or structures that support the initiative. Example: The coalition approved an action plan identifying priorities, responsibilities, and implementation dates. Media coverage and communication: Coverage through radio, television, print, online news, and other channels, distinguishing independent coverage from the initiative's own communications. Example: A local radio station aired three interviews about the initiative. The team recorded the dates and topics, noting that broadcasts alone do not show how many people listened or acted on the information. Financial and other resources: Grants, donations, and in-kind contributions, such as meeting space, equipment, or donated services. These are resources supporting the work rather than outcomes of the intervention. Example: A fundraising lunch generated $8,000 in gross revenue for local substance use prevention and recovery-support efforts. The team recorded event expenses separately to determine the net amount available. Services and activities delivered: Classes, workshops, publications, referrals, and other services or communications provided through the initiative. Example: Childcare providers delivered four nutrition education workshops. Records documented attendance, languages offered, and participant feedback. Community actions: Activities intended to encourage changes in programs, policies, practices, or community conditions. Example: Residents and coalition members met with local service providers to request evening appointments for people unable to attend during daytime hours. Event logs can help document these activities and resources consistently. Select measures that relate to your goals and intended decisions rather than trying to record everything. An example of an event log appears later in this section. Outcome measures Outcome measures describe changes relevant to the initiative's goals, such as improved access, changes in practices, or changes in people's experiences and well-being. New programs, policies, and practices may be intermediate outcomes when the initiative aims to change community systems. Their adoption does not automatically demonstrate improved conditions or establish that the initiative caused the change. Examples of intermediate community changes include: Changes in programs: New or adapted services that respond to community priorities. Example: A community center introduced a parenting-support program developed with local families. Later monitoring examined who could access it and whether participants found it useful. Changes in policies: Adoption or revision of rules and commitments that guide organizational or community practices. Example: Following discussions with residents and the coalition, a service agency adopted a policy requiring its appointment system to offer evening options. The team documented the policy's approval and planned to track implementation. Changes in practices: New or revised ways of carrying out work. Example: Local service providers began offering evening appointments. The team then tracked availability, use, and whether the change reduced scheduling barriers. Together, implementation and outcome measures help explain what the initiative is doing and what is changing. Interpret them alongside community feedback and information about other influences. A count of new policies, for example, becomes more useful when you also know whether they were implemented and whom they benefited. Why do you need to monitor your progress? Monitoring is useful when the information leads to discussion and decisions. Before collecting data, agree on what the team needs to understand, who will review the findings, and how often. A focused monitoring system can help in the following ways: Data can show where the initiative places its effort. For example, records might show extensive service delivery but little progress on a planned policy change. Both may be valuable; compare the pattern with the initiative's goals and community priorities to decide whether adjustments are needed. Data can help identify who is reached and where change is occurring. Is the initiative making progress in schools but encountering barriers in other settings? Who can access the activities, and whose experiences are missing? Examine differences where the information is adequate and can be reported without compromising privacy. Data can reveal which strategies are being implemented. For example, records may show that information sessions are taking place while planned peer support or service referrals have not yet started. This can prompt discussion about resources, responsibilities, and implementation barriers. Data can support learning, communication, and accountability. Staff and community partners can use findings to improve activities, explain accomplishments and challenges, invite participation, and inform funding decisions. Reports should represent the full picture rather than highlight only favorable results. How do you monitor your progress? Begin by agreeing on a manageable set of measures, clear definitions, and responsibilities for collecting and reviewing information. Decide how records will be stored, who can access them, and how summaries will be used. The following steps describe a practical system built around event logs. Collect data by completing event logs and other forms regularly Event logs are structured records of important activities and developments. They can document actions taken by the initiative and new or modified programs, policies, or practices relevant to its goals. Record the initiative's role and supporting evidence without assuming that every related change resulted from its work. An event log might include: The date of the event, using a consistent format A description of the event, including: How it relates to the initiative's goals and why it matters What happened, what evidence supports the record, and what follow-up is needed Relevant details, including: The roles or groups involved, avoiding unnecessary identifying information Which organizations contributed staff time, funding, space, or other resources The community setting, strategy, or objective addressed Whether this was a new activity, a repeated activity, or an update to an earlier record For example, consider a hypothetical youth well-being coalition working with students to expand their role in school decisions. A member records: "On September 15, student representatives and coalition members met with the school principal to propose a student-led action committee. The principal approved the committee's formation, and students agreed to develop its membership process and priorities. The approval creates an opportunity for student leadership; the committee's launch and influence on decisions will be tracked separately." The event log records the date, participants' roles, purpose, decision, and next steps. Meeting notes provide supporting documentation. Separating approval from implementation helps the coalition avoid counting a planned change as a completed activity. Involve staff and community members in completing the logs People directly involved in an activity are often well placed to document it. Assign responsibility for each record so that information is not missed or counted more than once. Agree on a prompt reporting schedule, such as within a week when practical. Provide a simple template, examples, and accessible ways to contribute, then send completed records to the person or team coordinating monitoring. Gather information carefully and accurately The time required depends on the initiative's size, activity level, and reporting needs. Try the system on a small scale to estimate the workload and simplify unnecessary steps. Train contributors to use consistent definitions, distinguish observations from interpretations, and identify information they have not yet confirmed. Review records for missing details, duplicate entries, and errors. Organize the data so that it can be used Store records in a format the team can maintain, such as a shared spreadsheet, database, or organized paper system. Use consistent categories and a unique identifier for each event. Keep sensitive information in appropriately restricted records, and document corrections or changes in definitions. Clear organization makes it easier to compare reporting periods and answer questions without repeatedly reconstructing what happened. Summarize the data and share findings with the group Prepare regular summaries that connect activities and observed changes with the initiative's goals. Use counts, brief descriptions, or charts as appropriate, and explain gaps or limitations. Distinguish new developments from repeated activities and avoid treating every event as equally important. Discuss findings with staff and community partners, agree on any action needed, and identify who will follow up and when. In Summary Monitoring helps a community initiative understand its implementation, track progress, and respond to emerging information. A useful system combines clear measures, consistent records, and regular discussion of findings. Event logs can document activities and community changes, while surveys, interviews, and other evaluation methods help explain experiences and outcomes. Use what you learn to guide action, and keep the monitoring process practical enough to sustain. Contributor Aimee Whitman Eric Wadud Resources Online Resources Data Collection for Program Evaluation is a toolkit provided by the Northwest Center for Public Health Practice. It offers information, templates, and resources to assist in planning your own data collection for program evaluation. Evaluating Your Community-Based Program [pdf] is a handbook designed by the American Academy of Pediatrics and includes extensive material on gathering information. The CDC offers an extensive publication about how to Gather Data. An extensive table is included in the PDF that provides the advantages and disadvantages of various data collection methods. The Magenta Book - Guidance for Evaluation provides an in-depth look at evaluation. Part A is designed for policy makers. It sets out what evaluation is, and what the benefits of good evaluation are. It explains in simple terms the requirements for good evaluation, and some straightforward steps that policy makers can take to make a good evaluation of their intervention more feasible. Part B is more technical, and is aimed at analysts and interested policy makers. It discusses in more detail the key steps to follow when planning and undertaking an evaluation and how to answer evaluation research questions using different evaluation research designs. It also discusses approaches to the interpretation and assimilation of evaluation evidence. McCormick Foundation Evaluation Guide is an extensive guide to planning an organization’s evaluation, with several chapters specifically dedicated to gathering information and using it to improve the organization. The Performance Measurement for Public Health Policy (PDF) was developed by APHA and the Public Health Foundation to help health departments and their partners assess and improve the performance of their policy activities; this tool is the first to focus explicitly on performance measurement for public health policy. The first section of the tool gives a brief overview of the role of health departments in public health policy, followed by an introduction to performance measurement within the context of performance management. It also includes a framework on page 5 for conceptualizing the goals and activities of policy work in a health department. The second section of the tool consists of tables with examples of activities that a health department might engage in and sample measures and outcomes for these activities. The final section of the tool provides three examples of how a health department might apply performance measurement and the sample measures to assess its policy activities. Print Resources Fawcett, S., Paine, A., Francisco, V., Schultz, J., Richter, K., Lewis, R., Williams, E, Harris, K., Berkley, J., Fisher, J., & Lopez, C. (1994). Work group evaluation handbook: evaluating and supporting community initiatives for health and development. Lawrence, KS: Work Group on Health Promotion and Community Development, University of Kansas.
