Magellan
Weekly operations meeting: resolve the exceptions that need a decision
Run a weekly trucking operations meeting around specific decisions, responsible people and evidence that the agreed work is complete.
Everyone gives an update. Dispatch is busy, recruiting needs drivers, billing is chasing documents and safety is following up. The company owner asks the same questions as last week and takes on several more tasks.
A meeting can produce plenty of discussion while leaving the work unchanged. Check whether each case received a decision, a person responsible for the next action or confirmation that the agreed work is complete. If every department leaves with the same uncertainty it brought in, the meeting has described the work without moving it.
A useful case identifies the issue, its business impact, the latest verified fact, the decision needed and the person who can act. Background belongs in the supporting record. Meeting time belongs to the point where authority, coordination or judgment is required.
This meeting format is an operating recommendation. FMCSA's Safety Management Cycle (https://csa.fmcsa.dot.gov/about/Intervene) offers safety-specific context for investigating the processes behind a recurring problem. A weekly operations review can likewise trace the actual handoff rather than repeat the department's symptom.
Not every open task belongs in the meeting. Routine work with a responsible person and a next step can remain in the normal queue. Bring exceptions that cross departments, require authority, have become overdue or reveal a repeated operating weakness.
Use a consistent threshold appropriate to the business. The threshold should help people escalate significant issues early, not force them to wait until Friday because that is when management meets. Urgent safety, service and legal matters need their own immediate route.
Limit the agenda to what the group can actually resolve. A long list encourages shallow discussion and rushed promises. If a case lacks essential facts, assign the fact-finding step and the person responsible rather than letting the whole room speculate for twenty minutes.
An action needs a concrete result, a responsible person, a due date and evidence of completion. “Improve communication with drivers” is an intention. “Operations will issue the approved contact instructions to the defined driver group and verify the first-shift handoff by Wednesday” describes work that can be checked.
The right level of detail depends on the task. Avoid turning the action list into an instruction manual, but include enough to make the expected result clear to the person doing the work.
Name one person responsible for completion. Others may contribute, but “dispatch and safety” can leave each team expecting the other to finish. If the task actually requires sequential work, record the handoff and who takes responsibility next. Shared involvement is not a substitute for visible responsibility.
A case the meeting can decide
Illustrative case: “Nine delivered loads for Customer A are awaiting one disputed authorization. Billing has preserved the requested charges and supporting records. The commercial manager must decide the contract-based next step by Wednesday; billing will then record the authorized invoicing decision.”
The meeting may assign fact-finding if the contract question is unresolved. Its useful output is the decision or next action with a named person responsible. A smaller open-item count is not a valid target if staff achieve it by closing items that still need work.
Suppose missing delivery documents appear in three consecutive meetings. Each week, management tells billing to follow up. Billing does, and the same problem returns with new loads.
The review should trace where documents are collected, checked and transferred. It may find that drivers upload files successfully but nobody verifies legibility before the load moves to the next status. Repeated billing follow-up treats the symptom after the easiest correction point has passed.
The resulting action might name someone to establish and test a document-quality handoff on a limited sample. The next meeting examines the result and decides whether to adopt the process. It does not merely ask whether billing sent more reminders. This turns a recurring topic into a change the business can evaluate.
Review previous commitments before adding new ones. Ask what was completed, what evidence supports closure and what remains blocked. If a due date moved, record the reason and the new decision rather than quietly replacing the old date.
Distinguish an outside dependency from internal inactivity. “Waiting for customer” should identify the request, the last contact and the next escalation. “Waiting for owner approval” should identify the actual decision the owner needs to make. These descriptions help management remove a barrier instead of simply observing delay.
Topics
- Management
- Action ownership
- Management meetings
- Exception review