- Join the correct company with a Dispatcher invitation code.
- Check Dashboard, Activity and Operations chat at the start of the shift.
- Use Load Calculator before accepting or assigning a load.
- Create the route and assign the correct Driver, truck and trailer.
- Monitor route statuses, percentage, notes and shared locations.
- Confirm the BOL/POD is uploaded with the correct Related route.
- Update maintenance requests and review Driver Forms before ending the shift.
1. Joining and signing in
- Use Join company, register with your own email, confirm the email and enter the Dispatcher invitation code supplied by the Owner.
- After sign-in, verify the company name is correct and the sidebar shows Dashboard, Load Calculator, Dispatch, Fleet, Team, Maintenance, Documents, Chat, Reports, How to Use and Settings.
- If the code is invalid or expired, request a new code from the Owner. Do not register a second account unless the first account is intentionally abandoned.
2. Start-of-shift workflow
- Open Dashboard and review active routes, online Drivers, open maintenance and planned profit.
- Open the bell and process unread route, document, maintenance and form activity.
- Open Operations chat for company-wide updates, then check private unread Driver conversations.
- Review Dispatch for routes that are Unassigned, waiting for location, delayed, at delivery or missing POD.
3. Load Calculator
- Enter rate type, rate, loaded miles, deadhead, accessorial revenue, fuel assumptions, tolls, reserve and other costs.
- Choose the Driver pay method and enter the correct rate. Compare profit and profit per mile with company policy.
- Use calculation in a route so the financial estimate is carried into Dispatch. Drivers never see this financial section.
- Treat the calculator as a planning tool; verify final invoices, payroll and actual expenses outside RoadReady.
4. Creating and assigning routes
- Enter route/load number, Driver, origin/destination, exact pickup/delivery addresses, appointment times, equipment and instructions.
- Select the correct Driver before saving. If the Driver changes, edit the route and confirm the new Driver received the assignment.
- Use Assigned for a new route. Route percentage depends on the status sequence, so keep statuses accurate.
- Do not place private financial details in Driver instructions or Operations chat.
5. Monitoring route execution
- Open a route to see status-based progress, POD status, latest shared location and Driver activity.
- Waiting for location means the Driver has not manually shared a current position. Send a private message asking the Driver to use Share current location.
- Use Add update or route notes for operational events that should remain in the timeline.
- Use Open Driver chat for route-specific questions. Use Operations only when the whole company needs the update.
- When the Driver marks Delivered, confirm the signed POD is linked before considering the route administratively complete.
6. Fleet and Team
- Use Fleet to add or edit trucks and trailers if the Owner permits this operational workflow. Keep unit status accurate before assigning equipment.
- Team shows Owner, Dispatchers and Drivers with online presence. Use Message for private chat and Assign route from a Driver card.
- Dispatcher accounts cannot invite or remove team members. Send those requests to the Owner.
7. Documents
- Use the Driver filter to open a Driver document folder, then filter by BOL, POD or another type.
- Document-to-Driver assignment is based primarily on Related route. Correct route selection prevents files from appearing under Unassigned/company files.
- Photos selected through Documents become a PDF; a ready PDF remains unchanged. Confirm page order and readability after upload.
- Use clear titles such as POD - Load 1048 or BOL - Winnipeg to Chicago. Avoid generic names such as image or document.
8. Maintenance
- Review Driver repair requests and attached photos. Confirm vehicle, location, safe-to-drive answer and priority.
- Move requests through New, Approved, Scheduled, In Repair, Complete or Cancelled.
- Urgent and Out of Service issues require direct communication; changing a status in the app is not a substitute for safety procedures.
9. Driver Forms
- Reports contains submitted Accident/Incident, Cargo Damage, Reefer Temperature and Border Checklist forms.
- Open supporting files, read all fields and contact the Driver for missing information.
- Escalate safety, cargo, insurance, customs or legal issues according to company procedures. RoadReady records the report but does not replace required external reporting.
10. Chat and notifications
- Use Operations for shared instructions and private chat for one Driver.
- Read receipts show whether a message was opened. Do not send repeated messages solely because a Driver is temporarily offline.
- Install RoadReady to the Home Screen and enable push notifications from Settings for new messages and operational updates.
- If chat or unread counts look wrong, open How to Use and run the system check before reporting the issue.
11. Reports and end-of-shift handoff
- Review route financials, completed routes, missing PODs, open maintenance and Driver Forms.
- Post a concise handoff in Operations or private Dispatcher chat: active load, current status, next appointment, issue, required follow-up and document status.
- Do not mark a route Delivered simply to clear it from the active list. The status must reflect the actual trip.
12. Dispatcher limitations
- You cannot manage Stripe billing, change company branding, create invitation codes or remove users.
- You can manage operational routes, financial estimates, fleet, Drivers, maintenance, documents, reports and chat.
- Contact the Owner for subscription, access or company identity changes.
Common system rules
Live synchronization
- RoadReady uses Supabase Realtime. New routes, messages, documents, maintenance updates and activity notifications should appear without manually refreshing. The sidebar indicator should show Live.
Route-document linking
- Always select the correct Related route when uploading a BOL, POD or trip document. RoadReady uses that route to connect the file to the assigned driver and to show POD received on the route.
Document photos
- In Documents or Uploads, one or more selected photos are converted into one PDF. A ready-made PDF uploads unchanged. Chat photos remain normal images.
Permissions
- Owner, Dispatcher and Driver accounts do not have the same access. Never share one login between people; invite each person with the correct role.
Support
- For account, billing or technical help, email roadreadyfleetos@gmail.com and include the company name, account email, device and a screenshot of the issue.
FAQ
Why is a document under Unassigned / company files?
The file was not connected to a route and RoadReady could not determine a Driver. Edit the workflow by uploading again with the correct Related route.
Why does POD pending remain on a delivered route?
A document of type POD must be uploaded and linked to that exact route.
Does RoadReady continuously track Drivers?
No. A Driver shares a single current position only after tapping Share current location.
Why does a route percentage look wrong?
Progress is status-based. Check that the route follows the normal status sequence and correct any inaccurate status.
Should BOL/POD be sent in chat?
Use Uploads/Documents for retained route documents. Chat images are for quick communication and are not the primary document record.
Who can manage billing and users?
Only the Owner can manage Stripe billing, create invitation codes and remove Drivers or Dispatchers.