How to measure the cost of manual freight work
Measure four things: staff time, response delay, avoidable cost, and constrained capacity. Use two normal weeks of your own work. Do not start with a vendor's savings percentage. Start with how often the task happens and what each occurrence requires.
Why the cost stays hidden
Manual freight work is spread across inboxes, TMS screens, spreadsheets, carrier portals, and short conversations. One follow-up takes only a minute. The same follow-up repeated across active files becomes a job.
WiseTech Global reported that 35% of respondents in its logistics productivity research did not measure productivity or set specific targets. Magaya's 2025 survey found that 49% of surveyed forwarders had digitized half or less of their processes. Both findings point to the same practical problem: many teams feel the burden but cannot show where it sits.
Measure four kinds of burden
Staff time
Count every manual touch, not only the main task. Include opening the email, finding the file, checking the TMS, sending the follow-up, reading the reply, renaming the attachment, entering the update, and correcting mistakes.
Response delay
Measure the time between the work arriving and the useful response. For quotes, this is RFQ receipt to ready-for-approval draft. For milestones, it is carrier reply to updated TMS record. Waiting time matters even when nobody is actively working on the task.
Avoidable cost
Record charges, overpayments, credits, rework, and customer concessions that a better process might have prevented or found sooner. Keep the evidence. A cost estimate without the shipment, invoice, or event behind it is not proof.
Capacity
Track work that the team delays, declines, or leaves incomplete because routine tasks consume the day. This can include unanswered RFQs, late customer updates, partial invoice checks, and files that need overtime during a volume spike.
A two-week baseline
- Name the start and finish. "Quote handling" is too broad. "RFQ email received to quote ready for approval" can be measured.
- Choose normal weeks. Avoid a holiday or unusual disruption unless that event is part of the problem you need to solve.
- Count volume and touches. Record how many items entered, how many were completed, and how many manual actions each item required.
- Time a representative sample. Measure the work across different customers, modes, and exception types.
- Record failures separately. Missing data, portal outages, conflicting rates, and human mistakes need their own counts.
Extend the baseline if the workflow is seasonal or contains rare but expensive exceptions.
Scorecards for four freight workflows
| Workflow | Time and speed | Cost and capacity |
|---|---|---|
| Milestone chasing | Touches per shipment, staff minutes, reply-to-TMS latency | Overtime, overdue updates, active files per coordinator |
| Exception monitoring | Staff hours watched, lead time before expiry | Charges prevented, charges disputed, urgent recoveries |
| Quote drafting | RFQ-to-draft time, manual touches | Completion rate, unanswered RFQs, quotes per desk |
| Invoice audit | Minutes per invoice, time to dispute | Audit coverage, dollars flagged, duplicate or incorrect lines |
Turn the baseline into a business case
Use a simple monthly model:
Monthly workflow burden = staff hours x loaded hourly cost + documented avoidable cost.
Then report response time and capacity beside the dollar figure. Do not force every operational problem into a financial estimate. A faster quote response or earlier exception alert may be valuable even before you can tie it to recovered revenue.
Count headcount savings only when a real staffing decision changes. "Hours returned" is accurate. "Employees replaced" is not, unless that has actually happened.
Regulatory deadlines can change the value
Some workflows carry time limits. The Federal Maritime Commission's detention and demurrage billing rule requires invoices to be issued within defined periods and gives billed parties at least 30 calendar days to request mitigation, a refund, or a waiver. A slow review process can consume part of that window.
This does not mean every forwarder should automate invoice audit first. It means deadlines belong in the workflow scorecard when they affect the cost of delay.
Choose the first build
Rank workflows by burden, repetition, rule clarity, error cost, and how safely a person can review the result. The best first workflow is not always the largest cost. It is the one that returns useful time and can be proven without taking an irresponsible risk.
Define the post-launch report before the build starts. Use the same measures from the baseline. If the work has moved to another dashboard or a new checking task, the result should show that too.
Frequently asked questions
Measure monthly staff time, response delay, preventable charges or errors, and constrained capacity. Use your own loaded labor cost and operating records instead of a generic industry savings percentage.
Two normal working weeks usually capture enough variation for a first decision. Extend the baseline when volume is seasonal or the workflow has rare but costly exceptions.
Frequent workflows with a clear start and finish are easiest to measure. Milestone chasing, quote drafting, document collection, and invoice reconciliation are common examples.
No. Count headcount savings only when a real staffing decision changes. A safer case values hours returned, delays reduced, costs caught, and additional work the team can handle.
Sources
Measure one live workflow
Bring the process that keeps stealing time. We will map the burden, decide whether it fits automation, and outline what the first build should prove.