Route Documentation Built for Permit Agents
Permit agents live between the carrier's route and the jurisdiction's application form — and everything between those two is transcription. RoadScope gives permit services a route record that generates the application inputs directly: jurisdiction route lists, turn-by-turn descriptions, and supporting constraint documentation that reviewers can actually verify.
RoadScope does not file applications or replace your jurisdiction relationships. It replaces the manual assembly of what goes INTO the application — and keeps documentation synchronized when routes change mid-process.
How this work gets done today — and what changes
The problem
Permit turnaround is the product permit agents sell, and the slowest, most error-prone part of it is producing route documentation that matches the actual route — per jurisdiction, in each authority's expected form.
The current process
Receive route details from the carrier by phone or email; trace the route on a web map; type turn-by-turn descriptions by hand; split the description at each jurisdiction boundary; re-key dimensions and route data into each application; repeat when the route changes.
Where time and errors are lost
Hand-typed route descriptions drift from the real geometry, and a mid-process re-route quietly invalidates already-prepared documents. Each jurisdiction's re-description multiplies the typing and the chances of a mismatch — and a mismatch means a resubmission cycle the client blames on you.
How RoadScope changes it
The route lives as a record, not a description. Turn-by-turn directions extract from the actual geometry, permit route lists organize by jurisdiction automatically, the Permit Auto-Fill Generator pre-populates common application fields, and a re-route means regenerating outputs rather than reconciling documents.
The concrete result
Application documentation that matches the route by construction: fewer mismatch rejections, re-routes absorbed in minutes instead of an afternoon of re-typing, and a per-move record you can show the carrier when questions come back from the authority.
From carrier request to application-ready package
Capture the Move
Set up the route from the carrier's origin, destination, and constraints — as a route record, not an email thread.
Check Weight & Dimensions
Screen the axle configuration with the Axle Load Calculator and review jurisdiction OS/OW requirements alongside the route.
Generate Per-Jurisdiction Documentation
Turn-by-turn descriptions extracted from the geometry and permit route lists split by jurisdiction — with Permit Auto-Fill pre-populating common application fields.
Absorb Changes
When the route shifts mid-process, regenerate the affected outputs from the updated record. Documentation cannot silently go stale.
What RoadScope Enables
- Turn-by-turn route descriptions extracted from actual route geometry
- Permit route lists organized automatically by jurisdiction
- Permit Auto-Fill Generator pre-populating common application fields
- Jurisdiction OS/OW requirement reference alongside the route
- Axle Load Calculator for configuration screening before application
- Regenerate-on-change documentation that stays synchronized with the route
Typical Users
Permit service firms, permit agents and expeditors, carrier in-house permit departments.
Primary Outputs
Jurisdiction route lists, turn-by-turn route descriptions, pre-populated application fields, constraint documentation PDFs, per-move route records.