Coverage queue
Loads without a carrier rise to the top, sorted by pickup time and lane.
A freight brokerage manager needs to know which loads still lack a carrier, which check calls are overdue and where margin is slipping before the day ends. A freight manager dashboard puts open loads, dispatcher assignments and margin reporting on one screen.
A load usually starts as a shipper request, becomes a quote and then a covered load once a carrier accepts it. Along the way, the rate desk, the dispatchers and the account reps each touch the record. The handoffs happen across email, phone calls and a transportation management system that not everyone reads the same way.
The break points are familiar. A covered load has no check call logged for hours, a quote sits unanswered because the rep was working another lane, and a repriced load skips the margin review. A manager often learns about those problems late in the day, when the shipper has already called to ask.
The general manager opens the dashboard at the start of the day. The carrier coverage queue lists loads with no carrier and pickup times inside the next few hours, sorted by urgency. The open load coverage view shows the shipper, the lane, the quoted margin and the dispatcher who last touched each load.
The manager reassigns a load to a dispatcher with the right lane experience, and the change appears on that dispatcher's list at once. Later, overdue check call alerts flag a load in amber, and the manager reads the note the dispatcher left. At close of business, the brokerage daily margin report lists covered loads, repriced loads and margin by lane for the owner.
Many brokers use McLeod for the system of record and DAT for load postings, although other products are just as common. Most brokerages also run an accounting tool that holds invoices and payments. The manager dashboard should read from those systems and never ask staff to enter the same margin twice.
Accounting teams usually want exports they can reconcile against invoices, so the reports should produce clean columns. Team chat can carry exception alerts, while the dashboard stays the place where decisions are logged. We would list each connection in the written scope before any development starts.
Loads without a carrier rise to the top, sorted by pickup time and lane.
Move a load to another dispatcher and the change shows on their list at once.
Overdue check calls flag the load, with the last note and the time it was logged.
Repriced loads that fall below the agreed margin show up for review the same day.
Covered loads, repriced loads and margin by lane appear on one page for the owner.
Every rate, margin and status change records the person and the time it was made.
Brokerage systems hold shipper pricing, carrier insurance and operating authority details, so access should follow each person's role. Carrier safety information should reach only the staff who vet and cover loads. The company should confirm its own contract and data handling terms before the dashboard reads any of those records.
Freight rules differ by mode and by state, so the build should store the rules the company actually uses rather than assume them. Records that support a claim, such as delivery timestamps and signed bills of lading, should be kept unchanged. Every edit should show who made it and when, which protects the brokerage if a dispute arises.
Price moves with how many roles the dashboard serves, how many systems it reads and whether alerts reach phones by text. The starting point for a mobile build is $4,500, and the exact figure is set in writing once the scoping call ends. The schedule depends on those same factors.
The clearest way to protect scope is a first release built around the coverage queue, the margin view and one daily summary. Forecasting, carrier scorecards and lane profitability models can wait for a later phase. Post-launch support is available, so each addition can be scoped and priced on its own.
Dispatchers adopt a dashboard when it shortens their own day. Start with one lane group, run the queue beside the current process for a short stretch and collect the reasons people still open a spreadsheet. Those reasons usually point to a missing field or a confusing label, and they are inexpensive to fix early.
Managers need a clear habit too. Agree a fixed time for reviewing the exception list, and give the owner a short summary instead of a full report. A dashboard opened at the same time each day becomes part of the routine rather than another screen to ignore.
No. The dashboard reads from the transportation management system and writes back only the tasks and alerts it owns. Rates, documents and billing stay in the system of record. We would settle the exact fields and sync timing before the build is scheduled.
The rules are set with the brokerage, using pickup times, gaps between check calls and margin thresholds. A load can carry more than one flag, and each flag shows the rule that triggered it. Managers can adjust the thresholds as the team learns what works.
Margin visibility is a role decision. Many brokerages show it to managers and owners only, while dispatchers see the rate they need to cover a load. We would set those permissions before launch.
The record updates as soon as the new information arrives, and the next report reflects it. The earlier report keeps its original timestamp, so the brokerage can see what was known at that time. Nothing is overwritten silently.
Speak with SIZ Group at +1 254 323 2698 and walk through your coverage rules before anything is built.