From Field to Fiber: Why Process Is the Real Infrastructure with Dakota Lott-Werkheiser

At the end of every fiber project, something tangible gets handed off. 

A construction print-a design that moves from sheets to the street. 

For all the complexity in broadband infrastructure — the software, the capture tools, the routing models — what ultimately moves a project forward is clarity. Clear data. Clear handoffs. Clear ownership. 

From the Dakota’s perspective, that clarity doesn’t happen by accident. It’s built long before construction begins. 

And when something breaks in a project, it’s usually not because the tools failed. 

It’s because the process did. 

A Seat Across the Entire Lifecycle 

A Data Manager doesn’t sit neatly inside one phase of a fiber project. The role intersects with nearly all of them: fielding, design, permitting, construction. 

“There’s not really a place where I’m not involved,” Dakota explained. 

His strongest influence happens at the beginning. Before crews go to the field. Before design files are created. Before permitting requirements start shaping routing decisions. 

That early alignment is critical: 

• What data needs to be captured? 

• How will it be structured? 

• Who needs it next? 

• What does “complete” actually mean? 

  
  

When those questions aren’t clearly defined, small workarounds start to appear. A field gets reused for something it wasn’t meant for. A naming convention shifts. A temporary solution quietly becomes permanent. 

Those adjustments often seem harmless in the moment. 

But data compounds. And inconsistencies multiply. 

By the time they surface in QC, they’re no longer small. 

Collected Data vs. Usable Data 

Digital capture has transformed the industry. But technology alone doesn’t make data usable. 

Organization does. 

Usable field data is structured so that someone who has never been on-site can immediately understand what was captured and why. It’s labeled intentionally. Required fields are actually required. Information isn’tburied in unrelated attributes. 

That structure must be defined before crews step into the field. 

• Where is this data going? 

• How will it be validated? 

• What triggers review? 

Without those answers, teams spend more time interpreting than designing. 

The Hidden Cost of Rework 

Re-fielding is rarely just about labor hours. 

It’s about momentum. 

When crews return to capture missed details, they aren’t progressing the next phase. When assumptions about crossings or permitting requirements prove incorrect, designs must be revisited. Schedules tighten. Budgets strain. 

Tools like GeoCam help to reduce this friction. But even with better technology, early assumptions remain one of the largest risk factors in fiber deployment. 

The projects that move efficiently are the ones that ask those questions early — and document the answers clearly. 

Data Ingestion: The Make-or-Break Phase 

When data arrives in the system, the first evaluation isn’t whether it exists. 

It’s whether it’s consistent. 

Field names should reflect their actual contents. Required attributes should be populated accurately. Redundant or filler fields should be minimized. 

Consistency enables scale. 

Without it, every downstream team has to reinterpret intent. That slows design. It complicates permitting. It increases review cycles. 

Quality control, therefore, cannot be a final checkpoint. It must be embedded throughout the lifecycle. 

Succesful systems allow teams to: 

• Flag incomplete entries immediately 

• Require critical fields before submission 

• Enable near real-time review between field and office 

When QC controls are built into the process, rework decreases significantly. 

Permitting: Where Weak Data Surfaces 

Designers and permitting authorities often expose gaps that earlier phases overlooked. 

Incomplete documentation. Incorrect assumptions about utility restrictions. Missing dimensional details. 

Permitting entities operate differently across regions. Some require extensive detail and documentation. Others have long-standing agreements that alter requirements. 

Clean, structured data doesn’t guarantee approval — but it gives designers the time and clarity needed to create strong submittals. 

A well-organized dataset reduces clutter. It allows teams to focus on presentation and compliance instead of backtracking to locate missing information. 

The smoother the handoff between phases, the stronger the final submission. 

Construction: The Most Expensive Place to Learn 

Construction is where planning meets reality. 

Trade-offs made during fielding show up in redlines. Assumptions surface quickly. Constraints that were underestimated become immediate obstacles. 

And this is the most expensive phase to correct upstream data issues. 

When fixes happen in the field — especially against deadlines — costs multiply. 

Strong process earlier in the lifecycle protects construction teams from unnecessary friction. It reduces interpretation. It limits surprises. It creates alignment between design intent and real-world execution. 

Process Over Tools 

In a rapidly evolving technology landscape, it’s easy to assume better software solves operational problems. 

But tools move data. 

Process moves projects. 

Automation, capture platforms, and GIS integrations are powerful. In high-volume workflows, they are essential. But without a clear process guiding how and why data is structured, tools simply accelerate inconsistencies. 

Process comes from experience — from understanding how projects break, where handoffs fail, and what assumptions tend to create risk. 

Technology should reinforce that discipline, not replace it. 

What Success Actually Looks Like 

When the process is working well, it’s rarely dramatic. 

Meetings are shorter. Handoffs are cleaner. Teams spend less time clarifying and more time building. 

Success looks like: 

• Fewer refielding cycles 

• Cleaner permit submissions 

• Reduced redlines in construction 

• Clear ownership between phases 

And perhaps most importantly, fewer surprises. 

Fiber projects are complex by nature. But complexity doesn’t have to mean chaos. 

If there’s one takeaway from the Dakota’s perspective, it’s this: 

Define your process first. Build your tools around it. And protect the handoffs between every phase. 

Because projects don’t fail when data moves. 

They fail when it doesn’t move cleanly from field to fiber and back to the field.