NGO Project Cycle Management (PCM): Six Phases, One Thread
Every institutional donor — the European Commission, AFD, UN agencies, most bilateral agencies — organises its funding around Project Cycle Management. The approach dates from the 1990s, borrows the logical framework from USAID's 1970s work, and is now the shared grammar of the sector. Knowing it means knowing what the donor will ask for at each stage, and when. This article walks the six phases with the practical question for each: what must exist at the end of this phase for the next one to work? It is a companion to our complete guide to project management for NGOs.
Why a cycle and not a line
The cycle closes on itself for a reason: what evaluation learns at the end of one project is supposed to feed the identification of the next. In practice this loop is the first casualty of funding pressure — the next proposal is due before the last evaluation is read. Organisations that keep the loop alive are those that write lessons where the next design team will find them, which is a documentation question before it is a methodological one.
Phase 1 — Identification
Purpose: establish that a real need exists, that the organisation is the right one to address it, and that a project is the right instrument. Tools: context and stakeholder analysis, problem tree, needs assessment, review of what other actors already do. Output: a concept note of a few pages.
The test: can you state the problem without mentioning the solution? If the concept note starts from "we will build a training centre", identification has been skipped.
Phase 2 — Formulation
Purpose: turn the idea into a fundable, implementable plan. Tools: objective tree, logical framework, activity schedule, budget by result and by donor line, risk analysis, sustainability analysis. Output: the full proposal and its annexes.
The test: does every indicator have a baseline or a plan to collect one in the first quarter? Does every budget line map to an activity? Our guide to responding to a call for proposals covers the donor-specific requirements of this phase.
Phase 3 — Financing
Purpose: secure the agreement and understand its terms. Tools: contract negotiation, review of general conditions, co-financing plan. Output: a signed funding agreement and an internal briefing that translates it into rules the team can follow.
The test: can the field finance officer say, without opening the contract, what the eligibility dates are, which procurement threshold applies, and when the first report is due? If not, the briefing has not happened. This is the moment to set the project up in your management tool — budget lines, eligibility period, reporting calendar — before the first expense.
Phase 4 — Implementation
Purpose: deliver the activities, produce the results, stay within the rules. Tools: monthly workplans, budget-versus-actual reviews, procurement plans, partner management, risk register reviews. Output: activities done, evidence filed, interim reports submitted.
The test: at any moment, can you answer three questions in under ten minutes — how much is committed against each donor line, where each indicator stands against its target, and where the supporting document for any given expense is? If any answer takes a day, implementation is running on reconstruction rather than on data.
Phase 5 — Monitoring and evaluation
Purpose: know whether the project is on track (monitoring) and whether it worked (evaluation). Tools: MEAL plan, indicator tracking with dated values, mid-term review, final evaluation against the OECD-DAC criteria (relevance, coherence, effectiveness, efficiency, impact, sustainability). Output: evaluation report and management response.
The test: is monitoring data collected by the people doing the activities, as they do them, or by a MEAL officer reconstructing it before the report? The former is a system; the latter is a heroic effort that stops when the officer leaves. Our complete MEAL guide goes into the design of such a system.
Phase 6 — Closure
Purpose: end the project cleanly for the donor, the community and the organisation. Tools: final narrative and financial reports, asset disposal plan, archiving, handover protocol, lessons-learned workshop. Output: accepted final report, final payment received, archive complete, lessons recorded.
The test: did the closure checklist start six months before the end date? Ineligible expenses, missing receipts and unspent balances are all cheaper to fix while the project is still live. Our project closure guide provides that checklist.
The thread through the cycle
What connects the six phases is not a document but a structure: the same logframe, the same budget lines, the same indicators, carried from formulation to closure without being re-created at each step. When they live in separate files — the proposal in Word, the budget in Excel, the indicators in another Excel, the receipts on a drive — every phase begins by reconciling the previous one. When they live in one place, each phase is simply the next view of the same project.
This is the design principle behind Abvius: the project is created once at the financing stage with its donors, budget lines and eligibility period; the MEAL module carries the logframe and indicator values through implementation; expenses, commitments and supporting documents accumulate against the same lines; and closure reports are generated from what was recorded along the way. For organisations running several cycles at once, our guide to multi-project management explains how the structure scales. To see it on your own project, start a free trial.