Feature Requests

Allow each user (or the account globally) to set a default Payment Type that gets pre-filled when a load is created.

When opening a load in Dispatch Board 2.0, only the latest time is shown (e.g. 09:00 PM). For FCFS loads that have a window (e.g. 06:00–09:00), show the entire time range instead of only the final timestamp.

Allow the Overview section data to be exported as a .pbix file so Power BI users can load it directly into their dashboards.

### Purpose Measure driver reliability, service performance, and safety Auto-create safety intervention tasks from Samsara events Provide documented coaching records (FMCSA defensibility) ### Scoring frequency Weekly (operational visibility) Monthly (disciplinary / incentive use) ### Total score: 100 points ### Score categories & weighting | Category | Weight | Data source | |---|---|---| | On-Time Pickup (OTP) | 25 pts | TMS / Dispatch | | On-Time Delivery (OTD) | 25 pts | TMS / Dispatch | | Load Rejections | 15 pts | Dispatch logs | | Safety & Compliance | 35 pts | Samsara + Safety | ### KPI definitions (summary) OTP / OTD (25 pts each) — arrive within ±15 min of agreed window. ≥98% = full score; sliding scale down to 0 at <85%. Broker/customer delay = dispatch exception (no driver penalty); driver-error delay counted. Load Rejections (15 pts) — rejecting an assigned load without an approved reason. 0 rejections = 15 pts; sliding scale to 0 at ≥3. Approved reasons (no penalty): HOS conflict, equipment safety defect, verified illness/emergency, FMCSA/policy violation. Safety & Compliance (35 pts) — event-driven and Samsara-integrated. Deductions per verified event: speeding (-3 / -5 / -10 by severity), harsh braking/accel (-2), phone use (-7), seatbelt (-5), HOS (-10), preventable accident (-15 to -35). Floor at 0. ### Samsara safety-event workflow (critical) Samsara generates a speeding/safety alert Safety task auto-created (high-level intervention) with driver, event type, timestamp, location, speed Safety team notified (email / Slack / task board); status Open Required actions: driver contacted within 24h, coaching performed, video reviewed if applicable Documentation required: date of contact, safety agent name, driver acknowledgment, coaching notes, corrective action Task closure: status → Resolved, linked to driver file, retained for audit FMCSA defensibility: "Motor carrier identified unsafe behavior, intervened promptly, and documented corrective action." ### Overall driver rating | Score | Rating | Status | |---|---|---| | 90–100 | Excellent | Eligible for incentives | | 80–89 | Good | Normal operations | | 70–79 | Watch | Coaching required | | 60–69 | At Risk | Written warning | | < 60 | Critical | Suspension / retraining | ### Reporting Driver view: personal score, 90-day trend, event log Management view: bottom 10%, event frequency, OTD/OTP by dispatcher, coaching completion rate Audit view: event → task → resolution chain with timestamps and corrective-action proof

Add an enforcement option that prevents dispatching a truck whose documents (registration, inspection, etc.) are expired.

Add a field to Work Order creation notifications that shows the total amount of the Work Order. Today the notification has the work-order metadata but not the total.

Credit Memos are currently excluded from the Aging Report. Include them so the aging view reflects the customer's net position.

Add a dashboard for driver hiring and retention metrics, including turnover rate, average length of employment, and average time-to-hire.

Allow company fee % to be configured per load type — for example, 10% on Amazon loads and 12% on standard loads — instead of one flat company fee for all loads.

Based on the FMCSA inspection type/outcome, define rules that automatically create credits or deductions for the driver — so violations and pass-throughs flow into payroll without manual entry.