Problems that creep: managing slow-building risks as conditions, not events

Businesses are generally good at responding to things that happen. A machine stops, a customer complains, a delivery is missed, someone is injured. The signal is clear, people gather, and action follows. They are much worse at responding to things that become. A maintenance backlog grows a little each month. Overtime creeps up. Dust settles in a workshop that “always looked like that”. A supplier quietly becomes more critical. Quality drifts. Spreadsheets multiply. Nothing seems urgent on any single day.

That is exactly why these slow-building problems become serious. They lack the sharp signal that triggers action, so they are noticed only when the consequence arrives: a breakdown, an injury, an illness, a key person leaving, a customer lost. By then, reversing the cause is slow and expensive.

This article explains why slow-building risks need to be managed as conditions rather than events, how familiarity turns warning signs into “normal”, how to define and monitor a condition, and why controls for one problem can create another. It is general information. Some slow-building hazards, such as airborne dust, noise and fatigue, are covered by work health and safety duties; Safe Work Australia and your state or territory regulator publish guidance, including exposure standards for some airborne contaminants.

Events and conditions

An event asks: what happened? A condition asks: what is the business becoming?

“The main compressor fails” is an event. “Bearing wear progressing beyond agreed vibration and temperature limits” is a condition. “A worker develops a dust-related illness” is an event. “Airborne dust exposure in the workshop gradually increasing” is a condition. The event is what everyone remembers. The condition is what could have been managed.

Research on dust control on construction sites, by Jian Zuo and colleagues in 2017, illustrates the pattern well. Managers varied widely in how seriously they took dust; some saw it as a health risk, others as a nuisance. Many treated dust outbreaks as one-off events linked to particular work or weather rather than as an ongoing site condition that needed continuous monitoring. Many relied on looking rather than measuring, and regular monitoring was often done only when specifically required. The lessons apply well beyond dust.

Four misreadings

• No incident means the control is working. Slow-building risks give weak feedback. A business can run for years without an obvious event while exposure accumulates.
• If it were a problem, we would see it. Human senses are poor instruments for gradual change. Fine dust, slow wear, gradual drift and rising fatigue are hard to see until they are severe.
• We have a policy, so it is controlled. Control depends on what is measured, noticed and acted on in practice.
• One control solves it. Controls interact. Water suppression for dust, for example, uses water, which may be scarce in exactly the dry conditions when dust is worst. A fix in one place can create a problem elsewhere.

How warning signs become normal

People who work around a condition every day stop noticing it. Familiarity lowers perceived urgency:

• Minor vibration becomes “how the machine runs”.
• A workaround becomes “how the process works”.
• Regular overtime becomes “what delivery requires”.
• A backlog becomes “normal workload”.
• Dust becomes “part of the workshop”.

The absence of immediate harm reinforces the habit: “we’ve done it this way for years”. For gradual risks, that reasoning is especially weak, because the delay between exposure and consequence is exactly what stops experience from teaching the lesson. Someone new to the business often sees what everyone else has stopped seeing, so ask newcomers what surprised them. The making a risk register change decisions article covers turning indicators into triggers that prompt action.

Define the condition and its normal range

Managing a condition needs a few things an event-based approach does not:

1. A definition of the condition, not just the eventual event.
2. A normal range: what “acceptable” looks like, ideally measured when things were known to be good.
3. Leading indicators: measures that move before harm occurs.
4. A monitoring frequency that matches how fast the condition can change.
5. Thresholds and trends: a level that triggers action, and a rate of change that triggers action even within limits.
6. An owner of the trend: someone responsible for the condition between incidents.
7. A periodic challenge of whether the control method still suits the condition.

The trend matters as much as the level. A value inside the limit but moving quickly in the wrong direction deserves attention now, not when it crosses the line.

Measure what senses miss

Where people cannot reliably see or feel a change, use measurement. That might be a simple instrument, a regular count, or a periodic professional assessment:

If monitoring only happens after a complaint, a regulator’s request or a visible incident, the business is managing reactively. How often something is monitored reveals what the business really treats as controllable.

Controls interact

Controls should be judged as a group, not one at a time. Adding inspections can improve defect detection while slowing flow and hiding the real process problem. Tight access restrictions on systems can reduce one risk while encouraging staff to create unauthorised workarounds. Extra approvals can reduce decision risk while delaying work and encouraging people to bypass them. Adding more machines to an existing dust extraction system can reduce the airflow at every machine on it.

The aim is not maximum control. It is a stable, acceptable condition at a reasonable total cost. The changing the odds or changing who pays article covers why designed controls usually outlast those that depend on daily vigilance.

Commercial conditions creep too

Slow-building conditions are not only physical. Some of the most damaging sit in the accounts and the customer list:

• Margin erosion. Small discounts, unrecovered price rises and extra service given away gradually lower the margin, until the business is busy and barely profitable.
• Debtor days. Customers pay a few days later each quarter, and the cash gap widens without any single late payment looking serious.
• Customer or supplier concentration. One relationship grows from a fifth of the business to half, one order at a time.
• Skills ageing. The people who know how to run older equipment or serve older customers retire, and nobody has learned from them.
• Spreadsheet sprawl. Critical calculations move into files only one person understands.

