Streamlining management at schoolSecurity & your dataEverything it doesBlog
EduBoldBook a demo

Build your timetable/The film

An empty grid is not a timetable.

EduBold does more than hand you an empty grid. Define the periods, rooms, teaching demand and constraints, and a constraint solver places the working week.

R-033Plays on YouTube, with sound. Open on YouTube

Build your timetable/The problem today

Most timetable software hands you a grid and wishes you luck.

Somebody spends weeks of the summer placing every period by hand, keeping track of which teacher is where and which room is free.

Then a teacher leaves or a section is added, and it is wrong by the second week of term.

An empty grid with a login is not software.

Build your timetable/In the film

What you give it, and what it gives back.

  • You definePeriods, rooms, demand
  • You addConstraints, preferences
  • You setA time limit
  • It placesThe whole week
  • It reportsA score you can compare
R-033How the timetable engine works, as the video describes it.

Build your timetable/What EduBold changes

From the school’s rules to a placed week.

  1. Describe the school.

    Periods, rooms and the teaching demand for each class and subject.

  2. Add the rules.

    Constraints are records you create, test against a context, and switch on or off. Teacher preferences go in as part of the solve.

  3. Generate.

    A scheduler places lessons greedily and backtracks where it has to, within the time limit you set.

  4. Compare and check.

    Each timetable carries an optimisation score and placement statistics. Clashes are found, ranked and given suggested fixes.

What EduBold does here

  • Places the whole week from your periods, rooms, demand and constraints
  • Takes teacher preferences into the solve, and scores how well each was met
  • Scores each timetable, so two attempts can be compared
  • Finds clashes, ranks them and suggests fixes

Build your timetable/Questions

What a school asks about this.

How does the timetable generator work?

It is a classical constraint solver. It places what it can greedily and backtracks where it has to, within the time limit you set.

What if the whole week cannot be placed in time?

When the time limit you set runs out, it stops backtracking and places the rest greedily, so it always returns an answer. If it cannot run at all, it says so plainly instead of leaving an empty timetable.

Can teachers’ preferences be included?

Yes. Preferences are an input to generation, and a satisfaction score shows how well each teacher’s preferences were met.

Read what the film says

Ask most school ERPs about the timetable and they hand you an empty grid to fill in yourself. Which is not software. That is graph paper with a login. Somebody spends three weeks of their summer on it, and it is wrong by the second week of term. EduBold generates it. You define the constraints, the periods, the rooms and the teaching demand, and a constraint solver places the entire week: greedy where it can be, backtracking where it has to be.

Next

See it with your own school’s records.

A demo is half an hour, and it runs on your data, not our sample. Tell us this film is the part you want to see, and we will start there.