Why do many work plans fail?
A work plan fails when the people who must use it cannot. It is too long, too vague, or written without field staff. It lists “community mobilization, months 1 to 12” and nothing else. Nobody knows who starts on Monday.
A good plan answers a simple question for each person: what do I do this month, who do I need, and what must happen first?
What should a work plan contain?
Each row of the plan is a task. Give every task these fields:
| Field | Example |
|---|---|
| Result or output | Output 2: 40 hygiene sessions held |
| Task | Select and train 10 community facilitators |
| Owner | Field coordinator |
| Start and end | March to April |
| Site | Districts A and B |
| Resources | Training venue, materials, transport |
| Depends on | Facilitator criteria agreed, budget released |
| Status | Not started, in progress, done, delayed |
The “depends on” field is the one most plans miss. It shows what could block each task.
How do you build it, step by step?
- Start with the logframe. Take each output and list the activities under it. The logframe is the source of truth.
- Break activities into tasks. A task should fit within about a month and have a clear finish line. “Train facilitators” is better than “capacity building”.
- Assign one owner per task. Others may help, but one person answers. Link this to your RACI matrix; see how to build one.
- Set dates backward from deadlines. Start with donor reports, distribution dates or the rainy season, then work back.
- Mark dependencies. Note which tasks cannot start before others finish.
- Add milestones. Choose five to ten key moments, such as “first training complete”.
- Check resources. Match tasks against budget, vehicles, staff time and procurement lead times.
- Review with the field team. Ask what is unrealistic and fix it.
What constraints do field plans need to show?
Field work has limits that a head-office plan can hide. Mark these on the plan:
- seasons, floods, harvest and holidays that limit access or attendance,
- security windows and movement approvals,
- procurement lead times, since a purchase may take weeks,
- staff recruitment time,
- donor report and approval dates.
If a task needs a purchase, set its date after the procurement step, not at the same time. Our article on coordinating field operations covers shared site planning.
How do you keep it short and readable?
- Show the next three months in detail and later months at a higher level.
- Use the language your field staff work in.
- Give each person a one-page view of their own tasks.
- Avoid more than 60 to 80 task rows. If you need more, split by output or by site.
- Use plain verbs: select, train, deliver, count, report.
How do you keep it alive?
A plan that is not updated becomes fiction. Review it monthly in a short team meeting:
- Mark tasks done, in progress and late.
- Ask why late tasks are late.
- Move dates and record the reason.
- Check whether delays affect results or the budget. If they do, follow your change request process.
Keep each earlier version with its date. It shows how the project changed.
What does a monthly view for a field team look like?
Give each field team a one-page view for the month. It should show:
- the tasks they own, with dates and sites,
- the resources arriving, and when,
- the tasks that depend on them, and the people waiting,
- the next reporting deadline and what data they must collect.
Review it with the team lead at the start of each month, and ask a simple question: what could stop us? Write the answers next to the tasks and decide who will act on each. This takes 30 minutes and avoids many surprises. Post the page where the team will see it, or send it in a format they can open on their own devices.
Where EMPOBase fits
EMPOBase’s Programs module includes Field Operations and Projects, so field activity planning sits next to the logframe, RACI and Stakeholders for the same project. It holds what your team enters; it does not set dates for you or detect dependencies automatically. Field reporting in EMPOBase is online, so plan for connectivity at your sites. See the field-to-results workflow or the platform page.