What to look for
Fire service PPE laundry is a regulated, high-consequence operation. The software you choose needs to do more than help you organise work — it needs to prevent compliance failures before they happen and produce auditable evidence when they are demanded.
Compliance enforcement, not compliance recording
The most important distinction in this category is between a system that records compliance activity and a system that enforces compliance rules. A recording system logs that a wash occurred, that an inspection was completed, that a garment was dispatched. An enforcement system blocks dispatch if the garment's wash count is exceeded, prevents inspection closure if a mandatory body-map zone was skipped, and auto-condemns garments when a rule is triggered — without waiting for a human to notice.
Recording systems give you a retrospective audit trail. Enforcement systems prevent audit failures from occurring. For a fire service PPE laundry, you need enforcement — because a failed audit finding is not just an admin problem. It is a contract risk and a liability.
Immutable audit trail
Every inspection, wash, repair, dispatch, and condemnation event needs to be recorded in a way that cannot be altered after the fact. This is not just good practice — ISO 23616 requires it, and any competent auditor will probe whether records can be edited.
Ask specifically: can a manager edit a wash temperature record after it has been saved? Can an inspection certificate be amended after it has been signed? If the answer is yes, the audit trail has a gap. Look for systems that use append-only event logs with timestamps and user attribution, where the original record is preserved even if a correction is made.
Individual garment tracking from new stock to condemnation
Batch-level tracking is not sufficient for fire service PPE. ISO 23616 requires per-garment records — not "this batch of 50 structural jackets was washed at 75°C" but "structural jacket UID VRX-00312 was washed in batch B-2024-0419 at 74.8°C on programme P4." This means every garment needs a unique identifier, and every action taken on that garment needs to be recorded against that UID.
Without individual tracking, wash count limits are unenforceable, coverage gaps are invisible, and a lost garment is just a statistical discrepancy rather than a specific item that can be located and recovered.
Wearer protection monitoring
A fire service laundry's core obligation is not to wash garments — it is to ensure that wearers are protected at all times. This means the system needs to monitor each wearer's PPE coverage continuously, detect when a wearer is uncovered (because their garments are in service or condemned), and alert the laundry team to resolve the gap.
Look for a system with a genuine protection engine that runs on a schedule, triggers on status changes, and surfaces coverage gaps to both the operations team and the client. A system that only calculates coverage when you ask it to is not sufficient.
Client self-service portal
Brigade H&S managers and contract managers will ask for compliance reports, inspection certificates, and coverage status updates. If your team has to produce these manually, that is a recurring admin cost and a relationship friction point. A client portal that gives the brigade direct access to their own data — live coverage status, downloadable compliance packs, inspection certificates — reduces the reporting burden on your team and strengthens the client relationship.