It was a Tuesday morning in September 2022. I'd been handling lift planning orders for about three years at that point, and I thought I had it pretty well figured out. The phone rang—it was a project manager asking about a 400-ton lift we had scheduled for the following month. He wanted to confirm the rigging specs.
"Sure thing," I said. "We're using the Manitowoc 777 for that job. Standard configuration."
"Great," he said. "That's what I have in my notes too."
Two weeks later, we were on-site. The crane was there. The load was there. And the crane couldn't reach the lift radius we needed by about 12 feet. That's when I learned that "standard configuration" means different things to different people. Specifically, I'd assumed a lattice boom crawler crane model with a standard boom length. He'd assumed a configuration with a different jib setup. Neither of us had checked the other's assumption.
The cost to fix it? $3,200 in crane reconfiguration fees and a 3-day delay. That's when I created my first real checklist.
For months after that, I thought the problem was simple: I needed to be more careful when confirming crane model specifications. Check the model number. Double-check the boom length. Verify the counterweight. I made a little post-it note on my monitor that said "CONFIRM EVERYTHING."
But here's the thing—I kept making similar mistakes. Not the same mistake, exactly, but variations of it. I'd get the right crane model but the wrong attachment. Or the right specifications but the wrong configuration for the job site. Each time, it cost time and money. Each time, I felt like an idiot.
The most frustrating part? I was following my checklist. I told myself I was being careful. But the errors kept slipping through. You'd think that having a written list would catch everything, but it doesn't if you're checking the wrong things.
After the third incident—a $1,800 mistake involving a telehandler attachment that was incompatible with the work platform—I was ready to quit the industry entirely. What finally helped wasn't a better checklist. It was understanding why my checklists weren't working.
Let me break down what I eventually figured out. The surface issue—"I need to check more carefully"—wasn't the real problem. The real problem had three layers I hadn't been seeing.
I used to think that the crane's spec sheet told you everything you needed to know. It doesn't. The specifications for a Manitowoc 2250, for example, will tell you its max lift capacity, boom length options, and ground bearing pressure. But they won't tell you how that crane behaves differently when you're lifting at 80% radius versus 50% radius. They won't tell you that a specific job site's soil conditions might require different cribbing than the manual suggests.
That's not a flaw in the specs—it's a limitation of how we interpret them. I was treating spec sheets like a shopping list when I should have been treating them like a starting point for a conversation.
Here's something nobody taught me in training: every person involved in a lift plan makes assumptions. The engineer assumes the site conditions are as drawn. The crane operator assumes the rigging team has the right hardware. The project manager assumes the configuration is what was discussed in the planning meeting. None of these assumptions are malicious. They're just... assumed.
The problem is that assumptions multiply. Two assumptions per person, four people involved, that's 16 potential points of failure. And each assumption seems perfectly reasonable to the person making it. I once assumed that "lattice boom crawler cranes" listed on a job order meant a specific model because that's what we'd used on the last three projects. I didn't check. It wasn't the same model. That was a $1,200 lesson I'll never forget.
This is the one that took me the longest to understand. I'm a trained engineer. I'm supposed to trust documentation. When something is written down, approved, and filed, my brain automatically treats it as correct. That's actually a good thing most of the time—it lets you make decisions without verifying every single detail from scratch.
But it's also a trap. I'd look at a lift plan that had been signed off by three different people and assume it was right. I'd check the crane model, see the right number, and stop checking. The mistakes weren't in the things I checked—they were in the things I didn't think to check because they were "already verified."
Let's talk money, because that's the language my boss understood. I kept a log of every mistake I personally made or caught in my first three years. I'm gonna share the numbers, but don't quote me on the exact figures—I might be misremembering some of the smaller ones.
In 2021, I was involved in 6 significant specification errors across our crane fleet operations. Total cost in rework, delays, and lost productivity: roughly $8,500. In 2022, after the 777 incident I mentioned earlier, I improved that to 3 errors totaling about $4,200. But I was still making mistakes, and they were still expensive.
The real kicker wasn't just the direct costs. It was the hidden stuff:
After the third rejection of a lift plan in Q1 2024—each for a different reason—I created our pre-check list. I'd say it's saved us an estimated $8,000 in potential rework in the past 18 months. Five minutes of verification beats five days of correction, every single time.
I'm not gonna give you a 47-step process, because that's not how people actually work. Here's the short version of what changed for me:
1. I stopped assuming that written specs were final. Now, before any lift plan goes out, I do a reverse check—I run through what the plan can't do, not just what it can. This catches mismatches between what's specified and what's actually needed.
2. I started asking questions that had obvious answers. "Is this the crane we discussed?" turns into "This is a lattice boom crawler crane, right? Not a telescopic or truck-mounted? And you're sure about the radius?" It feels awkward at first. It's saved me from at least three costly assumptions.
3. I embraced the awkward silence. The best question I ask now: "What am I not asking?" I stole this from a senior engineer who had 30 years on me. It sounds silly, but it makes people think about the thing they assumed was obvious. That question alone caught a job site access issue that would have made our planned crane configuration impossible.
Look, I'm not saying I never make mistakes anymore. I absolutely do. But the big ones—the ones that cost thousands and make you want to crawl under your desk—those have mostly stopped. The 12-point checklist I created after my third major error has caught 47 potential issues in the past 18 months. 47 things that would have cost time, money, and credibility.
Five minutes of verification. Beats the alternative every time.
Our application engineers provide lift-plan-specific recommendations at no charge.
Ask an Engineer