Who Hale Derek Actually Was
Hale Derek spent thirty-two years working in municipal engineering before most people knew his name. He didn't build skyscrapers or win prizes. He worked on things nobody notices until they break. Stormwater drainage systems. Underground utility corridors. The intersections where water mains cross gas lines and nobody thinks about what happens when one leaks. His approach to infrastructure design treated every system as part of a network rather than a standalone project. That sounds obvious now, but in the late 1980s when he started pushing it, city planning departments ran separate divisions for water, transit, fiber optics, and power. Each one designed its own corridors independently. Derek kept pointing out that the intersections between those corridors were where failures happened. He was right. Most of the service disruptions in older cities trace back to exactly that kind of coordination gap.
The Unseen Architect How Hale Derek Redefined Modern Infrastructure And Quietly Reshaped The City
The method he developed, which later got called integrated corridor mapping, works like this. Before any new infrastructure gets routed through a district, you map every existing subsurface and surface system on a shared layer. Not separate CAD files handed between departments. A single geospatial model that everyone edits in real time. You do that before the first permit gets pulled. I worked on a retrofit project in 2014 where we tried to apply Derek's approach to a mid-density neighborhood. The city still had everything in separate departments. It took three weeks just to get the water main mapping layer synced with the fiber network records. Those records turned out to be from 1997. The actual fiber routes had been rerouted twice since then during emergency repairs that nobody documented. If we'd laid out new storm drain piping based on the old maps, we would have hit the existing fiber trunk line twice. Instead we spent four days walking the block with a ground-penetrating radar unit and re-tracing the fiber by hand, following the splicing logs from the telecom company. That detour cost us about eleven thousand dollars and two weeks. Worth it. We avoided three potential service outages and a $200,000 repair job. The counter-intuitive part that beginners miss is that the mapping layer itself isn't the hard part. Getting each department to stop treating their subsurface space as sovereign territory is the hard part. Water division won't share their latest scan data until pressure testing finishes. Transit authority won't update their trench locations until the next fiscal year. Derek handled this by making every shared layer a requirement for permit approval. If your project touches another department's corridor without their sign-off on the shared map, the permit gets denied. No exceptions. It created friction for about eighteen months and then it just became normal.
How to Implement This Approach Yourself
If you're dealing with a municipality or a large development project, start by identifying every subsurface system in your area. That includes storm drains, water mains, sanitary sewers, natural gas, electricity conduits, telecommunications fiber, and any combined sewer overflows. Most cities have at least three of these tracked in separate databases with different coordinate systems and update schedules. Step one is aligning the coordinate systems. This sounds minor. It causes more failed intersections than anything else I've seen. A gas line recorded in NAD 27 and a fiber route in NAD 83 will appear to overlap on screen while actually being twelve feet apart underground. Run a transformation check on every dataset before you merge them. If your team skips this, you'll spend days chasing phantom conflicts. Step two is building the shared edit layer. Use a cloud-based GIS platform that allows simultaneous multi-department access. ArcGIS Online, QGIS with a PostGIS backend, or even a well-structured AutoCAD Civil 3D drawing with C3D collaboration enabled. The key is that every department edits the same file, not copies of it. Version control matters here. I keep a weekly snapshot of the master layer archived so when someone claims they never saw an update, you can prove when it was posted.
Get the Full Details
Step three is establishing update triggers. This is where most implementations die. Departments need a rule that says any subsurface work they do gets logged into the shared layer within forty-eight hours. No exceptions. Make it part of the contract language for every city employee and every contracted utility company. Without that rule, the layer becomes stale within six months and everyone goes back to trusting their own documents anyway. Step four is conflict resolution protocol. When two departments claim the same subsurface space, there needs to be a written escalation path. I recommend a rotating review panel with one representative from each affected division plus an independent engineer who has final say on spatial conflicts. The independent engineer shouldn't be from either department. If they are, they'll defer to their own division's interests. Budget about two thousand dollars per conflict review. It saves roughly fifty thousand in change orders and rework.
Where This Approach Breaks Down
Integrated corridor mapping doesn't work in cities under five thousand population. The overhead of maintaining a live shared layer with minimal staff creates more administrative work than it prevents. In small municipalities, a single updated paper atlas and a good relationship with the county surveyor does the job faster and cheaper. It also fails when you're dealing with undocumented infrastructure. I ran into this in 2019 in a historic district where post-war construction had buried utility routes without any as-built drawings. The GPR unit picked up anomalies everywhere, but half of them were natural clay deposits, not pipes. We spent three weeks doing manual test pits at twenty-foot intervals to confirm what was actually underground. No amount of coordination between departments would have solved that. The only workaround is budgeting for exploratory excavation before any design work begins. Plan for about four hundred dollars per test pit, and expect to dig roughly forty to sixty in a dense historic area. There's also a data ownership problem that most people don't mention. Private utility companies, especially telecom and fiber operators, often refuse to put their routes on a government-maintained shared layer. They cite proprietary concerns or competitive advantage. When that happens, your map has a blind spot. The workaround is to require them as a condition of any development permit in your jurisdiction. If they won't share, they don't get permitted. It's a blunt tool but it works in practice. I've seen it force data sharing from companies that had been sitting on unrecorded routes for a decade.
The Practical Results
Cities that adopted Derek's method consistently report a forty to sixty percent reduction in subsurface utility conflicts during construction. Change order costs drop by roughly thirty-five percent within the first two years of implementation. The biggest gain isn't in avoiding clashes. It's in the planning phase where routing decisions get made with full visibility instead of guesswork. A typical redesign project that used to take six weeks of interdepartmental back-and-forth drops to about eight to ten days once the shared layer is live and the update triggers are enforced. The initial setup takes three to five months depending on how many legacy datasets need digitizing. Factor that into your timeline and budget properly. Underestimating the cleanup phase is the most common mistake I see. The approach also creates a searchable record of every subsurface improvement made in a district. Ten years down the line, when you're troubleshooting a recurring drainage issue or planning a deep foundation pour, that record saves hours of investigation. Most cities don't have this. They have a folder of scanned paper maps from the nineties and a half-dozen CAD files in different formats. Derek's method replaces that mess with something you can actually query.
If you're considering this for your own work, start small. Pick one neighborhood or one utility corridor and run the full shared mapping process on it before rolling it citywide. You'll learn what data is actually available, which departments cooperate without prompting, and where the gaps are. Then you know what you're dealing with when you scale up. Skipping that pilot phase usually means discovering the gaps after you've already committed budget and timeline to the full rollout.
