Zwrotnik
Refunds of pupils’ monthly tickets: an application with a photo of the ticket, verification at school, a list for the accounts department and a transfer file.
Local government
One case, one workflow, one register
School ticket refunds, the canteen storeroom, card-based entry, room bookings. Each module runs one process from request to the summary for the accounts department, without retyping data and without a notebook in the school office.
Ticket refund application
- Pupil
- N. Adam, class 6a
- Journey
- Dąbrówka – School
- Carrier
- PKS
- Valid
- 01.09–30.09.2026
- Ticket price
- PLN 128.00
- Refund (50%)
- PLN 64.00
This is what a case looks like
A school ticket refund, step by step
An example from the Zwrotnik module. The statuses are the same ones school staff see in the app.
PParent
Submits an application from a phoneChooses the period, enters the ticket price and adds a photo of the ticket. No visit to the school.Submitted
SSchool
Checks and acceptsA staff member sees the photo of the ticket and the pupil’s details. They accept it or return it for correction with a comment.Accepted for payment
SSchool
Closes the periodAfter the application deadline, downloads the list for the accounts department and the transfer file.Period closed
BBank
Pays out from the fileThe Elixir-format file goes into the school’s online banking. The applications are given the status Settled.Settled
Roles and statuses from the app. Sample data, without facility names.
What comes out of the app
Settled
Column names and summary as on the printout from the app. The data are examples; account numbers are masked.
A document that goes into the binder
An example from the Zwrotnik module: the payment list the accounts department receives after the period is closed. Layout and columns as on the printout from the app.
List of pupils eligible for a refund of purchased monthly tickets
| L.p. | Parent/Legal guardian | Pupil’s surname and first name | Bank account number | Monthly ticket amount |
|---|---|---|---|---|
| 1 | N. Anna | N. Adam | PL •• •••• •••• •••• •••• 2941 | PLN 64.00 |
| 2 | S. Marek | S. Maja | PL •• •••• •••• •••• •••• 1180 | PLN 71.00 |
| 3 | D. Ewa | D. Piotr | PL •• •••• •••• •••• •••• 7733 | PLN 64.00 |
| 4 | W. Tomasz | W. Kamil | PL •• •••• •••• •••• •••• 0526 | PLN 55.00 |
Total refund amount: PLN 254.00
In words: two hundred and fifty-four zloty /00 grosz
Modules
Four apps, each for one job
They work separately. What links them is one login and the same way of granting permissions per facility.
Storeroom and canteen
Receipts, issues to the kitchen, physical stocktake and PDF summaries. A meal from the menu linked to the issue document.
Access control
Cards on the doors, a log of taps from the readers and a group presence report at the end of the day.
Bookings
Rooms, sports pitches and community halls in one calendar, with the request and the decision in the same workflow.
What they have in common
The same login, the same permission rules
Every module is built on the same foundation, so the municipality learns one way of working.
One account
A staff member logs in once, with the same account for every module. When employment ends, the account is disabled in one place.
Permissions per facility
A head teacher sees their own school; the department at the council office sees all of them. Roles are assigned by the municipality’s administrator.
PDF documents
Lists, summaries and forms are generated from the data in the app and carry a number, a date and an author.
Change history
Every edit is recorded: who changed what, and when. For resolving a dispute, not for looking over people’s shoulders.
Beyond the modules
Processes that can be put in order too
We start with one process, not with a big rollout.
Document and case workflow
Hand-offs between departments, deadlines, case assignment and change history in one place.
Reporting
Data collected once and compiled automatically, instead of merging spreadsheets by hand before the deadline.
Integrations between systems
Line-of-business, finance and accounting systems and registers, linked via API or file exchange.
Digital accessibility
WCAG 2.1 AA compliance from day one
For a public body it is a statutory requirement. We check it by measurement, not by eye.
Contrast and keyboard
Contrast of text and interface elements calculated, keyboard-only operation, visible focus, correct heading structure.
User modes
High contrast and larger text, toggled in the header of this page, with nothing to install.
Accessibility statement
We help prepare it and keep it in line with the actual state of the website.
Let’s start with one process
You tell us about the issue that hurts most. We tell you whether and how it can be put in order, or why it is not worth it.