The Problem That Doesn't Wait
The previous article looked at the mentorship void — how compressed timelines have squeezed out the development time junior staff need. But there’s another consequence of the valley’s pace that hits production teams regardless of experience level: the standards they’re working to don’t stay still.
In The CAD Standards Problem, I talked about the challenge of navigating different agencies with different expectations. That’s a structural problem — it exists because the agencies are different. This article is about a different problem: the standards themselves change, and they change constantly. New checklists, revised formatting requirements, updated digital submittal processes, modified note standards — every agency in the valley evolves at its own pace, on its own schedule, and almost never in coordination with the others.
For production staff, the structural problem is hard enough. The temporal problem — things changing underneath you while you’re working — is what makes it exhausting.
When the Ground Shifts Mid-Project
The most damaging revisions aren’t the ones that happen between projects. Those are manageable — you update your templates, adjust your approach, and move on. The ones that cost real time and money are the changes that land in the middle of active work.
A firm may spend weeks refining a plan set for submittal, only to learn that the agency has updated a note format, changed a detail requirement, or rolled out a new digital review platform since the project started. The design is still valid. The engineering is still sound. But the presentation — the sheets, the notes, the formatting — no longer matches what the reviewer expects.
I’ve seen a team prepare a full plan set for resubmittal after addressing every comment from the first review, only to discover that the agency had updated its title block requirements between review cycles. The engineering corrections were done. The sheets were coordinated. But the title blocks were wrong — and the agency wouldn’t accept the resubmittal until they were updated. That’s a day of production time spent on something that had nothing to do with the design.
Mid-review changes are even worse. When a standard shifts while a plan set is actively being reviewed, designers are forced to address the original review comments and incorporate the new requirements simultaneously. Two separate sets of changes, on the same sheets, under the same deadline. There’s no clean way to manage that without a system built to handle it.
The Update Nobody Announces
Some agency changes are published clearly — a new standards manual, an updated checklist, a formal notice. Those are disruptive, but at least they’re visible. The changes that do the most damage are the ones nobody announces.
A reviewer starts enforcing a requirement that wasn’t in the published standard. A checklist gets quietly updated on the agency’s website without a revision notice. A digital submittal portal changes its file naming requirements. A new reviewer joins the agency and interprets existing standards differently than their predecessor.
These aren’t hypothetical scenarios. I’ve talked to designers who found out about a changed requirement only after their plan set was rejected — and when they checked the agency’s website, the updated standard had been posted weeks earlier with no notification. The information was technically available. The communication was effectively invisible.
For production teams juggling multiple active projects across multiple agencies, tracking these quiet changes is nearly impossible without a system for it. And most firms don’t have one.
What Constant Change Does to a Production Team
The technical cost of agency revisions — rework, delays, extended review cycles — is measurable. The human cost is harder to quantify but just as real.
I’ve seen a team get a plan set through two rounds of review, only to have a third reviewer flag a note format that the first two never mentioned. That kind of experience makes people stop trusting the process — they start bracing for surprises instead of focusing on the work.
When the rules keep changing, designers stop committing fully to any approach. They hedge. They over-document. They build in extra time for revisions they assume are coming, even when they might not. That defensive posture is rational — it’s a survival mechanism — but it slows everything down. A team that’s constantly preparing for the next disruption has less capacity to focus on the current project.
The worst part is that the frustration isn’t proportional to the difficulty of the change. A title block update takes 30 minutes per sheet. A note format revision takes an hour across the set. These aren’t complex tasks — they’re tedious ones. And tedious rework on changes that feel arbitrary is what drives good people out of the profession.
Staying Ahead Instead of Catching Up
When I work with firms on this problem, the first thing I look at is how they’re tracking agency changes — and the answer is almost always “we’re not.” Someone finds out about a new requirement when a plan set gets rejected, they fix it for that project, and the knowledge stays in that person’s head. The next project that goes to the same agency? Different designer, same surprise, same rework.
The starting point is what I call a revision log — a simple, shared document that tracks every agency change the firm encounters. Not a comprehensive database of every standard — just a running record of the changes that actually affect your plan sets. When a reviewer sends back a comment that references a new requirement, someone logs it: which agency, which requirement, what changed, and when you found out. Over time, that log becomes an early warning system. You start seeing patterns — which agencies update frequently, which requirements tend to shift, which review cycles are most likely to introduce new expectations.
The next layer is building your templates to absorb change instead of breaking under it. In The CAD Standards Problem, I talked about using a single base template instead of agency-specific ones. That principle is even more important here. When a note format changes, you need to update it in one place and have it propagate across every project — not hunt through 15 active project files making the same edit. Dynamic blocks, note libraries, style-based formatting, and centralized detail sheets are the tools that make this work. When a change comes in, the question should be “which library file do I update?” — not “which 30 drawings do I open?”
The third piece is building change management into the production workflow itself. When a new requirement is discovered, who’s responsible for updating the templates? How does that update get communicated to the rest of the team? Is there a checkpoint before submittal where someone verifies that the plan set reflects the latest known standards for that agency? Most firms I’ve worked with have no formal process for any of this. The update happens ad hoc, the communication is verbal, and the verification is “I think we’re good.” That’s how the same agency change catches a firm off guard twice.
This is a core part of what I do at Frye CAD Consulting — building template systems and change management workflows that let firms respond to agency revisions in hours instead of days, and in one place instead of thirty.
A Hidden Cost That Can Be Controlled
Agencies will keep updating their standards — that’s not going to change. But the cost of those updates doesn’t have to land on production teams as unplanned rework. With the right tracking, the right template architecture, and the right change management workflow, firms can absorb revisions efficiently and predictably instead of reactively and painfully.
This is the seventh article in a multi-part series exploring the real challenges facing Southern Nevada’s engineering and surveying workforce. In the final article, I’ll examine the case for automation and why modernizing workflows is essential for firms that want to stay competitive.