What is the difference?
People use “program” and “project” loosely, and donors do not all use them the same way. For planning inside your own organization, a simple split works well.
| Project | Program | |
|---|---|---|
| Time | Has a start and end date | Runs for years, often with no fixed end |
| Funding | A grant or a set of grants | Several grants over time |
| Goal | Specific results, set in an agreement | A broader change in a sector or area |
| Lead | Project manager | Program manager or head of programs |
| Example | A 24-month clean water project in two districts | A water, sanitation and hygiene program in a region |
A project ends and is closed. A program continues as projects begin and end under it.
Why does the structure matter?
Without it, every project is its own island. Each has its own plan, indicators and reports, and nobody sees what the organization achieves in total. A program level lets you:
- share technical staff and approaches across projects,
- bridge funding gaps when one grant ends before the next starts,
- report to donors and boards on results at the level that matters to them,
- use the same indicators across related projects.
How do you decide what goes together?
Ask three questions about each project:
- Does it aim at the same change as other projects? Several projects that all try to reduce child malnutrition belong together.
- Does it use the same technical team or method? Shared expertise is a good reason to group.
- Does it serve the same population or area? Work in one district often needs coordination.
Do not group by donor. A donor may fund projects in five sectors, and a program built around the donor tells you nothing about your own strategy. Track donors as a separate view, which also helps when one project has several donors.
What does a simple structure look like?
Keep it to three levels:
- Organization with a strategy.
- Programs, each with a goal, a lead and a small set of shared indicators.
- Projects, each with a charter, budget, work plan and team.
Add a fourth level only if you must. Sub-programs and “portfolios of portfolios” are hard to explain and harder to maintain.
For each program, write a one-page description: the goal, the population, the main approaches, the projects now under it, and who leads.
What should the program lead do?
The program lead is not a super project manager. Their job is to:
- keep projects aligned with the program goal,
- review indicators and results across projects each quarter,
- spot gaps and overlaps, for example two projects targeting the same households,
- plan the next grants so that work does not stop,
- support project managers who are stuck.
Project managers still own day-to-day delivery, budget and the donor relationship for their grant. A project charter makes the split clear.
What mistakes should you avoid?
Three mistakes are common when NGOs set up programs.
- Programs that are only folders. If a program has no goal, no lead and no shared indicators, it is just a label. Give each program a purpose or drop it.
- Programs built around one donor. When the donor leaves, the program structure collapses. Build around the change you want to see.
- Too many programs. A small NGO with eight programs and ten staff cannot manage them. Three or four is often enough.
Review the structure once a year, when you plan your strategy. Merge programs that overlap, close ones with no active projects, and start new ones only when you have a goal and a lead.
Where EMPOBase fits
EMPOBase’s Programs module has records for Programs, Projects and Donors, so you can organize your work by program and project. Project planning tools such as the Project Charter, RACI, Stakeholders and Closure Checklist sit alongside them. The program level is for organizing and viewing; your team still decides what belongs together, and the software does not merge budgets across donors for you. See the platform page for more.