How Education Works | Joint Sector Reviews & Mutual Accountability — How Governments and Partners Turn Annual Evidence Into One Shared Education-System Review

HEW-NODE-0165 · How Education Works · joint sector review, education sector plan, annual review, mutual accountability, sector performance, annual monitoring report, policy dialogue, government ownership, development partners, civil society, action tracking, implementation evidence, financing dialogue, learning and follow-through

An education system can have hundreds of indicators and still lack a shared moment when the whole sector decides what the evidence means.

One ministry unit may know that teacher recruitment is late. Another may know that construction is underspent. Development partners may hold project data. Civil society may see access barriers that do not appear in national averages. Regional offices may understand why a policy is stalling. None of this automatically becomes one coherent system judgement.

A joint sector review is designed to create that judgement.

The value of a sector review is not the meeting itself. It is the disciplined conversion of fragmented evidence into a shared diagnosis, a small set of decisions and an accountable next cycle.

This node sits beside the How Education Works hub, Education Sector Planning & Annual Operationalisation, Education Sector Analysis & System Diagnosis, Education Policy Implementation, Adaptive Delivery & Monitoring, International Education Finance & Development Partner Coordination, and Education Open Data, Public Reporting & School Transparency.

Those pages keep their jobs. Sector Planning owns the plan. Sector Analysis owns deep diagnosis. Adaptive Delivery owns ongoing implementation management. Development Partner Coordination owns how external actors and finance align with national systems. Open Data owns public reporting. This node owns the recurring cross-sector accountability forum: how governments and partners periodically assemble evidence on sector-plan implementation, test whether commitments were delivered, agree corrective action and carry those decisions into the next planning and budgeting cycle.

The 60-Second Read

• A joint sector review is a structured review of education-sector plan implementation, not merely a conference.
• Government ownership matters because the review should strengthen national planning rather than create a parallel donor process.
• The annual implementation report is often more important than the event agenda.
• Indicators should be few enough to support judgement, not so numerous that the review becomes data recitation.
• The review should distinguish progress, delay, failure, changed assumptions and missing evidence.
• National averages should be disaggregated where they conceal geographic or group-level problems.
• Finance belongs beside implementation: underspending, delayed releases and unfunded commitments can explain weak delivery.
• Stakeholder participation should be designed around information and decision rights, not symbolic invitations.
• Development partners should bring their project evidence into the same sector frame where possible.
• Civil society can provide challenge, local evidence and accountability that administrative systems miss.
• The review should end with a short, owned action matrix rather than dozens of aspirational recommendations.
• Every action needs an owner, deadline, evidence requirement and review point.
• Unresolved actions should return at the next review rather than disappear when the meeting ends.
• Reviews should separate implementation failure from a plan that has become unrealistic.
• A changed context may justify revising targets rather than pretending the original assumptions still hold.
• Repeatedly missing data is itself a system finding.
• Reviews should feed the budget calendar early enough to change allocations.
• Independent challenge can improve credibility but should not replace government decision authority.
• The review cycle should learn from its own quality: late reports, excessive indicators and weak follow-through should be repaired.
• The purpose is mutual accountability for one education plan, not mutual attendance at one meeting.

One-Sentence Definition

A joint sector review is a government-led, evidence-based periodic process in which education stakeholders collectively assess implementation of the sector plan, examine results and constraints, agree corrective actions and renew accountability for the next delivery cycle.

The First Distinction: Review Is Not Monitoring

Monitoring can happen continuously through dashboards, reports and management routines. A sector review is the point where that evidence is brought together for collective judgement and decision.

Monitoring asks what changed. The review asks what the change means for the plan, commitments, financing and next action.

The Second Distinction: Mutual Accountability Is Not Shared Authority Over Everything

Partners can challenge evidence, explain their own delivery, commit finance and agree actions. Government still carries public authority for national education policy. A joint review should deepen accountability without turning national policy into a committee where every actor has identical authority.

