Where the Data Starts — and Where It Breaks Down
The previous article looked at how disorganized project files undermine production — broken Xrefs, missing data shortcuts, version control problems. But there’s a layer underneath all of that: where the data comes from in the first place. Before a single grading line is drawn or a utility alignment is designed, someone has to go out into the field, collect the data, and bring it back to the office. That data becomes the foundation for everything that follows — existing conditions, topography, utilities, control, boundaries, and the real-world constraints that shape a project.
For all its importance, the connection between field crews and office staff is often fragile. Miscommunication, missing information, unclear instructions, and inconsistent workflows create a disconnect that affects designers, drafters, engineers, and ultimately the entire project team. When that link breaks down, the consequences ripple through the entire plan set — redesigns, delays, and frustration on both sides.
The Pace Problem
The valley’s development cycle moves quickly. Field crews are often juggling multiple sites, tight schedules, and last-minute requests. They may be asked to collect additional shots, verify utilities, or establish control with little notice. In the rush to keep up, documentation sometimes becomes secondary.
Meanwhile, the office is waiting. Production staff can’t move forward without accurate data. When the field information arrives incomplete, unclear, or inconsistent, office staff are left trying to interpret what happened on site. A missing shot, a mislabeled point, or an unclear note can stall an entire sheet set.
This isn’t a matter of skill on either side — it’s a matter of workflow. Field crews are doing their best under pressure, and office staff are doing their best with what they receive. The problem is the gap between them.
What Gets Lost Between the Field and the Desk
The communication failures between field and office tend to fall into two categories — and they require different solutions.
The first is incomplete or ambiguous field documentation. A field note might say “utility located” but not specify depth, material, or condition. A shot might be taken on a feature that isn’t labeled. A control point might be set without a clear description of how it ties into the project. When this information reaches the office, staff are forced to fill in the gaps — and their best guess isn’t always right. I’ve seen a designer build an entire utility layout based on field notes that said “8-inch water” without specifying whether that was an existing main or a proposed stub. The field crew knew which one they meant. The designer didn’t — and the redesign cost two days.
The second is unclear or incomplete instructions going the other direction — from the office to the field. An engineer may give instructions that make sense in their head but don’t translate clearly in the field. A designer may request additional shots without explaining what they need them for. A field crew may interpret instructions differently than intended. The office then requests clarifications or additional shots, which delays the project and frustrates the field crew. The cycle repeats until someone finally slows down long enough to clarify the intent.
Around here, where projects involve grading, utilities, traffic control, and horizontal control sheets, even small misunderstandings in either direction can cascade through the entire plan set.
When the Disconnect Hits the Plan Set
When field data is incomplete or unclear, the consequences aren’t isolated to one sheet. Grading plans get redone, utility alignments shift, plan and profile sheets need new surfaces — and traffic control plans have to be adjusted to match what’s actually out there. It cascades through the entire set.
I’ve seen a designer spend half a day building a surface from survey data, only to find out the field crew used a different coordinate basis than what was in the project. Nobody was wrong — there was just no documented standard for how that handoff was supposed to work. That’s the kind of gap that turns a two-hour task into a two-day problem.
These revisions take time — time that teams rarely have. Agencies expect timely submittals, developers push for aggressive schedules, and internal deadlines stack up quickly. When the field-to-office connection breaks down, the office is forced into reactive mode, scrambling to fix issues that could have been avoided with clearer communication in both directions.
Building the Bridge
When I work with firms on field-to-office workflow, the first thing I usually hear is “our field crews just need to give us better data.” And sometimes that’s true — but it’s rarely the whole story. In most cases, the office has never clearly documented what “better data” actually means.
The starting point is a field-to-office standards document — not a thick manual, but a concise reference that answers the questions both sides actually deal with. What point descriptions does the office need for each type of feature? What information should accompany a control point? What format should field notes follow so the office can use them without a follow-up phone call? Most firms I’ve talked to have never written any of this down. The expectations live in people’s heads, which means every new field crew member or new office hire has to learn them through trial and error.
The next layer is standardizing the handoff itself. How does field data get delivered to the office — email, shared drive, project folder? Who’s responsible for importing it? Is there a checklist that the field crew completes before delivering the data, confirming that all requested shots were collected and documented? A simple delivery checklist — even a one-page form — eliminates most of the “I thought you had it” conversations that slow projects down.
The third piece is closing the feedback loop. When the office finds a problem with field data, how does that information get back to the field crew in a way that actually prevents the same issue next time? In most firms, it doesn’t — the designer fixes the problem, the project moves on, and the same miscommunication happens again on the next project. Building a short debrief into the workflow — even a 10-minute conversation after each data delivery — gives both sides a chance to catch misunderstandings before they become redesigns.
I’ve spent years on both sides of this gap — working from survey data in the office and understanding what field crews are dealing with on site. Bridging that disconnect is one of the most practical investments a firm can make, and it’s a core part of what I do at Frye CAD Consulting.
A Disconnect Worth Fixing
The field-to-office disconnect is one of the most persistent challenges in the local engineering and surveying industry. It affects productivity, quality, morale, and project schedules. But unlike some of the other problems in this series, this one has a clear path to improvement — it just requires treating the handoff as a system instead of assuming both sides will figure it out.
This is the fifth article in a multi-part series exploring the real challenges facing Southern Nevada’s engineering and surveying workforce. In the next article, I’ll examine the mentorship void — and why younger designers struggle to advance in an industry that moves too fast to slow down and teach.