Day 7 of 8 · 6 hours · Mock exam 2

Phase 4: implementation, monitoring, control and change management

Learning objectives for today
  • Lead implementation: coordinate the team, partners and suppliers.
  • Monitor progress, compare it with the plan and decide on actions.
  • Manage changes, issues and reporting according to governance rules.

Keep the course at home: free PDF handout with exercises, key takeaways and quiz answers.

Download this lesson as PDF Complete manual (PDF)

Your working day : 6 h

The course alone is not enough: this plan spreads the 6 hours of the day. Tick each step once done.

1Doing the work

Implementation carries out the plan: mobilise the team and partners, launch procurement, carry out activities, deliver outputs. The project manager coordinates, motivates, removes blockages, protects the team and ensures quality and accountability.

Everyday tools: short regular meetings, monthly work plan, task tracking board, field visits, meetings with partners and community committees.

2Monitor and control

Monitoring collects and analyses information on progress (activities, outputs, spending, schedule, risks, indicators). Control compares reality with the baseline plan and decides on corrective actions (to get back on plan) or preventive ones (to avoid a future variance).

Example: at mid-term, 40% of the budget is spent while 60% of the planned work should be done, and only 35% actually is. The project is behind schedule (35% done instead of 60% planned) and costs more than planned for the work done (40% spent for 35% done). Analyse the causes before acting.

3Change control

A change in scope, schedule or budget is never decided alone and verbally. The change control process: 1) written request; 2) analysis of the impact on all constraints (scope, time, cost, quality, risks, beneficiaries); 3) decision at the competent level according to tolerances, and by the donor if the contract requires; 4) update of the plans; 5) informing stakeholders.

Scope creep is the gradual addition of unapproved work ("while you are here, also build…"). It consumes budget and time without a decision. The reflex: thank the person, record the request and put it through the process.

4Issues, decisions and lessons along the way

The issue log records each issue: description, date, impact, owner, action, deadline, status. The decision log keeps track of who decided what and why, useful for audit and adaptive management.

Lessons should not wait until the end: a short review after each important stage makes it possible to correct course during the project.

5Reporting and accountability

Reports serve decision-making, not only the donor: monthly internal report (progress, spending, risks, issues, decisions requested), narrative and financial reports to the donor, feedback to communities on what has been done and on the follow-up given to their complaints.

A good report is accurate, compares actual with planned, explains variances and proposes actions. It does not hide problems: transparency is an accountability requirement.

Exercise: change request

Situation. The village chief asks the project to add 2 water points near the school, on top of the 15 planned. Estimated cost: USD 14,000; extra time: 4 weeks; tolerances: 10% of the budget (USD 180,000) and 3 weeks.

Task. What do you tell the village chief, and what path does the request follow?

Answer. Thank them and explain that any change must be studied and decided, without promising anything. Write a change request and analyse the impact (14,000 / 180,000 = 7.8% of the budget, within tolerance; but 4 weeks, beyond the 3-week tolerance; a change of output, so outside delegated authority). The decision belongs to the steering committee, and probably to the donor since an output changes. Then update the plans and tell the community the answer.

Guided reading

Official, free documents. Answer the questions in writing: in an open-book exam, knowing where to look wins.

  1. Project DPro Guide, "Project implementation" phase
    PM4NGOs, 2nd edition (free) · Open the document

    • Which monitoring and control processes does the guide describe?
    • How does the guide describe change control?
    • Which logs and registers does the project manager keep during implementation?

Deliverable of the day : Monthly report and change request for your common-thread project

Imagine month 6 of your common-thread project. Write: 1) a one-page monthly report (planned and actual progress, planned and actual spending, 3 updated risks, 2 issues and their actions, decisions requested from the committee); 2) a complete change request for a realistic change (description, reason, quantified impacts, options, recommendation, decision level).

Marking grid (out of 20)

Planned / actual comparison quantified and interpreted6 pts
Risks and issues clearly separated, actions and owners4 pts
Complete change request with impacts on all constraints6 pts
Correct decision level according to tolerances and the contract4 pts
See the model answer points (after writing your deliverable)

Expected points. The report clearly says whether the project is ahead or behind, and whether it costs more or less than planned for the work done. The change request presents at least two options (including "change nothing") and states whether the donor must approve.

Key points

  • Monitor = collect and analyse; control = compare with the plan and act (corrective or preventive).
  • Compare work done with work planned and with actual spending before concluding.
  • No change of scope, time or budget without a written process and a decision at the right level.
  • Scope creep is fought by putting every request through change control.
  • Issue log, decision log, honest reports and feedback to communities.
A question about this module?

Ask the other participants: they are taking the same course as you.

Ask my question See this module's discussions

💼 Programme management jobs

Put this course into practice: the latest jobs in this field.

See all 1290 Programme management jobs →

Prepare for the written test and interviewA model written test in this field, interview questions with sample answers and the STAR method.See the model test →
Further reading: course references
  1. PM4NGOs (2020). Project DPro Guide (PMD Pro, 2nd edition): project management for development professionals. pm4ngos.org/methodologies-guides/project-dpro
  2. PM4NGOs (2026). Exams & Certificates: format, rules and fees of the Project DPro exam. pm4ngos.org/candidates-and-learners/exams-certificates
  3. PM4NGOs (2024). Practice / Sample Exam: free Project DPro Foundation practice exam. pm4ngos.org/candidates-and-learners/practice-sample-exam/project-dpro-pmd-pro-foundation
  4. PM4NGOs (2019). MEAL DPro: monitoring, evaluation, accountability and learning guide. pm4ngos.org/methodologies-guides/meal-dpro
  5. CHS Alliance, Groupe URD, Sphere (2024). Core Humanitarian Standard on Quality and Accountability (CHS). www.corehumanitarianstandard.org

Daily quiz

8 questions to check what you have learned. Answer them all to complete the day.

1A local donor verbally suggests that the project manager extend the project to a second village. What should be done?
2Planned to date: 50% of the work. Done: 40%. Spent: 45% of the budget. What do you conclude?
3An action taken to prevent a variance from happening in the future is:
4What is scope creep?
5What does the issue log contain?
6In a donor report, how should a major delay be handled?
7A change request adds an output to the logical framework. Who must usually approve it?
8Why keep a decision log?

← Day 6Day 8 →