We showed up with four truckloads of steel and nowhere to put it

School project. 650 tons of structural steel total — including 100-foot-plus long-span joists for the gymnasium. Nice sized project.

Our first mobilization was the north half — outer classrooms and hallway steel. Four truckloads. Five-man crew. Crane and operator on site. Everything scheduled, everything planned.

Then we pulled in.

The bricklayer had taken over the site. His materials were everywhere. His mixing station sat right where our staging area was supposed to be. And his lull had chewed the access roads into deep ruts — the kind that make you question whether a loaded flatbed can even get through without sinking.

Our laydown area was gone.

We had four trucks of steel rolling in, a crane set up and on the clock, five ironworkers ready to go — and very minimal space to work with.

We had no choice but to make the best of a bad situation. But "making the best of it" meant double-handling every piece of steel. Unload it once, move it to a temporary spot, then move it again when we needed it for the pick. The shakeout process that should've been clean and efficient turned into a mess. Every pick took longer. Every sequence got shuffled.

We lost a full day of productivity. Five men plus crane and operator — burning hours while we worked around a problem that didn't need to exist.

And here's the thing that kept running through my head the whole time: if the long spans had been scheduled for this mobilization, we'd have been in real trouble. Those need room. Room to unload, room to stage, room to rig. There is no double-handling a 100-foot long span in a tight site. That would've shut the job down.

We got lucky on the timing. But luck isn't a system.

What a 30-minute site walk would have caught

If I'd driven out to that school two weeks before mobilization — no crew, no crane, just me and the erection drawings — I would've seen the bricklayer's setup. I would've seen the ruts. I would've seen that our staging plan didn't match reality.

And I would've picked up the phone, called the GC, and said: "We need to talk about site access and laydown before I ship steel."

That phone call costs nothing. Showing up and finding out costs you a full crew day.

The pre-site visit turns a five-figure problem into a free phone call.

Here's the system I built after that job

I wrote a full SOP for pre-site visits. It's mandatory on every project — no exceptions. My PM walks through it before we mobilize any job. Here's the core of what it covers, and it's stuff you can start using tomorrow.

1. Ground and road conditions

This is the one that burned us on the school job. Are the roads compacted and accessible? Any soft spots, mud, or ruts from other trades' equipment? Does the site need additional stone or grading before you can get a loaded flatbed in and out safely?

If the answer is "maybe" — that's a phone call to the GC before you ship steel. Not after.

2. Laydown and staging — mark it up

Don't just look at the laydown area. Mark up a site plan with your designated staging zones. Color-code them — one color for your steel, a different color for access paths, a different color for crane setup.

Then send that markup to the GC. Now it's documented. Now there's a record that says "this area was designated for our materials." If another trade takes it over before you mobilize, you've got documentation. If you need to file for non-productive time, you've got proof.

3. Other trades' status

This is the checklist item most guys don't think about until it's too late. Who else is on site right now? Where are their materials staged? Is anyone blocking your laydown, your erection area, or your crane setup zone?

On the school job, the bricklayer's mixing station and lull damage were the entire problem. A site visit two weeks earlier would've caught it and given us time to coordinate with the GC.

4. CMU pockets and anchor bolts

If your steel is going into CMU — and on a school job it usually is — you need to spot check pockets before you show up with a crew. Check size, location, and elevation. If plates require grouting, verify it's 100% complete. If leveling nuts are required, make sure at least one per column is shot to grade by the concrete sub.

Here's one most guys learn the hard way: if it's a pocket-to-pocket condition, you need one side open through the wall — or a slot high enough to enter the beam or joist with one side pitched high. If that's not there when your crew shows up, you're dead in the water.

Spot check top-of-plate elevations against the erection plan. If they're off, that's an RFI before mobilization — not a field fix on erection day.

5. Crane setup and access

Can the crane you quoted actually get to the building? Is there room for outriggers? What's the ground bearing — do you need crane mats or cribbing? What's the farthest pick radius, and does it match what you estimated?

Confirm the access path for both the crane and the delivery trucks. And establish your signal person and communication method — radio, hard line, or phone — before day one.

6. Document everything in one place

We use the Raken app. Every pre-site visit gets documented through a checklist form inside Raken — timestamped photos, field notes, everything branded and organized in one report.

Whatever tool you use, the rule is the same: if you didn't document it, it didn't happen.

After the visit, send a summary email to your team. Subject line: "Pre-Site Visit — [Project Name] — [Date]." Attach the checklist report and any marked-up plans. Now your foreman, your office, and your file all have the same information before a single piece of steel leaves the shop.

The rule that makes all of this work

No steel gets mobilized until the pre-site visit checklist is signed off. That's the rule. Not optional. Not "when we have time." A hard stop in our process.

If the PM walks the site and finds a problem — a laydown conflict, bad roads, anchor bolts not set — it gets resolved with the GC before we ship steel. Not after the crew is standing there at full rate.

The part most owners get wrong

"I already know my job sites. I don't need a checklist."

Maybe you do. But your PM doesn't know every site. Your foreman driving to a new project Monday morning doesn't know it. And the guy you hire next year definitely doesn't know it.

The checklist isn't for you. It's for the company that runs without you standing on every job.

That's the whole point. Documentation is protection. And this is one of the simplest, highest-value systems you can build.