Rushing & Taking Shortcuts

Nobody rushes at the start of a task. Rushing arrives partway through, once something has already gone wrong — a late delivery, a wrong measurement, a machine that would not start, an hour lost to weather. By the time anyone is moving fast, the time is already gone, and that changes what rushing actually is. This Rushing & Taking Shortcuts Toolbox Talk (Safety Talk / Tailgate Talk) is about the thirty seconds in which the decision gets made.

Here is the distinction that carries this whole talk: rushing does not make the work faster. It makes the work shorter. Your hands do not move at double speed and your tools do not cut quicker. What actually happens is that steps come out — and because nobody consciously decides which ones, they come out in the order of what is easiest to skip rather than what matters least. You are not going quicker. You are doing less, and choosing badly which less.

The delay is already sunk#

This is the part that changes how a crew thinks about it.

If you lost forty minutes waiting for a delivery, those forty minutes are gone. They cannot be recovered by moving faster, because the work still contains the same number of actions and each one still takes the time it takes. The only way to "catch up" is to remove something.

So the honest question is never how do I go faster? It is what am I about to leave out, and can I afford to?

Ask it that way and the decision changes character. I will skip the anchor setup is a very different sentence from I will hurry up, and it is the same decision.

And once it is stated as an edit, it can be discussed. A crew can have a sensible conversation about which twenty minutes of work to drop from the end of the day. It cannot have a sensible conversation about "getting a move on."

The arithmetic, honestly#

Shortcuts persist because they work. Being fair about that is what makes this talk credible.

Setting a proper anchor point instead of free-climbing: perhaps four minutes. Walking three floors for the right tool instead of using the wrong one: maybe six minutes. Waiting for a banksman before reversing: two minutes. Fitting the guard back after clearing a jam: ninety seconds.

Those savings are real, and they repeat. Somebody taking that shortcut twice a day for a year genuinely saves days of their life. That is why "don't take shortcuts" delivered as an instruction fails — it is asking people to disbelieve something they can measure.

The correct framing is that this is a bad trade repeated, not a stupid decision made once. The saving is small, certain and immediate. The cost is large, uncertain and delayed. Human beings are systematically poor at that comparison, and the fact that the trade has paid off two hundred times is exactly what makes the two hundred and first feel safe.

The five moments#

Rushing is not spread evenly through a shift. It concentrates, and knowing where is more useful than being told to slow down.

Recovering a delay. The single most common. Something was lost earlier, and the crew is trying to make it back.

When somebody is waiting. A crane hovering, a concrete truck turning, a crew standing idle, a road closure with an end time. This is the strongest trigger there is, and the least talked about — because the cost of the wait is visible, immediate and has a face attached to it, while the cost of the shortcut is invisible and probabilistic. Nobody wants to be the reason twelve people are standing still.

The last ten percent of a task. The job is essentially done, the mind has moved to the next thing, and the remaining steps feel like formalities. This is where guards do not go back and edges stay open.

Immediately after an interruption. The interruption cost time, and the recovery is where the missed step happens.

When the alternative is coming back tomorrow. Finishing tonight avoids a return trip, remobilising, and another permit. That calculation is entirely rational and it is where a great many serious incidents live.

What comes out first#

When steps are removed under pressure, the order is remarkably consistent — and it is worth knowing because it is the opposite of the order you would choose deliberately.

The check goes first. The pre-use inspection, the look around, the test before touching. It goes first because nothing visibly breaks when you skip it — you get away with it immediately and permanently, until once.

Then the second person. The spotter, the banksman, the verifier — released to do something more productive. That is the layer that catches other people's errors, and it is given up precisely when error rates are highest.

Then the setup. The anchor, the platform, the isolation, the containment.

And finally the restore. The guard, the cover, the guardrail, the tidy — the last five minutes of the task, done by people who have mentally finished.

Notice that every one of those is a control, and none of them is the productive work itself. Rushing does not remove the drilling or the lifting. It removes everything wrapped around it.

Where the duty sits#

There is no OSHA standard on rushing, and the wider question of schedule pressure belongs to the time management talk in this library rather than here — that is where sequence, crew size, durations and the employer's levers are dealt with. Do not treat this talk as covering that ground.

What applies:

Section 5(a)(1) and recognised hazards. A programme that reliably produces shortcuts is a recognised hazard once it is known, and should be reported as a condition rather than a personality trait.

1926.21(b)(2) — instruction in the recognition and avoidance of unsafe conditions.

1926.20(b)(2) — frequent and regular inspections by competent persons, which is how removed guards and open edges get found.

1926.32(f) — the competent person with authority to take prompt corrective measures, which is who a crew needs when the honest answer is that the remaining work does not fit.

What can go wrong?#

A guard not replaced after clearing a jam, because the machine was already running late.

A spotter released to speed up a lift.

Reversing without a banksman because the truck is on a slot.

A ladder used for a two-minute job at a height that warranted a platform.

Working under a suspended load to save a re-rig.

An isolation shortened because the permit desk had closed.

The last edge left open because the crew is off the floor in ten minutes.

A second trip avoided by finishing something at dusk that should have waited for daylight.

How do we manage this properly?#

Name the edit, not the pace. Ask what are we leaving out? rather than can we speed up? — it turns an attitude into a decision that can be examined.

Treat the lost time as lost. Replan the remaining work honestly instead of compressing it, because compression is only ever removal in disguise.

Say out loud when someone is waiting. Naming the pressure — "I know the truck is turning" — takes most of its force away and lets the crew decide together rather than each person deciding alone.

