How Education Works | School Staffing Establishments & Position Control — How Approved Posts Become Real Teachers Without Losing the Wage Bill

HEW-NODE-0077 · How Education Works · Staffing establishments, authorised posts and position control

A school can need a mathematics teacher, recruit a qualified mathematics teacher, and still be unable to appoint that person.

The reason may not be educational. It may be structural.

The school has pupils. The timetable has mathematics periods. The headteacher has identified the vacancy. A candidate is available. Yet the central establishment register still shows the old staffing allocation, the finance ministry has not released a funded post, or the payroll system will not accept an appointment that is not tied to an authorised position.

This hidden layer is called staffing establishment and position control.

It is the bridge between workforce planning and actual employment:

enrolment and curriculum need → staffing norm → approved position → funded position → vacancy → appointment → deployment → payroll → occupied post → review.

If this bridge is weak, education systems can simultaneously report teacher shortages, payroll overruns, unfilled vacancies and staff in the wrong places. If it is strong, each school can see which posts it is entitled to, which posts are funded, who occupies them, which are vacant, and what happens when enrolment or curriculum demand changes.

This article sits beside How Education Works, Teacher Workforce Forecasting, Teacher Recruitment, Teacher Deployment, Teacher Payroll, School Timetabling, School Budgeting and Education Management Information Systems.

Those pages keep their own jobs. This page does not own long-range teacher forecasts, candidate selection, deployment policy, payroll processing or school timetabling. It owns a narrower node: how an education authority defines, authorises, funds, records and controls the actual posts that schools are allowed to fill.

The 50-Second Read

A staffing establishment is the approved set of positions assigned to an organisation or school.
Position control links each person to a valid post rather than letting hiring and payroll grow independently.
Teacher need is not the same as an approved post. Need comes from learners, curriculum and workload; approval adds policy and budget constraints.
A useful position record has a unique identifier, school, subject or role, grade, funding source, status and occupant.
Headcount, full-time equivalent and number of positions are different measures and should not be mixed.
Vacancies should be visible from the same position register used for recruitment and payroll.
Temporary staff, substitutes and acting appointments need explicit treatment so they do not become invisible parallel workforces.
Transfers should move the person between positions without duplicating salary or leaving phantom vacancies behind.
Position control must be reconciled regularly with payroll, HR records, school census data and actual school rosters.
The aim is not bureaucratic restriction. It is to make sure every salary payment corresponds to a real, approved education job that still serves a real need.

One-Sentence Definition

School staffing establishment and position control is the system that converts teacher requirements into authorised, funded and traceable posts, then keeps those posts aligned with appointments, deployment, vacancies and payroll over time.

Start With a Simple School

Imagine a lower-secondary school with 720 learners.

Its timetable requires enough teaching periods in mathematics, English, science, humanities, languages, physical education and other subjects. Teachers also need time for preparation, feedback, meetings, professional learning and student support. The school therefore does not simply divide 720 pupils by a pupil-teacher ratio and obtain a trustworthy staffing number.

It must ask a more detailed question:

What combination of roles, subjects, grades and workloads is required to operate this school under the approved curriculum and staffing rules?

That requirement becomes a proposed establishment. Finance and education authorities then decide what can be authorised and funded. Each approved post becomes a position that can be occupied by one person or, in some systems, shared by several part-time staff whose combined workload equals the authorised full-time equivalent.

The position is the seat. The employee is the person sitting in it.

Confusing the seat with the person is one of the fastest ways to lose control of a workforce system.

Need, Position and Person Are Three Different Objects

A mature workforce system keeps three objects separate.

1. The need

This is the educational requirement. It may be expressed as mathematics teaching periods, counselling hours, laboratory supervision, special-support capacity or another function.

2. The position

This is the authorised job slot: for example, Teacher, Mathematics, Grade T3, School 1047, 1.0 full-time equivalent.

3. The person

This is the employee appointed to the position, with identity, qualifications, employment status, salary and service history.

A need can exist without a position. A position can exist without a person. A person should not normally receive a regular salary without being linked to an authorised employment basis.

This three-object model prevents several common errors. It stops a vacancy from disappearing merely because a teacher has transferred. It prevents one person from occupying two full-time positions accidentally. It lets a system abolish an obsolete post without deleting the employee record. And it lets planners see unmet need separately from funded capacity.

Why Education Systems Need an Establishment at All

Education ministries employ some of the largest public workforces in many countries. Teacher salaries often dominate recurrent education expenditure. That scale creates a coordination problem: thousands of schools can identify needs, but the state must still keep the total wage bill sustainable and distribute staff fairly.

The establishment is the controlled interface between local need and public employment authority.

Without it, a decentralised hiring system can add staff faster than the budget can absorb. With an establishment that is too rigid, schools can remain understaffed long after enrolment has changed.

The design problem is therefore not “control versus freedom.” It is how to make staffing rules responsive enough to education demand while preserving fiscal and administrative integrity.

The Establishment Formula

Different systems use different staffing norms. A formula may consider:

student enrolment;
class-size policy;
curriculum periods per subject;
teacher contact-time rules;
school level;
subject specialisation;
small-school minimum staffing;
special educational support needs;
language provision;
boarding or residential functions;
geographic isolation;
leadership and administration;
laboratory, library or workshop requirements;
approved non-teaching support roles.

A primary school may use a relatively simple class-teacher model. A secondary school often requires subject-by-subject calculation because a school can have enough teachers in total while still lacking physics or mathematics coverage.

This is why Teacher Workforce Forecasting and School Timetabling are important siblings. Forecasting estimates future supply and demand across the system. Timetabling proves whether the staffing mix can actually deliver the week. Position control sits between them and turns approved need into employable posts.

A Pupil-Teacher Ratio Is Not an Establishment

Suppose a system targets one teacher for every 30 pupils. A school with 600 pupils appears to need 20 teachers.

But 20 teachers may be impossible to timetable if the curriculum requires specialist science, mathematics, language, arts and technical subjects in small cohorts. Conversely, a tiny rural school may need several teachers even when enrolment would justify fewer under the ratio.

Ratios are useful planning indicators. Establishments are operating designs.

Positions Need Unique Identities

A reliable position register should not contain only a list of employee names. Each authorised post should have its own identifier.

A position record can include:

position ID;
school or organisational unit;
job family;
subject or functional specialisation;
grade or salary band;
full-time-equivalent value;
funding source;
budget programme;
permanent, temporary or project status;
date created;
date authorised;
current occupant;
vacancy status;
reason for vacancy;
planned abolition or transfer date;
approving authority.

When every position has an identity, transactions become auditable. A recruitment request refers to a position. A transfer leaves one position and enters another. A payroll record points back to the occupied position. A budget forecast can count the cost of filled and vacant positions separately.

Headcount, FTE and Positions Are Not the Same

Three measures are often mixed:

Headcount counts people.
Full-time equivalent converts working time into a standard workload.
Positions count authorised posts.

Two half-time teachers may equal two people, one full-time equivalent and one full-time position split between them. One person temporarily acting in an additional role may remain one headcount but be linked to an acting allowance or secondary assignment.

Finance, HR and education planners need to know which measure they are using. Otherwise a system can appear overstaffed in headcount while understaffed in actual teaching time.

Funded and Unfunded Positions

An education authority may approve a structural need that cannot immediately be financed.

That creates two useful states:

authorised and funded — the post may normally be filled;
authorised but unfunded — the need is recognised, but appointment requires later budget authority.

Hiding the second category makes workforce shortages look smaller than they are. Treating every approved need as immediately recruitable can create payroll liabilities without money.

The establishment register should therefore preserve both educational need and fiscal status.

The Vacancy Is a Position State, Not a Separate Spreadsheet

A vacancy exists when an authorised position has no current occupant and is available, or expected to become available, for staffing action.

If vacancies are maintained separately from the position register, the two lists drift. Recruitment may advertise a post that has already been filled, or fail to advertise a position that became vacant after a transfer.

The stronger model is event-based:

employee leaves position → position status changes to vacant → vacancy approval checks occur → recruitment or transfer fills position → vacancy closes.

One underlying object, several controlled states.

Not Every Vacancy Should Automatically Be Refilled

A teacher retires. The easiest administrative action is to recruit a replacement into the same post.

But enrolment may have fallen. Curriculum requirements may have changed. Another nearby school may now carry more demand. The departing teacher may have taught a subject that is no longer the binding constraint.

Vacancy control is therefore a review gate. Before recruitment begins, the system can ask whether the position should be refilled, reclassified, transferred to another school, converted to another subject or abolished.

This prevents yesterday’s staffing pattern from becoming tomorrow’s permanent structure by inertia.

Position Control and Recruitment

