Management indicators H/E and I/O at the start of the school year in the public sector

Open data API in a single place

Provided by DEPP – Ministère en charge de l’éducation nationale

Get early access to Management indicators H/E and I/O at the start of the school year in the public sector API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.02.06 21:32
Created
2024.09.17
Available languages
English
Keywords
second-degre, encadrement, service-des-enseignants, ressources-humaines, public, personnels
Quality scoring

Dataset description

This dataset presents the management indicators H/E and I/S **at the start of the school year** , by institution and level of training as well as the totals by department and by academy. **H/E indicator: weekly teaching hours per pupil (number of hours per pupil)** This indicator corresponds to the ratio of the number of weekly teaching hours delivered by teachers at a given level of training to the number of school-status pupils at that level of training. It depends in particular on the schedules of the programmes and the sizes of the divisions (or classes) in which the lessons are taught. An H/E indicator of 1.5 means that for every 100 pupils, 150 teaching hours of teachers are mobilised. **H** corresponds to the number of hours of weekly instruction provided in front of pupils **E** is the sum of the students in the entire class The observed differences in H/E must be compared with the number and size of schools (the smaller a school and therefore the more small a department has, the higher the H/E) and the distribution of education levels (the more vocational training is present, the higher the H/E). In addition, the numbers taken into account in the H/E are those of the classes. However, many lessons are taught in front of groups of students. A second indicator is therefore used: the average number of pupils per structure (whole class or group), I/O. This makes it possible in particular to analyse the differences in the means allocated per class (I/O) to the average number of pupils per given structure. **I/O indicator: pupils per I/O structure (average number of pupils per structure)** Average number of staff in the structures (whole classes or groups) weighted by the number of teaching hours provided in each structure. It makes it possible to estimate the number of pupils with school status for whom a teacher is responsible on average for one hour of lessons. It is lower when students attend classes in small groups than when classes are delivered in front of entire classes. **E**: number of pupils in a structure weighted by the number of teaching hours provided in that structure **S**: Number of weekly teaching hours in front of pupils NB: If the headcount of a structure is less than 2, the numerator and denominator of the I/O indicator shall be noted as missing for that structure. Thus, the sum of the number of teaching hours per institution and level of training used for the I/O calculation may differ slightly from that used for the H/E calculation. Indicators can take the value "ns" when they are not significant, usually due to a very low number of students in the level of training. The date of observation shall be 1 November of each year. This date varies between institutions and from year to year from 1 September to 15 December.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks