Customer zone

{# The current page's path in each language, read by switchLang in base.html. Rendered in the navbar on a full load and appended (out of band) to every HTMX partial, because an hx-get page change swaps main but not the navbar, and the Swedish letter slugs (/produkten/, /priser/, /film/) cannot be derived from the English path by adding or removing /en. #} SV EN

Demo films · Film 2 of 8 · 5:50 · Narrated · v0.7.55

From pattern to case

Two reports on the same student become a request to the student health team, the request is picked up, and the case moves on to the principal — while the teacher who filed the report still sees only their own part.

app.skolshield.se

Chapters

Previous film From incident to report Next film The student health team meeting

Read the walkthrough as text

More films

All the demo films

Film 1 · ·v0.7.55

From incident to report

The same corridor incident is reported two ways — inside the system and through the fast lane — so you can compare the routes in. Then we follow the report through to the mentor's screen.

Film 3 · ·v0.7.55

The student health team meeting

The meeting is booked, the agenda builds itself from the cases, and during the sitting the meeting page reads straight from the case. The minutes are written, the meeting is closed against what the law expects, and the mentor and the teacher each get their own text, nothing more.

Film 4 · ·v0.7.64

The mentor's lane and the team's questions

The mentor raises a concern, the student health team makes it a case, and she is not on it. Still she has a lane of her own in the case: her notes and the team's replies. The other way round, the team asks the teacher and the mentor from the case; each reads only the question and answers in a thread of their own. All of it lands on the case.

Film 5 · ·v0.7.55

The degrading-treatment chain

A quick report with one box ticked, a week later another — and the app remembers. Ticking "repeated" starts the chapter 6 chain: the principal acknowledges and reports to the responsible authority, guardians, investigation and measures are documented where the report lives, and the case cannot be closed until everything is there. Finally, the document for the responsible authority or the Schools Inspectorate.

Film 6 · ·v0.7.54

Who sees what

One incident, one address, three different pages. The mentor who wrote the report, the student health team and a teacher who only teaches one of the two students open the same incident, and the other student's name is masked in the teacher's card. Then a note is shared, and the whole incident is opened with a logged decision.

Film 7 · ·v0.7.55

One student page, six roles

The same address for everyone in the film. The mentor sees the report whole, the teacher gets only the teacher text and a 403 on the case, the student health team sees the sender's name, the principal has the tools nobody else has — and the IT administrator and the reporter role do not get in at all. Every read is in the log.

Film 8 · ·v0.7.63

From the classroom to the huvudman

One kommun, three schools, one installation. The mentor flags repeated kränkning and the chapter 6 chain opens the case by itself; the health team adds her concern to that same case, she writes her notes to the team on it, the principal acknowledges, reports to the huvudman and lifts the case there. The central health team picks it up, sees the whole kommun in one overview and answers the mentor.

The films were recorded in the demo. It stands open.

The same environment and the same data — but you do the clicking, in whichever role you like.

Open the demo Book a walkthrough