Recruitment should begin from a valid vacancy, not from a general desire to hire.

A recruitment requisition can require:

position ID;
proof the post is funded;
current vacancy status;
required qualification or subject;
school and location;
employment grade;
approval chain;
target appointment date.

Once a candidate is selected, the appointment transaction closes the vacancy and records the occupant. This is the handoff to Teacher Recruitment.

Position Control and Deployment

Deployment decides where teachers serve. Position control determines which authorised seat they occupy there.

Suppose Teacher A transfers from School North to School South.

A clean transaction should:

confirm the destination position exists and is valid;
record the effective transfer date;
end occupancy of the origin position;
create occupancy of the destination position;
update vacancy status at the origin;
update payroll coding and duty station;
update school and HR rosters;
preserve service history.

If those steps occur in separate systems at different times, the teacher can be paid against the old school, appear as an employee of the new school and leave both schools with misleading vacancy figures.

Position Control and Payroll

Payroll answers: who should be paid, how much, and when?

Position control adds another question: against which authorised post?

The strongest public-sector designs reconcile the employee, appointment, position, duty station and payroll entry. A salary cannot be explained only by a name on a list; it should be traceable to a valid employment relationship and position authority.

This helps detect anomalies such as:

employees paid after separation;
two people paid against one full-time position without authorised job sharing;
one employee occupying incompatible full-time positions;
payroll records with no current school assignment;
school rosters containing teachers absent from payroll;
staff paid under the wrong grade or funding source.

The broader salary process belongs to Teacher Payroll. This node supplies one of payroll’s most important controls: proof that the employment seat exists.

Temporary Teachers Need Positions Too

Systems often control permanent posts carefully and lose visibility over temporary labour.

Temporary teachers may cover maternity leave, long-term illness, surges in enrolment, unfilled specialist vacancies or emergency programmes. They are legitimate parts of workforce capacity, but they should not live in a shadow register.

A temporary assignment should identify:

why it exists;
which post or workload it covers;
start and end dates;
funding source;
employment authority;
whether the permanent post remains encumbered by another employee;
what event ends the temporary arrangement.

Otherwise temporary solutions can become permanent costs without a deliberate decision.

Substitutes Are Different Again

Short-term substitute coverage may not justify creating a new permanent position. The system can instead link substitute service to the absent teacher’s position or to a controlled substitute pool.

The companion Teacher Absence and Substitute Coverage page owns the continuity problem. Position control ensures the replacement arrangement does not accidentally duplicate the underlying permanent post.

Acting Appointments and Secondments

A teacher may temporarily act as a department head. A principal may be seconded to a district office. A teacher educator may return to school after a project.

These cases show why position history matters. The system needs to distinguish substantive position, temporary assignment and acting responsibility. Otherwise an acting appointment can create a false permanent vacancy or a returnee may have no controlled path back to an establishment.

Small Schools Need Minimum Viable Staffing

Pure formula allocation can punish small and remote schools.

A school with 40 pupils may still need enough adults for safe supervision, multi-grade teaching, school leadership and basic administrative continuity. The staffing cost per learner will be higher than in a large urban school.

Position control should therefore implement policy rather than blindly equalise ratios. Geographic access and minimum service obligations can justify floor staffing.

Large Schools Need Mix, Not Only Volume

A large school may have the correct total number of teachers and the wrong subject mix.

Thirty teachers cannot replace a missing physics specialist if no one is qualified to teach physics. The establishment should therefore preserve function and subject detail where it affects curriculum delivery.

This is especially important in secondary education. UNESCO IIEP’s 2024 guidance on secondary teacher management emphasises analysing teacher requirements, allocation and utilisation together rather than treating staffing as a simple count.

The Establishment Review Cycle

Positions should not be frozen forever. A regular review can use:

updated enrolment;
new curriculum rules;
class-size policy;
school openings and closures;
subject uptake;
teacher workload rules;
new inclusion requirements;
budget ceilings;
retirement forecasts;
vacancy duration;
utilisation data;
local demographic change.

A common rhythm is annual alignment with the budget and school year, with controlled in-year adjustments for exceptional cases.

Reorganisation Without Chaos

When a school loses enrolment, abolishing positions immediately can destabilise staff and learning. When a school grows rapidly, waiting for the next full budget cycle can leave classes uncovered.

A mature system uses transition rules:

