The RoadScope Manual

Log in, then open the Map workspace from the home screen. The header shows your active map, Tools, Share, and your profile.

In the Routes tab, click "Plan a Route" to draw or import a corridor. Each route is a project record that POIs, photos, documents, reports, and deliveries attach to.

Add POIs (35+ purpose-built types), attach geo-tagged photos, and capture clearance measurements. Tag each item with a phase: Preplan, Road Survey, or SharedMap.

Open the Reports Hub to produce interactive HTML reports — the Route Survey Report (master), Clearance Profile, Envelope Report, and more — plus the Client Delivery Portal link in one place. Every artifact lands in the Document Hub with a sequential version label (V01, V02, V03 …).

Send the route to a RoadScope Navigator crew with NAV Live Dispatch, or share the Client Delivery Portal link with the client.

In a project, open the Collaborative Survey panel and click Pair MeasurePRO. RoadScope generates a 7-day RS-XXXXXX pairing code. Enter that code on the MeasurePRO device to stream measurements straight into the project.

The Survey Import modal includes a built-in camera-setup walkthrough and a field workflow checklist for 360° captures.

Open the recording in Insta360 Studio (the free app that comes with the camera), click Export → 360 video with the default settings, then drag the exported .mp4 into Import 360° survey together with the camera's original _00_.insv file — RoadScope reads the GPS track from it (a .gpx track from another device works too). Each video can be up to 16 GB; for longer drives split the recording into clips in Insta360 Studio.

Photos uploaded to a POI keep their EXIF GPS coordinates and timestamps and become attached evidence on the POI record.

Use the field app for live GPS elevation profiling, offline POI capture, and photo evidence on any phone.

Switch between Google Maps road, satellite, hybrid, and terrain basemaps — plus regional data layers — without losing your data. Set your preferred default in Settings. Layer visibility (basemap, overlays, imported layers) is remembered per map in the Layers panel.

GPS-based elevation profiles with colour-coded grade severity. Spot steep grades, sustained climbs, and traction-risk segments at a glance.

Bridge inventories, structures, and roadworks for North America and Europe overlay automatically based on route geography. Data for all 27 EU member states from external Route Intelligence sources is now included on a weekly refresh cycle.

Per-segment weather risk reports time-aligned to the projected time of arrival. Read the top-line risk banner: Good to Travel, Use Caution, High Weather Risk, or Do Not Dispatch.

Compare two surveyed routes side-by-side across distance, clearance constraints, grade profile, POI counts, and permit complexity. Export the comparison as a PDF for permit packages.

Open the Rail panel (Products → Rail in MapPro, or /rail-miller). Document rail crossings, search community rail constraint records, and consult the jurisdiction-specific OS/OW Rail Rules Reference Library.

Enter your load height, width, and safety margin in the Clearance tab. RoadScope compares your envelope against every POI clearance on the route and flags Conflicts (clearance insufficient) and Cautions (within safety margin) with colour-coded badges.

Conflict POIs show a red Danger badge on the map, in the POI list, and in reports. Where a special maneuver is required — wide swing, split escort, pilot car stop — a Special Maneuver badge shows the maneuver outline on the map.

The Cross-Check panel shows the tightest clearance across all Bridges, Utilities, and other types at a glance — without scanning the full POI list.

At intersection POIs in the Field App, tap L / R / Straight / U-Turn to record the verified direction. Colour-coded chips appear on POI rows and popups in the office, and geometry-derived directions fill in automatically when no field value has been recorded.

All CSV/Excel exports include a Turn Direction column. The Turn-by-Turn report includes turn-direction chips alongside each intersection entry.

In the Routes tab, click the bell on a route card or open the Route Watch drawer from the Tools menu and click Start a watch. If the survey has no convoy data, the Declare convoy envelope dialog asks for Height, Width, optional Length, and Gross weight before continuing.

