n
28

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.
2 comments

Log in to join the discussion

Log In
2 Comments
kareng27
kareng271mo 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.
6
abby308
abby3081mo 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.
3