Basics
Getting started
Create an account with your work email, confirm it, and the setup wizard asks five things: company name, number of vehicles, number of drivers, business type and your depot address. The depot is where every route starts and ends.
- 1Sign up and confirm your email.
- 2Finish the 5-step setup.
- 3Optionally load demo data to explore with realistic routes.
- 4Add your own vehicles and drivers under Fleet & contacts.
Basics
Workspaces & multiple companies
A workspace holds one company's vehicles, drivers, customers, deliveries and routes. Data never crosses workspaces — this is enforced inside the database, not just the screen.
- 1Open the workspace name at the top of the side menu.
- 2Switch between workspaces, or choose New workspace.
- 3Your device remembers the last workspace you used.
Daily work
Adding deliveries
Deliveries can be typed in one by one or imported from a spreadsheet. Address fields show real places from Google as you type, so every stop lands exactly on the map.
- 1Press N on the Deliveries page or use Add delivery.
- 2Start typing a customer — saved customers fill in address, phone and usual order.
- 3Pick a time slot, weight and notes.
- 4Or use Import to upload a CSV with many deliveries at once.
Good to know
- Customer memory saves boxes, product and taste on every save.
- Use By driver view to see each driver's tasks grouped together.
Daily work
The planner
The planner is where a day takes shape. It follows four steps shown at the top: Review deliveries, Optimize, Adjust, Assign to drivers.
- 1Check the Not on a route pool for unplanned deliveries.
- 2Press Optimize to build balanced routes automatically, or New route to pick a driver yourself.
- 3Drag stops between drivers, or use the Assign button on any stop.
- 4Lock a route when it's final so optimizing again won't change it.
Daily work
How route optimization works
RouteBase groups stops by direction from your depot (sweep clustering), orders each group by always driving to the nearest next stop, then improves the order by un-crossing lines (2-opt). It respects your max stops per route and minutes per stop.
Good to know
- Locked routes are never touched.
- Settings let you choose whether drivers return to the depot.
- Optimization runs instantly on your device — no waiting.
Daily work
Day timeline & breaks
Under the planner map, each driver has a bar on a day timeline. Drag a bar to change the start time in 5-minute steps; every arrival time follows. Breaks (default 30 minutes at 12:00) are inserted before the first stop after break time.
Good to know
- Drag the coffee cup to move a break.
- Late stops turn orange instantly.
On the road
Live map & telemetry
The Live map shows every driver, their route and progress. Click a driver to see speed, next stop, ETA, distance left and expected return to the depot.
Good to know
- Speed is an estimate until the driver app reports real GPS.
- Needs attention on the Overview lists drivers running more than 10 minutes late.
On the road
Driver PDFs
Each driver section on the Deliveries page has a PDF button. It downloads a printable list with the driver, vehicle, totals and every stop in driving order with a tick-box.
Insights
Analytics
Analytics shows deliveries per day, on-time rate, failures by reason and workload per driver so you can spot trends and balance your fleet.
Admin
Team, roles & ownership
Settings → Team & roles lists everyone with their role. Owners and admins can invite by email, change roles and remove people. The owner can transfer ownership to another member.
- 1Owner — everything, including transfer.
- 2Admin — settings and team.
- 3Dispatcher — plan and manage deliveries.
- 4Driver — see their own work.
Admin
Keyboard shortcuts
Press ⌘K / Ctrl+K anywhere for search & actions. Press G then a letter to jump pages (G D = Deliveries, G P = Planner). N adds an item on the current page, / focuses search, ? shows all shortcuts.
Technology
Architecture at a glance
RouteBase is a web application. The screens run in your browser, the business data lives in a managed database, and a small set of trusted outside services handle maps, payments and email. Heavy work such as route optimization happens on your own device, so your stop list doesn't have to leave the browser to be planned.
Good to know
- All traffic is encrypted with HTTPS.
- Each request carries a signed login token; the database checks it on every row.
Technology
Services & APIs we use
We only use services that are needed to make a feature work. Here is every outside service, what it does for you, and what it receives.
| Service | Used for | What it receives |
|---|---|---|
| Google Maps JavaScript API | Maps on Overview, Live map and Planner | Map area being viewed, your browser's IP |
| Google Places & Geocoding | Address suggestions while typing | The text you type into an address field |
| OpenStreetMap Nominatim | Backup address lookup | Address text when Google has no match |
| OSRM (open routing engine) | Road-following lines and driving times | Coordinates of stops on a route, no names |
| Waze, Google Maps, Apple Maps | Navigation from the driver app | Only the destination, when the driver taps Navigate |
| Lovable Cloud | Database, sign-in, file storage, server functions | All workspace data, protected by row-level security |
| Lovable AI Gateway | The setup chat for new workspaces | Your answers in that chat — never your deliveries |
| Paddle | Checkout, invoices and tax (merchant of record) | Billing name, email, country, payment details |
| Resend | Account and notification emails | Recipient email and message content |
Good to know
- We do not use advertising trackers or sell data to anyone.
- Payment card details go directly to Paddle — RouteBase never sees them.
Technology
How information reaches everyone
When a dispatcher changes something, it is saved to the database first. Every other screen then picks it up — no copy is kept on a separate server.
| Who | How they get updates | How often |
|---|---|---|
| Dispatchers (workspace) | Data reloads after every change and in the background | Instantly after saving, refreshed every 15–30 s |
| Drivers (driver app) | Signed-in app reads only routes assigned to them | On open, after every action, and every 15 s on a trip |
| Customers (RouteTrack) | Private link with a secret code for one delivery | Every 15 s while the page is open |
| Printed lists (PDF) | Generated in your browser from current data | When you press the PDF button |
| Sent through Resend | Sign-in, invitations and account messages |
- 1Dispatcher plans and presses Send times to drivers.
- 2Times and stop order are saved to the route.
- 3The driver app shows the new plan on the next refresh.
- 4When the driver taps Navigate, the customer's RouteTrack starts showing the van.
Data & privacy
What we collect
We collect what is needed to plan and run deliveries — nothing more. Below is the complete list, why we need it, and how long it stays.
| Data | Why | Kept |
|---|---|---|
| Account: name, email, password hash | Signing in and identifying you | As long as your account exists |
| Workspace: company name, depot, plan | Running your workspace | Until the workspace is deleted |
| Vehicles & drivers: names, plates, models, phone | Planning and assigning routes | Until you delete them |
| Customers & deliveries: address, phone, boxes, notes, attachments | Planning and proof of delivery | Until you delete them |
| Driver location | Live map and RouteTrack | Only during an active trip; latest position only |
| Proof of delivery: status, time, comments, photos | Showing what happened at each stop | Until you delete the route |
| Billing: plan, subscription status | Access to features | As required by tax law (via Paddle) |
| Technical: browser type, error logs | Keeping the service stable | Short-term logs |
Good to know
- Driver location is only requested when a trip is started — never on first open.
- You can export or delete your workspace data at any time by contacting us.
Data & privacy
Security model
Every business table carries the ID of the workspace it belongs to. The database itself refuses to return a row unless the signed-in user is a member of that workspace. This is called row-level security, and it applies to the app, the driver app and agent integrations alike.
- 1Signed login token proves who you are.
- 2Database checks your workspace membership on every row.
- 3Your role (owner, admin, dispatcher, driver) limits what you can change.
- 4Files are stored in private folders that follow the same workspace check.
Good to know
- RouteTrack links show one delivery only and the driver's first name.
- Admin-only actions such as creating driver logins check your role on the server first.
Data & privacy
How we use AI
AI is only used in the setup chat for new workspaces, to turn your answers into a list of vehicles and drivers. The AI never writes to the database itself — your browser saves the result after you confirm. Your deliveries, customers and routes are never sent to an AI model.
Data & privacy
Agent integrations (MCP)
Assistants such as Claude or ChatGPT can connect to RouteBase after you sign in and approve them. They can only look, never change anything, and they see exactly the workspaces you can see.
- 1List workspaces
- 2Read deliveries for a date
- 3Read routes with driver, vehicle, distance and time
- 4Read drivers and vehicles
Data & privacy
Your rights & data requests
Your workspace data belongs to you. You can ask for a copy, a correction or deletion at any time by emailing mha.business.contact@gmail.com. See the Privacy policy for full details.
Admin
Languages
RouteBase is available in English, Dutch, German, French, Spanish and Turkish. Your choice is remembered on your device.