People and cards
A pupil or staff member with a MIFARE or Unique card. The card has a name, a number and a PIN from the controller, and can be deactivated or transferred to another person.
Access control
Who came in and when, recorded, not remembered
Proximity cards on the doors, a log of taps from the readers and a group presence report at the end of the day. The module collects events from the controllers already installed in the school and turns them into a list: who, through which door, at what time.
Presence of group 6a on 22.09.2026
- People in the group
- 24
- Cut-off
- 12:00
- First entry
- 07:38:05
- Last exit
- 16:51:44
- No taps
- 1 person
- Limit
- 8 h
The caretaker knows every child
And he knows which doors creak. He just doesn’t have to remember who came in through the side entrance after lessons. The reader records that.
How it works
From card to report
The events come from the controllers on the doors. The app does not invent them; it only puts them in order.
SSchool office
Adds the person and the cardFirst name, surname, group. The card has a number, a type and a PIN matching the controller. The card number is unique within the school.Card active
PPerson
Taps the cardThe door controller decides whether the door opens. The reader records the tap with the time, direction and result.Event: access
AApp
Matches taps to peopleBy card number and PIN. An unknown card or a denial also goes into the log, as its own event type.Event log
SSchool office
Downloads the daily reportGroup, date, device. For each person: first entry, last exit and time on site, with any excess over the limit.PDF: group presence
Daily report
Columns as on the printout from the app. A person with no taps has blank times, not “absence”. Sample data.
Group presence on one sheet
Entry is the first tap before the cut-off time, exit is the last one after it. The school sets the cut-off and the time limit.
Presence of group 6a on 22.09.2026
| No. | Full name | Entry time | Exit time | Time on site | Excess time |
|---|---|---|---|---|---|
| 1 | N. Adam | 07:41:12 | 15:32:40 | 7 h 51 min | 0 min |
| 2 | D. Piotr | 07:49:03 | 16:40:21 | 8 h 51 min | 51 min |
| 3 | L. Julia | 07:55:48 | 13:05:10 | 5 h 10 min | 0 min |
| 4 | R. Olga |
Features
What you get in the module
Devices and doorways
Door controllers addressed by IP, each with named doorways. Single and double doors.
Groups
A class, support staff, teachers. The group is the basis of the daily report.
Event log
Access, denial, unknown card, exit button, device start-up. Filter by person, type and date.
PDF reports
Group presence for a day and a personal report for a date range: entry, exit, time on site, excess over the limit.
Card-based surveys
A kiosk in the corridor: a pupil taps their card and answers a school survey. Results in the app.
Limits
What this module does not do
On a page about children’s safety, this matters as much as the list of features.
Does not show where anyone is
What is recorded is a card tap at a specific door, not a person’s location in the building. There is no map and no “who is in school” view.
Is not work monitoring
Time on site is the difference between the first and the last tap. It is not a working-time record and does not replace the class register.
Does not open doors and has no cameras
The door controller decides whether the door opens. The app does not control the lock remotely and does not connect to CCTV.
Does not keep data indefinitely
You set the retention period, in line with your own legal basis. We agree the scope of the log before go-live.
What changes
Before and after launch
Today
- Side door wedged open
- Keys copied because nobody knows where they are
- Working out after the fact who was in a room
- Group presence list written up by hand
After the rollout
- Entry with a card assigned to a person
- A lost card deactivated with one click
- Log of taps, filterable by person and date
- Group presence report in PDF at the end of the day
Questions
What people ask about most
Do we need to replace the locks?
The module works with card-operated door controllers. If the school already has readers, we connect them. If not, we start with one door, usually the main entrance.
Is this monitoring of children?
No. What is recorded is a card tap at a door. The app does not know where a person is in the building and has no cameras.
Is this working-time monitoring?
No. The report shows the first and the last tap of the day. It does not distinguish breaks or work-related outings, and it is not a working-time record.
What about a lost card?
The school office deactivates it in the app and issues a new one. The tap history of the old card stays in the log.
How long do we keep the log?
You set the retention period, in line with your own policy and legal basis.
Where do we start?
With one building, one controller and a list of people with their groups. We issue cards in stages.
One day
A day at school
7:40, entry
Pupils tap their cards at the main entrance. Each tap goes into the log with the time and direction.
During the day
An unknown card at the side entrance is a separate event in the log, not something nobody knows about.
17:30, report
The school office downloads the group’s presence for the day. Anyone with no taps is on the list with blank times.
Let’s start with one door
All it takes is a list of people with their groups and one controller. We configure the rest together.