The Third Distinction: Annual Review Is Not Annual Reinvention

A sector plan usually spans several years. The annual review should test implementation and assumptions, not rewrite strategic direction every twelve months because one indicator moved.

Major revision is justified when evidence shows that the strategy, context or resource envelope has materially changed.

There Is an Established International Practice

The Global Partnership for Education’s Practical Guide for Effective Joint Sector Reviews in the Education Sector treats the review as a platform for mutual accountability and sector dialogue rather than a stand-alone event. Country review reports published by GPE show the model in operational use across different education systems.

IIEP-UNESCO’s planning work likewise places annual implementation reporting and review inside a wider monitoring, evaluation and learning system. In Jordan, for example, the Ministry of Education and UNESCO convened a 2025 Joint Annual Review Meeting around the annual monitoring and evaluation report for the Education Strategic Plan, using the review both to take stock and to inform the next planning cycle.

Start With One National Results Framework

A joint review becomes fragmented when every partner arrives with a separate indicator set. The sector plan should provide the primary results framework, with additional project indicators used only where they illuminate a sector question rather than compete with it.

This is one reason indicator discipline matters. IIEP has documented planning work where ministries reduced unwieldy indicator sets to make annual reporting and review more manageable.

Build the Annual Implementation Report Before the Meeting

• planned result;
• baseline;
• annual target;
• actual result;
• trend;
• geographic and population disaggregation;
• budget allocated;
• budget released;
• budget spent;
• major activities completed;
• implementation constraints;
• changed assumptions;
• evidence gaps;
• management response already underway.

The report should reach participants early enough to be read. A review dominated by first-time presentation leaves too little time for interrogation and decision.

Do Not Treat Every Indicator Equally

Some indicators represent final education outcomes, some describe intermediate service conditions and some simply track activities. A school-construction count and a learning outcome do not carry the same causal meaning.

The review should organise evidence around results chains so participants can see whether a weak outcome reflects missing inputs, weak implementation, a broken mechanism or an unrealistic theory of change.

Classify the Status of Each Commitment

• On track: delivery and result are broadly consistent with plan.
• At risk: progress is plausible but current evidence shows material threat.
• Off track: target or milestone is unlikely without corrective action.
• Blocked: delivery depends on an unresolved external decision or resource.
• Superseded: the original commitment is no longer the correct course because context changed.
• Unknown: evidence is too weak to judge.

“Unknown” should remain a legitimate status. Invented certainty hides data-system weaknesses.

Disaggregate Before Declaring Success

National enrolment can improve while one province deteriorates. Average completion can rise while disability inclusion remains stagnant. Teacher numbers can grow while rural shortages deepen.

Joint reviews should therefore test distribution as well as totals. The exact disaggregation depends on lawful data availability and policy relevance.

Finance Must Sit Beside Performance

A programme can appear to have an implementation problem when the actual problem is that funds arrived six months late. Another programme can underspend despite full releases because procurement stalled. A third can spend fully while failing to produce the intended output.

Review financial execution and physical delivery together. The Budget Execution & Public Expenditure Tracking owner supplies the deeper mechanics; the joint review asks what those mechanics mean for sector-plan commitments.

Use the Budget Calendar

A review held after next year’s budget is already fixed may generate good recommendations with no financing path. Schedule the review early enough that findings can influence annual operational plans, medium-term ceilings and partner allocations.

Government Leadership Should Be Visible

The ministry should own the review agenda, evidence process and final action matrix even when external partners finance technical preparation. Otherwise the review can become another project obligation rather than a national management instrument.

But Government Leadership Is Not Government Monologue

Mutual accountability requires space for challenge. Regional officials, teachers, civil society, learners, parent representatives, non-state providers and development partners may hold evidence that central government does not.

The design question is which voices are needed for which decisions, and how participation is structured so evidence can affect the outcome rather than merely decorate the agenda.

Participants Need Different Roles

