In my first year at Gensler (2017), I was handed what I thought was my big break. A mid-size commercial office building in downtown Seattle, owned by a client who wanted to explore an office-to-residential conversion. It was the kind of project I'd been itching to get my hands on. I was 22, fresh out of grad school, and I was convinced I could handle it.
Two weeks in, I submitted the initial feasibility study. It looked perfect on my screen. The report had the right zoning analysis, the structural load calculations were solid, and the pro forma showed a respectable 12% return. I checked everything myself, approved it, and processed it.
We caught the error when I got a call from the client's project manager. She was confused. "Your report mentions a window-to-wall ratio of 40%. The drawings we sent you show a ratio of 55%."
My stomach dropped. She was right. I'd used the wrong set of survey drawings—the ones from the tenant improvement project in 2014, not the updated shell-and-core survey from 2016.
The result came back as a complete redo. $3,200 of billable work, straight to the trash. Plus a one-week delay while my team re-ran the daylighting analysis and adjusted the floor plan layouts.
That's when I learned: 5 minutes of verification beats 5 days of correction. Period.
The Birth of the Pre-Flight Checklist
After that mess, I sat down with our senior project architect to figure out how to prevent it from happening again. We looked at the six-month post-mortem data from our office. Three projects had issues related to mismatched source documents. One had a structural miscalculation because someone used the wrong column grid. (Source: Gensler internal project review, Q4 2017).
We created a simple, 12-point checklist called the "Project Kickoff Verification." It was nothing fancy—just a list of things to confirm before you start any major deliverable:
- Survey Date: Is the underlying survey the latest version? (I made this the first item, for obvious reasons.)
- Program of Requirements: Does it match the client's signed scope? (Not the verbal agreement from the last meeting.)
- Zoning Code Edition: Are we referencing the 2024 code, or the 2021 code that's been superseded? (This is a surprisingly common pitfall in cities that update every year.)
- Structural Load Assumptions: Confirm with the structural engineer before finalizing the floor plan. (We once had a team design for 80 psf when the code required 100 psf.)
- Energy Model Baseline: Is the baseline match to the current climate zone data? (Surprise, surprise—some team members were still using 2016 weather files.)
- Client Review List: Has the client signed off on the last set of markups? (Not the email where they said "looks good"—the formal approval.)
- Renderings File Paths: Are all linked files pointing to the current server location? (We lost a presentation once because a third-party model wasn't linked properly.)
- Budget vs. Actual: Are the cost estimates based on the latest market data? (Prices as of Q1 2018; verify current rates.)
- Permitting Precedents: Have we checked with the local building department for recent interpretations? (A new code official can throw a wrench in the works.)
- Fire & Life Safety Plan: Does the egress plan accommodate the new residential units? (Conversion projects often require additional staircases.)
- Acoustic Strategy: Are we accounting for the difference between office and residential noise standards? (STC 45 vs. STC 55 is a big jump.)
- Client Sign-Off: Final approval before submission.
The first time we used it, the senior architect laughed and said, "This is what we should have been doing all along." (Which, honestly, was a polite way of saying, "Your $3,200 mistake was totally avoidable.")
The Numbers Don't Lie
The 12-point checklist I created after my third mistake has saved us an estimated $8,000 in potential rework over the past 18 months. That's a conservative number. I don't have hard data on the total industry-wide cost of document mismatches, but based on our 5 years of conversion projects, my sense is that data-entry errors (like using wrong drawing versions) account for about 8–12% of all first-delivery issues in our sector.
I wish I had tracked cost savings more carefully from the start. What I can say anecdotally is that since we implemented the checklist, we've caught 47 potential errors. That's 47 times someone submitted something that would have required a redo. The cost per redo in our group averages about $170 per hour (Source: Gensler project accounting, Q2 2023). So even if half of those were minor, we're looking at significant savings.
The Checklist is the Cheapest Insurance
I'll be blunt: I have mixed feelings about the checklist. On one hand, it feels like an admission of incompetence—like we can't be trusted to do our jobs without a list. On the other, the most seasoned architects I know use them. The difference isn't whether you use one; it's whether you admit it.
This worked for us, but our situation was specific. We're a mid-size B2B team with predictable project types—mostly commercial-to-residential conversions. If you're dealing with ground-up residential developments or mixed-use projects, the calculus might be different. Your mileage may vary if you're a smaller boutique firm with a different risk profile.
I can only speak to domestic operations. If you're dealing with international logistics or clients in different regulatory environments, there are probably factors I'm not aware of. (This was true 10 years ago when digital collaboration was limited. Today, project management software has largely closed that gap.)
The 'local is always faster' thinking comes from an era before modern logistics. Today, a well-organized remote vendor can often beat a disorganized local one. The same logic applies to verification processes. A disciplined, remote team with a strong checklist can often outperform a local team that relies on intuition.
The Bottom Line
Most problems are preventable. A checklist is the cheapest insurance you can buy. If you don't have one, create one. It doesn't have to be perfect—just start with one item that catches the most common error in your workflow. Add items as you find more. That's it.
Done.
Prices as of Q1 2025; verify current rates. This approach worked for us, but your situation may differ. The 12-point checklist idea is ours, but the underlying principle is universal: verify before you execute.
