9.2 The Project Management Cycle: Identification, Planning, Implementation, Monitoring and Evaluation

Key Takeaways

  • TOS competencies G.1.3, G.2.1 and G.2.2 require candidates to explain the project management cycle and apply tools for identification, planning, implementation, monitoring and evaluation.
  • The cycle runs identification, formulation and appraisal, financing, implementation, monitoring, evaluation and feedback into the next identification.
  • Monitoring is continuous and asks whether implementation is on track; evaluation is periodic and asks whether objectives were achieved and why.
  • Formative evaluation improves an ongoing project; summative evaluation judges a completed one.
  • The standard evaluation criteria are relevance, effectiveness, efficiency, impact and sustainability.
Last updated: September 2026

9.2 The Project Management Cycle

Blueprint anchor. TOS competency G.1.3 requires candidates to explain the Project Management Cycle; G.2.1 repeats it at sub-topic level; and G.2.2 requires applying tools for project identification and planning, implementation, monitoring and evaluation. These are the highest-frequency competencies in Topic G.


1. The Phases of the Cycle

PhaseCentral questionPrincipal outputs
1. IdentificationWhat is the problem and is a project the right response?Situational analysis, needs assessment, problem tree, project idea
2. Formulation / designWhat exactly will be done, by whom, with what?Objectives, logical framework, work plan, budget, indicators
3. AppraisalIs the design sound and worth funding?Feasibility, cost, risk and gender appraisal; approval or revision
4. Financing / mobilisationWhere do the resources come from and on what terms?Approved budget, memorandum of agreement, procurement plan
5. ImplementationIs the plan being carried out?Delivered activities and outputs, financial reports
6. MonitoringAre we on track, and what needs adjusting now?Progress reports, indicator tracking, corrective actions
7. EvaluationDid it achieve its objectives, and why or why not?Evaluation report, lessons, recommendations
8. Feedback / learningWhat does this teach the next project?Revised design standards; new identification

The cycle is closed, not linear: evaluation feeds identification. A project whose evaluation changes nothing has completed a line, not a cycle.


2. Identification Tools

  • Situational analysis using a dimensional scan of the community.
  • Needs assessment through survey, focus group discussion or participatory appraisal.
  • Problem tree — the core problem in the trunk, causes below as roots, effects above as branches. Converting each element to its positive form produces the objective tree, and the chosen branch of that tree becomes the project strategy.
  • Stakeholder analysis — who is affected, who has influence, who must be involved, who may resist.
  • Prioritisation matrix — scoring candidate problems on magnitude, severity, feasibility, community concern and available resources.

3. Planning Tools

The logical framework (logframe) is the standard planning matrix and appears frequently in items.

Narrative summaryObjectively verifiable indicatorsMeans of verificationAssumptions / risks
GoalLong-term change contributed toImpact indicatorsNational or municipal statisticsConditions beyond the project hold
Purpose / outcomeChange in participantsOutcome indicatorsSurvey, recordsParticipants able to act
OutputsDeliverablesOutput indicatorsActivity reports, attendanceOutputs are used as intended
ActivitiesActionsInputs and budgetFinancial recordsResources arrive on time

The vertical logic reads upward: if activities are done, outputs are produced; if outputs are produced and assumptions hold, the outcome follows. Naming assumptions honestly is what separates a logframe from a wish list.

Other planning tools: the work and financial plan, the Gantt chart for scheduling, the work breakdown structure, and the responsibility matrix assigning each activity to a named person.

SMART indicators are specific, measurable, attainable, relevant and time-bound. "Improved wellbeing" is not an indicator; "proportion of enrolled children attending at least 85 percent of school days in the second semester" is.


4. Implementation

Core management tasks: mobilising and orienting staff, procurement in accordance with public procurement rules where public funds are used, community organising and participant enrolment, scheduling, financial control and liquidation, documentation, coordination with the local government unit and partners, and risk management as conditions change.

The most common implementation failures in social welfare projects are procurement delay, staff turnover, weak documentation, and drift from the design under local pressure — for example, quietly substituting easier-to-reach participants for the intended hardest-to-reach group.


5. Monitoring Versus Evaluation

MonitoringEvaluation
TimingContinuous, during implementationPeriodic: mid-term, terminal, or ex-post
QuestionAre we doing what we planned?Did it work, and why?
FocusInputs, activities, outputsOutcomes, impact, and the causal account
WhoProject team, community monitorsOften includes external or independent evaluators
UseImmediate correctionDecisions on continuation, redesign, scale-up

Formative evaluation is conducted while the project runs, to improve it. Summative evaluation is conducted at or after the end, to judge it. Process evaluation examines how implementation actually occurred; outcome evaluation examines what changed; impact evaluation attempts to attribute change to the project against what would have happened otherwise.

Standard Evaluation Criteria

CriterionQuestion
RelevanceDid it address a real and priority need?
EffectivenessWere the objectives achieved?
EfficiencyWere resources used economically for the results obtained?
ImpactWhat wider or unintended changes followed?
SustainabilityWill the benefits continue after the project ends?

Social work practice adds equity (who benefited and who was left out) and participation (whose decisions shaped the project) as criteria in their own right.


6. Worked Practice Application

A municipality implements a twelve-month day-care improvement project in eight barangays: rehabilitating centres, training child development workers, and supplying learning materials.

PhaseWhat was doneWhat the social worker contributes
IdentificationEnrolment and nutrition data reviewed; parents' assemblies held in all eight barangaysEnsures the problem tree separates causes (worker skill, facility condition, parent participation) from effects (low readiness)
FormulationLogframe with outcome "school readiness scores improved among enrolled children" and outputs on facilities, training and materialsInsists that assumptions — that parents will continue to enrol, that workers will remain in post — are written down
AppraisalCosted and reviewed; risk of worker turnover flaggedRecommends a retention measure, since training a worker who then leaves converts an output into a loss
ImplementationFacilities rehabilitated; 24 workers trained; materials deliveredDetects that two barangays enrolled easier-to-reach children and restores the intended targeting
MonitoringMonthly attendance, session delivery and material use tracked by barangay child development committeesUses community monitors so that monitoring itself builds capacity
EvaluationTerminal evaluation against the five criteria plus equity and participationReports that outputs were met, outcomes rose in six of eight barangays, and that the two exceptions coincide with worker turnover
FeedbackFindings taken to the municipal development councilRecommends that the next cycle fund a worker retention allowance, closing the loop

The examinable point is in the last row: the evaluation finding changed the next design. That is what makes the sequence a cycle.

Test Your Knowledge

Which statement correctly distinguishes monitoring from evaluation?

A
B
C
D
Test Your Knowledge

In a logical framework, what belongs in the assumptions column at the output level?

A
B
C
D
Test Your Knowledge

A mid-term review is conducted so that the project team can adjust delivery before the project ends. This is best described as:

A
B
C
D