Skip to main content
Spanworth

Menu

Book a demo

Timetable changes

When the timetable changes mid-week.

An edit spreads through paper and chat. The day the college teaches is whichever copy arrived last.

Friction

What breaks on paper

How the mess shows up when fees, attendance, or the timetable run in silos.

  • The edit travels sideways

    A room change or group swap lands in a message, a printout, or a local file. The clerk never sees a single pending queue.

  • Pending is invisible

    Professors teach from a draft that was never approved. Attendance sessions follow that draft or never appear at all.

  • The calendar is ignored

    Holidays and day substitutions live in another sheet. Working dates and substituted weekdays do not drive the sessions people mark.

Already live

The flow already running

How Spanworth holds the same work end to end, without a side spreadsheet.

  1. The edit

    The professor opens Schedule, fills subject, course, group, and room on a slot, and submits. New or changed slots stay pending.

  2. The wait

    The clerk opens Schedule Approval, filters to Has pending, and reviews subject, group, day, hour, and room.

  3. The decision

    Approve when the slot is correct. Reject with a required note so the professor can fix without another meeting.

  4. The calendar

    Working days, holidays, and day substitutions stay with the clerk. Sessions fire on those dates against approved slots.

  5. The day

    The college teaches the approved timetable. Attendance opens against that day, not the copy still in a chat.

Span

Where that record lives

Open the live capability that already closes this mess, then the role that runs it.