Set the Start and End dates (defaults to 30 days, maximum 180), adjust the Corridor buffer slider (25–500 m, default 75 m), and choose notifications — in-app alerts are always on, with an optional Email digest when events are detected. Click Activate watch to run the baseline scan immediately.

Watched routes show blocking (red), verify (yellow), and info (green) event counts. Each event carries a severity chip and a state — New, Updated, Lifted, or Active — with the road, reason, and distance along the route. Acknowledge events with the eye control; unacknowledged alerts ring the route’s bell with a numeric badge.

From a watch’s detail view use Scan now, Pause/Resume, or End watch. The header shows a Watch active radar badge whenever watches exist, and the drawer shows the next automatic scan time. A scan that could not fully evaluate the corridor is reported as incomplete — never as clear.

Route Watch currently monitors the Québec road-event network. The corridor is the route line plus your configured buffer, so events on adjacent ramps and crossings are caught too.

Confirm the route and version, convoy envelope, scan time, corridor buffer, jurisdictions, and selected sources. Then inspect every source status and the geographic and time coverage. A result only speaks for the sources, area, and time actually evaluated.

Missing means required evidence was not supplied. Failed means the source or check did not complete. Stale means the evidence may no longer represent current conditions. Partial means only part of the requested corridor, time range, or source set was evaluated. Out-of-coverage means the source does not support that place or condition. None of these states means clear, pass, or safe.

Triage blocking, verify, and informational findings, including New, Updated, Active, and Lifted events. Configure Route Watch through the planned move date and assign someone to review notifications. An incomplete scan remains incomplete even when no blocking event was returned.

Open the source and evidence history. Check authority, observation time, confidence, location, units, and whether the evidence applies to the declared convoy. Resolve contradictions and confirm critical constraints with suitable current evidence such as field measurement, engineering review, or the responsible owner, utility, or authority.

Record the decision, rationale, assumptions, exceptions, reviewer, and follow-up actions. Evidence history preserves observations and supersession. A decision dossier packages evidence and reasoning for audit; it is not professional approval, engineering certification, a permit, or a declaration that a route is safe.

Print or save the Corridor Intelligence Decision Checklist with the project record. Stop or escalate when a critical source is missing, failed, stale, partial, contradictory, or out-of-coverage.

Click the scenario dropdown above the map (it shows the active scenario name or Main study) and choose New scenario, or use Create Scenario from the survey rail. The new scenario activates automatically.

With no scenario active you are in Main study — all routes, files, and POIs are visible with no filtering, exactly like the pre-scenario behaviour.

An active scenario automatically shows POIs that fall inside the corridors of its routes. Matching recomputes when you activate the scenario or change routes and POIs.

With a POI selected while a scenario is active, use Pin to scenario to include it even outside the corridor match, or Hide from scenario to exclude it. Pins are scenario-specific and reversible (Pinned — remove pin).

Each scenario offers Rename, Duplicate, and Delete. Deleting a scenario keeps all routes and files — they simply return to Main study. Shared maps can be scoped to a scenario so recipients see only that study.

Select a Turn POI and choose Analyze intersection swept path. Define the boundary — Auto-suggest from road data or Draw boundary manually — then Accept boundary, pick the equipment combination from your Equipment Library, and simulate.

After simulation, drag the handles to adjust the path, double-click the line to add a point, or right-click / long-press a handle to delete it. The simulation re-runs automatically as you edit.

Verdicts are PASS, CONDITIONAL PASS (passes only if flagged removable obstacles are removed), or FAIL, with maximum clearing length/width, minimum edge clearance, and any collisions. A Simulation error means the setup needs fixing — it is not a physical FAIL.

Open the collapsible Vertical profile panel under the map. Sample elevation along the guideline via the API (approximate, ±1–2 m, screening only) or Import CSV profile with s,z columns in metres. Results show PASS, FAIL – Grounding, or ERROR, with minimum clearance location and approach/departure/breakover angles.

