Organizing Permits & Project Documents
How the OS/OW Document Center, V01/V02/V03 versioning, and Permit Application Auto-Fill keep an entire OS/OW project audit-ready from kickoff through close-out.
Key Takeaways
- •Centralize permits, regulations, engineering letters, and field photos per project
- •Auto-fill jurisdictional permit applications from your route, load, and equipment data
- •Track every revision with V01/V02/V03 versioning and a full audit trail
OS/OW projects accumulate documents quickly: permits, regulations, engineering letters, insurance certificates, photos, and route documentation. Without a structured place for these artifacts, teams waste time searching email and shared drives — and lose the audit trail that protects them.
The OS/OW Document Center
The Document Center is a project-level workspace that organizes every supporting document a permit office, escort company, or driver might need.
Folder Structure — Preset folders for the typical OS/OW workflow: Permits, Regulations, Route Documentation, Engineering, Insurance, and Field Photos. Custom folders are supported per project.
Linking Documents — Any uploaded document can be linked to a specific POI (an engineering letter for a particular bridge) or to the route as a whole. Linked documents surface alongside the POI in the map and in generated reports.
Permit Application Auto-Fill
Permit Application Auto-Fill takes data you have already captured — the route, the load envelope, the equipment configuration, and the carrier details — and pre-populates the appropriate jurisdictional permit application.
How to Use It — Open the route, choose Generate Permit Application, select the issuing jurisdiction, and review the populated fields. Fill in any remaining jurisdiction-specific fields and export as PDF.
Reusable Profiles — Save your carrier details and tractor/trailer configurations once in the Equipment library; auto-fill pulls from them on every future application.
Important — Auto-fill produces a strong starting point, not a finished filing. Always verify every field against the issuing authority's current requirements before submission.
Versioning & Audit Trail
Every generated artifact lands in the Document Hub with a sequential version label (V01, V02, V03…). Older versions are preserved. Use Mark as Official to flag the current authoritative revision and Compare to see what changed between two versions.
Audit Trail — Every upload, replacement, and download is logged with the user, timestamp, and version label. When a permit office, insurer, or claims adjuster asks who provided what and when — the answer is in the record.
Sharing the Right Copy
When you share a Client Delivery Portal link or email a deliverable, RoadScope includes the version label so recipients know exactly which revision they are viewing. Drivers receive the briefing version that matches the dispatched route, not whatever was emailed last week.