Work Plan: What It Is and What to Include

What Is a Work Plan?

A work plan is the document that turns a program's design into a schedule of activities for a set period, usually one year. It says what will be done, when, by whom, with what budget, and toward which results and targets. The program team or implementing partner writes it, and the funder, government counterpart or steering committee typically approves it before activities and spending begin.

Most funded programs submit an annual work plan (AWP), sometimes called an annual work plan and budget (AWPB). It sits between the logframe, which says what the program is meant to achieve, and day-to-day task planning, which says who does what this week. Evaluations also have work plans, which usually appear inside the inception report and cover the evaluation team's tasks and dates rather than a program's activities.

Why It Matters

The design documents tell you what the program is for. They rarely tell you what to do in March. The work plan is where intentions become dated tasks with owners and money attached, and it is the document most staff consult during the year.

It is also an agreement. IFAD's guidelines describe the approved plan as a commitment by management and implementing agencies to carry out a set of activities and reach certain targets, and as the funders' approval to spend the money set out in the annual budget. In UNDP's practice the signed annual work plan is a legal agreement between UNDP and the implementing partner for activities in a given calendar year. UNFPA goes further: no funds can be committed to an implementing partner before a workplan is signed, and the workplan is the only mechanism for budgeting and releasing program funds.

Finally, the work plan is what monitoring compares against. Without a dated plan, "behind schedule" and "underspent" have no meaning.

What Does a Work Plan Include?

An annual work plan typically covers these elements:

1. Results and Targets for the Period. The outputs and outcomes the program will deliver this year, with the annual target for each indicator. Targets come from the logframe or results framework, adjusted for what is realistic given progress so far. See Target Setting.

2. Activities Linked to Each Result. Every activity sits under the output it contributes to. An activity that cannot be tied to a result is a candidate for removal, and a result with no activities will not be delivered.

3. Timeline. Start and end dates by month or quarter, usually shown as a Gantt-style chart. Mark dependencies, such as procurement that must finish before training begins.

4. Responsible Person or Partner. One named owner per activity, plus the implementing partner or unit where work is shared.

5. Budget per Activity. The cost of each activity, rolled up by output, cost category and funder. IFAD's guidelines ask for the consolidated budget by component, by category and by financier. See M&E Budget for costing monitoring and evaluation work.

6. Inputs and Procurement. Staff time, equipment, vehicles, consultants and supplies, with a procurement schedule for large purchases, because delivery dates often decide activity dates.

7. M&E and Reporting Activities. Data collection rounds, reviews, evaluations, learning events and report deadlines belong in the plan with dates, owners and budget like any other activity. They fall behind when they live in a separate document. See MEL Plans.

8. Risks and Assumptions. The main threats to the plan this year (seasonal access, approval delays, security, staff turnover) and what the team will do about each. See Risks and Assumptions.

9. Milestones. The checkpoints that show the plan is on track, such as a sub-grant signed, baseline complete or first cohort enrolled. See Milestone.

Many funders also want a short narrative: progress to date, the focus for the coming year, and a justification for any change from the original design. IFAD's guidelines suggest 2 to 4 pages on performance to date and 4 to 8 pages on strategy and focus, with the detailed work plan tables in an annex.

Example Outline

An annual work plan for a mid-sized program might run 15 to 30 pages plus annexes:

1. Introduction: program summary and how this plan was prepared (1 to 2 pages)
2. Progress and performance to date: results achieved, spending, lessons (2 to 4 pages)
3. Constraints and actions required: what must be fixed this year, and by whom (1 page)
4. Strategy and focus for the year, by output or component (4 to 8 pages)
5. Results and targets for the year (1 to 2 pages)
6. Consolidated budget by output, category and funder (2 pages)
7. Risks, assumptions and milestones (1 to 2 pages)

Annexes: detailed activity plan with budget lines, logframe, procurement plan, staff or partner plan, M&E calendar.

A small sample of the activity schedule (Annex 1 in the outline above), for a made-up youth skills program:

Work Plan vs. Logframe vs. MEL Plan

The three documents are often written from each other and are easy to blur.

The work plan draws its results and targets from the logframe, and it should schedule the data collection and reviews described in the MEL plan. See Logframe and MEL Plans.

Common Mistakes

Activities copied from the proposal. Planning "10 trainings in year 3" because the design says so, without asking whether this is still the best way to reach the output. Review progress and context before each annual plan.

No link to results. A list of activities with no outputs or targets above it cannot be monitored for effect. Group activities under the result they serve.

Plans that ignore capacity. Setting targets the team and partners cannot deliver leads to late approvals, rolled-over budgets and a hard annual review. Check each quarter's load against who is available.

M&E left out. Baselines, data reviews and evaluations that are missing from the work plan are the ones that get skipped or underfunded.

A plan nobody updates. A work plan that is never compared with progress becomes a filing requirement. Review it at least quarterly and record changes with the reasons.

Variation by Program Size and Funder

Small grants and single-partner projects. A one- to three-page table with activity, dates, owner and cost is often enough. Keep the structure of the logframe but not the narrative.

Large multi-component programs. Each implementing partner or component usually prepares its own plan, and the program office consolidates them. IFAD's guidelines describe workshops where partners compare plans so activities are synchronized, followed by consolidation, steering committee review and funder approval.

UN agencies and government counterparts. The annual work plan is a formal, signed document. In UNDP practice, plans for later years can be less detailed at the start and must be completed in detail before signature. UNFPA workplans can cover several years, but funds are committed only as the agreement and available resources allow.

U.S. government awards. The award or agreement sets what must be submitted. USAID's ADS 201 says the COR or AOR is responsible for approving implementation or work plans, and an activity MEL plan must include at least one performance indicator for each activity-level outcome, with baselines and annual targets. Always confirm the exact work plan requirement in the award document.

Evaluation work plans. These list evaluation tasks, dates and responsibilities, and are agreed with the client in the inception report.

In every case the test is the same: could a new staff member read the plan and tell what must happen this quarter, who does it, and what it costs?