← Back to Work Career Pattern · 2014–2019

The Civil Engineering Speedup

Road-profile drafting, point by point, became capture → calculate → plot. At least 10x faster, and I stopped second-guessing every point.

The payoff

At least 10x faster than the trained, by-hand method, likely more — 10x is the figure I'll stand behind. Paving plans carry the fatter budgets, so this is a big part of how I came in under budget when almost no one did.

And because the method is fully defined, the win isn't only speed: I verify two inputs — the station/offset data and the cross-section label — and then trust every output, instead of policing hundreds of points by hand and hoping I caught them all. The work is handled, and it's off my mind. That is the relief K1 sells, lived from the inside.

image · 03-profile-before-after.png · pending

Side-by-side comparison. Left, labeled "by hand," shows a partial, effortful drawing. Right, labeled "system-plotted," shows a complete, clean set of four curb profiles plus the centerline. The contrast should read instantly: effort and gaps vs. complete and clean.

The problem

Not just the centerline.

Drafting the profile views in a paving plan isn't just the road centerline. Each side of the road carries two more profile lines — the gutter and the top of curb — so a full plan is the centerline plus four curb profiles. The geometry transitions along the road to handle drainage, driveways, and pedestrian access, and each transition changes the shape, independently on the left and right.

The trained method was to calculate and place every point by hand, one at a time. At that pace a single plan took forever.

What I built

A defined, multi-stage system where each tool does only what it's best at.

The points flow from one tool to the next:

01 · CAPTURE 02 · CALCULATE 03 · HAND OFF 04 · PLOT OUTPUT AutoCAD Civil 3D station + offset Excel four-line tables Text File X/Y pairs LISP Routine reads + draws Civil 3D Profile plotted VERIFY TWO INPUTS · TRUST EVERY OUTPUT
  1. Capture — Civil 3D's picker hands you station and offset at any point you click in plan view. I capture the transition points and the cross-section type at each one.
  2. Calculate and compile — Excel looks up the standard cross-section and calculates the elevations, building a station-and-elevation table for all four lines (with linear interpolation where a side has no point at a given station).
  3. Hand off — the points compile into formatted X/Y pairs and export to a text file.
  4. Plot — a LISP routine, called from the command line, reads the text file and draws the whole profile directly onto the profile view in AutoCAD Civil 3D. You pick which profile to push to, and it graphs itself.
How it works

Stepping across the peaks instead of descending into every valley.

The slow way is to descend into every valley and climb back out, over and over: calculate a point, place a point, check a point, repeat for hundreds of points. My system steps across the peaks instead. Each peak is the one thing a tool is strongest at — Civil 3D's geometry pickers, Excel's calculation and compiling, LISP's plotting — and I build the bridge that hops from peak to peak on the shortest path.

I'm not loyal to one program. I read where each one lets data in and out, and I connect them so the drafting does itself.

THE OLD WAY back and forth on every point, by hand THE SYSTEM I BUILT verify two inputs — trust every output
The honest frame

W-2 work. My tools, my edge.

This was W-2 work, built while employed at the firm. I operated inside it; I did not deliver it for an outside client. I built these tools on my own time and kept them as a private edge to protect the IP. The tools, the speedup, and the method are genuinely mine.

Have something that looks like this pattern?

Book a 15-min intro call

Free. 15 minutes. I'll know in the first 5 if I can help.