Save the analysis with a name and report profile — or Save as new version while editing. Saved results attach to the Turn POI and flow into the Turn-by-Turn report, with a combined PASS (H+V) / FAIL (H+V) verdict when both analyses exist. The Project Report consolidates verdicts across every analyzed intersection.

In the Reports Hub, choose AI Report Studio and click Start AI Analysis. The AI analyzes POIs, clearances, bridges, grades, and rail data, then drafts an editable Executive Summary (Headline, Overview, Top Risks) and per-section Justification, Key Findings, and Recommendations.

Use Revise the report to request narrative changes. You get before/after diffs and choose Apply edits or Discard. Engine-derived numbers, verdicts, and risk levels are never rewritten by the AI — changing those requires an explicit override.

Upload your own report template (.pdf, .docx, or .html). Extracted sections are mapped to the POI taxonomy; ambiguous sections must be confirmed, manually defined, or excluded before the template can be activated.

A Pre-publish checklist gates Generate Final Report; a failed check can only be bypassed via Override with justification, which is permanently logged. Each analysis consumes one draft from your plan’s monthly AI report draft allowance.

Open Max Load from the map tool palette (or the floating Max Load button) for a chat agent that can list maps and routes, search POIs and POI Discovery, and run Route Intelligence scans. Every write is a proposal: review the Before/After card and click Apply or Skip — nothing is changed without your confirmation, and applied actions are logged.

From Tools, open POI Discovery on the active map. Choose a search scope: Route corridor (with a buffer in metres), Map area (the currently visible view), Radius (km around a centre point), or Region (province / state).

Restrict results by Height, Width, or Both with numeric thresholds so only constraints relevant to your load appear.

Results are grouped by type with counts and distances. Tick the POIs you want and click Add to route; POIs owned by other organizations can be requested with an optional Message to the owner.

In the Route Generator, click the orange Events button to overlay current closures (red), construction (orange), incidents (yellow), and restrictions (purple) on the candidate route. Click a marker for details, or use the Road Events panel to pan to each event. A warning appears if the event data is stale.

Each POI and route carries one or more phases: Preplan, Road Survey, SharedMap.

Use the phase filter pills (All / Preplan / Road Survey / SharedMap) in the POIs tab filter panel to control the list and the map at once — markers and routes narrow to the selected phase, and an active filter chip stays visible until cleared.

Move every visible POI of a given type — every bridge, every utility — between Preplan and Road Survey in a single action. POIs in hidden regions or excluded by other filters are not affected.

Reports can be scoped to a specific phase to produce phase-targeted deliverables (e.g., a SharedMap-only client package).

A single panel for every interactive HTML report: Route Survey Report (master), POI Report, Work Required, Survey Plan + Weather, Rail Information, Clearance Profile, Province/State POI Report, Width Report, Envelope Report, Maximum Envelope Report (Interactive), and the AI Report Studio. Each report generates a self-contained interactive HTML deliverable with a public share link and auto-saves to the Files tab.

The Envelope Report compares your load envelope against every route constraint — clearance (height), corridor width, and an overall pass/fail. The Maximum Envelope Report (Interactive) adds live height/width sliders, clearance profiles, an obstacle register, field photos, and a simulator. Add multiple loads with "+ Add load"; the governing envelope takes the maximum dimension across loads. A creator edit link lets you correct the delivered page after generation.

From the Reports Hub, choose AI Report Studio and click Start AI Analysis. The AI analyzes POIs, clearances, bridges, grades, and rail data, then drafts an editable Executive Summary and per-section narratives. A Pre-publish checklist gates Generate Final Report; failed checks can only be bypassed with a logged, justified override.

Reports grade every evaluated constraint against your declared load with a shared verdict engine: PASS, MARGINAL (inside the safety band), FAIL, or NOT EVALUATED (missing data — never a silent pass). High-voltage lines automatically subtract the jurisdiction’s required minimum air draft before grading. A governing-constraints table shows the single worst constraint per route and dimension with its position and margin.