freeze a vacancy before declaring a person surplus;
redeploy through attrition where practical;
allow temporary growth posts where demand is demonstrably rising;
review small changes over multiple years to avoid oscillation;
protect hard-to-recruit subjects from crude across-the-board cuts;
coordinate with transfer cycles and retirement timing.

Position control is therefore not merely a database. It is a rule system for changing organisational capacity without breaking service.

The Finance Connection

Each authorised position carries an expected cost.

That cost may include base salary, employer contributions, allowances, hardship payments, leave costs and other compensation. Budget planners need to distinguish:

cost of filled posts;
cost of vacancies expected to be filled;
cost of temporary coverage;
cost of planned new positions;
savings from abolished or delayed positions.

A vacancy is therefore not automatically a permanent saving. If the school still needs the teacher, the salary may simply be delayed until recruitment succeeds.

This is where Education Costing, School Funding Formulas and Budget Execution & Public Expenditure Tracking connect to the workforce.

The Ghost Position Problem

People often discuss ghost workers: names receiving salary without valid service. There is another problem: ghost positions.

A ghost position is an establishment record that remains active even though the school closed, the role was abolished, the programme ended or the position was duplicated during a system migration.

Unused position records can become future entry points for improper appointments. Good controls therefore reconcile schools and organisational units as well as employees.

School-Level Verification

Central databases are strongest when schools can verify what the centre believes.

A school staffing statement can show:

approved positions;
funded positions;
current occupants;
vacancies;
temporary staff;
teachers recorded as on leave or secondment;
posts awaiting abolition or transfer.

The principal certifies whether the statement matches reality. Differences become cases for correction rather than silently persisting for years.

Position Control and the School Census

The School Census may collect teacher and enrolment data annually. HR systems may update appointments continuously. Payroll changes monthly.

These sources do not need to be identical in timing, but they should be reconcilable.

If the census reports 24 teachers, HR reports 27 employees and payroll pays 29 people associated with the school, the difference needs explanation. It may be legitimate—staff on leave, district-based specialists, recent transfers—or it may reveal stale records.

Position Control as a Master-Data Problem

Several identifiers must agree:

school ID;
position ID;
employee ID;
job code;
grade;
subject or function;
budget programme;
funding source.

If one system calls a school “Central Secondary,” another “Central High,” and a third uses an obsolete code, automated reconciliation becomes unreliable. Master data must therefore be governed, not improvised locally in every spreadsheet.

The Monthly Reconciliation

A practical control cycle can compare:

authorised position register;
HR appointment records;
school roster;
payroll file;
recent transfer, leave and separation transactions.

Exceptions are classified: timing difference, approved special case, missing transaction, duplicate record, invalid appointment or unexplained payment.

The goal is not to make every data source identical on the same day. It is to ensure differences are known, temporary and resolvable.

Failure Mode 1: Hire the Person Before Approving the Seat

A school recruits urgently and expects finance to solve the funding later.

Repair: use an emergency authority with explicit duration and funding, or require a valid position before permanent appointment.

Failure Mode 2: Use Total Teacher Count as the Only Rule

The school meets its numerical allocation but cannot deliver key subjects.

Repair: include subject and functional requirements where curriculum delivery depends on them.

Failure Mode 3: Keep Vacancies in a Separate Spreadsheet

Recruitment and HR disagree about which posts are open.

Repair: make vacancy a controlled state of the position record.

Failure Mode 4: Move the Person but Not the Position

A transfer updates the school roster but payroll and establishment remain at the old location.

Repair: treat transfer as one transaction with linked updates and an effective date.

Failure Mode 5: Never Abolish Obsolete Posts

School closures, curriculum changes and reorganisations leave old posts active indefinitely.

Repair: run periodic establishment reviews and close positions through controlled status changes rather than deleting history.

Failure Mode 6: Ignore Temporary Labour

Permanent staffing looks controlled while temporary contracts accumulate outside the register.

Repair: record temporary assignments, authority, funding and end conditions in the same workforce architecture.

Failure Mode 7: Count People Instead of Workload

Part-time staff inflate headcount while teaching capacity remains low.

Repair: report headcount, positions and FTE separately.

Failure Mode 8: Let Finance and Education Maintain Different Establishments

The ministry of education believes a post exists; treasury does not recognise it.

Repair: create one governed authorisation chain and shared position identity across HR and finance.

Failure Mode 9: Freeze the Formula While the System Changes

