Vklass schema is built into Vklass but does not lock you into Vklass. The tool can run entirely standalone and exposes an open, OpenAPI 3-specified API that reads and writes the school's data in both directions. The timetable should never be the reason you cannot choose the systems that suit your organization best.
Vklass schema fetches base data and existing published lessons from Vklass into the timetabling work, and finalized timetables are published back to Vklass. The same data is used in the timetabling tool, in the platform and in every exchange. The other exchange routes are described below.
For schools using Vklass as their learning platform, the timetable is part of the platform, and no integration is needed. Vklass schema reads schools, classes, teaching groups, students, teachers and rooms directly from the same database as the rest of Vklass. You log in with the same account as in the school's other everyday work: federated, with strong e-identity or split by role (see sign-in on your terms).
There are no duplicate registers and no sync errors at the start of term. When the student register is updated in Vklass, the timetabling is already in step.
Permissions for organization, school and timetabler carry over from Vklass. There is no extra account to administer and no separate user management.
Finalized lessons are published to Vklass and reach teachers, students and guardians in the schedule they already use. A preview shows exactly what will be published before you finalize.
Vklass analys works with lesson data in Vklass. Vklass schema creates the planning basis for the entire school year and publishes finalized lessons to the Vklass lesson register, which is the same register that Vklass analys reads.
The Teaching Time report shows scheduled, offered and canceled time per subject or course. For core subjects, there is also a view of weekdays and time blocks, plus school-level correlations between lesson time after lunch and average grades. Correlations need to be interpreted in context and do not show causation.
Vklass schema keeps the lessons' weeks, day, time and length together with groups, classes, teachers and rooms. That gives a structured picture of how teaching and resources are planned before the timetable is finalized.
When the timetable is finalized, the lessons are published to the Vklass lesson register, with a preview that shows exactly what will be written before you confirm. The lesson sync in Vklass analys then works with the same lessons. The result is a chain from planning to follow-up with no files in between.
Vklass analys does not currently fetch room or room capacity in this flow. Facility and capacity utilization is therefore not part of the connection described.
Vklass schema can run entirely standalone, independently of Vklass, the learning platform. Base data is then fetched from your student information system through the open API. Finished timetables are delivered onwards to the systems you already use: learning platform, attendance application or an app for guardians.
That means you can choose Vklass schema for the timetabling alone without changing anything else in your system map. A later change of learning platform or student register does not affect the timetabling work either.
The API is built on an open, OpenAPI 3-specified information model for school data (the SS 12000 specification) covering persons, groups, activities and calendar events across the school's operational processes. Vklass schema implements it in full, in both directions.
Classes, groups, students and teachers are imported from the student information system through the API. You load the system's export directly into the tool's base data view. Persons, duties and group memberships are mapped automatically and without supplier-specific customization.
If you create classes and teaching groups in the timetabling tool first, the student information system can fetch the base data from Vklass schema through the same API. Then no one has to re-register it by hand.
Finished lessons are exposed through the API. Any absence or attendance application that supports the information model for lesson import can therefore fetch the timetable from Vklass schema without a custom-built integration.
The information model specifies data exchange between school administration, work distribution, timetabling, attendance management and grade management. It gives the school's systems one common language.
The API is fully open to you as a customer, for both reading and writing. Your systems can read, create, modify and delete every schedule data object (persons, groups, rooms, activities and calendar events) through a write API. It follows the same object model as a compatible extension.
The API uses OAuth 2.0 with client credentials and Bearer tokens and has standardized error responses (Problem Details). Versioning announces deprecated versions well in advance with Sunset headers, following established public-sector REST API guidelines.
Organization administrators can access complete interactive API documentation (OpenAPI 3) directly from the tool. There they can test calls and view schemas and fields without waiting for an integration consultant.
Up to one million API transactions per month, with adjustable limits per hour, day and week for each customer. Every call is logged and the log is visible to organization administrators. That gives full traceability of which systems have fetched and changed what.
Not everyone in the group attends every lesson session. Vklass schema therefore supports plus and minus students: individual students can be added to or removed from specific lesson sessions without changing the teaching group.
A student joining another group for occasional sessions is added to the lesson and appears in the teacher's attendance list. The student stays in their ordinary group.
A student with an adapted study program is removed from individual sessions. The lesson disappears from the student's schedule and the attendance list is correct for the teacher.
Plus and minus students are included when lessons are exposed through the API, so attendance lists are correct in receiving systems too.
Vklass schema imports timetable data from the exchange formats your current timetabling and student information systems already produce, so you start from a ready-made basis instead of an empty timetable.
Open an export from your current tool in Vklass schema. Lessons with time, date, group, teacher signature, subject and room follow along, so you get a ready-made basis instead of an empty timetable to start over in.
Vklass schema exports in the other direction too. A timetable built in Vklass schema can be delivered onwards to the school administrative systems you already use, through the API or established exchange formats.
The format support makes the switch controllable: import with a validation report, shadow timetable and comparison on your own data before you decide. You can also go back just as easily.
Switching timetabling tools should be a controlled decision. That is why we work step by step, and you see your own timetable in the tool before you decide.
We go through your current timetabling basis together, for example an export from your existing tool.
Your timetable is loaded into Vklass schema and you receive a validation report showing the state of the data before anything changes in your operations.
You build the next timetable in Vklass schema in parallel with your current process, with the same groups, teachers and rooms.
Compare the results side by side against criteria you set in advance: gaps, day lengths, teaching-time plan and qualifications. Decisions are made on facts.
The timetable is finalized and published to Vklass or through the API to your systems. During the first weeks you get extra close support.
Standards are our way of competing on trust: you should choose Vklass schema because it is the best fit and not because it is hard to leave.