> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ardoiseeduc.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Academic: grades, report cards, attendance
> Grade entry, the report card lifecycle, homework, attendance and discipline.
This page concerns Ardoise School in the OHADA scope, subject to enabled modules and permissions. School, school accounting and payroll are not offered in Austria. Check local requirements; CountryConfig does not certify compliance.
## The lifecycle of a report card
A report card always follows the same order:
Each teacher enters the grades for their subject, for their class.
The Supervisor enters attendance, lateness and each pupil's discipline score.
The Censeur generates the term's report card and **validates** it.
Once validated, the report card becomes visible to parents (marketplace portal) and printable by the secretariat.
A report card cannot be changed after validation without going through this circuit again - that is deliberate: it guarantees that a report card handed to a family matches exactly what the Censeur validated.
## Exam papers
An exam paper follows its own circuit, separate from the report card's, because it carries a
constraint the report card does not: **it must stay secret until the exam is sat**.
### The exam session
The Censeur first schedules the **session**: the class, the subject, the exam period (defined in the
school's academic calendar), the date, the start and end time, and the room. It is the session that
fixes when the exam is sat - and therefore the moment from which the paper may stop being
confidential.
The teacher chooses neither the exam period nor the class/subject: they follow from what the
Censeur has scheduled and from what the teacher already teaches.
### The paper's circuit
The teacher writes their paper in Ardoise - headings, numbered questions, marking scale, tables,
images, page breaks and **mathematical formulas** - or uploads a file already prepared. The
paper carries the teacher's name and the subject.
Once ready, the paper is submitted to the censorat. A version is frozen at that moment, so that
what is reviewed is exactly what was submitted.
The Censeur reviews the laid-out paper and **validates** it, or asks for changes, stating what
must change. A returned paper goes back to the teacher.
A validated paper goes to the secretariat for printing, school letterhead included.
Pupils sit the exam on the scheduled date and time.
The teacher enters marks **question by question**. The total feeds the pupil's grade in the
same grade book as everything else - there is no second marking system.
Once the exam has been sat, the paper can be published as a revision resource.
### Confidentiality
A pupil **never** has access to a paper being written, submitted, validated or upcoming - not
through the interface, not through a direct link to the file, and not through search. The only
thing a pupil can see is a paper **published to the library after the exam**.
The **marking scheme** is kept separately from the paper: validating a paper never makes its
answer key visible.
### Publishing a paper after the exam
Publication is never automatic, and it is refused as long as the exam is not over.
Concretely, for an exam scheduled on 25.08.2026 from 09:00 to 11:00, the paper cannot join the
library before 11:00 - and the button states the exact reason for the refusal rather than simply
being inactive. An exam with no scheduled session cannot be published at all.
Publishing the paper does not publish the answer key.
## Homework
A piece of homework is an exercise a teacher sets for their class, with a hand-in date. Homework
is deliberately **outside the exam paper approval circuit**: no submission to the censorat, no
separate marking scheme, no confidentiality window. Forcing that validation chain onto every
exercise set for Tuesday would make no sense.
### Setting work (teacher)
Each teacher creates homework for the subjects they teach, and only those: it is impossible to
set work in a colleague's subject or to mark their copies. A piece of homework carries a title,
instructions (rich text), a hand-in date, a maximum score (out of 20 by default, like the rest of
the grade book) and an "accept late hand-ins" setting.
Homework saved as a **draft** stays invisible to pupils. On **publication**, every pupil in the
class is told through the notification centre, exactly once: editing and republishing the work
does not produce a second message.
### Doing the work (pupil)
The **Homework** entry in the student portal shows a single list, ordered by urgency, where every
row already says where it stands: overdue, due today, due tomorrow, handed in, handed in late, or
the mark received.
Opening a piece of work puts the instructions and the writing space on the same screen. The
pupil's draft is **saved automatically** as they write; nothing reaches the teacher until they
hand in, and the text survives a dropped connection or a change of page.
Once the work is **handed in**, the copy becomes genuinely read-only: the pupil can no longer
change it.
### Late hand-in
If the teacher accepts late hand-ins, work handed in after the date is still accepted: it is
simply **marked as handed in late**. That is a statement of fact, never an automatic penalty;
what the lateness costs is the teacher's judgement. If late hand-ins are refused, hand-in closes
at the due date.
### Marking and notification
The teacher sees, per assignment, who has handed in and who has not, then marks each copy (out of
the assignment's maximum score) with optional feedback to the pupil. The pupil is told about
their mark through the notification centre they already have; re-marking a copy does not produce
a duplicate.
## Timetables
The censeur opens calendar and planning, checks the year, classes, subjects, assigned teachers and weekly workload, then uses automatic generation. Configure teaching periods in the current flow with non-overlapping start/end times. Explicitly confirm replacement when a grid already exists.
Google OR-Tools CP-SAT respects exact minutes: **2.5 hours = 150 minutes**, without rounding to three hours. Periods must be able to compose that workload. Current constraints prevent teacher/class overlaps and cap a subject at 120 minutes per day. Solving is deterministic for the same input and configuration.
Read the returned state: `OPTIMAL` means the model's objective was optimised; `FEASIBLE` means an admissible solution was found without proof of optimality. Review the grid before use. Invalid input, an infeasible solve or a persistence failure must preserve the previous grid.
Structured per-slot teacher availability, physical-room capabilities, durable period configuration, dated holiday exceptions and deeper preference optimisation remain incomplete. Holidays visible in the calendar do not automatically become solver constraints. Teachers view their own slots in their portal.
## Discipline and attendance
Each pupil starts the year with a stock of discipline points (configurable per school). Incidents and absences entered by the Supervisor adjust that score, which then feeds the report card.
## Extracurricular activities
Activities (sport, clubs, tutoring) are created by the management or the Censeur; pupils sign up through the secretariat or, depending on the configuration, directly through their parents.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.