New curriculum, inclusion requirements or demographic shifts make old staffing norms obsolete.

Repair: review staffing norms as policy instruments, not eternal constants.

Failure Mode 10: Approve Posts Without Monitoring Fill Time

A funded post remains vacant for two years and the system continues counting it as capacity.

Repair: track vacancy duration, recruitment stage and service impact.

A Staffing Establishment Dashboard

approved positions by school and role;
funded versus unfunded positions;
filled positions;
vacancy rate;
median vacancy duration;
critical-subject vacancies;
temporary staff count and FTE;
positions occupied by staff on long-term leave or secondment;
positions pending abolition or transfer;
school-level staffing variance from norm;
employee-position-payroll mismatches;
positions with no valid school or organisational unit;
schools operating below minimum viable staffing;
schools above establishment and reason;
projected wage bill for authorised establishment.

A dashboard should lead to action. A vacancy rate without subject, location and duration can hide the difference between one-week turnover and a chronic two-year shortage.

A Centre-to-Edge Position-Control Chain

National policy defines staffing norms, employment classes and workforce rules.
Education planners convert enrolment and curriculum into staffing requirements.
Finance authorities set wage-bill ceilings and fund positions.
HR authorities create and maintain authorised positions.
Districts or regions review local distribution and exceptional needs.
Schools verify occupants, vacancies and real operating need.
Recruitment teams fill valid vacancies.
Payroll pays valid employees against valid employment authority.
Audit and assurance test whether records match reality.

The chain fails when one actor believes another has already performed the control.

A Practical Design Sequence

Define the staffing objects. Separate need, position and person.
Set transparent staffing norms. Make the drivers and exceptions explicit.
Create unique position IDs. Do not rely on employee names as the structural key.
Connect positions to funding. Distinguish authorised from funded.
Make vacancy a position state. Let recruitment begin from controlled vacancies.
Integrate transfers. Move the person between valid positions with effective dates.
Include temporary arrangements. Keep substitutes, acting appointments and temporary contracts visible.
Reconcile payroll. Every paid employee should have explainable employment authority.
Verify with schools. Compare central records with actual rosters.
Review the establishment regularly. Allow positions to move, change or close as need changes.
Track exceptions. Overrides should have owners, reasons and expiry dates.
Preserve history. Close records; do not erase the trail.

Current Authoritative Guidance

Teacher-management guidance consistently treats recruitment, allocation, utilisation, information systems, careers and institutional controls as connected parts of one workforce system. UNESCO’s International Institute for Educational Planning updated its secondary teacher-management guidance in 2024, emphasising analysis of requirements, allocation and utilisation. Its teacher-management training materials likewise cover forward planning, recruitment, allocation, monitoring tools and the institutional framework that regulates the workforce. World Bank public-financial-management work has repeatedly shown why teacher payroll, staffing controls and budget systems have to reconcile: salary expenditure is too large and operationally important to manage as a detached administrative afterthought.

Exact public-service establishment rules differ by country. Some systems centralise post creation; others delegate staffing authority to school districts or schools. Some fund positions directly; others fund schools and allow local hiring within budget. The transferable principle is narrower: the education need, the authorised post, the person occupying it and the money paying for it should remain reconcilable.

Canonical Owner Boundaries

Teacher Workforce Forecasting owns long-range teacher supply and demand.
Teacher Recruitment owns candidate attraction, selection and appointment processes.
Teacher Deployment owns distribution of teachers across schools and subjects.
Teacher Payroll owns salary calculation and payment.
School Timetabling owns conversion of teachers, subjects, rooms and student pathways into the working week.
School Budgeting owns annual school-level financial allocation and use.
Education Management Information Systems owns the broader administrative data architecture.

This node owns the authorised employment seat between those systems.

The Return Path

Return to the school that needed a mathematics teacher but could not appoint one.

A mature system can now explain the blockage. The school’s timetable shows a genuine mathematics requirement. The staffing norm recognises it. The establishment register creates a mathematics position. Finance confirms the post is funded. The position becomes vacant and recruitable. A qualified candidate is appointed. HR records the occupant. Deployment places the teacher at the school. Payroll pays the correct person against the correct position. The school verifies that the teacher is actually there.

Nothing about this is glamorous.

That is precisely why it matters.

An education system can promise a teacher to every classroom only when it can trace the invisible administrative path that turns a real learning need into a real, funded, occupied post.

Return to the How Education Works hub.