Skip to main content

Moving a lesson

Dragging lessons around the week — placing from the drawer, what a double lesson needs, and whether the app should let you create a clash.

Placing a lesson is a drag. Pick it up, drop it where it should go, and the grid updates.

Lessons come from two places: the grid itself, when you are moving something already placed, and the unassigned drawer, when you are placing something for the first time. The gesture is the same.

While you drag near the edge of the window, the grid scrolls with you, so a long timetable does not have to be moved in stages.

Allow conflicts, or block them

The switch beside the Conflicts count. Allowing a clash is the default, because timetabling is iterative — switch to blocking once you are past that stage.
The switch beside the Conflicts count. Allowing a clash is the default, because timetabling is iterative — switch to blocking once you are past that stage.

Beside the Conflicts button there is a switch with two settings, and it is the single most important thing on this page.

Allow conflicts is the default. A drop onto an already-busy slot is permitted, the clash is created, and the grid flags it. Block conflicts refuses that drop instead and shows a message.

Allowing conflicts is the right default, and not a lax one. Real timetabling is iterative: you often need to put a lesson where it clashes, see the shape of the problem, and fix it from there. A tool that refuses the intermediate step forces you to solve everything in your head first.

Switch to Block conflicts when you are past that stage and want the app to stop you making the timetable worse.

Note that a slot holding another lesson is not automatically a clash. Two lessons can share a slot quite legitimately when they involve different teachers, rooms and groups — that is parallel teaching, not a double-booking. What counts as a conflict is a shared resource, not a shared cell.

Someone working through a share link may have this decided for them: a link can be issued in block-conflicts mode, and then the switch is visible but fixed.

Double and triple lessons

A lesson longer than one period needs somewhere its whole length will fit.

Two different rules apply, and they behave differently:

It must fit inside the day. In the normal day × time view, a triple lesson cannot start in the second-to-last period, because it would run off the end of the timetable. This is physical, and it applies whatever the conflict switch says.

Whether the slots it covers are free is a clash question, so it follows the switch. With conflicts allowed, a block may overlap parallel lessons in the slots it spans, exactly as a single-period drop may. With conflicts blocked, every slot it covers has to be empty.

Dragging in a pivoted view

When the Lens has pivoted the grid to rooms, teachers or student groups, a drop does more than move the lesson in the week: it also assigns it to the row you dropped it on. Dropping a lesson onto the Lab 2 row puts it in Lab 2.

The student-group pivot is the exception. There, a lesson that already has groups cannot be dragged out of its row — it moves in time only. Changing who is taught is a real edit, and a stray drop should not quietly add a cohort to a class. The exception to the exception is a lesson with no groups at all: that one can be dropped into a row, because a first assignment is unambiguous.

What cannot move

A lesson locked in time cannot be dragged, in any view. A lesson locked only in space (its room) can still be dragged to another time, except in the Rooms view, where a drag would change its room. If a drag will not start, check the lock state on its card.

Undoing

The undo control in the header reverses recent moves, and Ctrl+Z does the same.

If you have gone further than undo can reach, restore a backup — and if you are about to attempt something large, take one first.