• Decision owners: can commit government action or policy change.
• Delivery owners: explain implementation reality and own follow-through.
• Finance owners: explain budget constraints and releases.
• Evidence owners: maintain the data and methods.
• Challenge participants: test claims and bring independent or local evidence.
• Partners: account for their own commitments and align support.
• Secretariat: preserves decisions, actions and unresolved questions.

Not every participant needs to speak on every issue. A well-designed review uses roles to prevent both domination and performative participation.

Development Partners Should Review Their Own Commitments Too

Mutual accountability fails if only government performance is examined. Partners may have delayed disbursement, fragmented reporting, changed project scope or imposed parallel systems that create administrative burden.

The International Education Finance & Development Partner Coordination owner defines the wider relationship; the review creates a recurring place to test whether alignment commitments are actually being honoured.

Review the Plan, Not Just the Ministry

Education outcomes can depend on finance ministries, public-service commissions, construction agencies, local government, transport, health, social protection and digital infrastructure. Where commitments cross sectors, the relevant owners should be brought into the review rather than treating the education ministry as if it controls every dependency.

Make the Review Problem-Led

A common weak format is programme-by-programme presentation. Each department reports activities, declares progress and moves on. A stronger format clusters evidence around a small number of system questions:

• Why is lower-secondary transition off track?
• Why are teacher vacancies increasing in rural districts?
• Why is school construction underspending?
• Why did textbook availability improve without a corresponding improvement in classroom use?
• Why are girls’ completion gains concentrated in only half the regions?

Problem-led review turns reporting into diagnosis.

Use Pre-Review Technical Sessions

Technical teams can reconcile data definitions, resolve obvious errors and identify disputed findings before senior decision-makers meet. This protects the main review from spending hours on denominator disputes that should have been settled earlier.

Preserve Genuine Disagreement

Consensus is useful but not always honest. If government and a partner interpret evidence differently, record the disagreement, the evidence each side relies on and what additional analysis is needed.

Forced consensus can make the final report look clean while weakening institutional learning.

Separate Data Quality From Performance Quality

A missing attendance figure does not prove attendance is poor. It proves the system cannot currently establish attendance confidently. That is a different problem requiring a different action.

The Education Statistics Quality Assurance & Data Validation owner governs the evidence system; the review should preserve “unknown” rather than converting weak data into strong conclusions.

Track Assumptions, Not Only Targets

A plan may assume a stable school-age population, a certain teacher-recruitment rate, expected construction prices or donor financing. When those assumptions change, apparent underperformance can have a structural explanation.

Each major plan result should have a small assumption register. The annual review can then ask whether the plan is off track because implementation failed or because the world changed.

Do Not Protect Targets From Reality

Targets should not be changed simply because they are inconvenient. But keeping a target that has become impossible after a major shock can turn performance management into ritual.

A transparent review can recommend target revision when assumptions materially change, while preserving the original target and explanation in the historical record.

The Action Matrix Is the Real Output

• finding;
• decision;
• specific action;
• named institutional owner;
• supporting actors;
• deadline;
• required evidence of completion;
• resource implication;
• escalation route;
• next review point.

A recommendation such as “strengthen teacher deployment” is not an action. “Human Resources Directorate to publish the revised rural-vacancy allocation rule by 30 September, with district vacancy data and implementation circular” is much closer.

Limit the Number of Actions

Reviews often produce fifty recommendations because every participant wants their issue represented. This can destroy follow-through.

Prioritise the small number of actions whose completion would materially change implementation. Other observations can remain in the report without becoming formal commitments.

Carry Unfinished Actions Forward

Every new review should open with the previous action matrix. Which actions were completed? Which were late? Which were superseded? Which remain blocked?

This creates institutional memory and prevents annual reviews from resetting accountability to zero.

Build a Decision Log

A sector plan evolves. Record why targets were revised, why funds were reallocated, why one activity was stopped and why another was accelerated. Later reviewers should be able to reconstruct the reasoning rather than seeing only the new number.

