Good morning
Operations Calendar
Daily routes, ERO, adhoc, and package counts per station — saved to the database for future lookback. Call-out data is pulled from Attendance (visible to managers only). Trend charts for this data are on the Records tab.
Compliance
Back-office and periodic paperwork — exemptions, break discrepancies, and attendance tracking.
Records
Lookback and documentation tools — reference the past rather than act on today.
Route & Package Trends
Routes and package volume over time, by station — matches whatever period is selected on the Dashboard's Operations Calendar.
Van Parking
Update spot numbers daily. Grounded vans stay in the list but are excluded from assignment.
Auto-saved
Add a van not in the list:
Bulk Spot Update
↑ Upload .xlsx
or type below (one per line, format: EDV 1:150)
Van assignment priority order
Vans are assigned in this order. One per line. Vans without a parking spot are skipped automatically.
Drivers
Driver directory — display names, contact numbers, and van preferences.
Auto-saved
Name is the driver's name as it appears on the roster — first name or full name (full name wins if both match). Preferred Name is what prints on the DayList; blank uses the roster name as-is. Preferred Van(s) are reserved before general assignment; list multiple comma-separated in priority order:
EDV 30, EDV 31 Transporter ID and Email are Amazon-sourced identifiers — filled in automatically by the roster sync below, or editable by hand.
| Name (roster) | Phone | Preferred Name | Preferred Van(s) | Transporter ID |
|---|
Scorecard
Coaching
Messaging
Send assignments and text back and forth with drivers.
Message Template
Tokens:
{van} reads “NOT ASSIGNED — see dispatch” when no van is set, and {spot} renders as “ (Spot 42)” or blank, so the line stays clean either way.
{name}
{route}
{lane}
{wave}
{van}
{spot}
{staging}
{pkgs}
{comm}
{van} reads “NOT ASSIGNED — see dispatch” when no van is set, and {spot} renders as “ (Spot 42)” or blank, so the line stays clean either way.
Preview
Length
Recipients
| Driver | Phone | Route | Van | Message | Status |
|---|
Send
Texts send through your secure server function — no gateway password in the browser. Sending is enabled when you're signed in and the send function is reachable. If it isn't set up yet, use Copy or Export CSV.
Generate DayList
Upload both files, then click Generate.
Ops Plan *
DSP-DayOfOpsPlan.xlsx
Roster (optional)
Roster .xlsx or .csv
Fleet Log
Track vehicle issues, maintenance notes, and status for each van.
Auto-saved
| Van | VIN | Status | Latest Note | Last Updated | Notes |
|---|
Delivery Notes
One card per address. All note types editable inline. Fuzzy duplicate detection on add.
Auto-saved
Add / Update Note
Address *
Note Type
Route Code (optional)
Note *
DCR Exemption
Upload one or more RTS .xlsx / .csv files. Optionally add a reference CSV for join data. Output is a cleaned, deduplicated .xlsx.
RTS Data File(s)
Drop RTS file(s) here or click to browse
.xlsx, .xls or .csv — multiple files will be combined
Reference CSV (optional — for Attempt Time, Business Hours, Address join)
Drop reference file here or click to browse
Joined on Tracking ID = TBA Number
Payroll Compliance
Cross-reference delivery data with Paycom/ADP time punches to identify break discrepancies.
Dispatch Desk Data
Upload the delivery data export from the The Dispatch Desk browser extension. Get the extension from Settings → The Dispatch Desk Extension.
Drop scrape export here or click to browse
Accepts the amazon_*.csv from The Dispatch Desk or a .json export
Payroll Provider Data
Upload the XLSX or CSV exported from your payroll provider (Paycom, ADP, etc.)
Drop payroll file here or click to browse
Supports .xlsx, .xls, and .csv formats
Attendance
Occurrences in a rolling six-month window, per the 702 Logistics attendance policy. This tracker records and surfaces standing — all disciplinary decisions remain at management's discretion.
OK 0–3
Coaching 4
Final coaching 7
Termination-eligible 10
Organization ›
Your DSP and station details, and payroll defaults. These sync to your whole team.
Matches the DSP column in the ops plan to pick your routes, and shows in the header.
Used in export filenames.
Recommended time when a driver's In-Day punch is missing.
Excluded from the payroll compliance engine entirely (no punch/break checks). One name per line, as they appear in the delivery data.
My Profile ›
Sets the name used in your Dashboard greeting (instead of your email handle). Only visible to you — everyone sets their own.
Change My Password ›
The Dispatch Desk Extension browser extension ›
Scrapes delivery/ops data from Amazon Logistics for payroll compliance and daily assignments. Install once, then export data to upload on the Payroll tab.
- 1Unzip the download, go to chrome://extensions, enable Developer Mode, click Load Unpacked, and select the folder
- 2Open The Dispatch Desk extension, set your date range, and click Run
- 3When the scrape completes, download the export and upload it on the Payroll tab
Database Backup ›
Export a full snapshot of your Firebase database, or restore from one. Restore via Firebase Console → Realtime Database → ⋮ → Import JSON, or use the section restore below.
Export Database
Download a complete JSON snapshot of all app data — parking, fleet, preferences, delivery notes, DCR, and payroll.
Restore Database
Upload a previously exported JSON, then choose whether to restore everything or just specific sections.
Drop backup JSON here or click to browse
About ›
The Dispatch Desk ·
Deployed on Netlify · Firebase Realtime Database
Deployed on Netlify · Firebase Realtime Database