Protect the last ten percent. Restore is part of the task, not what happens after it. Program time for it and check it happens.

Never release the second person to save time. They are the cheapest control on site and they are given up exactly when they are needed most.

Decide about tomorrow before dark, not at dark. The choice between finishing tonight and returning is best made with an hour of daylight left.

Make stopping legitimate. If nobody has ever heard a supervisor say "leave it, we'll do it properly in the morning", nobody will propose it.

And report a schedule that only works when steps are skipped. That is a condition, and it belongs in the same channel as any other.

Before you start#

• Confirm what time has already been lost today, and that you are not trying to recover it.
• Confirm what you would remove if you fell behind, and whether you could afford to.
• Confirm whether anyone will be waiting on you — crane, truck, crew, road closure.
• Confirm the restore steps for your task and that time exists for them.
• Confirm the second person for this task is staying, whatever happens to the schedule.
• Confirm you could say that the remaining work does not fit today, and to whom.
• Confirm what happens if this job is not finished tonight — honestly.
• Confirm nothing in the plan only works if everything goes right.

Talk it over#

• What is the shortcut on this site that everybody takes?
• How much time does it actually save — be specific?
• When did you last rush because somebody was standing waiting for you?
• Has anyone here heard a supervisor say "leave it until tomorrow"?

The bottom line#

Rushing does not make work faster; it makes work shorter. Hands do not move at double speed — steps come out, and because nobody consciously chooses which, they come out in the order of what is easiest to skip. That reframes the decision: the honest question is never how do I go faster but what am I about to leave out, and can I afford to? The delay is already sunk — lost time cannot be recovered by speed, only by removal. Be honest about the arithmetic: an anchor is about four minutes, the right tool six, a banksman two, refitting a guard ninety seconds — savings that are real and repeating, which is why instruction alone fails. It is a bad trade repeated: small certain immediate saving against a large uncertain delayed cost, and two hundred payoffs are exactly what makes the next one feel safe. Rushing concentrates in five moments — recovering a delay, when somebody is waiting (the strongest and least discussed, because the wait has a face and the risk does not), the last ten percent, straight after an interruption, and when the alternative is coming back tomorrow. And what comes out is always in the same order: the check, then the second person, then the setup, then the restore — every one a control, none of them the productive work itself.

Frequently asked questions about rushing and shortcuts#

Why doesn't telling people to slow down work?

Because it addresses pace, and pace is not what changes. Rushing removes steps rather than accelerating actions, so a worker told to slow down still faces the same gap between the work remaining and the time available. The instruction that works is different: name the edit — ask what is about to be left out and whether that is affordable.

If time has already been lost, why can't it be made up?

Because the work still contains the same number of actions and each still takes the same time. Lost time is sunk. The only mechanism available for "catching up" is removing something, which means every catch-up is an edit whether or not anyone says so out loud. Saying it out loud is what allows the crew to choose which edit sensibly.

How much time does a shortcut actually save?

Less than people assume, but genuinely something — roughly four minutes for an anchor point, six for walking to fetch the right tool, two for waiting on a banksman, ninety seconds to refit a guard. Those savings are real and they repeat, which is precisely why shortcuts persist. It is a bad trade repeated, not an irrational one-off.

What is the strongest trigger for rushing?

Being waited on. A crane hovering, a truck turning, a crew standing idle, a road closure with an end time. The cost of the wait is visible, immediate and attached to people who are watching, while the cost of the shortcut is invisible and probabilistic. Nobody wants to be the reason a dozen people are standing still, and that pressure does more than any deadline.

Which steps get dropped first?

Always roughly the same order: the check (because nothing visibly breaks when you skip it), then the second person — spotter, banksman, verifier — then the setup, and finally the restore. Every one of those is a control, and none is the productive work itself. Rushing never removes the drilling or the lifting; it removes what is wrapped around them.

Is this the same as the time management talk?

No, and they are deliberately separated. The time management talk covers schedule pressure as an employer problem — sequence, crew size, durations that include setup and clear-up, and the levers only management holds. This talk covers the moment of decision: what happens in the thirty seconds when a worker decides what to leave out.

Is there an OSHA standard on rushing?

No. The applicable duties are general: Section 5(a)(1) on recognised hazards — and a programme that reliably produces shortcuts becomes one once known — 1926.21(b)(2) on instruction in recognising and avoiding unsafe conditions, 1926.20(b)(2) on frequent and regular inspections by competent persons, and 1926.32(f) on the competent person's authority to take prompt corrective measures.

Download the rushing and shortcuts toolbox talk PDF#

Get this rushing and taking shortcuts toolbox talk as a print-ready PDF — available in English, Spanish, Portuguese, and Turkish. Print it, hand it to the crew, and collect signatures on the included attendance sheet.

Download the PDF — free account required. New members get 5 free downloads.

Related toolbox talks#

• Time Management
• Common Unsafe Behaviors
• Human Error
• Complacency in the Workplace

Sources#

• OSHA, 29 CFR 1926.21 — Safety training and education: https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.21
• OSHA, 29 CFR 1926.20 — General safety and health provisions: https://www.osha.gov/laws-regs/regulations/standardnumber/1926/1926.20
• NIOSH, Construction Safety and Health: https://www.cdc.gov/niosh/construction/default.html

Written by FieldSafetyTalk's safety professional — a CSP, ASP, CHST and OSHA Authorized Outreach Trainer with 14+ years of international construction safety experience across federal, heavy civil, and industrial projects.

Hazards covered