Route Intelligence for Heavy HaulAnswers for every RoadScope surface: maps, POIs, routes, Route Intelligence, field capture, reports, sharing, team workspace, permits, AI and your account
Choose the support option that works best for you
Chat with the SolTec support team from inside RoadScope.
Leave a message — we reply by email
Live chat is available to signed-in RoadScope users.
Open and follow a ticket from inside the app (Tools → Support)
Speak directly with our technical experts
Enterprise customers only
+1.438.533.5344
Step-by-step manual, deep-dive docs and the Knowledge Base
Organised by product area — pick a category or search. Each answer links to the manual or docs article that goes deeper.
Last reviewed September 10, 2026
Open /request-survey (no account needed). The wizard walks through five steps — contact & company, transport, vehicle & load dimensions with explicit units, the route, and a review — and a checklist keeps Submit locked until everything required is in. For the route you can have it computed from origin/stops/destination, draw it by clicking on the map (each leg snaps to the road), or upload a KML/KMZ/GPX/GeoJSON file; in every case you approve the trace on the map before sending. You get a reference number and a confirmation email, and the survey team is notified.
Your request lands in the SolTec team queue with the status "New". The team reviews it and, once accepted, turns it into an internal working map (with your project name, vehicle and load dimensions, and the approved route) and sends you an email confirming that the request was accepted for review. You will then hear from the team about next steps. The working map itself is internal; it is not shared with you and no account is needed on your side.
Open Tools → My Maps and click "Create New Map". Give the map a name and customer, enter the loaded-combination dimensions (or pick a saved transport configuration), and click Create. The map opens in MapPro where you can plan a route, add POIs and attach files.
Tools → My Maps lists every map you own or collaborate on, with search, sort and archive filters. Inside MapPro the Map → Maps panel shows the same list so you can switch maps without leaving the workspace.
MapPro (the main Map workspace) is the full route-survey environment: POIs, routes, corridors, scenarios, reports and team tools. MapLite (/map) is a lightweight map for quick lookups and light POI edits on a phone or a shared link; it shows Route Intelligence teasers and lets you jump into MapPro for the full feature set.
Tools → Help opens this Help Center; Tools → User Manual is the step-by-step guide per feature; Tools → Knowledge Base covers OS/OW background; Tools → Feature Catalog lists every capability with its current status. In MapPro the Help rail entry opens the same resources plus live support. Each help family shows a "Last reviewed" date so you know how current it is.
Tools → Feature Catalog lists every RoadScope capability with its lifecycle status (available, beta, planned) and where it lives in the interface. Use it to confirm whether a feature exists before searching for it.
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.
The Overview panel is the map's information sheet: name, customer, project dates, vehicles & loads, corridors, project tasks, transfer/duplicate actions and the survey status. Edit it any time; reports read their header data from here.
Yes. MapPro supports map tabs: open a second map from the Maps panel and it appears as a tab above the map. Each tab remembers its own panel, zoom and active layers, and Route Intelligence scans stay parked with the map that started them. Closing a tab never deletes anything.
POIs, routes, files and settings save automatically as you edit. "Save All" forces any pending drawing or annotation edits to write immediately — use it before closing the browser on a slow connection. The workspace also restores your last panel, zoom and layer state per map when you return.
The Layers panel toggles basemaps (Google road/satellite/terrain, OpenStreetMap), overlays such as road events, NBI and provincial bridge inventories, imported SweptPRO layers, GeoTIFF/raster imports, 3D models and drawing layers. Layer visibility is remembered per map.
The Files panel holds every file attached to the map — permits, plans (DXF, DWG, PDF), photos, imported packages and generated reports — with labels, versions and a Plan Viewer for measuring on drawings. Permit-related documents are also reachable from Permit Documents & References.
Data continuity shows the integrity status of a map's files and shares: weekly backups, retention, restore drills and the integrity badge of each deliverable. Use it to prove a report or share link is still the version you issued.
A scenario is a transport study inside a map: its own vehicle configuration, selected routes and POIs, and reports. Use Scenarios to compare two loads or two seasons on the same corridor without duplicating the map. Items not assigned to a scenario belong to the default "Main study".
Open Settings (rail) or My Profile → Preferences and choose the distance and height unit. Clearance fields, reports and exports follow the selection; every value is stored with the unit you entered plus its SI equivalent, so switching never rounds your data.
In MapPro right-click the map (or long-press on mobile) and choose "Add POI", or use the POIs panel "+" button. Pick a type (bridges, overhead wires, signs, turns, curfews, railway crossings and 35+ more), enter measurements and notes, attach photos and save. POIs snap to the nearest route and receive a route sequence number.
Open the POI and drop images into the Photos area, or capture directly from the phone camera in the Field App. Geotagged photos are placed automatically; you can annotate them (arrows, text, measurement callouts) and mark one as the report photo.
Every POI type exposes the relevant fields — vertical clearance (per lane where available), roadway width, posted weight limits, span lengths, curfew schedules. Enter values in your preferred unit; the app stores the entered value with its unit and computes pass / marginal / fail verdicts against the loaded-combination dimensions.
Badges summarise the verdict of a POI against the current load: red = fails the required clearance/width/weight, amber = marginal (inside the safety margin), green = passes, grey = not evaluated because a value is missing. Height-danger badges also appear on the map markers and in exports.
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; measures appear in the Route Survey Report "Work Required" section and in the Work Required Report.
Yes. POI inspection forms add checklists, condition ratings and photo evidence per POI type. Inspections are timestamped and summarised in the reports' derived findings.
POI Discovery (Route Intelligence → POI Discovery, or /poi-discovery) searches every POI your company has ever captured, plus shared community POIs, by area, type, dimension and text. Attach a found POI to the current map instead of re-surveying it.
Workspace → POI Library is your company's curated set of reusable POIs. Workspace → POI Use Requests tracks requests from other companies to reuse one of your POIs on their map, with approve / decline actions and an audit trail.
Add a Turn POI and pick the direction; turns are auto-numbered along the route and detected turns can be reviewed after a route is created. Directions appear as colour-coded chips in the POIs panel and export to CSV, Excel and reports.
Open Map → Routes and click "Plan a Route". Draw waypoints, snap to roads (Google, HERE or ORS routing), or import a GPX/KML/GeoJSON trace. Routes can be split into legs, merged and classified (survey, liaison, alternate). Elevation and grade are computed automatically.
Route Intelligence → Route Generator (/route-generator) builds candidate routes between an origin and destination for your load dimensions, using truck-aware routing and known restrictions, and lets you import the result into a map as a route.
Road Profiles are survey-grade vertical profiles of the road surface (from ProfilingPRO, NMEA journals, GPX or CSV). Open Map → Road Profiles to import, merge, compare, edit (derived profiles) and export them, and to run grounding / vertical clearance checks against a trailer configuration.
Open Products → SweptPRO Simulation, pick a vehicle from the Equipment Library (or an AutoTURN import) and an intersection on your route. The simulator produces the swept envelope, obstacle conflicts and a verdict. SweptPRO desktop packages can also be imported as layers.
The Analysis panel gathers the envelope (maximum load envelope along the route), width analysis, region summaries and grade review for the active route, with links to the matching Reports Hub outputs.
The Median panel runs the median-encroachment engine: for divided highways it computes where a long combination would cross the median or the opposing lane in curves, and feeds the Median Encroachment Report.
The Rail panel (Rail Miller module) manages crossing clearances, rail-owner contacts and the OS/OW rail rules reference library; railway crossing POIs feed the Rail Information report.
Products → Axle Load Calculator (/tools/axle-load-calculator) checks per-axle legal weights and Bridge Formula compliance for US states and Canadian provinces from an axle layout you enter or pick from the Equipment Library.
Products → Equipment Library (/equipment-library) stores tractors, trailers and loads with dimensions, axle spacing and weights. Entries feed transport configurations, SweptPRO, the Axle Load Calculator and report headers.
The Convoy panel configures the loaded combination and escort vehicles used by the shared-map envelope tab and RoadScope Navigator: overall height, width, length, weight and the number of pilot cars.
The Transport panel records the loaded-combination dimensions and weight for the map — the values every verdict, badge and report uses. Confirming a configuration locks it as the reference for a movement; it is the single source of truth for vehicles & loads.
Route Intelligence unlocks structure and restriction data along a route or drawn area: NBI and Canadian bridge inventories, Québec MTMD structures and truck network, European bridge data, OpenStreetMap structures, road events and community POIs. Results show Match / Excluded / Unknown against your dimensions. Tools → Route Intelligence Data (/ri-data) lists sources, freshness and your contributions.
A route belongs to one map. A corridor is a reusable origin → destination record registered in the Corridor Library that several maps, movements and permits can reference. Map → Corridors links the current route to a corridor so route history and Route Watch accumulate across projects.
Workspace → Corridor Library (/company/corridors) is the company-wide list of registered corridors with their vehicle configuration, last movement, known constraints and watch status. Spawn a new map from a corridor to start a repeat move with everything pre-filled.
Workspace → Corridor Status (/company/corridor-status) shows every registered corridor with its Route Watch health (clear, changes detected, not evaluated), open action requests and the freshness of its last scan, so dispatch can see at a glance which corridors need a re-survey.
Route Watch re-scans a saved corridor on a schedule against road events, closures and structure data and alerts you (email, SMS or in-app) when something changed since the last survey. Enable it from the Corridors panel or the Corridor Status dashboard; a corridor is only reported "clear" when it was actually evaluated.
Route history lists past movements, road profiles and studies recorded on the same corridor — including those from other maps in your company — so you can compare a new load against what already travelled there.
A movement is a studied, declared or documented passage of a specific configuration on a corridor. Declare a passage after the transport, attach the closure evidence and the movement becomes route memory that future studies and Max can rely on.
Decisions is the validation log: who approved which transport configuration, report or corrective measure, on which data version and with which technical right. Entries are created by the server when a sign-off happens and cannot be edited afterwards.
Turn on the Road events overlay in the Layers panel (or from the Routes panel). Events come from provincial/state feeds inside their coverage area and are refreshed regularly. Route Intelligence results, the overlay, Route Watch and Max's route briefing all classify the same events against your active route with an INFO / ADVISORY / WARNING / CRITICAL level — an active full closure on the route is flagged "ROUTE CONFLICT — ROAD CLOSURE", a temporary width, height, weight or length limit smaller than your load is a "TEMPORARY … CONFLICT" — each with its source agency and how long ago it was updated. Nothing is re-routed automatically; when no event is known you see "No known government event identified", never "clear".
Open /fieldapp on a phone (install it as a PWA for offline use). Sign in as an operator, pick the map and capture POIs with photos, measurements and GPS accuracy. Captures queue offline and sync when connectivity returns. Assigned tasks and verification requests appear under Field App → Tasks.
Each capture stores the device-reported horizontal accuracy alongside the coordinates; the accuracy circle is drawn on the map and exported with the POI. Missing accuracy is stored as unknown — never as zero. If GPS is poor, wait for the circle to shrink, move away from tall structures, or place the POI manually and note it.
Record with an Insta360 camera, export the video from Insta360 Studio, then open Map → 360° Street View (Insta360 panel) and drop the video plus its GPX/telemetry into the browser — nothing to install. Frames are extracted, aligned to the route and published as a street-view layer; POIs can be created directly from a frame.
Open the viewer and press Measure (ruler icon), then click the base of the object and its top. The readout gives an estimated height with the distance it used and where that distance came from: ground geometry (needs the capture's camera height above the road, entered in the Insta360 import wizard and correctable from the readout), a snap to a visible POI / route / layer within 4° of the click, or a distance you type in — the tool never invents one. Points follow the panorama while you look around and clear when the frame changes. Nearby POIs (pin icon) lists POIs within 200 m and draws them on the panorama.
Drive video plays a geo-referenced survey video (from a MeasurePRO ZIP or API upload) synchronised with the map: scrubbing the video moves the marker along the route and clicking a POI seeks the video to that point.
MeasurePRO (field LiDAR) sends measurements either as a ZIP package you import from Import / Export, or live through the MeasurePRO API once your company is paired (Company Admin → MeasurePRO). Each measurement carries its provenance and re-syncs replace only MeasurePRO-sourced media.
ProfilingPRO packages (road profiles, POIs, media, NMEA journals) import from Import / Export → ProfilingPRO. Content is detected by file type: profiles become Road Profiles, POIs are typed from the package, media links by directory and everything else is attached as files.
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, SweptPRO packages and RoadScope / MapHub archives. The AI import wizard maps unknown column layouts for you.
Import / Export → Export produces CSV, Excel, GeoJSON, GPX and KML/KMZ of POIs and routes with route sequence and chainage, photo bundles, and the same data via the public API. Reports export from the Reports Hub as interactive HTML and signed PDF.
When a spreadsheet does not match a known layout, the import wizard asks the platform AI to propose a column → POI field mapping, which you review before anything is written. It counts against the monthly AI draft quota of your plan.
Export a RoadScope archive (ZIP) from Import / Export, then import it into another account or map. Legacy MapHub archives import the same way. Weekly account backups can be downloaded from My Profile → Backup.
Reports & Delivery → Reports (Reports Hub) produces the Route Survey Report (master), POI Report, Work Required Report, Survey Plan + Weather, Rail Information, Clearance Profile, Province / State POI Report, Width Report, Envelope Report, Median Encroachment Report, Road Profile Report, the interactive Maximum Envelope Report, the Evidence Registry and AI Report Studio drafts. Every issued report lands in the Files panel with a version label.
Before issuing, the Reports Hub runs a data-completeness check: missing dimensions, POIs without measurements, unconfirmed transport configuration. Fix the listed items or acknowledge them; the check prevents a report from silently passing a constraint that was never evaluated.
User menu → Interactive Reports (/profile/reports) lists every report you issued across maps, with the version, integrity badge and viewer link. The Report Viewer (/report-viewer/:shareId) is what recipients open; it is read-only and tied to the issued snapshot.
Reports & Delivery → Report Builder (/roadscope/reportbuilder) is a page-layout editor for custom deliverables: drag data blocks (POI tables, maps, photos, measures), free-frame text and your logo onto A4/Letter pages, bind them to live map data, then publish a frozen snapshot as PDF. Max can edit a Report Builder document on request.
The Evidence Registry is an append-only record of every measurement, photo and document a report relies on, with source, date and contradictions detected between sources. It is issued from the Reports Hub and can be opened from any report.
Generate the Driver Briefing PDF from Reports & Delivery, or send the route through NAV Live Dispatch so the crew sees turn-by-turn hazards on RoadScope Navigator.
Open the Share panel → Collaborators and invite by email as viewer, editor or manager. Collaborators see the map under My Maps; per-map collaborator seats are billed according to your plan. My Profile → Collaborations lists maps shared with you.
Project Guest View (/pm-guest/:token) is a tokenised read-only page for external stakeholders of a project: milestones, tasks and deliverables without a RoadScope account.
Yes. Map comments are attached to the map (with an optional POI reference) and notify collaborators; comment drafts are kept locally if you navigate away before posting.
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) manages employees and roles (owner, admin, surveyor, viewer), the access matrix per map, invitations, the audit log, MeasurePRO pairing, branding for reports and the company Route Watch policy. Only owners and admins see it.
Workspace → All Maps, Workspace → All Routes and Workspace → All POIs list company-wide records with owner, last update and filters, and open the map directly. Platform admins additionally have an All Maps view across every company.
Workspace → Action Dashboard (/actions) tracks action requests: work you asked a utility, road authority or contractor to do (lift a wire, confirm a clearance), the reminders sent, the recipient's answers in the portal and closure verification. Reminders continue automatically while a request is open.
Recipients receive an email with a secure portal link; they can confirm, decline, attach evidence or ask a question without an account. Their response is recorded as evidence on the request and, once verified internally, the request closes.
Work → Project Dashboard (/projects) groups maps into projects with milestones, deliverables and a timeline. My PM Tasks (/my-tasks) shows the tasks assigned to you; Workspace → Team Tasks (/company/tasks) lists every project task across the company; Verification Requests lists field verifications awaiting a surveyor.
Tools → Route Survey Books (/survey-books) are project-level books that gather several maps and their reports into one deliverable index for a client or a permit file.
User menu → Timesheet lets surveyors record time per day and map, then submit the week for approval by a company admin. Approved timesheets are visible in Company Admin.
Every POI, route and report carries a phase tag. Filter the workspace by phase, bulk-switch items between phases and expose only the phases you want on a shared map.
Permits → Permit Manager (and the Permits panel in MapPro) tracks permit applications per jurisdiction for a movement: required documents, submitted values, reviewer divergences and expiry. The AI permit scanner extracts key fields from an uploaded permit PDF; auto-fill pre-populates applications from route, load and equipment data.
In the MapPro Permits panel, Create route from permit reads the permit's approved routing description as an ordered highway chain (junctions, exits, mile offsets, county lines, border crossings) and previews it on the map. Every step shows whether the routing engine actually drove the permitted highway there; detours off the named highways and steps that could not be placed are listed so you can drag the line back or fix the text. For a multi-state move, Chain permits lets you tick one permit per jurisdiction, confirm the direction of travel and save one continuous route with a segment per permit — hand-offs between permits are checked and each segment carries its curfews, escort and travel restrictions.
Tools → Permit Documents & References (/document-center) is the OS/OW Document Center: permits, regulations, jurisdiction packs and supporting documents organised per project, with visibility rules for shared maps.
Permits → Public Utilities Registry (/utility-registry) lists utility owners (power, telecom, rail) by region with contacts and approach-distance rules; a utility route check flags which owners a route crosses so you can send action requests.
Jurisdiction packs define the minimum approach distances and clearance rules per province/state. Verdicts on overhead wires and high-voltage lines use the pack that matches the POI location, and a mismatch between the map's jurisdiction and the pack is flagged in the report.
Max (AI rail entry, or /assistant) answers questions about the active map — POIs, routes, corridor memory, reports, rail rules and project tasks — using live read tools, and can open panels, start imports, draft report sections and edit Report Builder documents on request. Max never fabricates measurements and cites the record it read.
AI Report Studio (Reports Hub) drafts narrative reports from your map data using your own templates, with a revision chat and a quality gate that blocks unsupported numbers. Drafts count against the monthly AI draft limit of your plan.
Yes. My Profile → AI access (/profile/ai) issues a scoped, expiring access token for a map; paste it into Claude, ChatGPT, Gemini or Copilot following the on-screen instructions and the assistant can read that survey's POIs, routes and reports. Report recipients get the same via the AI landing page linked from a delivery.
User menu → My Profile covers identity and logo, preferences (units, theme, language options), notifications (email/SMS, Route Watch and corridor alerts), collaborations, maps, contribution quality, backups, support tickets and AI access.
New accounts start a 14-day trial. User menu → Subscription (/profile/subscription) shows your plan (Starter, Operator, Enterprise), usage against limits (maps, POIs, storage, AI drafts), invoices and the refund guarantee. Upgrades apply immediately; downgrades at the end of the period.
User menu → API Keys (/profile/api-keys) creates and rotates keys for the REST API; webhooks are configured under Settings → Webhooks and fire on POI/route/report events. The API reference is at /api.
Plans include a device limit; signing in on an extra device ends the oldest session. Company admins can review sessions in Company Admin.
The Field App (/fieldapp) installs as a PWA and captures POIs, photos and measurements offline, syncing when back online. MapPro and MapLite require a connection for map tiles and Route Intelligence data.
Current Chrome, Edge, Safari and Firefox on desktop; Chrome and Safari on mobile. WebGL is required for the 3D digital twin and 360° viewer.
Allow location access in the browser, keep the device outdoors with a clear sky view, and wait for the accuracy circle to settle below your tolerance. Airplane mode, battery savers and in-app browsers (e.g. inside a messaging app) commonly block GPS — open the site in Chrome or Safari directly.
The public Service Status page (/status) shows live status for every user-impacting subsystem (map tiles, elevation, routing, Route Intelligence sources, email) from the same health probes that drive the indicator on this Help Center page. Inside the app a banner also appears at the top when one of those dependencies is degraded and clears automatically when the probe recovers. Platform admins see the full System Health page.
Use Tools → Support (or email support@soltec.ca) with the map name, browser, device and steps to reproduce. Feature ideas are welcome — the Feature Catalog shows what is already planned.
More ways to learn and get help with RoadScope
We could not reach the health service.
Our support team is standing by to help you succeed with RoadScope.