ABOUT

Built inside a real school, for the people who run its week.

Not a startup that went looking for a problem. A school problem that needed a real engine, built where the problem was, and still running there every term.

Who builds it.

Leo Bancroft

Co-founder · engine and infrastructure

Wrote the constraint engine, the curriculum packs and the infrastructure it runs on.

LinkedIn ↗

Erik Gerbst

Co-founder · product and schools

Works across the product and the way it presents itself to the schools that buy it.

LinkedIn ↗

Two people. When you email support, you reach one of them — not a queue, and not a reseller. The company posts at LinkedIn.

Timetabling is the hardest administrative job in a school, and we refused to fake it.

Most tools flatten every school onto one grid and leave the hard part to a person with a spreadsheet and three weeks of August: reconciling every student’s subject choices against every teacher’s availability, every room’s capacity and every curriculum’s minimum hours — all at once, for everyone, with no exceptions allowed.

Schedual runs a genuine constraint-satisfaction solver, the same class of engine used in industrial logistics. It does not draft something plausible for you to correct. It returns a week in which every hard rule holds simultaneously, or it tells you precisely which rule cannot be satisfied and why.

École Privée Bilingue Internationale, Geneva. Running the published week since 2025.

How Schedual came to be.

An international school in Geneva runs the IB Primary Years, Middle Years and Diploma programmes together — nine hundred and ten students sharing one set of teachers and rooms across three entirely different curricular models. Its timetable was built by hand every year. Every year it cost weeks, and every year it still produced clashes that only surfaced once students received their sheets.

We built the engine for that school first, and it has generated its live published week since 2025. Adding IGCSE, GCSE and A-Level, the French Baccalauréat and US high schools did not require a second product: the solver core is curriculum-agnostic, and each system is described to it as a pack — what its stages are, and how its students choose.

910students on one live solve
3IB programmes running together
58 sto a full whole-school week
2025in production, every term since

What we optimise for.

Correct before pretty
A timetable that looks tidy and breaks one rule is worth nothing. Hard constraints hold, or the week does not publish. We would rather tell you a week is infeasible than hand you one that quietly is not.
The whole job, not the demo
Generating a grid is the easy half. Publishing it, getting it into every pocket, covering an absent teacher at 07:40, exporting to Pronote, and keeping last term’s version to compare against — that is the job.
Your data stays yours
Self-hosted on European infrastructure we control. Age-encrypted daily backups with a 30-day object lock. No third-party analytics, no ad tech, and we never train a model on your school.
Honest about limits
We say what the solver cannot do, and we say when a school’s constraints are genuinely unsatisfiable rather than pretending otherwise. A tool that oversells itself costs a coordinator their August.

Schedual SAS, hosted in the European Union.

A French company. Student data sits on European infrastructure we control, with a signed data processing agreement available on request and a plain list of everything we hold.

Talk to us