The distinction between an unsafe act and an unsafe condition is the most practical sorting tool in the safety program, because it decides the fix: the act is corrected with training, supervision, and behavior, and the condition is corrected with maintenance, housekeeping, and engineering. The definitions post on this site covers the theory; this post is the field guide, with the forklift examples that the supervisor meets on the floor and the fix each one takes.
The act examples
The unsafe act is the behavior: the choice that increases the risk. The operator who speeds through the intersection is committing an act. The operator who drives with the load raised is committing an act. The operator on the phone while driving, the walker who cuts across the aisle instead of using the walkway, and the worker who bypasses the inspection are all committing acts. The signature of the act is the choice: the behavior could have been different, and the fix is the feedback and the training that changes the choice.
The condition examples
The unsafe condition is the hazard: the state of the workplace that increases the risk regardless of the behavior. The wet patch on the dock apron, the pallet overhanging the rack, the blocked sightline at the intersection, the cracked tire on the reach truck, and the faded walkway line are all conditions. The signature of the condition is the absence of choice: the hazard exists whether anyone behaves well or badly, and the fix is the maintenance, the housekeeping, and the engineering that removes it.
The mixed cases
The field gets interesting in the mixed cases, where the act and the condition meet. The operator who speeds through the intersection with the blocked sightline: the speeding is the act, and the blocked sightline is the condition, and both get fixed, the feedback for the behavior and the mirror or the camera for the geometry. The walker who cuts across the aisle where the walkway has a dead end: the shortcut is the act, and the dead-end walkway is the condition, and the design fix is what actually removes the shortcut. The mixed cases are where the field test on this site earns its keep: ask what the worst outcome was, and ask whether the behavior or the environment produced the exposure.
The sorting question
The sorting question is simple: would this exposure exist if every worker behaved perfectly? If yes, it is a condition, and the fix is the environment. If no, it is an act, and the fix is the behavior. The question forces the honest classification, and the classification forces the right fix, which is the observation data and the near-miss log applied to each event. The Risk Scorer on this site does the same sorting at the operation level, scoring the exposure by mechanism so the fixes follow the score.
The field habit
The field habit in the review
The classification habit belongs in the review as much as on the floor, and the review application is worth naming. The near-miss log is sorted by the two classes each week: the act events go to the coaching and the training, and the condition events go to the maintenance and the engineering. The sorting is the leading indicator that shows whether the operation’s exposure is a behavior problem or an environment problem, and the Risk Scorer on this site applies the same split at the operation level. The KPI review reads the act-to-condition ratio over time, and the trend tells the program where the investment belongs. The field habit is the daily classification, and the review habit is the weekly aggregation, and the two together are what turn the distinction into prevention.
The habit is to classify every near miss and every observation with the two questions: the act or the condition, and the fix that follows. The habit turns the safety program on this site from a collection of responses into a system, because the act gets the coaching, the condition gets the engineering, and the mixed case gets both. The field guide is the supervisor’s reference, and the classification is the discipline that the serious event prevention runs on.
