Software for a volunteer fire brigade and a sports club: dues, timetable, kit
A volunteer fire brigade and a sports club share the same pain: a member register, dues, duty and a facility calendar. OSP and club software instead of Excel and Facebook.
A volunteer fire station and a sports club look like two worlds from outside. Inside, the pain is the same: a club member register (or a unit roster), club dues, a duty rota, kit that is “somewhere”, and a calendar that lies when two groups want the same hall. People type OSP software, sports-club software, e humies, sports-facility timetable or simply volunteer fire brigade + “dues” into Google — and land on generic NGO SaaS that can do a mailing list and cannot do an appliance, a pitch or a Saturday-night duty. A narrow custom system pays when those three things must be one truth, not when someone said “we should go to the cloud”.
This is a cousin of association and foundation software, not ministry ERP. An OSP is an association with a fire-protection role and a local centre (a hall, a fête, a youth fire team). A club is a physical-culture association with facilities, training and often a ticket. Both live on dues, grants, the 1.5% tax designation and people who will not fill Excel after evening drill. If any of that lives in the treasurer’s notebook and a Facebook “hall timetable”, the season ends in a complaint, not a protocol.
The sector is not a slide. Statistics Poland, NGO activity in 2024 reported 113.1 thousand NGOs in 2024 (+7.7% year on year), with 7.6 million members. Typical associations were 29.0%, foundations 19.8%, sports associations 17.8%. Rural women’s circles were 15.3% and volunteer fire brigades 13.1%. OSP and sports clubs are not a catalogue footnote. They are two of the thickest pipes in the sector.
Registered OSP units are a different measure from the GUS share. fakty.ngo.pl (Klon/Jawor), from REGON/KRS at 31 December 2024, says OSP — also associations — number almost 17 thousand, drawing on “The condition of NGOs 2024”. We do not mix that figure with fires, call-outs or crew counts — we do not take those from the National Headquarters of the State Fire Service. OSP software is not a dispatch system replacing SWD. It is the unit’s back office: people, dues, kit, duty, the hall.
Why OSP and a sports club fit one engine (and where they already do not)
Both are usually associations. They have a general meeting, a board, members, a fee, inventory, a hall or a pitch, an event once a quarter and a treasurer who works after hours. A club member register and a roster of volunteer firefighters differ in fields (medicals, appliance-driving rights vs age group, position, a player licence) but not in the need for one person card. Club dues and an OSP membership fee are the same mechanism: period, amount, relief, arrears, a receipt. A sports-facility timetable and a booking of the station hall are the same resource calendar. Appliance inventory and a ball inventory are the same store with another checklist.
They split when the club sells a pass or a ticket and the OSP keeps rescue-kit records for inspections and insurance. We do not build “one combine for all of fire-and-sport Poland”. We build an engine: person → fee → resource (hall / pitch / appliance) → event (training / duty / fête) → document. Field templates are two. The database and permissions are one if the municipality shares IT back-office, or separate if there are two boards and two tax ids. We will say which side of that sentence is true for you.
- Shared: member, fee, general meeting, minutes, inventory, hall, event, attendance.
- OSP: duty, crew, rescue kit, medicals, qualifications, youth team, a municipal contract — no pretend SWD.
- Club: training group, licence, sports-facility timetable, ticket, pass, referee, pitch.
- What we do not glue on day one: State Fire Service dispatch and a club merch shop in the same MVP basket.
Where Excel fails a volunteer fire brigade
A volunteer fire brigade lives on a rhythm a generic CRM does not know. Drill in the evening, duty at night, a fête or a competition at the weekend, on Monday the treasurer chasing unpaid dues, the president hunting last year’s minutes because the municipality wants a grant report. Kit “is on the books” until someone needs a specific set and it sits with a firefighter who is away. Five people have the station keys and nobody knows who locked up. The hall booked “on a verbal” clashes with youth-team training. That is not a lack of patriotism. It is a lack of a number on a thing that should have a number.
- Dues and the member list in two workbooks that diverge after every general meeting.
- Kit with no location and no inspection date — a card that says “exists” instead of “lives here, valid until”.
- Duty on a Messenger group: who goes, who covers, who no longer takes nights.
- The station hall booked three times for the same Saturday: a christening, a village meeting, own drill.
- Youth firefighters and adults in one notebook with no parent consents and no medical dates.
- A grant and 1.5% in a folder of scans that cannot be tied to kit spend.
- A new president inherits a cardboard box, not passwords.
We do not write how often a unit turns out or how many fires it fights. Those numbers sit in State Fire Service reporting, not in our brief. OSP software should mean that when you turn out, the back office (who is on the books, what kit left, who stays at the station, who opens the hall tomorrow) does not live in one chief’s head. Dispatch stays where it is. We hold the unit as an organisation.
Where a Facebook timetable fails a club
Sports-club software dies in August and January. August: intake, parent consents, groups, dues, who is on which hall hour. January: arrears, licences, a tournament, a ticket, a pitch clash with an outside hire. The coach writes “tomorrow 5 pm, who can’t?”. A parent cannot see whether the child is booked on Wednesday. The treasurer cannot see whether the quarter’s dues are in before you let the player onto a fixture. The hall is “free” in a spreadsheet from three days ago. A referee arrives for a match that vanished in a private message.
This is closer to gym passes and class booking and online tickets than to corporate CRM. A resource (lane, pitch, hall, rink), a clock (slot + reset + nets), people (coach, referee, a loaned keeper), a product (dues, pass, ticket, camp). If any of that lives outside the system, Saturday ends in a double booking or an empty hour you still pay the municipality for.
Member register, dues and the search phrase “e humies”
A club member register (and a firefighter roster) is the foundation, not an “HR module”. A person has a name, a contact, a join date, a status, a fee, consents, notes. On an OSP you add medicals, courses, qualifications, a board role, youth-team supervision. At a club: group, age band, parent, licence, health limits only when needed and when you have a basis. One person may be a firefighter and a player’s parent — two contexts, one identity, two organisation tax ids if they are two associations.
People who search e humies usually want this: an electronic member and dues file, not a “community app”. The name is mangled; the need is simple. OSP software and sports-club software start on the person card. The rest (ticket, duty, store) sits on that card, or you will again have three truths.
Club dues are the cheapest income and the easiest to lose. Period, amount, sibling relief, junior relief, a board exemption, a due date, a channel (transfer, BLIK, cash at training). The system assesses, shows a parent or a firefighter a balance, and enforces whether a player in arrears may travel — by your resolution, not our morals. An SMS 7 days before and 3 days after is cheaper than a row at the meeting that “nobody chased”. Cash at training is a small-club fact. The coach should not be a till without a receipt. A panel payment (or a BLIK code on the fee) takes the treasurer job off the coach.
- A price list per group / status, with a start date.
- Relief and exemption with a resolution — a field, not an exception in the treasurer’s head.
- A reminder and a block on camp / fixture booking at an arrears threshold you set.
- 1.5% and donations separate from the fee — another document, another thank-you.
- An export to the bookkeeper; if you raise invoices from the panel (hall hire to a firm) — a KSeF path.
Sports-facility timetable and the station hall
A sports-facility timetable is what a room calendar is to an escape room: a resource hates a double booking. Hall, pitch, orlik, pool, club gym, the station hall, the yard by the garages. Each resource has opening hours, a reset (nets, flooding, cleaning), who may book (coach, board, outside hire) and a rate. “5–6:30 pm orlik, U13” blocks the same orlik for a firm that wants “a quick after-work tournament”. Without an availability engine, the loudest Facebook message wins.
Outside hire is income and conflict. A separate path: enquiry, quote, deposit, invoice, site rules, a lighting deposit. A club side does not click the same widget as a firm. The same calendar, a different booking type. Kinship with ticket sales: when you let the public in, the facility slot and the ticket pool must know each other. A player app is not a condition of the timetable. A page is enough. Native Android when a coach at a second site really needs an offline roll.
- Resource: name, type, capacity, kit, reset time, owner.
- A repeating session: weekday, exceptions (holiday, tournament, a broken floor).
- A one-off: match, camp, a rank exam, a general meeting, a christening in the OSP hall.
- Outside hire: price list, deposit, invoice, bond, rules.
- A clash visible before the save, not after two teams arrive.
- A week view for the coach and a season view for the facility manager.
Inventory, duty, events — without a second spreadsheet
Kit in a volunteer fire brigade is not “office assets”. It has inspections, certifications, insurance, often a grant inventory number and liability when it leaves the station. The system holds name, number, place, inspection date, a document, a status. Issue for a call-out or a drill is a movement, not “we took it, it will come back”. A return with an exception opens a task. We do not quote equipment norms or how many appliances a unit “should” have. Those are rules and municipal contracts. We give fields you treat as mandatory at an inspection and with an insurer.
An OSP duty rota is a cousin of a field-service crew roster: who, when, which duty phone, who covers, who does not take nights because of shift work. The system does not send a crew to a fire. It shows who is booked on the night and who confirmed. A club roll is for licences, for “real attendance” fees and for who travels. The coach ticks on a phone. Offline in a hall with no LTE — local save, send later.
A station fête, a fire-sport contest, a weekend tournament, a match with a crowd: an event with a date, a resource, a people list and sometimes a till. Online tickets enter when you really sell admissions with a pool and a QR. When you collect entry fees from eight teams by transfer — an event, a list and a payment status are enough. We do not force an offline QR gate onto a fête that still runs on a tin and two kinds of sausage.
Youth, grants, KSeF and e-Deliveries
Youth fire teams and junior groups are children’s data. Consent to an SMS about a cancelled session follows from membership. Consent to a match photo on the club Facebook is separate. Consent to a camp overnight and to “asthma, take the inhaler” is narrower still. The system keeps consent versions, date and purpose. More: GDPR in applications. EU hosting. On a trip the coach needs an offline list. A PDF on a private phone is worse than a panel with a role and retention.
An association on the KRS falls into the e-Deliveries calendar like other non-public entities — we do not mix those dates with CEIDG. The panel does not replace the box. It keeps the letter on a case and a task with a deadline. KSeF — only when an invoice to a firm is born in the panel (hall hire, a perimeter board). A membership fee is usually not a VAT invoice. We do not scare a treasurer who takes 20 zł from a junior.
Generic NGO SaaS or a custom stack
Generic association tools can do members, dues, sometimes a meeting and mail. They break on a sports-facility timetable, rescue-kit inventory, duty and a QR ticket. Fitness SaaS can do a pass and a gate; it cannot do a statute, 1.5% and a youth fire team. “Fire” tools are often kit logs or a messenger; they are rarely treasurer and hall manager at once. Custom OSP software pays when the unit (or a union of units / a club with a hall) has a process a licence will not take, or when member and child data should stay on your server under your processing agreement. Twenty-five members, one fee, a hall once a week — a good spreadsheet or light NGO SaaS is enough. We will say so. Comparison: package or custom.
A week the system must survive, not decorate
Monday in a volunteer fire brigade: the treasurer closes weekend payments, the chief looks at who did not confirm duty, someone reports that a tent from the fête is still at the village head’s. Wednesday: drill, a roll, kit out and back, one torch dead. Friday: the municipality wants an annex to the station-upkeep contract, the president hunts a policy. Saturday: the hall is out for a birthday, youth drill at 10:00 — without a timetable that is a phone call at 9:40. OSP software does not shrink that week to a slide. It gives each thread a number so they do not live in one group named osp_wazne.
Monday at a club: coaches enter weekend absences, a parent asks for a refund on a tournament the opponent cancelled, the hall manager sees a mark on the floor after Saturday’s hire. Wednesday: peak sessions, a changing-room clash, Thursday’s referee not yet confirmed. Friday: dues that “definitely went” and did not hit the account, and a decision whether the junior travels. Sunday: a match, a list, a first-aid kit, the pitch key, who collects the posts. Sports-club software has to carry that week without a second workbook named matches_spring.
How we implement without killing the season
We do not migrate twenty years of notebooks in week one. We set person cards, a dues price list, facilities, a duty or training template. We bring active members and open arrears. After two weeks you see whether the coach ticks attendance and whether the hall timetable has a double. Only then: a ticket, a kit store, a parent portal, a second unit. Coach or chief training is an hour. If the screen needs a board meeting to tick a roll, the screen is wrong.
A native app: firefighter and coach in the field — yes, Android, large buttons, offline. Parent and fan — a mobile-first page. A Play Store app for fans pays when you have a regular ticket and a “kick-off moved” push. For OSP a “report a fire” app for residents is not our product and we do not pretend it replaces the emergency number. Shared password “osp / password on the board” does not pass.
A weekend tournament is the exam of a sports-facility timetable. Three pitches, twelve teams, referees, entry fees, a parent asking when their child plays. MVP is not a live table like a big federation. MVP is: pitch slot, team, hour, a confirmed referee, paid entry, a guardian contact. A result can be typed. A “fan app with a goal push” is another product if you are not selling a stand ticket. Outside-team entry fees are income and a dispute source. The tournament card: team, tax id if they want an invoice, amount, status; the match hits the timetable only after a deposit or the host’s decision.
Polish transfer titles are folk art: “dues”, “for Jaś”, “hall”, “for the appliance”, “1.5 not the fee”. Club dues without a matching tool leave the treasurer on the statement longer than on the pitch. The system suggests a match by name and amount; the treasurer confirms. It does not promise magic AI. It promises an unmatched transfer hangs on a list instead of dying between tabs. Cash has a daily report. BLIK on a specific fee ties itself. A refund for a cancelled camp is another document, not a negative fee in the same column that breaks balances.
The station is a building: boiler, appliance door, hall, kitchen, extinguishers, inspections. It is not a community portfolio from property-manager software, but the inspection calendar and the key cabinet are cousins. An OSP that lets the hall is a facility host. An OSP that only drills is a user. The system knows the role. A municipal upkeep contract has a date, an amount and a report. A case card, not a PDF in a private inbox.
Say whether you are an OSP, a club or both, member and facility counts, and whether the pain is dues, the timetable or kit. A quote for OSP software or sports-club software in 24 hours — first a register and a calendar that will not lie on Saturday, not a combine for the whole municipality.
Sources we do not stretch
NGO counts: GUS, NGO activity in 2024 — 113.1 thousand organisations, sports associations 17.8%, volunteer fire brigades 13.1%. Registered OSP: fakty.ngo.pl / Klon/Jawor — almost 17 thousand (REGON/KRS 31 Dec 2024, also kondycja.ngo.pl). No State Fire Service operational statistics (fires, call-outs, crew strengths) unless from a KG PSP publication — we do not invent them. KSeF: ksef.podatki.gov.pl. e-Deliveries: biznes.gov.pl. The rest is association back-office practice, not a firefighting manual.
Frequently asked questions
- Will OSP software replace dispatch and radios?
- No. We do not dispatch a crew and we do not replace SWD or the emergency number. We hold the unit’s back office: people, dues, kit, duty, the hall. Turnout stays in the procedures you already have.
- Will sports-club software replace the federation / league system?
- No. Licences and tables stay with the federation. We hold the member, the fee, the facility timetable, attendance and a ticket the federation will not run, because it is your site and your till.
- What is “e humies” — a separate product?
- It is a search phrase people use for an electronic member and dues file. We do not sell a separate brand under that name. We sell a register, dues and what sits on them: timetable, kit, duty.
- Must a parent install an app?
- No. A page with the timetable, a dues balance and consents is enough. The app is for the coach and the facility manager, maybe the OSP duty officer. A fan app — when you really sell a ticket with a push.
- How many members before custom makes sense?
- There is no magic number. At 25 people and one fee a SaaS or a sheet often does. Custom when you have two sites, juniors, a ticket, kit with inspections, or data should stay with you. Send the numbers — we will say honestly.
- Will the system issue KSeF invoices for dues?
- A membership fee is usually not a VAT invoice. KSeF enters when an invoice to a firm is born in the panel (hall hire, a board). Dates and duty: ksef.podatki.gov.pl and the bookkeeper, not our terms.
- Can one instance serve an OSP and a club in the same municipality?
- The same engine — yes. Two tax ids, two boards, two tills — two tenants or two organisation accounts, a shared resource calendar only when there is a loan agreement. We do not mix assets because it looks nicer on a demo.
- How fast can we start before the season?
- Register, dues and the next 30 days of timetable are weeks, not a year. Ticket, store and a parent portal come once the first month has no hall double and the treasurer is not keeping a parallel notebook.
Describe your project