Everywhere, building a timetable is still the chore of the new term.
Weeks spent in a spreadsheet, rooms booked twice, teachers chased by email, and a single cancellation that sends you back to the start. PariocAgenda takes your programmes, your teachers, their availability and your rooms, then builds a timetable that respects every one of your constraints. You get your time back — and your term.
Nobody volunteers for the timetable. Here is why.
Copy, paste, shift one row, start again. The file grows until nobody dares touch it any more.
A teacher in two places at once, a room booked twice: clashes are often discovered on the day itself.
Chasing forty teachers, merging their answers, and dealing with those who reply after publication.
One teacher unavailable on Tuesday and the balance collapses: hours cascade across the whole week.
The real cost is not only the time spent. It is the mental load of work you know is fragile, that you redo every semester, and whose every mistake is paid for in front of students.
You describe your department. PariocAgenda handles the rest, semester after semester.
Degrees, modules, subjects, credits, group counts and teaching hours. Entered once, reused every year.
Who teaches what, for how many groups, and when they are available. Each teacher fills in their own availability.
Number, capacity, projector, existing bookings. The engine will never offer a room that is too small or already taken.
The engine builds the semester timetable. Lock what works, regenerate the rest, then approve and share as PDF.
No database to install: your data stays in CSV files, on your own hosting.
The same job, without the lost weeks.
You no longer carry a file nobody else understands. Constraints are written down, checked and replayable at will. What used to be a dreaded project becomes ordinary work.
Factual answers about PariocAgenda: what it does, who it is for, and what happens to your data. Every answer stands on its own.
PariocAgenda is timetabling software for university departments and schools. From your programmes, your teachers, their availability and your rooms, it builds a complete semester timetable in minutes, with no room or teacher clashes. It is published by Parioca Technology and runs in a browser, with nothing to install on individual computers.
The engine explores a large number of slot combinations and keeps the one that satisfies four families of constraints at once: the availability declared by each teacher, room capacity and equipment, the number of groups per subject, and the teaching hours set by the curriculum. Clashes are therefore not fixed afterwards — they are ruled out by design. The grid covers six days, Monday to Saturday, and eight slots per day.
Six features cover the whole cycle: constraint-based generation; locking a slot that works, so it never moves again in later runs; availability entered by teachers themselves from their own account; room management including capacity, projector and outside bookings; PDF export ready to share; and a time-stamped record of every approved version.
Two PDF outputs are produced in one click: the overall timetable for the semester, and an individual timetable for each teacher. Every approved version is kept with its date and time, so you always know which version is the reference and what changed between two publications.
Three audiences, with three distinct levels of access: programme leads, who build and approve the timetable; teachers, who declare their availability and consult their schedule; and management and administration, who handle accounts and follow approved versions. Each person only reaches what concerns them.
They control the whole structure: entry of the curriculum (degrees, modules, subjects, credits, groups, teaching hours), teacher assignments, room declarations, generation, locks and targeted regeneration, then approval and PDF distribution.
Every teacher has a personal account where they tick their available slots, check the subjects and groups assigned to them, and download their timetable as a PDF. Availability is no longer collected by email: it is entered at source by the people concerned.
The overview: account and role management, a view of each teacher's teaching load, and access to approved timetables, dated and archived. Administration stays in control without going into slot-level detail.
No database is needed: PariocAgenda works with CSV files placed on your own hosting. Your data therefore stays with you, readable and exportable without any special tool, and installation amounts to copying the software files onto a PHP server.
Most of the work is the initial entry of the curriculum and the rooms; it is done once and reused every year. Once that structure is in place and availability has been filled in, generating a semester timetable takes minutes — and so does regenerating it after a change.
Their availability is corrected in their own space, the slots that still work stay locked, and the engine regenerates only the rest. You get a fresh, consistent proposal without undoing what was already approved and without rebalancing the week by hand.
PariocAgenda handles neither enrolment, nor grades, nor invoicing: it is not a student information system, but a tool dedicated to building and sharing timetables. It sits alongside your existing system rather than replacing it.
Access is opened institution by institution. Write to us through the contact form on this page, stating your institution and your role: we reply with a demonstration and the access terms for your department. Institutions already set up simply use the "Log in" button.
A question that is not answered here? Write to us — the answer will join this page. Page updated on 05/10/2026
A question, a demonstration, or access for your institution?
contact@parioca-technology.com
+33 1 23 45 67 89
12 rue de la Stratégie, 75008 Paris