HEW-NODE-0152 · How Education Works · policy coherence, cross-sector coordination, whole-of-government education, integrated child services, health, social protection, housing, transport, interagency governance, shared outcomes, referral pathways, joint planning, pooled funding, data sharing, accountability and system boundaries
A child can be absent from school because the school is weak.
But the child can also be absent because the bus never arrived, because the family moved after a housing shock, because untreated illness made attendance impossible, because a disability support decision is stuck between agencies, because food insecurity changes daily priorities, or because a social-protection rule unintentionally makes school participation harder.
Education systems eventually discover a difficult truth: many educational outcomes are produced partly outside the education ministry.
Policy coherence is the discipline of making sure one public system does not quietly undermine the outcome another public system has been tasked to produce.
This node sits beside the How Education Works hub, Education Policy, Education Sector Planning & Annual Operationalisation, District & Regional Education Offices, School Health Services, School Transport Operations, Student Support Referral & Case Coordination, Out-of-School Children & Education Re-Entry and Education Data Privacy & Student Records Governance.
Those pages keep their jobs. Education Policy owns education-sector choices. Sector Planning owns education plans. School Health owns health functions inside the school system. Transport owns movement to and from school. Student Support Referral owns the case-level handoff around an individual learner. This node owns the system-level coordination problem: how education aligns goals, rules, budgets, data, timelines and responsibilities with other public systems when the learner’s outcome depends on several sectors at once.
The 60-Second Read
- Education outcomes often depend on health, transport, housing, nutrition, social protection, digital infrastructure and local government.
- Cross-sector coordination is not the same as asking another ministry for help after a problem appears.
- Policy coherence begins by identifying where objectives, rules or incentives interact.
- One ministry can create barriers that another ministry then spends money trying to repair.
- Shared outcomes need separate accountability: collaboration should not make responsibility disappear.
- Joint committees are useful only when they have decision rights, data and escalation routes.
- Interagency work becomes stronger when dependencies are mapped before plans are finalised.
- A referral pathway is not a strategy unless receiving services have capacity.
- Data sharing should follow defined purposes, roles and privacy rules.
- Common identifiers can improve coordination but do not justify unrestricted data access.
- Budgets can be aligned without being fully pooled.
- Pooled budgets can reduce silo behaviour but can also weaken traceability.
- Integrated services work best when families experience one coherent route even if several agencies remain involved behind it.
- Local coordination often matters because housing, transport and social services operate geographically.
- National rules still matter because local collaboration without stable authority can become personality-dependent.
- Timelines must align: an education intervention can fail because a health or housing decision arrives months later.
- Shared indicators should not create a contest over who gets credit.
- Cross-sector initiatives need exit and review rules so temporary coordination bodies do not become permanent bureaucracy without purpose.
- Good coherence reduces contradictory policy, duplicate assessment and avoidable administrative burden.
- The objective is not one giant super-ministry. It is a public system in which institutional boundaries do not become learner barriers.
One-Sentence Definition
Education policy coherence and cross-sector coordination are the arrangements through which education authorities align objectives, rules, information, resources and responsibilities with other public systems when educational outcomes depend on shared causes or joint delivery.
The First Distinction: Coordination Is Not Integration
Two ministries can coordinate while remaining separate. They may share timelines, agree referral rules, align eligibility criteria or use a joint dashboard. Integration goes further: services may be combined around the user, budgets may be pooled, teams may work under one governance structure, or data may be joined more deeply.
The correct design depends on the problem. A school transport dependency may need coordination. A child with complex disability, health and education needs may require a more integrated service model.
The Second Distinction: Policy Coherence Is Not Policy Uniformity
Coherence does not require every ministry to pursue the same objective. Housing policy may need efficient land use. Transport policy may need network efficiency. Health policy may prioritise disease prevention. Education policy may prioritise access and learning.
The coherence question is whether those objectives interact in ways that create avoidable contradiction. A school catchment decision that ignores transport can increase absenteeism. A housing relocation programme that moves families far from schools can destabilise learning. A social-protection rule that requires weekday appointments may repeatedly remove children from class.
The Third Distinction: Shared Outcome Does Not Mean Shared Blame
Cross-sector work can become vague when everyone is “collectively responsible.” If attendance falls, who acts? If a referral is delayed, who owns the queue? If a transport subsidy fails, which budget repairs it?
Strong collaboration preserves named accountability inside the shared outcome. Several agencies can contribute to one result while each remains responsible for its part of the chain.
Current OECD Thinking: Education Is Increasingly a Cross-Sector System
The OECD’s Education Policy Outlook 2025 repeatedly identifies cross-sector collaboration as an important condition for supporting learners across stages of life. Its early-childhood analysis highlights integrated education, health and social-service frameworks, while later stages emphasise career readiness, digital well-being and wider support networks around learners.
The OECD’s Government at a Glance 2025 places policy coherence inside whole-of-government coordination: the problem is not only whether each ministry performs well independently, but whether policies across sectors reinforce or undermine one another.
Begin With the Learner Outcome, Not the Organisation Chart
Suppose the objective is to reduce chronic absenteeism. Starting from the organisation chart produces separate plans: education improves attendance systems, health improves access, transport optimises routes, social services support families.
Starting from the learner produces a different question: what are the recurring causal pathways into absence, which agency controls each pathway, and where does the handoff fail?
This is the core move in policy coherence: follow the outcome across institutional boundaries before assigning the work back to institutions.
Map Cross-Sector Dependencies Explicitly
- school access depends on transport and road safety;
- attendance can depend on health and family support;
- nutrition can depend on social protection, agriculture and food procurement;
- school capacity depends on housing and urban planning;
- digital learning depends on telecoms, electricity and device markets;
- disability inclusion can depend on health assessment, assistive technology and social services;
- re-entry can depend on child protection, justice and labour-market regulation;
- career pathways can depend on industry, labour ministries and qualification systems;
- early childhood can depend on health, family policy and municipal services.
The map should identify both dependencies education receives and effects education creates for other sectors.
Cross-Sector Problems Often Hide in Eligibility Rules
A child may qualify for a school service under one definition of disability and for a health service under another. A transport subsidy may use household income measured differently from a school meal programme. A social worker may require documentation the school does not collect.
These inconsistencies create administrative burden for families and frontline staff. Policy coherence can involve harmonising definitions where justified or creating translation rules when definitions must remain different.
Shared Definitions Need Governance
Terms such as “enrolled,” “resident,” “low income,” “disability,” “at risk” or “school age” can carry different legal meanings. Forcing one definition across all sectors can be wrong. Leaving differences undocumented can also be wrong.
A cross-sector data and policy dictionary can show where terms align, where they differ and which definition governs which decision.
Referral Pathways Are the Operational Core
At system level, coordination becomes real when one service can hand a case to another without losing the learner. The referral needs eligibility, receiving capacity, consent where required, status tracking, escalation and closure.
A referral form is not enough. If the receiving service has a six-month wait, education is still carrying the unresolved consequence.
Capacity Must Travel With Responsibility
Ministries sometimes solve a policy problem by transferring responsibility. Schools are told to identify mental-health needs, municipalities are told to transport high-need learners, social services are told to support re-entry.
If money, staff, authority and systems do not move with the responsibility, the transfer is administrative rather than operational.
Cross-Sector Collaboration Needs Decision Rights
Interagency committees often fail because they can discuss but not decide. Clarify which decisions can be made jointly, which remain with a lead ministry, which need cabinet or legislative approval, and which can be delegated locally.
A useful governance document is less interested in meeting frequency than in decision authority.
Choose a Lead Agency for Each Shared Result
One agency should normally own coordination for a defined outcome even when several agencies contribute. The lead does not own every service. It owns convening, progress visibility, unresolved dependencies and escalation.
This avoids the “everyone attended the meeting” version of accountability.
Use Shared Outcomes Carefully
“Improve child well-being” is too broad for operational coordination. “Reduce chronic absence among children receiving housing-stability support” is more manageable because the target population, outcome and cross-sector relationship are visible.
Shared outcomes should be narrow enough to manage and broad enough to matter.
Indicators Should Preserve Each Sector’s Contribution
A single final outcome is useful but insufficient. If attendance improves, which mechanisms changed? Transport reliability? Health appointments? Family support? School climate?
Use a results chain with agency-specific intermediate indicators so the system can learn rather than merely celebrate or blame.
Timelines Must Be Aligned
Education plans often follow school years. Health budgets may follow calendar years. Housing projects run on construction cycles. Social-protection eligibility may refresh monthly. Transport contracts may last several years.
Coordination needs a temporal map. A service delivered after the educational transition has passed may be technically successful and practically too late.
Housing and School Capacity Need a Shared Forecast
New housing changes school-age population geographically. School construction and land reservation take time. If housing agencies and education planners use different growth assumptions, schools can be built after overcrowding arrives or retained where families have already moved away.
The answer is not to merge agencies. It is to share scenario assumptions, planning horizons and geographic identifiers.
Transport and School Choice Interact
A school may be geographically close and operationally inaccessible if transport is unreliable. A new transit route can change effective catchments. A school-choice policy can generate travel demand transport planners did not anticipate.
Cross-sector planning should model the journeys created by admissions and school-network decisions, not treat travel as a family problem downstream.
Health and Education Share Time as a Resource
Medical appointments, screening, therapy and school all compete for a child’s time. Coordination can schedule services to reduce avoidable absence, bring some services into schools where appropriate, or design catch-up routes.
The goal is not to turn schools into clinics. It is to recognise that uncoordinated service schedules can create an educational cost.
Social Protection Can Protect Learning Continuity
Income shocks, food insecurity and housing instability can push children out of regular participation. Education agencies rarely control these causes directly.
Coordination can create automatic or simplified referral to support when school data signals a problem, subject to lawful use, consent and evidence boundaries.
Do Not Turn Teachers Into Universal Case Managers
Teachers see many problems early. That does not mean they should personally navigate health, housing, welfare and legal systems for every family.
Cross-sector design should reduce the burden on teachers by creating clear specialist handoffs and visible status rather than adding more forms and informal chasing.
Local Integration Needs National Infrastructure
Many learner problems are local. A district knows the transport operator, local clinics, housing office and community organisations. Local flexibility can therefore be valuable.
But local coordination is fragile if it depends entirely on personal relationships. National frameworks can provide referral standards, data-sharing templates, funding rules, minimum service expectations and escalation routes.
Vertical Coordination Matters Too
Cross-sector work can fail between levels of government even when ministries agree nationally. A national education ministry may coordinate with a health ministry, while schools depend on municipal clinics outside that agreement.
Map national, regional and local authority together. Horizontal coordination across sectors and vertical coordination across levels are different dimensions of the same implementation problem.
Joint Planning Does Not Require One Budget
Agencies can agree outcomes and timelines while keeping separate appropriations. This preserves financial accountability and may be enough when responsibilities are clear.
Pooled budgets can be useful where work is genuinely inseparable, but they create new questions: who controls spending, which audit rules apply, what happens to underspend, and which agency owns failure?
Aligned Incentives Matter More Than Pooled Money
A housing agency may be rewarded for rapid relocation while education is harmed by school disruption. A transport agency may optimise routes for average demand while special-needs transport remains unreliable. A health service may reduce waiting lists by scheduling children during school hours.
Cross-sector analysis should identify where one agency’s performance metric creates costs elsewhere.
Policy Coherence Needs a Contradiction Register
- policy or rule;
- lead agency;
- intended objective;
- education interaction;
- affected population;
- evidence of conflict;
- severity;
- repair owner;
- legal constraints;
- review date.
This sounds bureaucratic, but it can prevent far larger downstream bureaucracy by making contradictions visible early.
Cross-Sector Data Sharing Needs Purpose Limitation
Integrated services often create pressure to share more data. More data is not automatically better coordination.
Define which agency needs which field, for which decision, under what authority, for how long, and with what access controls. A common identifier can link records while access remains role-limited.
Consent Is Not the Only Governance Question
Some public services rely on statutory authority rather than consent. Others require consent for referral or data use. In every case, families need understandable information about what is happening and why where law permits.
Do not reduce cross-sector data governance to a checkbox. Authority, necessity, proportionality and safeguards matter too.
Shared Case Systems Can Create New Single Points of Failure
A unified case platform can improve coordination but also concentrate sensitive data and create dependence on one system. Access, resilience, audit logs, data minimisation and fallback procedures should be designed before the platform becomes indispensable.
Professional Cultures Need Translation
Teachers, doctors, social workers, planners and transport engineers use different vocabularies and evidence standards. “Risk,” “case,” “need,” “priority” and “outcome” may mean different things.
Joint work improves when teams make these differences explicit rather than assuming common words imply common models.
Cross-Sector Partnerships Need Boundary Rules
OECD’s 2025 paper School partnerships addressing child well-being and digital technology examines how schools work with external actors around well-being and digital challenges. The implication for system design is not that schools should absorb every social function. It is that partnerships need roles, governance and sustained capacity rather than informal referral alone.
Coordination Has a Cost
Meetings, data integration, joint planning, governance boards and reporting all consume time. More coordination is not automatically better.
Coordinate where interdependence is material. Keep interfaces simple where sectors can operate independently. A mature system knows which boundaries need bridges and which boundaries protect focus.
Use a Coordination Threshold
A practical test is to ask whether one agency’s unilateral action can materially change another agency’s ability to achieve its objective. If yes, formal coordination may be justified.
If the interaction is weak, information sharing or consultation may be enough.
Evaluate the Added Value of Coordination
Integrated services can feel intuitively good and still add bureaucracy. Evaluation should ask whether coordination reduces delay, duplicate assessment, missed referrals, family burden, cost or poor outcomes relative to the previous system.
The coordination structure itself should justify its existence.
Watch for Coordination Theatre
Common symptoms include many committees, no shared data, no budget authority, no service capacity, repeated referrals, unresolved disputes and annual reports full of partnership language but little change in the learner journey.
Coordination should be visible in faster, clearer and more reliable interfaces between services.
Case Study: The Housing Relocation Shock
Invented example: a city relocates hundreds of low-income families from one district to another during a housing renewal programme. Education receives the final address list two weeks before term begins.
Schools in the receiving district lack capacity, transport routes are not adjusted and special-needs services remain attached to the old district. No agency violated its own policy. The combined system failed.
The repair is a shared relocation trigger: once planned moves exceed a threshold, housing must provide education planners with anonymised demand forecasts months earlier, and individual transfer support activates later under appropriate data rules.
Case Study: The Clinic Appointment Problem
Invented example: children with a chronic condition attend hospital follow-ups every six weeks. Appointment slots are concentrated in school hours. Attendance data show repeated half-day absences.
Education cannot change clinical need. Health cannot ignore service capacity. Joint scheduling pilots create after-school blocks for stable follow-up cases, while complex cases retain clinical priority. The system reduces avoidable absence without turning educational convenience into a medical rule.
Case Study: The Referral That Went Nowhere
Invented example: schools are instructed to refer families facing food insecurity to a municipal programme. Teachers comply. The programme has a ten-week backlog and schools receive no status information.
The referral metric looks excellent. The service outcome does not. The repair links referral volume to capacity planning, gives schools a privacy-safe status code and creates escalation for urgent cases.
Case Study: The Digital Identity Conflict
Invented example: education, social protection and health each use different identifiers for the same child. Name differences and address changes create duplicate records.
A cross-sector identity-matching service improves linkage while keeping each sector’s access permissions separate. The improvement comes from shared reference infrastructure, not from creating one unrestricted database.
Failure Mode 1: Create a Committee Instead of a Mechanism
Repair: define decisions, owners, evidence, timelines and escalation routes before scheduling recurring meetings.
Failure Mode 2: Share a Goal but Not Capacity
Repair: map staffing, queues and budgets so referrals do not exceed receiving capacity.
Failure Mode 3: Pool Accountability Until Nobody Owns Failure
Repair: preserve named responsibility for each segment of the shared results chain.
Failure Mode 4: Share Data Because It Exists
Repair: use purpose limitation, minimum necessary fields, access control and retention rules.
Failure Mode 5: Ignore Timeline Mismatch
Repair: map planning and service calendars and define trigger points before critical education transitions.
Failure Mode 6: Turn Teachers Into Integration Infrastructure
Repair: create specialist coordination roles and clear handoffs rather than asking teachers to chase every service.
Failure Mode 7: Centralise Everything
Repair: coordinate only the dependencies that need coordination and preserve sector expertise and local flexibility.
Failure Mode 8: Localise Everything
Repair: provide national standards, funding rules and escalation so service quality does not depend on local personalities alone.
Failure Mode 9: Measure Partnership Activity Instead of Learner Friction
Repair: track referral completion, delay, duplicate assessment, family burden and unresolved dependencies.
Failure Mode 10: Keep Coordination Structures Forever
Repair: review whether the body still solves a real dependency, and retire or redesign it when the interface becomes routine.
The Cross-Sector Education Operating Chain
- Define the learner outcome or system problem.
- Map causal pathways across sectors.
- Identify which agencies control each pathway.
- Identify policy contradictions and reinforcing policies.
- Map legal mandates.
- Map service capacity.
- Map geographic responsibilities.
- Map planning and delivery timelines.
- Define a lead coordination owner.
- Define agency-specific responsibilities.
- Define shared outcomes.
- Define intermediate indicators by agency.
- Harmonise or translate key definitions.
- Design referral pathways.
- Define receiving capacity rules.
- Define escalation routes.
- Decide whether budgets remain aligned, pooled or partially pooled.
- Define data-sharing purposes and authority.
- Define common identifiers where useful.
- Set access controls and retention.
- Create national minimum standards.
- Allow local operating adaptation.
- Train frontline staff on the handoff.
- Launch with visible case/status tracking.
- Monitor delay and failure points.
- Review unintended incentives across sectors.
- Evaluate whether coordination adds value.
- Repair contradictions.
- Retire unnecessary coordination structures.
- Return lessons to sector planning.
A Policy Coherence Dashboard
- shared outcomes;
- lead agency;
- partner agencies;
- material policy contradictions;
- open dependency risks;
- referral volume;
- referral completion;
- median referral delay;
- receiving-service backlog;
- duplicate assessment rate;
- cross-sector data-sharing agreements;
- privacy incidents;
- joint budget commitments;
- unfunded responsibilities;
- local coordination coverage;
- family burden indicators;
- learner outcomes;
- unresolved escalations;
- coordination structures due for review.
Canonical Owner Boundaries
- Education Policy owns education-sector policy design broadly.
- Education Sector Planning & Annual Operationalisation owns the education-sector planning cycle.
- Student Support Referral & Case Coordination owns case-level learner support handoffs.
- School Health Services owns health service delivery within the school context.
- School Transport Operations owns school transport operations.
This node owns the coherence architecture between sectors: dependency mapping, contradictory policy repair, interagency decision rights, joint planning, shared outcomes, referral capacity, data interfaces and the accountability model that lets institutions cooperate without dissolving responsibility.
The Return Path
Return to the child who is absent.
The school sees an empty chair. The transport agency sees a route. The health service sees an appointment. The housing office sees a relocation. The social-protection system sees a household record.
The child experiences only one life.
Policy coherence is the work of making public institutions remember that fact while still preserving the expertise, legal authority and accountability each institution needs.
The public sector can remain institutionally divided without making the learner carry the cost of those divisions.
Return to the How Education Works hub.