Activity

What Is an Activity in M&E?

Activities are the direct work or services a program implements using its inputs. They are the actions the program takes. Examples include: delivering training, running clinics, building water points, holding community meetings, or distributing materials. Activities are distinct from inputs (what you have) and outputs (what you produce). An activity is the work itself.

Why Does the Activity-Output Distinction Matter?

Confusion between activity and output is one of the most common logframe mistakes. This matters because it affects how you plan and measure. If you write "conduct training" as an output (instead of an activity), you've skipped a logical step: the activity is conducting the training; the output might be "200 participants trained" or "training manual produced." When activities and outputs get mixed up, your results chain breaks and you can't evaluate whether you actually achieved your goal. Another pitfall: letting activities drive the program design. The common mistake is starting with "What activities can we do?" instead of "What change do we want to see?" Then designing activities to achieve that change.

How Does Activity Appear in a Logframe?

A good logframe lists activities in the middle layer. For example, the logframe might show: Input (two health workers) > Activity (conduct antenatal care clinics every Tuesday and Thursday) > Output (400 pregnant women provided with antenatal care). Some programs have dozens of activities; logframes typically show only the major ones (detail goes in a work plan or Gantt chart). It's useful to ask for each activity: "What output should this activity produce?" If you can't answer that, the activity might be off-track. Program staff often want to add more and more activities; logframes force prioritization by asking which activities are essential to reach your goal.