Skip to main content
    QHSEtech
    Updated 22 September 2026
    Software Guide · Reviewed 22 September 2026

    Fall protection software: equipment, anchors, competence

    A fall arrest system stops a fall only if three separate things are true at the same moment: the equipment is serviceable and in date, the anchor is rated and has been inspected, and the person using it knows how. Each is a different record with a different owner and a different expiry, and the failure mode is that they are tracked in three places that never meet. This guide evaluates software on whether it can answer one question — is this person, on this anchor, with this harness, safe to work right now — and on what it does when the answer is no.

    Jump to the 7 products

    Editorial responsibility: Dimitris Mitsios (Founder of The QHSE Standard; product marketing at Tekmon) · Tekmon pays for sponsored placements on this site (disclosure) · How pages are made · LinkedIn · Content date: 22 September 2026

    TekmonAd

    Explore its published safety, quality and maintenance workflows. Confirm modules and pricing in a scoped proposal.

    On this page (12 sections)

    Why this is the record that gets audited

    OSHA states that falls cause one in three construction worker deaths, and reports 389 fatal falls to a lower level out of 1,034 construction fatalities in 2024. Its general fall protection requirement for construction, 29 CFR 1926.501, was also the standard most frequently cited by federal OSHA in fiscal year 2024 — so this is simultaneously the most lethal hazard in the sector and the one inspectors write up most often. US OSHA: fall prevention campaign; US OSHA: commonly used statistics; US OSHA 29 CFR 1926.501: duty to have fall protection

    In Great Britain the duty is framed differently and is not height-threshold based in the same way: the Work at Height Regulations require work at height to be properly planned, supervised and carried out by competent people, with equipment selected and inspected accordingly. If you operate across both regimes, do not assume a configuration built to one satisfies the other — the trigger, the hierarchy and the inspection language all differ. Great Britain HSE: work at height; The Work at Height Regulations 2005 (SI 2005/735)

    What this means for software selection is narrow and useful: the system will be read by someone investigating an incident or responding to an inspection, and what they will ask for is the inspection history of a specific item, the certification of a specific anchor, and the competence record of a specific person, on a specific date. Everything else on a feature list is secondary to producing those three things quickly and provably.

    What counts as fall protection software, and what does not

    Fall protection covers several different control types, and software helps with some of them far more than others. Collective measures such as guardrails, covers and safety nets are physical controls that are inspected but not issued to a person. Personal systems, which are the focus here, divide into restraint, which stops a person reaching the edge, and arrest, which stops a fall once it has begun. Arrest systems add clearance, rescue and post-fall handling questions that restraint systems do not raise to the same degree.

    Software in this category normally keeps records: item registers, inspection results, anchor registers, authorisations and permits. It does not select a system, calculate fall clearance, or verify that an anchor will hold. Those are engineering and competent-person judgements, and a platform that appears to offer them should be asked what inputs it uses and who signs the result. Treat any claim that software makes work at height safe as outside what a records system can show.

    Three records, three different expiries

    Equipment lifecycle

    Harnesses, lanyards and self-retracting lifelines with inspection intervals, certification expiry and retirement. The hard part is not the schedule but quarantine: what stops an overdue or post-fall item being issued again.

    Anchor register

    Location, load rating, installation and inspection history, and usage restrictions. Ask how a temporary anchor is handled, and how an anchor that failed inspection is prevented from appearing on a permit.

    Competence

    Training and authorisation for the specific system in use, including rescue. A general working-at-height course is not authorisation to use a particular device; confirm the record distinguishes them.

    The demonstration: make the system say no

    1

    Issue equipment that is one day overdue

    Attempt to assign a harness whose inspection has just lapsed. Establish whether the system blocks it, warns, or records it silently — and who, if anyone, is notified.

    2

    Retire an item after an arrested fall

    Record that a harness took a fall and confirm it cannot re-enter circulation. Ask what the field user sees when they scan it, because the person who finds it next will be on site, not at a desk.

    3

    Fail an anchor inspection, then try to use it

    Mark an anchor as failed and attempt to raise a working-at-height permit against it. If the permit can still be issued, your control depends entirely on the issuer remembering.

    4

    Assign an uncompetent worker

    Try to authorise someone whose training has expired, or who is trained on a different device. Establish whether the check is device-specific or only a general course flag.

    5

    Produce the pack an inspector would ask for

    For one worker on one date, export the harness inspection history, the anchor certification and the competence record as one set. Time it. Confirm it is readable without a licence.

    A worked scenario: each check passes alone and the combination fails

    This scenario is hypothetical. A crew is booked to replace roof sheets on Thursday. The permit names one fixed anchor, three harnesses from the store and a self-retracting lifeline. Four checks should happen before it is issued: the inspection date of each harness by serial number, the last inspection and rating of the anchor against the number of people who will attach to it, each worker's authorisation for that lifeline model, and a rescue arrangement specific to that roof.

    Now suppose one harness is within its inspection interval but was logged as having arrested a fall in a previous job, the anchor passed inspection but is rated for one person while two will attach, and one worker holds a general course certificate but no authorisation for the lifeline model. A system that stores dates alone passes all three items. A system that stores ratings as free text raises no warning on the anchor. The value of the software lies in the joins between the records, which is why the demonstration should present exactly this kind of mismatch.

    How fall protection record systems commonly fail

    Serial numbers are typed as free text, so two harnesses of the same model cannot be told apart and a retired item can be re-entered as a new one.
    Anchors are described in words such as 'roof beam' with no location reference a worker could find, so inspection history cannot be tied to a physical point.
    Inspections are completed on paper and entered later, so the timestamp cannot show that the check happened before use.
    Competence is stored as a certificate date with no record of which system or device it covers, or whether rescue was part of the training.
    Quarantine status exists in the register but is not shown where equipment is issued or scanned, so the control relies on memory.
    Contractor equipment and contractor workers sit outside the register, although they may carry out much of the work at height.

    Questions for vendors, and how to read the answers

    QuestionA good answer showsA thin answer looks like
    Is each harness its own record?An item record with serial number, owner, issue history and service history that you can open from a scan.A count of 'harnesses' by type, or inspection forms with a free-text identifier.
    What stops a failed item being used?A status change that blocks assignment and is visible at the point of issue or scan.A flag that can be set but is not checked by anything else.
    How is an anchor linked to work?A selectable anchor record on the plan or permit that shows rating and last inspection and excludes failed anchors.An anchor typed into a text field on a form.
    How is competence tied to a device?Authorisation per system or model with its own expiry, and rescue training recorded separately.A single 'work at height trained' flag.
    What does an inspector receive?One export for a worker on a date that combines equipment, anchor and competence records.Three separate reports that someone assembles by hand.

    Questions that separate candidates

    Can overdue equipment be issued, and what happens if it is?
    How is post-fall equipment quarantined, and what does a field scan show?
    Does a failed anchor inspection block a permit against that anchor?
    Are temporary anchors handled differently from fixed ones?
    Is competence recorded per device, or only as a general course?
    Is the rescue plan attached to the permit, and is it specific to the location?
    Can inspections be completed offline, and what syncs back?
    Who is notified when an inspection lapses, and through what channel?
    Can equipment be traced to a serial number and an owner?
    Can the evidence pack be exported and read without the platform?

    Products whose records document fall-protection functions

    Few products in the catalog document anything specific to fall protection, so read this list narrowly. A product is listed when its researched profile records a function with a source that names fall protection, harnesses, lanyards or lifelines; the profile says whether that is an equipment register with service history, or inspection templates that you complete on a device. Those are different purchases: only a register can tell you that a harness is out of date before anyone puts it on. If you are evaluating the task rather than the equipment, use the working at heights guide, which covers planning, permits and rescue.

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    Same rule for every product: tagged “Fall Protection”, “Equipment Inspection”, “PPE Management”, “Safety Equipment”, “Inspections”, “Safety Management”, “Inspection Management”, “Audits & Inspections”, “Construction Safety”, “Offline Inspections” or “Mobile Forms”, with a sourced fall protection equipment or inspection records capability in its record, or one the vendor stated to us, labelled as vendor-stated. 7 qualify.

    What the admitting capabilities describe

    7 products currently meet the rule behind the list above: 3 through a documented capability, 3 through a conditional one and 1 through a vendor statement that no public page has yet confirmed. Counting by the wording of the capability names alone: templates or checklists appear in 5, equipment or records in 2, both in 1, and neither in 1. The grouping is by keyword and is a reading aid, not a classification made by the vendors.

    A template tells you that an inspection can be completed; a register tells you the state of a specific harness before anyone puts it on. A product admitted for templates has not been shown to keep item-level service history, and a product admitted for equipment records has not been shown to cover anchors or competence. Use the admitting capability on each card to decide which of the three records you still need to ask about.

    Sources and evaluation limits

    5 sources, checked 22 Sep 2026

    US requirements and fatality data: US OSHA: fall prevention campaign; US OSHA: commonly used statistics; US OSHA 29 CFR 1926.501: duty to have fall protection. Great Britain: Great Britain HSE: work at height; The Work at Height Regulations 2005 (SI 2005/735). All checked 22 September 2026.

    The OSHA figures quoted are for construction in the United States and are not a global rate; they are cited to explain why this record is scrutinised, not as a benchmark for your operation. We publish no estimate of incident reduction attributable to software, because we have not measured one and have not verified a published figure worth repeating.

    This page ranks nothing and tests nothing hands-on. Requirements differ by jurisdiction, industry and the equipment in use, and determining what applies to your work is a judgement for the people accountable for it. Software holds the evidence that a duty was discharged; it does not discharge it.

    Related Guides

    Working at Heights SoftwarePPE Management SoftwarePermit to Work SoftwareAsset Inspection SoftwareTraining Management SoftwareRisk Assessment Software

    More related guides

    Frequently Asked Questions

    What does fall protection software actually manage?
    Three records that expire independently: the equipment (harnesses, lanyards, self-retracting lifelines) with its inspection and retirement dates, the anchors with their ratings and inspection history, and the people with their competence and authorisation for the specific systems in use. The value is in the joins — being able to establish that all three were valid at the moment someone worked at height.
    Is there a single height at which fall protection is required?
    It depends on the jurisdiction and the work. In US construction, OSHA's general requirement at 29 CFR 1926.501 applies at six feet or more above a lower level. Great Britain's Work at Height Regulations are not framed as a single threshold; they require work at height to be planned, supervised and carried out by competent people with suitable equipment. Confirm what governs your sites rather than configuring to one rule.
    How important is post-fall equipment quarantine?
    It is the control most often missing in practice. Equipment that has arrested a fall must be removed from service, and the failure is rarely in the policy — it is that the item goes back in the store and the next person finds it. Test specifically what a field user sees when they scan an item that should be quarantined, rather than accepting that the system can record a retirement.
    Does a training course make someone competent?
    Not by itself, and the record should reflect that. Competence is for the specific system and task, including rescue, and a general working-at-height course does not authorise use of a particular device. When evaluating software, check whether the authorisation check is device-specific or simply looks for a valid course flag — the second is much easier to satisfy and much less useful.
    Which products should we look at?
    The list on this page currently holds 7 products, admitted by a rule: the researched profile must record a function whose source names fall protection, harnesses, lanyards or lifelines. Read the list narrowly. Each card states the admitting capability, which may be an equipment register or only inspection templates, and the page does not claim a specialist fall protection product beyond that. In practice the capability is usually assembled from PPE management, asset inspection, permit to work and training management, each of which has its own guide on this site with researched products and check dates. Ask for each module to be named individually on the quote.