Traverse Engineering
PRE-ENGINEERING ROUTE VALIDATION

Make fiber routes engineering-ready before design begins.

TRI™ Route Intelligence is an advisory validation report. It scores route risk, exposes hidden assumptions, and shows where field verification matters most, so your team catches span, ROW, and crossing problems before the engineering clock starts.

  • Advisory validation, not stamped engineering
  • Fixed-price tiers from $3,500
  • KML / KMZ / GeoJSON in → PDF + KMZ out

The problem

Routes rarely fail on the map. They fail in the assumptions.

A route can look fine until engineering exposes span, structure, ROW, and crossing issues. TRI finds the likely redesign drivers early, so teams verify the right segments before budget and schedule are committed.

Redesigns happen late

Constraints surface after engineering starts, when changes cost the most.

Feasibility often assumes constructability

Cost models break when ROW, crossings, and spans haven't been validated.

Field time is precious

TRI points verification effort at the segments most likely to cause surprises.

Who it's for

Built for teams that need constructable routes before they commit engineering dollars

Data center developers

Campus OSP, dark fiber corridors, and diverse-path entrances.

Hyperscale & colocation

Interconnect and backbone routes where schedule risk is real.

ISPs & BEAD builders

FTTx, middle-mile, and rural routes that need defensible assumptions.

Municipalities

City and county networks heading into design or grant applications.

Electric cooperatives

Co-op fiber builds on existing pole lines and new corridors.

Engineering & grant teams

A pre-scope check that surfaces surprises before your clock starts.

Deliverables

What you get with a TRI Report

Concrete artifacts your engineering team can use right away.

TRI Score

Overall and category readiness (span, structure, ROW, crossings, constructability), rated Green / Yellow / Red.

Assumptions Ledger

An explicit list of what the route depends on, and how confident each assumption is.

Risk-Flagged KMZ

A map file showing segment by segment where the engineering risk is concentrated.

Engineering Next Actions

A prioritized verification checklist: what to confirm first and where to focus field effort.

Know what TRI is (and isn't)

Validation before design. No scope creep.

TRI strengthens feasibility and early design decisions. It validates route assumptions and highlights constructability risk before budgets, scopes, and grant narratives are locked.

Not a feasibility studyIt supports your feasibility team. It doesn't replace them.
Not stamped engineeringAdvisory assessment only. No seal, no design instructions.
Not field verificationIt tells you where to verify, not that verification is done.

Process

How TRI works

AI-assisted analysis with human review of every flagged segment.

  1. Submit your route

    KML / KMZ / GeoJSON, or a corridor description, plus known constraints and deadlines.

  2. Route risk analysis

    Geometry, span assumptions, crossings, ROW indicators, and constructability are scored by segment.

  3. Human review

    High-risk segments are reviewed, scores sanity-checked, and recommendations refined.

  4. Deliver TRI artifacts

    A client-ready PDF and a risk-flagged KMZ, ready for your engineering team.

Advisory notice: TRI supports planning and risk mitigation. It does not replace field verification, make-ready, permitting approvals, or stamped engineering.

Pricing

Fixed-price TRI tiers

Pick the depth that matches your route's stage and risk. Turnaround is counted from receipt of complete route inputs.

TRI Lite
$3,500

Typical turnaround: 3–5 days

Early screening and corridor comparison.

  • Overall TRI Score
  • Top risk flags
  • Assumptions summary
  • Basic KMZ export
Request Lite →
TRI Pro
$18,500

Typical turnaround: 7–10 days

For data center campuses, grant-funded, or high-risk corridors.

  • Everything in Standard
  • Multi-route / scenario comparison
  • Priority human review of flagged segments
  • Engineering handoff notes
  • Review call with the principal
Request Pro →

Need multiple corridors or a rush timeline? Ask about a custom scope.

Also from Traverse

TAI™ Business Audit for small businesses

A business-intelligence audit for companies with 2–50 employees. A short discovery call becomes a prioritized roadmap showing where time is being lost and what to fix first.

Ask about a TAI audit →
TAI Business Audit
from $1,000
  • 30-minute discovery call
  • Prioritized roadmap of where time is being lost
  • Roadmap typically delivered within 48 hours

Separate from TRI. TAI audits are business advisory services, not engineering.

About

Founder-led, from the OSP side of the industry

Traverse Engineering LLC was formed in July 2019 in North Augusta, South Carolina. Owner Travis Canfield built TRI around a common outside-plant problem: routes that reach engineering on assumptions nobody has checked.

When you request a TRI report, you work directly with the principal.

Principal's prior experience

  • OSP Design Engineer, Cyient
  • Project Manager, Nexius
  • Project Manager, Byers Engineering (road relocation)
  • Project Manager, Essentia

Credential

IBM SkillsBuild: AI Practitioner (completion badge, Feb 2026)

Experience shown is the principal's individual work history with prior employers. It is not Traverse Engineering project history.

FAQ

Is TRI a feasibility study?

No. TRI is a pre-engineering validation report. It supports feasibility by identifying route risk, listing assumptions, and flagging the segments most likely to drive redesigns or change orders.

Is this stamped engineering?

No. TRI is advisory only and is not sealed by a licensed Professional Engineer. It does not replace field verification, make-ready, permitting approvals, or professional engineering review.

When should we run TRI?

Ideally before feasibility is finalized, to validate assumptions, and again before engineering starts. Most teams run TRI once per route concept.

What inputs do you need?

KML, KMZ, or GeoJSON is ideal. If you don't have that yet, send a corridor description and we'll walk you through intake.

Is TRI used for data center routes?

Yes. TRI fits campus OSP, dark fiber corridor validation, carrier-neutral interconnect routes, and builds connecting hyperscale campuses to backbone infrastructure.

How is AI used?

AI-assisted analysis screens the route and scores segments. A human reviews the flagged segments and the final recommendations before anything is delivered.

Find route surprises before engineering does.

Send your route file and get a decision-ready risk view.

Request TRI →