A client's basement blueprint from 1978 had a hidden structural column we almost missed.

We caught it because I decided to double-check the original survey against the city's digital archive on a slow Thursday, which saved us from a major framing error.

3 comments

3 Comments

maryh961mo ago

Oh man, I gotta push back a little on that. kareng27, I get what you're saying about process, but I think you're missing something important here. The city's digital archive is actually not part of the standard review checklist for most firms. It's a separate database that wasn't even around when these old buildings were done. So checking it isn't a normal step, it's a bonus layer of protection that most people skip. I'm not saying our process is perfect, but the fact that we caught it at all means we were already ahead. It's like finding a nail in a tire before it goes flat - sure, you wish you had a machine to catch it every time, but sometimes the human double-check is what saves you.

kareng272mo ago

That's a lucky catch, but honestly, relying on a slow day to find something that big feels risky. Good processes should catch those things every single time, not just when someone has extra time to dig. A missed column is a huge deal, so maybe the review steps need a solid look to prevent close calls. Depending on a random double-check just seems like a process waiting to fail.

abby3082mo ago

Right, because my entire structural review process runs on 'bored on a Wednesday' logic. I mean, we have checklists and everything, but maybe I should just start hiding a six-pack of energy drinks in the filing cabinet to simulate that slow-day urgency more often. It's definitely a more reliable system than my actual workflow.