Gestisci
The accounts of the school’s students and staff, from arrival to departure: created, kept in order and closed by a program that checks everything before acting.
Gestisci (Italian for "manage") was born from a simple fact: in a school with more than three thousand accounts across students, teachers and staff, digital accounts change every year. First-year students arrive, final-year students leave, substitute teachers come and go, and someone always forgets their password on the first day of school. Doing it all by hand means mistakes, duplicates and forgotten accounts left open. Gestisci grows out of my work as administrator of the school's platform, to follow every account through its whole life. It is an internal tool, which is why it is only described here.
What it does
- New staff from the school office: the office fills in a form for every arrival, extension or departure; Gestisci collects the requests, merges duplicates (even when the same person is entered twice) and prepares the new accounts, with a welcome email.
- Students moving up a year: in September it compares the class lists with the existing accounts, moves everyone into the right class and identifies those who have left the school.
- No duplicates: before creating an account it checks that the address doesn't already exist, perhaps parked somewhere else.
- Class teacher groups: it keeps them in line with the lesson timetable, including support teachers and language assistants, so that messages for each class council reach the right people.
- Departures: it finds accounts still active for people who are no longer part of the school and prepares their suspension, to be confirmed one by one.
- Password resets: a single procedure for students and staff, with the instruction message ready to send, and a list of accounts that were created but never activated.
The principle: see before you act
Gestisci never acts blindly. Every operation first goes through a plan that shows exactly what will change: accounts to create, move or suspend. Everything can be tried out in a dry run, and only what has been checked is carried out. Operations already completed are not proposed again, and uncertain cases, such as two people with the same name, are never decided automatically: a person decides.
How it is built
A Python application that talks to the school's platform through its official interfaces, with a form for the school office. Like all my projects: zero lines of code written by hand.