Introducing school software

Introducing school software: how the switch works at a school

The hardest question when a school goes digital is rarely which program is the right one. What is hard is the way there: who has a say, what does the data protection check say, when is the right moment, and how does the staff come along? This guide describes introducing school software for what it is – an organisational project with a software part to it. It is useful even if you end up choosing a different system.

Coming soon

  • GDPR-compliant
  • Hosted in Germany
  • Free for teachers

A product of SavePaper.work

Benefits

What an introduction really hangs on

Ask the people involved early

Staff, the staff council, parents' representatives, the data protection officer and the school authority do not pick the product – but they can stop it. Anyone who hears about a decision only after it was made has little reason to go along.

Data protection before the decision

Processing agreement, server location, roles and deletion concept belong in the assessment, not in the follow-up. Sign first and check afterwards, and the school ends up with a promise it cannot keep.

Start small, not big

One class or one module, a fixed run time, success criteria agreed in advance. A pilot that does not carry costs half a school year – a full launch that does not carry costs the trust of the staff.

Time the switch properly

At the turn of the school year, classes, courses and assignments are set up afresh anyway. Switching mid-term means doing the same work twice: once in the old system and once in the new one.

How it works

The introduction in four stages

From taking stock to regular operation is roughly one school year, but not a full-time project. The four stages can be managed alongside teaching if they come in this order.

1 2 3 4
  1. 1

    Take stock

    Write down what runs where today: the class register on paper, grades in spreadsheets, cover lessons on the noticeboard, parent contact through private messengers. That list is the basis – it shows what a system should replace and who is involved.

  2. 2

    People and data protection

    Get staff, the staff council, parents' representatives, the school authority and the data protection officer around one table before a decision is made. What the involvement requires in detail, and who can demand it, the federal states regulate differently.

  3. 3

    Pilot in one class

    One module, one class or one year group, for half a school year. Agree in advance what you measure success by – for instance that absences are logged at the end of the lesson and not on Friday.

  4. 4

    Roll out at year change

    The turn of the school year is the window: classes and assignments are set afresh anyway. From then on one way applies, and the paper route beside it stops on an agreed date.

In comparison

What carries an introduction – and what breaks it

Introduction with a plan
Scope at the startOne module, one class, a fixed run time
ResponsibilityOne named contact person in the building
The old wayPaper ends on an agreed date
Data protectionChecked and documented before the decision
Introduction on the side
Scope at the startAll modules at once for everyone
ResponsibilityWhoever happens to have time is in charge
The old wayPaper and system run in parallel indefinitely
Data protectionHanded in later, when somebody asks
In detail

Introducing software at school: three questions first

Who should be at the table early

School software touches almost every role in the building, and each of them can carry the introduction or stop it. The school management decides and is accountable. The staff work with it daily and are the first to notice when a route takes longer than the previous one. The staff council or teacher representatives have to be involved as soon as a system can report on working hours or the performance of employees; what is subject to co-determination, the federal states regulate differently. Parents' representatives are best told before the parents. The school's data protection officer assesses before anything is promised. And the school authority provides the network, the devices and often the budget. Whoever is passed over in that round speaks up later – usually at the worst possible moment.

Data protection comes before the decision

Responsibility for the data stays with the school, even when it only uses a system. That is why four questions belong before the choice and not after it. Is there a data processing agreement, and what does it say? Where do the servers stand, and who can technically access the data? What does each role see – does a teacher see only their own classes or the whole year group? And how long does which data stay stored before it is deleted? The processing then belongs in the record of processing activities. Which periods and which steps apply in detail differs by federal state; the school's data protection officer and the state authority are the right addresses for it.

Really reaching staff and parents

A system that only half the staff use costs more than none at all: it doubles the routes instead of replacing them. That is why the introduction needs one named contact person in the building, a short training session at a time when everyone is there, and a start with exactly one module – usually the digital class register or the cover plan, because both come up daily. On the parents' side the same holds. The invitation has to reach families who use no smartphone or speak little German as well. So plan a route on paper for the invitation, an office hour in the first weeks and a multilingual interface as a requirement for the system.

The window for switching is the turn of the school year

Classes, courses and assignments are set up afresh for the new school year anyway – that is the moment when a switch costs the least. Class and student lists come over as CSV, an existing timetable through the export file of the timetabling program used so far. What stays manual are grades and histories from the old system, which may well stay there as an archive.

FAQ

Frequently asked questions about introducing school software

The turn of the school year. Classes, courses and assignments are set afresh then anyway, and nobody has to run two systems for half a year. Switch mid-term and you transfer grades, absences and timetables a second time by hand. For a pilot in a single class this does not apply: that can start at any time.

No, and it is the most common mistake. Start with one module that comes up daily: the digital class register, the cover plan or parent communication. If that runs for a few weeks without questions, the next one follows. The modules belong together but do not require each other – the school platform grows with what you actually use.

That depends on the federal state and the type of school. As a rule the school management decides, bodies such as the school conference and the staff council are involved, and the school's data protection officer assesses the processing beforehand. Which involvement is binding is set out in the respective school law; the school inspectorate and the school authority answer that reliably.

The technology is the shortest part: create the classes, import the lists, invite the staff – that is a matter of hours. Time is taken by involving the bodies, the data protection assessment before the decision and the pilot, for which half a school year is a good length. Realistically a school year runs from the first question to regular operation.

Class and student lists SchuleVernetzt reads as CSV – first name, last name, class; a preview shows duplicates and faulty lines before saving. An existing timetable comes over through the import from the export file of the timetabling program used so far. Grades and histories do not move along: there is no import for them, they stay in the old system as an archive.

Listen before you steer – there is usually a concrete obstacle behind it and not a matter of principle. What helps: a contact person in the building rather than a hotline, a single module rather than ten, and an agreed end to the paper route. As long as both routes stay open, nobody decides for the new one.
Coming soon

Be there when SchuleVernetzt launches

We're building SchuleVernetzt at full speed. Leave your email and we'll notify you the moment your school can get started – free and with no obligation.

We use your address only to notify you at launch, and you can unsubscribe at any time.