Coordinate a Scissor Lift Incident After Contact With Shelving

Contact between a scissor lift and a shelving rack brings two demands at once. The site contact wants to keep the lift working for the rest of the shift, and they want an answer on whose fault this was. As the service manager, neither question is yours to answer on that first call. Your job is to get people safe, pull the unit out of service, and set a fact finding path that holds up later, without guessing at blame or damage from a partial account over the phone.

Why This Conversation Goes Wrong

The caller is usually under real pressure. A crew is waiting, a job is behind schedule, and the equipment looks fine from where they're standing. That pressure pushes toward two bad moves. The first is authorizing continued use because the contact sounds confident nothing is wrong. Confidence is not an inspection. A mast, platform, or outrigger can take damage that isn't visible from a glance, and if you clear a lift that later fails, you've turned a shelving bump into an injury.

The second bad move is agreeing with a fault story before you have facts. If the caller says it sounds like operator error, and you go along with that on the phone, you've prejudged something that might touch insurance, a workers comp claim, or a dispute over damaged racking. Once you've said those words, they're hard to take back, even if the inspection later tells a different story.

There's a third failure that's quieter but just as costly. If you never ask who owns the site incident report, you may never get one. Your service inspection ends up as the only written record of the event, and that's a weak position if the customer disputes fault weeks later with no report of their own on file.

How to Prepare Before You Pick Up the Phone

Know your isolation policy before the call, not during it. You should be able to state in one sentence how the unit gets tagged out and who confirms it happened. Know who normally owns incident reporting on that customer's site. Some sites have a named safety coordinator, others leave it to whoever answers the phone, so ask directly if it isn't obvious.

Know your own inspection lead time and who on your team performs it, so you can commit to a real date instead of a vague promise. Know exactly what you need back from the customer, their incident report, any photos of the contact point, and the names of anyone who witnessed it. Write these down ahead of a call like this so you're not building the list live while the customer is pushing you for a yes.

It also helps to think about this call as one version of a pattern you'll use again. The same discipline, separate the facts from the conclusions, applies to a Guide a Server Room Cooling Request Toward Verification call, where a customer wants a verdict on airflow before anyone has checked the unit, and to an Escalate a Forklift Battery Heat Concern call, where heat gets blamed on the battery before anyone has measured it.

What to Say

Wes, the site safety coordinator, opens with the pressure point. "We really need this lift for one more task before the shift ends. Can we keep running it? This sounds like it was on the operator, not the equipment."

Camille, the service manager, doesn't answer either part of that. "I need the unit tagged out and left down right now, nobody restarts it. Before anything else, has anyone been hurt, and who's filling out your site incident report?"

Wes says no one was hurt, and the report hasn't been started yet.

Camille responds, "Get that report going today, and name someone as the owner of it. On my end, I'll schedule a technician to inspect the lift, the mast, and the contact point on the shelving. Once your report is complete, send me a copy. Until both of those are done, I'm not going to say what caused this or whether it was operator error. That's exactly what the inspection and your report are for."

Wes pushes once more. "So you're saying it wasn't the operator."

Camille holds the line. "I'm not saying that either way. I don't have enough in front of me to say it either way, and neither do you yet. Once I've seen the unit and read your report, we'll both know more than we do right now."

That answer works because it's firm without being combative. Camille isn't refusing to help, she's refusing to guess. She also treats the operator fairly by declining to convict them on a secondhand account, and she gives Wes something concrete to do instead of an argument to win. The site's report and the service inspection become two separate records that can be checked against each other later, which is far stronger than one manager's opinion formed on a phone call.

Mistakes to Avoid

1. Clearing the lift for one more task because the caller sounds sure it's minor. Sound and structural condition are different things.
2. Agreeing with a fault story, even a soft one like "probably operator error," before a technician has looked at the equipment.
3. Skipping the injury question because the call feels routine. Ask it every time, first, before anything else.
4. Letting the call end without naming who owns the site incident report. If nobody owns it, it doesn't get written.
5. Promising a repair timeline or a return to service date before your technician has actually inspected the mast, the platform, and the point of contact with the shelving.

How to Practice and Score This Conversation

This call is easy to describe and hard to hold under real pressure, so practice it out loud before you need it. Ask a colleague to play the safety coordinator and push you the way Wes does, first for permission to keep using the lift, then for a verdict on fault. Notice where you're tempted to soften your answer just to end the call politely.

Score yourself, or have a coach score you, against three things. Did you isolate the unit and ask about injury before anything else. Did you name who owns the site incident report instead of letting that slide. Did you get through the whole call without assigning blame or predicting what the inspection will find. If you can answer yes to all three under pushback, you're ready for the real version.

DealSpeak's Equipment Rental practice conversations let you run this exact scenario against an AI counterpart that argues the way a real site contact does, then scores your response against those same three points. Running it more than once, with the counterpart pushing harder each time, is a fast way to find where your answers still drift toward speculation.

The pattern here isn't specific to scissor lifts. Isolate the equipment, name who owns the report, request the record, and hold off on conclusions until you have one. Get comfortable with that sequence and you'll use it just as easily on the next incident call, whatever piece of equipment it involves.