weeks lost
Manual allocation
Planning room by class takes weeks of coordination and still ships with conflicts.
For higher education
Class scheduling that solves itself.
Kampus allocates every class to the right room — capacity, laboratories, shifts and each professor's rules — then runs the campus in real time: bookings, attendance, visitors and reports.
People on campus82
Missed bookings03
Peak occupancy64%
Lost to no-shows57min
The problem
Every semester starts with the same spreadsheet.
Hundreds of classes, dozens of rooms, laboratories with fixed equipment, professors with real constraints, shifts that cannot overlap — and a coordinator rebuilding it all by hand, every term.
empty rooms
Invisible capacity
Rooms sit empty while cohorts are split — because nobody has live occupancy data.
attendance
Paper registers
Attendance is collected on paper, typed up late and impossible to audit.
campus
Open buildings
Laboratories, libraries and blocks with no control over who enters and when.
How it works
Four steps to a conflict-free semester.
Select the rooms, the cohorts and the subjects, write the rules that actually govern your campus — and let Kampus resolve the rest.
1Select the rooms
Rooms
Classrooms, laboratories and lecture halls with capacity, building, block and resources.
2Select the cohorts
Cohorts
Each cohort with its size, course and semester — Medicine 2022.1, Dentistry 2021.2.
3Select the subjects
Subjects
Subjects, workload, allocated cohorts and the professors who teach them.
4Add the rules
Rules
“Anatomy I always uses the anatomy lab at night.” Write the exception once.
The engine
Weeks of work, resolved in minutes.
The allocation runs against every rule you defined, optimising room occupancy across the whole campus. Conflicts come back listed with the class, professor, room and time attached — and every run autosaves with an author and a timestamp, so a version can always be rolled back.
Rule-basedConflict detectionVersion historyRe-runnable
Beyond the timetable
Then the semester actually runs.
Allocation is where Kampus starts, not where it stops. Once term begins, the same platform carries the day-to-day operation of the campus.
Live campus occupancy →
How full a room really is, class by class — not how full the timetable says it is.
Digital attendance →
Students confirm presence with their face or Digital ID. The register closes before class starts.
Access by enrolment →
Who may enter which block, which laboratory, at which hours — tied to the academic record.
Part of something larger
Built on the Skedway platform.
Kampus is a Skedway product. It runs on the same workplace intelligence platform deployed across more than 70 countries, and on the same device family — Arc panels, presence sensors and access control — reconfigured for campus work.
That means an institution adopting Kampus is not buying a first version of anything. The sensing, the access layer and the analytics have been running in large enterprises for years.
70+countries with Skedway deployed
1M+users on the platform
200+enterprise clients
2×Best of Show at InfoComm