Illustrative scenario
In this scenario, an établissement privé near Lyon records absences on paper, keeps marks in teacher-owned spreadsheets, and retypes both into termly bulletins. Moving them onto Skoolia makes the bulletin a product of the gradebook, absence notification same-day, and the school's RGPD position something it can state in one place.
This is a representative scenario modeled on typical Skoolia deployments for schools of this profile. The figures illustrate potential outcomes and do not describe an individual named customer.
Marks, absences and appreciations assembled per class automatically
Families told on the day rather than at the end of the week
Termly reports built from the marks already in the gradebook
Retention, access rights and processing recorded in one place
This scenario follows an illustrative établissement privé in the Lyon area covering collège and lycée, from sixième through terminale. It runs the French national curriculum, organises its year around three trimestres, and holds a conseil de classe for every class at the end of each one.
Its administrative rhythm is set by those three moments. Between them, vie scolaire records absences and lateness period by period, teachers keep their own marks, and the secrétariat holds the student file. At the end of each trimestre all three have to be brought together — and, before this scenario, that was done by hand.
Three times a year, each professeur principal spent an evening or more collecting marks from colleagues, cross-referencing the vie scolaire absence register, and typing appreciations into a document for the conseil de classe. The information all existed — it simply had to be gathered by hand, per class, every term.
Absences and lateness were recorded on paper slips collected each period and entered into a standalone register later the same day, or the next. Families were told at the end of the week. The delay meant a pattern of afternoon absences could run for several days before anyone outside the classroom noticed.
Termly bulletins were assembled in a word processor from marks that already existed in the teachers' own spreadsheets. Every transcription was a chance to introduce an error, and correcting a mark after the bulletin was printed meant reissuing the document rather than regenerating it.
Student data sat in a legacy application, several teacher-owned spreadsheets, and a shared drive. The établissement could not state, in one place, what personal data it held, how long it kept it, or how it would answer a parent's access request within the statutory delay.
In this scenario, the direction evaluates the incumbent French products alongside Skoolia and chooses Skoolia on four grounds:
Marks entered once by each teacher become the termly bulletin without a second transcription. Correcting a mark regenerates the document rather than requiring it to be reissued — which is what removes the retyping step rather than merely speeding it up.
Attendance is taken against the period the student was actually scheduled into, so an unexplained absence is visible immediately and a pattern across weeks is a query rather than an intuition.
Student records live in one system with documented retention periods and role-scoped access, so the établissement can answer an access request from a single place instead of searching a legacy application and a shared drive.
Teachers, vie scolaire, and the secrétariat work in French — including reports and notifications sent to families — rather than in an English product with French labels bolted on.
Student and staff records, class groups, and the current year's absence history imported from the legacy application and the secrétariat's spreadsheets. Responsables légaux linked to each student so notifications reach the right adults.
Class timetables, teacher availability, and room allocations entered, then the vie scolaire workflow configured — absence categories, justification handling, and the notification rules that decide which families are contacted and when.
Coefficients, assessment periods, and the school's own bulletin layout configured so termly reports generate in the format the conseil de classe already expects. RGPD retention rules and role-based access reviewed and recorded at the same time.
Separate sessions for teaching staff, vie scolaire, and the secrétariat, followed by opening the espace familles by level so the first week of parent questions arrived in manageable batches.
In this scenario, the professeur principal arrives at the conseil de classe with marks, absences, and prior appreciations already assembled per class — an evening's review rather than a week of collection. The judgement the conseil exists to make is unchanged; the assembly work in front of it is not.
Absences are recorded against the scheduled period as it happens, so families are notified the same day rather than at the end of the week. A pattern of repeated absence in a particular subject or time of day surfaces as a query rather than as something a teacher eventually mentions.
Termly bulletins are generated from the marks already entered, removing the transcription step and the class of error that came with it. Student data lives in one EU-hosted system with retention periods and role-scoped access recorded, so the établissement can answer a parent's access request from a documented position instead of a search.
The teaching judgement in a conseil de classe cannot be automated, and should not be. The gathering of marks, absences, and prior appreciations that precedes it is pure assembly — and it is where the professeur principal's evenings go.
A weekly absence report tells families what happened. A same-day notification lets them respond while it still matters — and surfaces a repeating pattern in days rather than after a term.
Every transcription between the gradebook and the bulletin is an opportunity for error, and the error is only discovered after the document has gone home. Generating the bulletin from the marks removes the class of mistake entirely.
An établissement cannot document retention or answer an access request across a legacy application, several spreadsheets, and a shared drive. Consolidation is what makes the obligation answerable at all.
Start a free trial or book a personalised demo. Implementation typically takes two to four weeks, including data migration from your current system.