How vigilant oversight shapes dependable MEP design
Some roles are only noticed when they fail: the sentry at the city gate, the lookout in the crow’s nest, the eyes that never sleep. At VP Engineering, our QA/QC team fills that role. They keep watch over every drawing, every connection, and every dimension, making sure no hidden flaw slips by.
In this edition of Stolen Fire, we’re giving you a closer look at what that vigilance really means, not just as a promise, but as a clear, disciplined process that safeguards every project we deliver.
Why QA/QC Matters
Plenty of firms say they “do quality work.” Fewer can show you how they guarantee it.
- Isquality a proactive, consistent process, or just a last-minute check?
- Isit shared by the team, or all left to one designer under pressure?
- Isthere a system of oversight, or does the architect end up carrying the burden?
At VP Engineering, QA/QC isn’t an afterthought. It’s part of the DNA of every project, built in from day one. That means many eyes, many angles, at every stage.
The Purpose of QA/QC
Our QA/QC department exists to give clients more than drawings. We give them confidence.
- ReduceCosts – Catch errors early to avoid rework, change orders, and
- BuildTrust – Deliver coordinated, code-compliant plans that make decision-making
- BoostEfficiency – Fewer surprises in the field, smoother execution
- GuaranteeCompliance – Every deliverable is checked against standards, codes, and
This isn’t about fixing mistakes after they happen. It’s about making sure they never have the chance to.
Why We Formalized the Process
Before we established a dedicated QA/QC department, quality checks depended on available time and individual engineers. That left blind spots. By formalizing the process, we shifted from reactive problem- solving to proactive quality-building.
Our design managers lead the effort. With years of experience, they don’t just look for compliance, they review for constructability, coordination, and long-term performance.
How It Works
Our process is structured but practical:
- MultipleSweeps – Reviews at 50%, 75%, and 90% completion, not just before the permit
- TwoLayers of Review – Designers self-check, then QA/QC performs an independent
- Full-DisciplineView – Every system is scanned for coordination gaps and
- ConstructabilityFirst – Reviews anticipate the needs of contractors and operators, not just permit reviewers.
What This Means for Clients
For architects, developers, and building operators, our vigilance means fewer RFIs, fewer redesigns, and fewer delays. Projects run smoother, risks get caught before they cost money, and headaches are avoided entirely.
As one of our design managers put it: “The problems we prevent are the ones no one ever hears about because we caught them before they could exist.”
What Makes VP Engineering Different
A lot of firms rely on the project engineer or architect as the final safety net. We believe that’s too much pressure for one person. Our approach is layered, deliberate, and consistent:
- ManyEyes – Multiple reviewers, multiple
- Consistency– The same standards across every
- SharedResponsibility – Designers own their work; QA/QC ensures nothing slips
It’s the difference between a single glance at the horizon and a watch that never rests.
Proof in Practice
On a recent multifamily project, our QA/QC team flagged an HVAC zoning issue that would have caused tenant comfort problems and expensive rework. On another, we caught mismatched civil connection points that would have delayed installation. In both cases, the client never knew, because the problems never made it past our review.
The Takeaway
Vigilance in design is not myth. It is method. It is the discipline of looking from every angle, at every stage, with eyes trained to see what others might miss.
In Stolen Fire, we believe knowledge is most valuable when it is shared. By opening this window into our QA/QC process, we hope to give our clients more than a service. We give them certainty. And certainty is the foundation on which the best buildings are built.