Link the Review to the Next Annual Operational Plan

Actions should flow directly into the next annual plan, budget and partner work programmes. If the review sits outside those systems, its recommendations can become a parallel list with no implementation home.

Link the Review to Procurement and Workforce Cycles

If textbook procurement must begin nine months before the school year, a review that identifies shortages after that deadline cannot fix the next cycle. If teacher posting closes in June, staffing actions need to arrive before the posting window.

Sector-review timing should respect the operational clocks it intends to influence.

Use Regional Reviews Where the System Is Decentralised

A national review can miss implementation variance. Regional or provincial reviews can surface local constraints before the national event, provided definitions and action-tracking methods remain compatible.

The objective is not to duplicate meetings at every level. It is to let evidence move upward and decisions move back down without losing context.

Field Visits Can Test the Paper Story

Where useful, pre-review field visits can compare reported implementation with school reality. A database may show delivered equipment while schools report missing installation, training or spare parts.

Field evidence is not automatically representative. It should be used as a diagnostic probe and combined with wider data.

Civil Society Participation Needs Evidence Access

Inviting civil society without sharing the implementation report early enough creates symbolic participation. Participants need enough information to prepare, challenge and contribute.

Confidential or personal data still require protection. The answer is not total disclosure but a review pack with sufficient aggregated evidence for meaningful scrutiny.

Learner Voice Can Be Useful When the Question Is Real

Learners can provide direct evidence about transport, safety, teaching materials, school climate and access barriers. Their participation should be linked to defined questions and safeguarding, not used as a ceremonial opening segment disconnected from decisions.

Independent Reviewers Can Add Challenge

An independent analyst or technical panel can test assumptions, methods and causal claims. Independence is particularly useful when performance evidence has financial or political consequences.

Independent analysis should challenge the evidence; it should not quietly become a substitute government.

Do Not Let Donor Reporting Consume the Review

A joint sector review should reduce fragmentation, not become the place where every partner demands a separate presentation against its own logframe. Where possible, project reporting should map into national results and identify only the additional evidence needed for specific financing agreements.

Review the Cost of the Review

Large events can consume substantial travel, consultant and staff time. A mature system asks whether the review process itself is proportionate. Better pre-circulated analysis and smaller technical sessions may improve decision quality more than a larger conference.

Digitise the Action Chain, Not Just the Slide Deck

A shared system can track actions, owners, deadlines, evidence and status between annual reviews. The technology should support accountability rather than create another reporting platform disconnected from ministry workflows.

Case Study: The Missing Teacher Problem

Illustrative example: national teacher numbers increased, but rural vacancy rates worsened. The review initially records “teacher recruitment achieved.” Disaggregated evidence shows that recruitment and deployment are different problems.

The action matrix shifts from “hire more teachers” to a package involving posting rules, hard-to-staff incentives, district vacancy publication and a mid-year mobility review. The review improves the problem definition rather than merely adding another activity.

Case Study: The Budget That Was Never Released

Illustrative example: school-rehabilitation targets are badly off track. The infrastructure unit is criticised until the review shows that only 45 per cent of the approved capital allocation reached the implementing agency by mid-year.

The corrective action belongs partly to treasury and cash-management processes, not only to the education infrastructure team.

Case Study: The Indicator That Nobody Could Reproduce

Illustrative example: the sector report claims a large improvement in completion. Civil-society analysts cannot reproduce the number because the denominator changed.

The review does not debate the policy significance until the statistics team publishes the revised method, restates the historical series and marks the comparability break. Evidence governance becomes an action in its own right.

Case Study: The Plan That Outlived Its Assumptions

Illustrative example: a five-year plan assumes stable school-age population. Large migration shifts enrolment toward urban districts. Several access targets become unattainable under the original school network.

The review records the changed demographic assumption, commissions updated school mapping and recommends formal plan revision rather than treating every local capacity failure as poor execution.

