Your drivers do not need to learn Gearflow. Each driver gets their own moves by email or text, reports each move done or not done, and carries the bill of lading that Gearflow prints from the move.
A driver's whole contact with Gearflow is a link on their phone. Without it, dispatch phones each driver with the day's moves, and the driver phones back when a load leaves and when it arrives. Nobody else can see where the move is.
Gearflow sends each driver their own moves. The driver opens a move from the link with no password, sees the route and the contacts, and reports progress with one tap. Every change shows on the move's timeline for dispatch and for the requester.
A driver is a user on your account. On accounts that use haul scheduling, the Add user and Edit user dialogs in Settings > Users have a Drives trucks switch. Under it, Can drive records the trucks the person can drive: Dump truck, Lowboy, Flatbed, Rollback or Step-deck. The Board and driver sourcing use these answers. Your Gearflow contact turns on haul scheduling for your account.
A driver must agree to texts before Gearflow texts them. Driver texts gets that agreement from your whole crew at once. Every account has it.
The table under the box shows each driver's state: Invited, Said yes, Stopped or Undelivered. Resend sends the invite one more time. Gearflow never sends it a third time. A driver who replied STOP must restart texts themselves.
Each email or text that Gearflow sends a driver about a move carries a link to that move. The link signs the driver in to that one move and nothing else. It does not open the rest of your account, so a forwarded link shows one move only.
The link stops working when one of these happens:
The driver page shows Stay signed in on this phone. When the driver taps it, they stay signed in on that phone, so they do not need a sign-in code every time they open Gearflow.
The assigned driver moves the move along with one button. Dispatch does not need a phone call.
These buttons are on the move in Gearflow, and on the driver page that a link opens, for the assigned driver. The driver does not need to sign in first. From the move's scheduled day, the driver page also shows Didn't happen, and Done while the move is still Scheduled. When the move is In transit, Mark dropped off takes the place of Done (see The end-of-day check).
On a dump-truck request, the buttons read Mark job started and Mark job ended.
Only the move's assigned driver sees these buttons. The driver role does not matter: a field user who is the assigned driver gets the buttons, and gets no other dispatch rights. People who dispatch moves change the status from the status menu instead.
From the move's scheduled day, the assigned driver also sees Didn't happen. The driver can say why in What happened? (optional), and then taps Report it didn't happen. The move goes back to Open with no day and no driver. Gearflow tells the dispatcher and the requester, and posts a message on the move.
At the end of each day, Gearflow asks each driver about the moves that are still Scheduled or In transit that day. The email "Did today's moves happen?" has two links for each move. A text has one link for each move. Each link opens the driver page with Didn't happen at the top, and Done for a move that is still Scheduled. For a move In transit, Mark dropped off takes the place of Done:
The check goes out at the Ask at time in the daily digest settings. It starts at 6:00 PM. The check goes out only while the daily driver digest is on.
The daily driver digest sends each driver tomorrow's moves the day before. Each driver gets one email with only their own moves. Dispatch does not build the list by hand.
People who dispatch moves turn it on from the Daily digest badge in the Mobilizations list header. The badge reads Daily digest: off until someone turns it on, and then shows the send time, for example Daily digest: 5:00 PM EST. Click it to open Daily driver digest:
The email subject is "Your moves for day — N moves". Each move shows the pickup and drop-off addresses, which open navigation, the truck and a View move link.
The digest has these limits:
On accounts that use haul scheduling, the digest is the daily dispatch:
Gearflow prints the bill of lading from the move. A driver must carry one on each load, and the move already holds everything on it.
The PDF has these parts:
Download it from the Actions menu (the three dots) on the move, or from the driver page. Gearflow prints it fresh each time, so an edit to the move shows on the next download.
Your Gearflow contact can also turn on Bill of lading on emails. Then the hired hauler gets the PDF with the award email, and your driver gets it with the assignment email. An RFQ never carries it: every hauler that bids gets the RFQ, and only the hauler that wins gets the load paper.