Each of these can be tracked with a simple measure reviewed monthly or quarterly: gross margin by job type, average days to payment, share of revenue from the largest customer, a list of skills held by only one person, a register of critical files. The point is the same as on the workshop floor: define normal, watch the trend and act before the consequence arrives.

Carry knowledge from job to job

In businesses that work job by job, conditions can become “new” every time a project starts. The dust problem on one site, the supplier that drifted late on another, the fatigue that built up on a long installation: each is discovered afresh by a new team. Keep a short list of recurring conditions and how they were managed, and review it at the start of each significant job. A condition that has appeared three times is not bad luck; it is a feature of how the business works.

Awareness and capability both matter

Whether a control is applied consistently depends partly on whether people see the consequence as serious and accept responsibility for acting. That does not mean replacing engineering controls with awareness campaigns. It means the technical and human sides work together. A good control that managers see as low priority will be applied inconsistently. A motivated manager without the right equipment or information cannot compensate forever.

A worked example

This is an illustration. A joinery business with twelve staff has had no serious incidents in years. The owner runs a review of slow-building conditions and picks three.

Dust. The dust extraction system was installed six years ago. Since then, two machines have been added to it, and filters are changed “when they look dirty”. The owner borrows an airflow meter and finds that airflow at the panel saw is about 60% of what was recorded when the system was commissioned. The condition is defined as “extraction airflow at each machine below 80% of commissioning values”. Airflow is now checked monthly, filters are changed on a schedule, a ducting contractor reviews whether the system can handle the added machines, and an occupational hygienist is engaged to carry out air monitoring and advise on what the business’s work health and safety duties require.

Overtime. Average overtime has risen from about 2 hours to about 7 hours per person per week over 18 months. Everyone describes it as “just how busy we are”. The owner sets a rolling four-week average with a threshold of 5 hours, above which a capacity review is triggered: whether to hire, subcontract, change lead times or decline work. The first review leads to a new hire and longer quoted lead times on custom work.

Maintenance backlog. Overdue preventive maintenance tasks have grown from 3 to 19, the oldest overdue for five months. The owner sets two indicators, the number of overdue tasks and the age of the oldest, with thresholds of 5 tasks and 30 days. One Friday afternoon each fortnight is protected for maintenance.

Each condition now has an owner, a normal range, an indicator, a frequency and a trigger. None of the three had produced an incident. All three were heading towards one.

How this applies to a small Australian business

• List five risks that can worsen without an incident: wear, dust, fatigue, backlog, drift, dependence.
• Define each as a condition with a normal range.
• Choose a leading indicator and a monitoring frequency for each.
• Set thresholds for both level and trend.
• Name an owner responsible for the condition between incidents.
• Measure what senses miss, and get professional assessment where health is involved.
• Check how controls interact, especially when equipment or processes change.
• Ask newcomers what surprised them.
• Check your duties. Safe Work Australia and your state or territory regulator publish guidance on hazards such as dust, noise and fatigue.

Signals worth watching

• “It’s always been like that” used to explain a problem.
• Monitoring that starts only after a complaint or incident.
• Rising overtime or leave balances that nobody reviews.
• Maintenance tasks rolling over month after month.
• Equipment added to systems designed for less.
• Measurements drifting towards limits without anyone acting.

Common mistakes

• Waiting for an event before acting on a condition.
• Relying on visual checks for gradual change.
• Setting limits without watching trends.
• Adding controls without checking their side effects.
• Leaving conditions without an owner between incidents.
• Treating awareness campaigns as a substitute for engineering controls.

Frequently asked questions

How do we choose which conditions to monitor? Start with those that could cause serious harm, are hard to reverse or have already shown signs of drifting. Five is a good number to start with.

Do we need expensive equipment? Often not. Simple instruments, payroll data, maintenance lists and inspection records cover a lot. For health hazards, a professional assessment is worth paying for.

How often should we check? Match the frequency to how quickly the condition can change. Fast-changing conditions need frequent checks; slow ones can be reviewed monthly or quarterly.

What if the trend is bad but still within limits? Act on the trend. It is cheaper to correct a drift early than to recover from crossing the line.

Who should own a condition? Someone who sees it regularly and has the authority to act on the indicators, not only the person who would respond to an incident.

Questions to ask

• Which of our risks build slowly rather than arrive suddenly?
• What does normal look like for each, and when did we last measure it?
• Which indicators would warn us early?
• What are we relying on our eyes to detect?
• Which of our controls might be creating new problems?
• Who owns each condition between incidents?

Bringing it together

Slow-building risks rarely produce the clear signal that triggers action, so they become normal until they cause harm. Manage them as conditions: define what normal looks like, choose leading indicators, measure what senses miss, set thresholds for both level and trend, and give each condition an owner between incidents. Check how controls interact, and pair engineering controls with genuine responsibility. A business that watches what it is becoming, not only what has happened, can correct course while correction is still cheap.

---

Source: KEVOS notes, drawing on J. Zuo, R. Rameezdeen, M. Hagger, Z. Zhou and Z. Ding, “Dust pollution control on construction sites: awareness and self-responsibility of managers”, Journal of Cleaner Production (2017), and on teaching material on environmental and operational risk. Examples and figures in this article are illustrations. This article is general information, not safety advice.