Clicking Generate Report first audits the survey for missing measurements, unclassified types, missing route associations, and free-text-only curfews. Fix the gaps or Proceed Anyway — proceeding embeds a "Data Gaps — Field Data Completeness" disclosure section in the deliverable.

Upload any permit PDF and RoadScope extracts jurisdiction, load envelope, conditions, and expiry into a structured record. All active permits appear in the Permits Summary section of every Full Report.

Project-level workspace for permits, regulations, route documentation, engineering letters, insurance certificates, and field photos. Documents can be linked to specific POIs or to the route as a whole.

Every artifact lands in the Document Hub with a sequential version label. Older versions are preserved, never overwritten. Mark as Official to flag the authoritative copy. Compare any two versions.

Permit application templates are pre-populated from your route data — jurisdiction, dimensions, equipment, and constraint summaries — saving long manual data entry.

From the dashboard, click New OS/OW Project and enter the project name, client, expected move date, and jurisdiction list.

The timeline view shows each phase — Pre-Survey, Field Survey, Report Preparation, Permit Submission, Move Execution — as a horizontal bar. Milestones pin to the timeline at critical dates: permit application deadlines, engineering letter due dates, scheduled move dates.

Every required output is listed with an owner, due date, status (Pending → In Review → Complete → Blocked), and a direct link to the generated artifact in the Document Hub.

RoadScope sends email reminders at 7 days and 1 day before each milestone. Overdue milestones surface as red indicators on the timeline.

Click the 3D tab from any project map. RoadScope switches to the 3D terrain view with your route, POIs, and any placed models overlaid on the terrain.

Open the 3D view, then use 3D Models → Import. GLB is the preferred direct format. A georeferenced GLB auto-places; other files start at the current map view so you can position them and adjust units, orientation, scale, and height offset in Properties.

RoadScope converts STEP/STP, IGES/IGS, STL, and OBJ files to GLB after you review the preflight notice. CAD and mesh sources are limited to 50 MB and conversion carries geometry only; use a direct GLB when embedded JPEG/PNG textures are required.

Browse community-contributed OS/OW structures (portal frames, bridge clearance rigs, staging fixtures) and place them with a live preview before committing.

Click Measure on any model card and click two points to get the straight-line distance between them, displayed in your workspace unit.

See active RoadScope Navigator surveyors live on the office map with current GPS, speed, and last-update time. Push a revised route (with selected POIs and a message) to a specific surveyor — they Load Route to switch instantly or Save for Later to keep it offline on the device. The dispatch panel tracks each send: Delivered to Device, Route Accepted by Surveyor, or Saved for Later.

Hand the client a live, branded interactive Shared Map of the survey via a single link. No login or software install on the client side. Updates you make in RoadScope are reflected automatically.

Recipients on the shared map can filter POIs by type and dimension ranges, use the header height-clearance banner to highlight conflicts for their specific load, and view photo thumbnails directly in POI popups.

Clients and stakeholders can leave General, Question, Approval Request, Needs Correction, or Missing Information comments. The map owner is notified by email.

Every generated report ends with an "Ask this survey with your AI" block — a QR code and short link recipients open to connect the survey to Claude, ChatGPT, Gemini, or Copilot with a read-only, single-survey token (90-day validity, revocable). Survey export ZIPs include the same access files, and full-survey shared maps show a connect panel once a report or export has opened the door.

Set your preferred unit mode in Settings → Workspace Preferences → Units: Metric (metres, km), Imperial (decimal feet, miles), or Feet & Inches (ft′ in″). The change applies across the platform: route distances, clearance fields, exports, permit auto-fill, and Street View ruler labels.

Short measurements display in metres or feet — with auto-promotion to km / miles for longer measurements — instead of awkward 0.03 km readouts.

Log hours per day and map from User menu → Timesheet (/timesheet), then submit the week for approval by a company admin. Approved timesheets are visible in Company Admin.

Use Restart Tour from the Settings tab, or the What's New modal, to revisit the in-app walkthrough and review the latest releases.

