Fleet Management Monthly Report Template for Carrier Owners
Build a monthly owner’s report that connects dispatch results, unpaid invoices, equipment downtime, and driver settlements. Use the copyable scorecard to assign follow-up work, not just collect numbers.
By TruckTA Editorial Team · TruckTA Resources
In this article
Your dispatch board shows completed loads. Billing has a different total, two trailers spent time in the shop, and drivers are asking about settlement adjustments. Before you book more work or add another truck, put those results in one report with consistent dates and clear ownership.
Use this fleet management monthly report as an owner’s decision packet: a summary scorecard, supporting detail, and an action log. The workflow below defines dispatch, receivables, equipment, and settlement measures for a multi-driver car-hauling operation. Copy the template into your spreadsheet, then keep the same definitions each month.
1. Set the reporting period and assign the inputs
Start the report with your company name, reporting month, cutoff timestamp and time zone, preparer, version, and review date. Add the trucks, trailers, and drivers included. Flag equipment added or removed during the month rather than comparing a larger fleet with a smaller one without explanation.
For this operating template, count transported vehicles by actual delivery date. Record invoice activity by invoice date, receipts by receipt date, and unpaid balances as of month-end. Label delivered-load revenue as an operational measure, not your accounting revenue or profit. Keep financial-statement treatment with your bookkeeper or accountant.
Record miles traveled within the reporting month. Keep unfinished trips in a separate month-end work-in-progress list. Don’t move their miles into next month just to match delivery revenue. If substantial work crosses the cutoff, flag that timing difference beside the revenue-per-mile result.
Assign dispatch to delivery counts, miles, and delay reasons. Give billing ownership of invoice balances and collection exceptions. Have the equipment lead supply downtime and assigned costs, while the settlement preparer supplies earnings, adjustments, and payment status. One person assembles the packet; each contributor checks their own inputs.
Finish record reconciliation before interpreting the results. Use the monthly bookkeeping closeout checklist for that upstream task. Keep this report focused on what changed, why it changed, and what you’ll do next.
Preserve a dated source snapshot. Keep load IDs, invoice IDs, driver IDs, and separate truck and trailer IDs in the supporting tabs. Mark missing information as missing, not zero. Show provisional totals explicitly and record later corrections in a revision log.
2. Measure dispatch output without hiding empty miles
Use two separate counts: completed customer orders and delivered vehicles. Define a completed order as one with all its vehicles delivered. Count each vehicle transport movement once at its final delivery. Exclude canceled vehicles and internal driver handoffs from the delivered-vehicle count.
For delivered-load revenue, assign the agreed carrier charges to completed deliveries. Keep approved accessorials separate from requested detention or other unresolved charges. For an order delivered across two months, document how you allocate its charges among vehicles. Don’t count the full order value twice.
Calculate deadhead percentage as empty miles divided by total miles, multiplied by 100. Treat a mile with at least one customer vehicle aboard as loaded for this measure. Don’t multiply truck miles by the number of cars carried. Keep any unclassified miles visible until dispatch resolves them.
Illustrative example: 40,000 total miles and 8,000 empty miles produce 20% deadhead. With $112,000 in delivered-load revenue, the monthly revenue-per-total-mile figure is $2.80. Those figures describe this sample only; they aren’t performance targets. Check unfinished trips before interpreting the revenue ratio.
Define on-time delivery against the agreed delivery window recorded before the move. Preserve the original window and the history of accepted changes. Divide on-time deliveries by deliveries with usable appointment and arrival records. Report that denominator and the missing-record count beside the percentage.
Break out exceptions by lane and cause: missing gate release, receiver delay, equipment trouble, driver availability, or dispatch planning. Compare similar equipment and work before comparing drivers. Don’t use raw revenue to rank a wedge doing regional runs against a larger carrier running a different mix.
Keep customer waiting time and approved detention revenue separate. In the detail tab, connect each delay to its load, location, duration, supporting record, and follow-up owner. That gives you something specific to discuss at the next booking.
3. Separate customer receivables from driver settlements
Track what’s unbilled, unpaid, and overdue
Build an invoice-level receivables tab with customer, invoice ID, related loads, invoice date, due date, original amount, payments applied, approved credits, and remaining balance. Add dispute status, last contact, promised payment date, and next action. Don’t treat an expected payment as money received.
For this template, age unpaid invoices by days past their recorded due date. Use current/not due, 1–30, 31–60, 61–90, and over 90 days past due. Mark missing due dates for review. Don’t mix invoice-age buckets with past-due buckets under the same heading.
Keep delivered-but-unbilled work outside invoiced receivables. Show its count, value, and oldest delivery date separately. Record the blocker, whether it’s a missing POD, an unresolved charge, or incomplete customer details. Assign somebody to clear it.
Use a balance check: opening invoiced receivables plus new invoices and debit adjustments, minus applied payments, credits, and write-offs, equals closing invoiced receivables. List unexplained differences rather than forcing a match. Have billing confirm the treatment of factoring, fees, and other settlement arrangements before using this check.
Illustrative example: $70,000 opening receivables plus $110,000 in invoices, less $100,000 in applied payments and $2,000 in credits, leaves $78,000. Another $8,000 of delivered-but-unbilled work stays on its own line. It isn’t part of that $78,000 invoice balance.
Show earnings and payment status separately
For each driver, show gross earnings assigned to the month under the documented pay arrangement. Separately show reimbursements, itemized adjustments, net settlement amount, payments issued, and unpaid approved balances. Keep pending disputes visible without quietly changing the underlying earnings.
Link each earnings line to the load or other pay basis. For shared loads, record each driver’s assigned portion and check the combined allocation. Compare settlement calculations with your documented terms using the car-hauler driver pay guide.
Use separate summaries for employee pay, contractor settlements, and equipment-owner settlements where applicable. Don’t combine their totals into a driver performance ranking. Show customer collection status beside a disputed load for context, but keep customer balances and driver balances in separate report fields.
4. Add equipment measures and fill the owner’s scorecard
Track trucks and trailers separately, then connect them through dated assignments. Put each repair on the unit that received the work. Keep unmatched expenses in an exception total instead of spreading them across the fleet without a documented allocation rule.
Choose scheduled service hours as your availability denominator and document the schedule before the month starts. Calculate equipment availability as scheduled hours minus equipment-unavailable hours, divided by scheduled hours, multiplied by 100. Count only downtime that overlaps those scheduled hours.
Keep ready-but-unassigned equipment separate from equipment downtime. Record driver-unavailable time separately too. For a truck-and-trailer combination, count overlapping downtime once when calculating lost combination hours. Retain each unit’s individual event for maintenance review.
For equipment costs, list fuel purchases, repairs, tires, and other selected categories separately. State the date basis and exclusions beside each total. If you calculate a cost-per-mile measure, use the matching unit’s miles and label exactly which costs are included. Don’t call a selected-cost subtotal profit or total ownership cost.
Copy this fleet management report template
Use the following as the summary tab. Enter current and prior results, then record the difference and explanation. For percentage measures, express the change in percentage points. Add an internal target only when you’ve agreed on its basis; don’t borrow an unexplained industry benchmark.
| Measure | Reporting basis | This month | Prior month | Variance / explanation |
|---|---|---|---|---|
| Completed orders / delivered vehicles | Actual delivery; count orders and vehicles separately | [counts] | [counts] | [change and cause] |
| Delivered-load revenue | Assigned carrier charges for completed deliveries | [$] | [$] | [volume, rate, or timing] |
| Total / empty / unclassified miles | Distance traveled within the month | [miles] | [miles] | [lane or data issue] |
| Deadhead | Empty miles ÷ total miles × 100 | [%] | [%] | [percentage-point change] |
| Revenue per total mile | Delivered-load revenue ÷ monthly total miles | [$/mile] | [$/mile] | [include unfinished-trip caveat] |
| On-time delivery | On-time ÷ documented deliveries; show coverage | [% and counts] | [% and counts] | [cause / missing records] |
| Delivered but unbilled | Month-end value, count, and oldest delivery | [$ / count / date] | [$ / count / date] | [blocker] |
| Closing invoiced receivables | Invoice balances remaining at month-end | [$] | [$] | [balance-check exceptions] |
| Past-due receivables | Total overdue plus each past-due bucket | [$ by bucket] | [$ by bucket] | [customer / dispute] |
| Driver gross earnings | Monthly work basis under documented terms | [$] | [$] | [work mix / adjustment] |
| Approved settlements unpaid | Approved unpaid balances at month-end | [$ and count] | [$ and count] | [reason / next action] |
| Equipment availability | Available scheduled hours ÷ scheduled hours | [% and hours] | [% and hours] | [unit / event] |
| Ready but unassigned | Scheduled hours available without assigned work | [hours] | [hours] | [dispatch explanation] |
| Equipment costs | Separate selected categories and unassigned costs | [$ by category] | [$ by category] | [unit / cost driver] |
| Unresolved data exceptions | Missing IDs, dates, miles, or supporting records | [count / value] | [count / value] | [owner / due date] |
Build supporting tabs for dispatch, receivables, settlements, and equipment. Keep the summary readable without hiding the detail. Every disputed number should lead back to a load, invoice, settlement line, mileage record, or work order.
For fleet percentages, add the underlying numerators and denominators before calculating the fleet result. Don’t take a simple average of truck percentages when the trucks have different mileage or scheduled hours. Show N/A when the denominator is zero, and explain why.
5. Review exceptions and assign next month’s work
Open the owner review with unresolved actions from last month. Then discuss the largest changes in dispatch, unpaid balances, equipment, and settlements. Read the explanation beside each number before deciding whether it calls for a change.
For every selected issue, write an action-log entry containing the measure, evidence, proposed cause, action, responsible person, due date, and closure evidence. Keep suspected causes labeled as suspected until somebody checks them.
For example, an illustrative deadhead increase from 18% to 23% is a five-percentage-point change. Ask dispatch to review empty legs by lane and equipment type. Don’t jump straight to blaming a driver or demanding more loads. Decide what route-planning change to test after reviewing the trips.
For an unbilled-load issue, closure evidence might be a completed billing packet and submission record. For a settlement mismatch, it might be the corrected calculation and documented follow-up. Make the action specific enough that next month’s reviewer can tell whether it happened.
Once the report definitions are stable, review how fleet data reaches the source records. TruckTA’s Imports & Integrations page describes reviewed CSV imports, supported connections, and AI-assisted Smart Load Import for supported documents. These are data-entry workflows; use this article’s scorecard as your own reporting layout, not a promised built-in monthly report. (truckta.com)
See TruckTA integrations with a sample of your current source files in hand. Check the supported workflow, field mapping, review steps, and duplicate handling before changing your process. Keep a person responsible for checking the imported records against the source.
Save the completed packet with its source snapshot and action log. Next month, reuse the definitions, explain any changes, and start by checking whether the assigned work was finished.
Editorial references
Sources checked
Requirements can change and may depend on jurisdiction, vehicle, weight, operation, and driver status. Confirm current applicability with the responsible agency or a qualified adviser.
- SubSectionscsa.fmcsa.dot.gov · checked November 11, 2026
- Trainings FMC CSA 13 005 VM Inspect Repair SMCcsa.fmcsa.dot.gov · checked November 11, 2026
- Supporting documentsfmcsa.dot.gov · checked November 11, 2026
- How should i record my business transactionsirs.gov · checked November 11, 2026
- P538irs.gov · checked November 11, 2026
- What kind of records should i keepirs.gov · checked November 11, 2026
Put it into practice
Keep your operation moving with TruckTA.
Bring loads, drivers, documents, payments, and settlements into one connected workspace.