Digitizing Książka Strzelnicy under the Polish Weapons Act

"Robimy to na papierze i na razie działa" is the most common answer we hear when we ask how a Polish range handles its Książka Strzelnicy today. Most of the time it is true - until an inspector shows up, or an insurer asks for a three-year history, or a member shows up with a weapon registered to another facility.

We did not want rangeOS to be a compliance product with a booking feature bolted on. We also did not want to sell a booking system with a disclaimer that compliance is the operator's problem. So before we wrote a line of code for the range silo, we mapped the Ustawa o broni i amunicji and the relevant rozporządzenia onto data structures.

What the law actually asks for

The session-log requirements are the ones that bite. For every range visit, your Książka Strzelnicy has to capture, at minimum:

• the member (identity confirmed against a valid license or the one-time kiosk scan for guests),
• the weapon (serial number, caliber, owner of record),
• the instructor or responsible person on shift,
• the ammunition consumed,
• the time window.

That list has to be legible, in chronological order, and reachable for at least five years. On paper that means a physical notebook staying within the facility, a filing cabinet, and a prayer that nothing catches fire.

What rangeOS does with that list

Every bullet in the list above maps onto a kiosk flow or an automatic capture:

• Member identity - kiosk scans the member's ID or licence on entry, cross-checks against the existing member record, or creates a one-time guest entry with a stored scan. Handwritten signatures stay legally valid; we store both.
• Weapon record - weapons are registered once to a member (or to the facility rental pool). Assigning a weapon to a booking is a one-tap action at the kiosk or on the operator's tablet.
• Instructor - pulled from the shift table. The Shift Manager knows who is physically on site with which competencies at any time, so the session log gets the right name without staff having to remember.
• Ammunition - every round consumed is deducted from the facility's inventory at shift-close via the kiosk reconcile. The session entry ties rounds to lane, weapon and shooter.
• Time window - start and end timestamps captured from the PIN validation at entry and the kiosk "checkout" tap at exit.

The five-year retention is where most systems fail

Keeping data is trivial. Keeping it accessible to an inspector in the form they expect is not. rangeOS stores every session log, every weapon allocation, every ammunition deduction in a single append-only ledger. The ledger is indexed by date, by member, by weapon and by instructor so a search like "show me everything shot from this pistol between March 2024 and August 2025" returns in under a second - not after a week of database archaeology.

When the Komenda shows up, we export a single PDF pack: chronological session log, weapon registry as of the inspection date, ammunition reconciliation, staff coverage, instructor competencies. Same format every time. No tailoring, no "let us find that folder".

What this does NOT replace

We are software. We are not the Polish Weapons Act. Your licence, your armory security, your instructor competencies - those remain your responsibility, and they remain outside the platform. What we do is make sure that the records you are legally obliged to keep are captured correctly the first time and retrievable on demand.

If the above reads like paperwork - yes. Good facility management is mostly paperwork held together by safety culture. rangeOS is the system that makes that paperwork invisible to the staff and bulletproof to the inspector.