Level 5 Challenge: Leading a Project
One project, from design through to the final report. Every decision tests whether the level-five courses have been put to work together, not each one in isolation.
- Length
- 50 min
- modules
- 5
- questions
- 9
- Pass mark
- 70%
Sign in so your progress is saved and you receive a certificate.
Requirements
🔒 This course is locked
Finish the required course above and this one opens.
Course information
- Level
- 5
- Difficulty
- Advanced
- Length
- 50 min
- modules
- 5
- questions
- 9
- Pass mark
- 70%
- Language
- Arabic / English
- Certificate
- Certificate of completion on passing
Who this is for
- Anyone who has finished the Level 5 courses
- Complex project leads
- Anyone wanting to test managing a full project
What you get
- A certificate with a public verification code
- The course recorded on your profile
- Credit towards your volunteer journey
What you will learn
Course contents
- The grant will not wait, and the community has not been consulted yetCurrent
- The partner is using beneficiary data in an activity that was not agreed
- Budget cut and the risk register
- The community rejects the approved plan — and has a good reason
- Sixty percent — the honest report and the pitch to a new partner
The grant will not wait, and the community has not been consulted yet
You are leading a project to improve drinking-water access in eight villages. The donor wants the full logical framework within forty-eight hours. The community consultation is scheduled five days from now.
You are leading a project to improve drinking-water access in eight villages in a rural region. The project runs for six months with a total budget of two hundred thousand dollars. This morning you received an email from the donor: they want the full logical framework — baseline indicators, measurable quantitative targets, and a detailed timeline — within forty-eight hours. Your first community consultation is scheduled five days from now and has not yet taken place. The logical framework is a document linking four levels: inputs to activities, outputs to results, and finally impact on people's actual lives. That chain cannot be accurate if it is not based on real knowledge of what the community is experiencing, what they see as priorities, and what has caused previous projects in this particular setting to fail. Community consultation in water and sanitation projects is not a formality added at the end of a document to meet a requirement; it is a fundamental data-gathering step that cannot be replaced by personal assumptions or data from similar projects in other areas. When impact indicators are built on assumptions rather than data, the document looks acceptable in month one, then unravels in month four: the indicators do not reflect a reality that can actually be measured in these specific villages, targets do not account for the social dynamics or agricultural seasons, and timelines ignore that some communities prefer mobilisation at particular times of year. At that point you find yourself facing a gap between what was promised and what can be delivered. A project leader in this situation does not choose between responding to the donor and maintaining design quality — they manage both through early and direct communication. A donor asking for a framework within forty-eight hours is not always aware that this is insufficient time for genuine community consultation. An organisation that takes the initiative to explain the context and presents a provisional framework with clear markings — indicating precisely what is confirmed and what awaits field verification in five days — shows its donor that it knows the difference between what it knows and what it does not yet know. That in itself is evidence of integrity. Good indicators for a water project do not measure what was built but what changed in people's lives. The number of water points established is an output indicator — it says what the team did. The percentage of households that moved from an unsafe to a safe water source is an outcome indicator — it says what changed for the beneficiaries. Did that change persist after the team withdrew? That is the true impact indicator according to the evaluation criteria you learned at level five — because a project whose results end when the project ends has achieved delivery, not sustainability. Choosing the right indicator from the outset determines what you will measure over six months and what you will present in the final report. The wrong indicator does not only lead to a misleading report — it leads to incorrect operational decisions during implementation because the team monitors what the framework measures rather than what actually matters.
Your decision
The donor insists on the full logical framework within forty-eight hours. Your consultation is scheduled five days from now. What is your move?
Indicators
After the community consultation, you choose the main indicator for measuring the water project's impact. Which of the following measures real impact rather than outputs?
The partner is using beneficiary data in an activity that was not agreed
In month three you discover that the local partner organisation is using the beneficiary lists in an electoral political activity that was not included in the partnership agreement. You have a meeting with the main donor tomorrow morning.
Discovering an ethical breach by a partner mid-project places you in a sharp conflict between two genuine priorities: preserving the partnership relationship you have built over three months and need to complete the project, and acting in accordance with the data-protection principles and Core Humanitarian Standard your organisation is committed to. The pressure to postpone the confrontation or minimise the problem is real and understandable — but it is dangerous precisely because it appears reasonable. Using beneficiary data in a political activity violates three principles at once. First: the principle of informed consent — beneficiaries agreed to share their data for the water project specifically, not for purposes outside it, and reusing it in a different context without their consent is an explicit violation of that agreement. Second: the do-no-harm principle — using individuals' data in a political activity may expose some of them to social, professional, or security risks in various contexts, risks they did not assess when they signed their consent. Third: the trust standard in the Core Humanitarian Standard — the trust a beneficiary extends to an organisation is the only capital that cannot be replaced, and violating it removes the organisation's ability to work with the community in the future. Documenting an ethical decision does not only mean writing what you decided to do — it means writing why you chose that particular option over the other available ones. A good document includes: the date and description of the discovery in objective language free of judgements about intentions, the principles or contractual clauses that conflict with what happened, the options you examined and reasons for ruling each out, the decision taken with its justification, and the planned follow-up steps with their timelines. This type of documentation serves a dual purpose: it protects the leader who took a difficult decision from later questioning of their motives, and it allows the organisation to learn from the incident to review partner-selection mechanisms and data-protection clauses in future partnership agreements. A leader who documents well is not constraining themselves — they are building the institutional memory that protects the organisation over the long term. Tomorrow morning's donor meeting is not an obstacle — it is an opportunity for early transparency if you act tonight in the correct sequence: a call to the partner requesting an immediate halt, then a written record of the discovery and the action taken, then telling the donor at the meeting what happened and what you did. The sequence matters: the halt comes first because the violation cannot wait, and documentation comes before the meeting because the donor deserves to see a document rather than just an oral account.
Ethical decision
What is your action tonight?
You discover the local partner is using the beneficiary list in an electoral campaign. You have a donor meeting tomorrow morning.
Documentation
You are documenting your ethical decision. Which of the following elements should be absent from the document?
Budget cut and the risk register
The organisation tells you the donor has cut total funding by twenty-five percent due to an internal funding crisis. At the same time, the main pipe supplier notifies you of a three-week delivery delay.
A budget cut mid-implementation is not a rare exception in humanitarian work — it is a scenario many project managers face in the field, and what distinguishes a good response from a poor one is not the absence of the problem but the way it is handled. The options available when the budget is cut significantly are usually four: first, narrowing the geographic scope — reducing the target villages from eight to six for example, while maintaining full work quality in the smaller scope. Second, reducing technical quality — keeping all villages while using lower-standard materials or services. Third, extending the timeline — slowing monthly activities and proceeding at a reduced pace within the available funding. Fourth, finding emergency alternative funding — seeking another funding partner or mobilising supplementary community resources. The first criterion for choosing among these options is: which causes the least harm to beneficiaries? In a water project specifically, narrowing scope while maintaining technical quality is usually better than expanding scope while degrading quality — because a safe and functional water point lasting ten years for five hundred people is better than an unreliable one for a thousand. But this criterion alone is insufficient: the final decision is not taken from the project manager's office alone. The process for changing project scope that you learned at level five passes through three stages: first, you prepare an options analysis with costs and impact on beneficiaries. Second, you present this analysis to your team and the community for their input. Third, you obtain written donor approval before implementing any change. Changing scope on your own without notifying the donor and waiting for approval may be considered a breach of grant conditions regardless of good intentions. At the same time, the main supplier notifies you of a three-week delay. This is the moment that proves the value of the risk register as a living document. If the risk of supply delay was logged in the register with a specific response plan — pre-identified alternative suppliers, alternative implementation timelines — then the action now is to activate that plan rather than think from scratch. If it was not logged, that in itself is a lesson to document: a risk register that is not updated monthly does not serve its purpose. The difference between a leader who applies risk management in practice and one who writes it for compliance shows at exactly this moment: the first opens the register, finds the risk and the plan, activates the plan immediately and notifies the donor. The second opens the register, finds the risk without a plan, and starts from scratch.
Budget decision
The budget has been cut by 25% in month four. Which of the following procedures aligns with quality and accountability principles?
Risk register
What is your first step?
The main pipe supplier notifies you of a three-week delay. This risk is logged in the risk register as "high probability – high impact" with a defined response plan including alternative suppliers.
The community rejects the approved plan — and has a good reason
The women of the area meet with you and inform you that the planned water point locations are unsafe for women in the evening hours. This was not raised in the first consultation. The design has donor approval.
Community participation in water and sanitation projects is not a charitable exercise or a checklist item for evaluation scores — it is an operational requirement that determines whether infrastructure will actually be used or remain on paper. A water point in an unsafe location that is not used at night has failed its core purpose, even if technically excellent and delivered on time. Women's security concerns regarding access to infrastructure are documented in humanitarian sector standards. Much of the failure in water projects is attributed specifically to sites being chosen on technical criteria — proximity to the source, ease of installation, low cost — without taking social usage data into account: who uses the water point, when, along which routes they reach it, and what security risks exist on those routes and at those times. Discovering this in month five rather than month one means the first consultation was not sufficiently inclusive. It likely did not include a separate discussion with women, or did not ask the right questions about usage times, access routes, and security concerns. This is a methodological error rather than one of intent — and its remedy is explicit acknowledgement and immediate correction, not defending the plan because it has donor approval. The project leader in this situation faces a tension between the approved design and the actual field need that has been discovered. Donor approval is not a document preventing learning — it is authorisation to implement what was agreed based on what was known at the time of design. When substantial new information emerges, the choice is not between "implement the plan" and "change the plan" — the choice is "how do I notify the donor of the new information and request a limited revision to the design that better serves the beneficiaries?" Good field adaptation begins with documentation: how many women reported the problem, which locations specifically, and what alternatives they suggested. It then moves to a technical assessment of the alternatives: can the location be moved technically? What is the additional cost? Then it reaches the donor with a request supported by documentation and justification. The community that sees a leader who listens to its concerns and adjusts the plan accordingly is the community that will maintain the infrastructure after the team withdraws and care about its continuity.
Adaptation
Community women inform you that the water point locations are unsafe in the evening. The design has donor approval. What are your steps?
Sixty percent — the honest report and the pitch to a new partner
The project is over. You achieved sixty percent of the quantitative targets — because of the budget cut and the field adjustment. The donor wants the final report. A prospective new partner wants a pitch for a second project.
Presenting results honestly — including what did not work — is the hardest test of level-five leadership. Pressure to inflate the picture comes from multiple directions: the donor wants to justify their investment to their own institution, the organisation wants to protect the funding relationship for future projects, the prospective new partner expects a success story that will move them to partner, and the team itself wants to feel that six months of effort bore fruit. All of these pressures are real and legitimate in their sources — but responding to them by inflating results produces three serious problems. First: it prevents institutional learning. What is not written clearly as a problem will not be corrected in the next project. If we write that the project "achieved its objectives" without clarifying that was only sixty percent of them, the next team working on a similar project will not know that the first design lacked sufficient consultation with women, will not know that the risk register did not include a plan for supply delays, and will not know that the first community consultation needed separate sessions. Second: it distorts the sector knowledge base. If every organisation writes reports that improve achievement ratios, the sector accumulates unrealistic expectations about what can be achieved with a limited budget in six months in a rural environment. And after five years, donors wonder why projects deliver less than they promise — and the answer is that good-looking reports built wrong expectations. Third: it creates an implicit promise to the next partner of results that cannot be guaranteed. When you present to a new partner a project with inflated results, they enter the partnership on the basis of expectations that do not reflect reality. When actual results fall short, they feel misled — and that is precisely what happens. Sixty percent with documented reasons and lessons learned is far stronger than one hundred percent built on incomplete or redefined figures. A donor who reads a report that honestly explains the budget was cut, that the field adjustment was necessary to protect women, and that the team made all the right decisions in facing these challenges — that donor sees responsible management worthy of trust in future projects. A new partner who hears a pitch that includes what was not achieved, with objective explanation and clear recommendations, trusts that what they are being shown reflects reality. And the partner who trusts is the partner who invests for the long term. Honesty in the pitch is not weakness or an admission of failure — it is evidence of professional maturity and confidence in oneself and the organisation.
Pitch and report
How do you structure your pitch to the new partner?
Your project ended at sixty percent completion. The reason is documented: budget cut and field adjustment. A prospective new partner hears your pitch tomorrow.
Integrated decision
How do you handle this situation in the moment?
During the final presentation to the donor, a team member publicly intervenes and corrects a figure you cited about the main indicator's achievement rate — stating the real figure is lower than what you said. The donor is watching both of you. You were not aware of the discrepancy before the meeting.
Finish the course
You answered 0 of 9 questions
Answer every question before finishing.
Standards this content is built on
- • PMD Pro — Project Management for Development Professionals (APMG International, 2nd edition)
- • OECD DAC Criteria for Evaluating Development Assistance (2019 revision)
- • Core Humanitarian Standard on Quality and Accountability (2024 edition)