Failure Modes and Repairs

• Meeting without evidence: repair by making the annual implementation report the primary input.
• Hundreds of indicators: repair by prioritising a manageable results framework.
• Government-only accountability: repair by reviewing partner commitments and cross-sector dependencies too.
• Presentation marathon: repair with problem-led sessions and pre-review technical reconciliation.
• Average hides inequality: repair with relevant disaggregation.
• Late budget timing: repair by aligning review dates with planning and budget cycles.
• Recommendation overload: repair with a short action matrix.
• No owner or deadline: repair by converting recommendations into accountable tasks.
• Annual reset: repair by opening each review with prior actions and a decision log.
• Forced consensus: repair by preserving legitimate disagreement and specifying what evidence would resolve it.

The Joint-Sector-Review Operating Chain

1. Confirm the sector-plan results framework.
2. Update indicator definitions.
3. Collect annual implementation evidence.
4. Validate data quality.
5. Disaggregate key results.
6. Reconcile financial and physical delivery.
7. Update major assumptions.
8. Draft the annual implementation report.
9. Circulate the report early.
10. Run technical pre-review sessions.
11. Identify major cross-sector problems.
12. Identify unresolved evidence disputes.
13. Review prior action commitments.
14. Structure the main review around priority system questions.
15. Hear government delivery owners.
16. Hear subnational and stakeholder evidence.
17. Review development-partner commitments.
18. Test whether targets remain realistic.
19. Agree corrective actions.
20. Assign institutional owners.
21. Set deadlines and evidence of completion.
22. Record disagreements and further analysis required.
23. Issue the agreed action matrix.
24. Integrate actions into annual plans.
25. Integrate financing implications into the budget cycle.
26. Track actions between reviews.
27. Escalate overdue high-priority commitments.
28. Review progress at the next cycle.
29. Assess the quality of the review process itself.

A Joint-Review Dashboard

• sector indicators on track;
• sector indicators at risk;
• sector indicators off track;
• unknown indicators;
• major geographic gaps;
• budget execution by priority;
• partner commitments delivered;
• prior actions completed;
• prior actions overdue;
• new actions agreed;
• actions with named owners;
• actions linked to budget;
• targets revised with documented rationale;
• evidence disputes unresolved;
• cross-sector dependencies unresolved;
• average report publication lag;
• review documents circulated on time;
• stakeholder participation by role;
• next decision checkpoints.

Canonical Owner Boundaries

• Education Sector Planning & Annual Operationalisation owns preparation and annual translation of the plan.
• Education Sector Analysis & System Diagnosis owns periodic deep diagnosis of the system.
• Education Policy Implementation, Adaptive Delivery & Monitoring owns continuous implementation management.
• International Education Finance & Development Partner Coordination owns external-finance and partner-alignment architecture.

This node owns the periodic shared accountability cycle that converts sector-plan evidence into collective judgement, decisions, tracked corrective actions and the next annual delivery cycle.

Sources and Further Reading

• Global Partnership for Education, Practical Guide for Effective Joint Sector Reviews in the Education Sector.
• IIEP-UNESCO, Educational Planning, Monitoring and Annual Review Practice.
• IIEP-UNESCO, Jordan Joint Annual Review Meeting 2025.
• IIEP-UNESCO, World Bank and UNICEF, Education Sector Analysis Methodological Guidelines.

The Return Path

Return to the annual review table.

There are ministry officials, finance officers, regional directors, partners and civil-society representatives. They do not need another ceremonial account of activity. They need a common answer to a harder set of questions: what actually changed, what did not, why, what evidence is trustworthy, what assumptions have broken, who now owns the repair and what will count as completion?

When those questions are answered well, the joint sector review becomes more than a meeting. It becomes one of the places where the education system remembers its promises.

Mutual accountability becomes real when last year’s commitments return as this year’s evidence.

Return to the How Education Works hub.