Workspace → Team Dashboard (/company/team) is the company home: members and roles, active maps, open tasks, verification requests and recent activity. Team Tasks (/company/tasks) lists every project task across the company.

Workspace → Company Admin (/company) is where owners and admins manage employees and roles (owner, admin, surveyor, viewer), the per-map access matrix, invitations, the audit log, MeasurePRO pairing, report branding and the company Route Watch policy.

All Maps, All Routes and All POIs (Workspace menu) list every record in the company with owner and last update; the POI Library holds curated reusable POIs and POI Use Requests tracks other companies asking to reuse one of yours.

Invite collaborators from the Share panel as viewer, editor or manager. Collaborators see the map under My Maps; per-map collaborator seats follow your plan. My Profile → Collaborations lists maps shared with you.

Schedule field surveys, assign them to team members, set due dates, and track progress from the Project Dashboard and Team Tasks.

Surveyors log hours per day and map from User menu → Timesheet and submit the week for approval; approved timesheets are visible in Company Admin.

Every change is logged and every issued version preserved. Sign-offs are recorded in the Decisions panel with the technical right and data version they applied to.

Export routes to mobile for real-time turn-by-turn navigation, hazard alerts, and convoy coordination. Included in Operator and Enterprise plans.

The /fieldapp surface installs as a Progressive Web App with cache-first behaviour for the shell. POI capture, photos, and live elevation work offline; data syncs when connectivity returns.

When a NAV crew is signed in, their live position appears on the office map for dispatch.

The left rail groups panels by pillar: Map (Overview, Maps, POIs, Routes, Corridors, Transport, Decisions, Movements, Route history, Scenarios, Road Profiles, Analytics, Layers, Files), Route Intelligence, Analysis, Products (SweptPRO, LoadPRO, ProfilingPRO, Rail), Work, Permits, Reports & Delivery, AI, Help, User and Settings. Import / Export opens as a hub modal from the rail.

Open a second map from the Maps panel (or right-click a tab → New tab) and it appears as a tab above the map. Each tab keeps its own active panel, zoom and layer state; Route Intelligence scans stay parked with the map that started them. Closing a tab never deletes data.

When you return to a map, MapPro restores your last panel, zoom, active layers and collapsed groups for that map and user.

Map → Data continuity shows weekly backups, retention, restore drills and the integrity badge of every file and share of the map — proof that a deliverable is still the version you issued.

MapLite (/map) is the lightweight map for quick lookups and light POI edits on a phone or from a shared link. It shows Route Intelligence teasers and a one-click jump into MapPro for the full workspace; export menus and the area inspector are available without the full rail.

Record the loaded-combination dimensions and weight in Map → Transport — the single source of truth every verdict, badge and report reads. Confirming a configuration locks it as the reference for a movement; weight left at 0 is treated as "not declared", never as zero.

Map → Decisions is the validation log: who approved which configuration, report or corrective measure, on which data version and with which technical right (and any competence role held, recorded for provenance — roles never block a sign-off). Entries are written by the server when a sign-off happens and are never editable.

Map → Movements lists studied, declared and documented passages on the corridor. After the transport, use Declare passage (or the guided Transport closure wizard) to attach closure evidence — driven kilometres, incidents, photos — and promote the movement to route memory.

Map → Route history shows past movements, road profiles and studies recorded on the same corridor across your company, so a new load is compared against what already travelled there. Max can answer questions from this memory.

Reports & Delivery → Report Builder (/roadscope/reportbuilder) opens the page-layout editor for the active map. Start from a template or a blank A4 / Letter document.

Drag data blocks (POI tables, route maps, photos, measures, corrective measures), free-frame text boxes and your logo onto the page grid. Pinned blocks repeat on every output page — use them for headers and footers.

Every data block binds to a catalogue field of the map (POIs, routes, vehicles & loads, measures). Bindings show an explicit state — bound, empty or missing — so nothing renders silently from stale data.

