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.
Everything a department needs, nothing more.
The engine tries many combinations and keeps the one that respects availability, rooms, capacity and teaching hours.
Happy with a slot? Lock it, then regenerate: it will not move again.
Every teacher gets an account and ticks their own slots. No more chasing anyone.
Capacity, projector, outside bookings: rooms are assigned with full knowledge of the constraints.
One overall timetable per semester, plus an individual timetable for each teacher.
Every approved timetable is kept and time-stamped. You always know which version is the reference.
Three uses, three levels of access.
You control the whole structure: programmes, assignments, rooms, generation and approval.
You reach your own space: your availability, your subjects and your timetable.
Accounts, roles and approved versions: administration stays in control without going into detail.
Three situations every department will recognise.
One degree, three tracks, forty teachers including many part-timers
Availability trickles in by email all through August; the "final" timetable changes four times before term starts.
Each part-timer ticks their slots in their own space. Generation is rerun in minutes with every new answer, without undoing what is already approved.
A master's programme short on rooms, only one with a projector
The equipped room goes to whoever asks first; the classes that actually need it go without.
Capacity and equipment are declared once and for all: the engine never assigns an unsuitable room.
A teacher becomes unavailable on Tuesdays, two weeks before term
The whole week has to be rebalanced by hand, at the risk of creating new clashes.
Their availability is corrected, the slots that still work stay locked, and a new proposal is generated for the rest.
Illustrative use cases: these examples describe typical situations, they are not testimonials.
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