Skip to main content
    QHSEtech
    Updated
    All glossary terms
    Content date: · No individual check logged· AI use

    Behavior-Based SafetyBBS

    Definition

    Behaviour-based safety — observing work practices and giving feedback to improve safe working, used alongside controls on equipment and conditions.

    Editorial definition: The QHSE Standard, updated 3 October 2026 · https://qhsetech.com/glossary/bbs

    Scope: Use observations alongside equipment design, working conditions and organisational controls; observation counts alone do not establish safer work.

    Example for your evaluation: Ask a vendor to record an observation, a contributing work condition and the resulting action.

    Sources checked: . Examples are editorial illustrations.

    How HSE and OSHA treat behavioural safety

    Behaviour-based safety, or BBS, is a family of approaches, not one defined method. The Health and Safety Executive describes behavioural safety approaches as defining safe and unsafe behaviours, observing behaviour, and giving feedback or reinforcement. Observers can be managers, peers or both, and feedback can range from specific comments given on the spot to general data fed back to a group. HSE lists benefits it associates with the approach: better conversations about safety, more visible management, supervisors who learn to observe and act promptly, and the possibility of indicators that look ahead of injuries instead of counting them afterwards.

    HSE is equally direct about the pitfalls. It says the approach needs a large and disciplined effort and often fails for lack of real commitment, that it can be seen as a watching or blame culture, that it tends to focus on easy and familiar issues and may draw attention from low-probability, high-consequence risks, and that it can shift the burden from management to individuals. It asks anyone adopting it to ask what evidence shows that behaviour change will improve safety and how the programme connects to the safety management system. HSE's page poses the evidence question without answering it, and neither HSE page on this subject is a standard or a legal requirement.

    OSHA's position on one related practice matters for the data. In a memorandum of 11 October 2018, OSHA said its injury-recording rule on employee involvement does not prohibit workplace safety incentive programmes or post-incident drug testing, and that rate-based programmes, which reward injury-free periods or low injury rates, remain permissible if they are not implemented in a way that discourages reporting. It described programmes that reward reporting near misses or hazards as always permissible. This page is general information, not legal advice, and the OSHA position is a United States one.

    What a BBS record set looks like in software

    • An observation record with date, location, task, observer role and the behaviours seen, recorded as safe, at risk or not observed, with free text for context.
    • A condition field on every observation, so equipment, workload, layout, lighting and tools can be recorded separately from what a person did.
    • A feedback note showing what was said at the time and whether the worker agreed with the observation.
    • Actions raised from an observation, with an owner, due date and closure evidence, routed to a supervisor or to the owner of the condition.
    • Observer coverage by team, shift and task, so gaps and heavy repeat observation of the same people are visible.
    • Participation and quality measures, such as the share of observations that raise a condition or an action, kept apart from injury statistics.
    • Access rules that decide who sees individual observations and who sees only team summaries.

    BBS, safety culture and a near-miss report

    BBS watches what people do at work and feeds it back. A safety culture is the wider set of shared values and management behaviour in a workplace, which an observation programme may influence but does not define. A near-miss report records an event that could have caused harm, usually raised by the person who saw it, while an observation is a planned look at normal work. Both feed the same action tracking, and neither is a measure of how safe a site is on its own.

    A hypothetical example: separating behaviour from conditions

    This case is invented to illustrate the record and describes no real company. A distribution warehouse logs 120 observations in a month. In 96 the observer notes no concern, and 24 record a concern. Of those 24, 15 describe a behaviour, such as walking in the truck lane, and 9 describe a condition, such as a blocked aisle, worn floor markings or poor lighting at a loading bay.

    The 15 behaviour concerns lead to short coaching conversations that the observer records. The 9 condition concerns go as actions to the maintenance or operations owner, with dates. The manager reads the 24 as a mix and not as 24 acts by workers, and the site does not link any bonus to injury figures or to the number of concerns found, so no one has a reason to under-report.

    Common misunderstandings about BBS

    • BBS does not replace engineering controls. HSE notes that behaviour approaches may pull attention from low-probability, high-consequence risks, and its summary says a programme must address engineering and systems as well.
    • A high observation count is not evidence of safer work. Quality, follow-up and the conditions found matter more than volume.
    • Rewards linked to low injury rates can discourage reporting. OSHA treats them as permissible only when not implemented that way, and programmes rewarding hazard and near-miss reports as always permissible.
    • Observation is not a way to assign blame. HSE lists a blame-culture perception among the pitfalls and asks for the link to the safety management system to be clear.
    • None of the sources opened presents BBS as a legal requirement. It is one optional method among others for learning about work.

    How BBS relates to other glossary terms

    BBS belongs with the terms about learning from work, controlling hazards and measuring activity.

    • Near miss: an event report raised by the person who saw it, rather than a planned observation.
    • Just culture: the approach to accountability that affects whether people report and accept feedback.
    • Hierarchy of controls: the order of controls in which changing behaviour and procedures comes after engineering measures.
    • KPI: the defined measures that an observation programme feeds, such as follow-up on actions.

    Records and evidence that usually exist for BBS

    • The observation form and the definitions of safe and at-risk behaviour in use.
    • Observer training records and coverage by team and shift.
    • Completed observations, with conditions and feedback notes.
    • Actions raised, with owners, dates and closure evidence.
    • Reports on participation, quality and follow-up for management review.
    • Any incentive or recognition scheme, with its rules and the reasoning for them.

    What a software tool needs to capture for BBS

    • A separate condition field and a separate behaviour field on every observation.
    • A feedback note that records what was said and the worker's response.
    • Actions that route to the owner of a condition, not only to a supervisor.
    • Access rules that keep individual observations from broad view.
    • Reports on follow-up and participation that are kept apart from injury rates.
    • Observer coverage views that show where observations are thin or concentrated.

    Catalog profiles documenting safety observation

    The list comes from the safety observation rule used by the behaviour-based safety software guide. It does not show that a product supports a particular behavioural method, which should be checked with a sample observation.

    Same rule for every product: tagged “Safety Observation” or “Behaviour Based Safety”, with a sourced safety observation capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

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

    All 10 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related software

    Frequently asked questions

    Does BBS replace engineering controls?

    No. HSE warns that behaviour approaches may draw attention from low-probability, high-consequence risks. Observations should also record equipment, workload and organisational conditions.

    Can observation data be used to reward teams?

    In the United States, OSHA's 2018 memorandum says rate-based incentive programmes are permissible if not implemented in a way that discourages reporting, and that rewarding hazard and near-miss reports is always permissible. Other countries have their own rules.

    What should a demonstration show?

    Ask to record an observation with a condition and a behaviour, add a feedback note, raise an action to the owner of the condition and report follow-up separately from injury rates.

    More safety terms