Publish creates a frozen snapshot rendered to PDF; the PDF is byte-stable on reprint and lands in the Files panel and Interactive Reports with a version label. Edits after publishing create a new revision.

Max can add, move or fill Report Builder blocks on request ("add a photo grid of the bridge POIs on page 2") and merges its edits with yours live.

From a POI (or a multi-selection) choose Corrective measure: pick the measure from the catalogue, the responsible party and the status (proposed, requested, confirmed, done). One measure can cover several POIs and appears in the Work Required section of the Route Survey Report.

Run the utility route check (Permits → Public Utilities Registry, or from the Routes panel) to see which power, telecom and rail owners the route crosses, with contacts and approach-distance rules.

Create an action request from the measure or from Workspace → Action Dashboard (/actions): recipients, deadline, the items to confirm and the evidence you attach. Recipients get a secure portal link and answer without an account.

The Action Dashboard shows every open request, the reminders sent (they continue automatically until the request is answered or closed), the recipient responses and attached evidence.

A request closes only after an internal verification of the recipient answer; the closure is recorded as a decision and the corrective measure status updates accordingly.

Permits → Permit Manager (and the Permits panel in MapPro) tracks applications per jurisdiction for a movement: required documents, submitted values, reviewer divergences and expiry. Only confirmed values are used — unknown is never treated as zero.

Upload a permit PDF and the scanner extracts the key fields for review; auto-fill pre-populates applications from route, load and equipment data in your unit preference.

Tools → Permit Documents & References (/document-center) is the OS/OW Document Center: permits, regulations, jurisdiction packs and supporting documents per project, with visibility rules for shared maps.

Permits → Public Utilities Registry (/utility-registry) lists utility owners by region with contacts and approach-distance rules used by the utility route check and action requests.

Jurisdiction packs define minimum approach distances and clearance rules per province / state. Overhead-wire and high-voltage verdicts use the pack matching the POI location; a mismatch with the map jurisdiction is flagged in the report.

Map → Road Profiles imports ProfilingPRO packages, NMEA journals, GPX and CSV traces. Profiles longer than a few thousand points are stored in cloud storage and streamed on demand; every export carries its datum.

Edits (trim, smooth, merge, gap handling) create new derived profiles by replaying operations — the source profile is never modified. Compare two profiles side by side and link a profile to a route for grade review.

Run the vertical engine against a trailer configuration to find grounding points (a ridge between supports) and vertical clearance losses; results feed the Road Profile Report and SweptPRO vertical analysis.

Import / Export → Import accepts CSV (including RSA laser CSV), Excel, GPX, KML/KMZ, GeoJSON/JSON, Shapefile, GeoTIFF, DXF, LandXML, AutoTURN vehicles, PDF, geotagged images, ZIP packages, MeasurePRO, ProfilingPRO and SweptPRO packages and RoadScope / MapHub archives. Content is detected by file type; unknown spreadsheet layouts go through the AI mapping step for your review.

Import / Export → Export produces CSV, Excel, GeoJSON, GPX and KML/KMZ of POIs and routes with route sequence and chainage, photo bundles and RoadScope archives. Reports export from the Reports Hub as interactive HTML and signed PDF.

A RoadScope archive moves a map between accounts; weekly account backups are downloadable from My Profile → Backup.

Identity and logo, preferences (units, theme), notifications (email / SMS, Route Watch and corridor alerts), collaborations, maps, contribution quality, backups and support tickets.

/profile/subscription shows your plan (Starter, Operator, Enterprise), the 14-day trial, usage against limits (maps, POIs, storage, AI drafts), invoices and the refund guarantee.

/profile/api-keys creates and rotates REST API keys; Settings → Webhooks fires on POI, route and report events. The API reference lives at /api.

My Profile → AI access issues a scoped, expiring read-only token for a map that you paste into Claude, ChatGPT, Gemini or Copilot following the on-screen instructions.

/profile/reports lists every report you issued across maps with version, integrity badge and viewer link.