The weekly shipping review is the most consistently disappointing meeting in a bulk commodity operation. Not because the people are wrong, not because the agenda is wrong, and not because the intent is wrong. The intent is exactly right: get the commercial, operational, quality, and finance functions into one room, look at the programme together, make the decisions that need to be made, and move forward with shared understanding.
The reality, week after week, quarter after quarter, is something smaller. The meeting runs for sixty minutes and delivers maybe twenty minutes of actual decision-making. The first half is absorbed by a process everyone recognises, but nobody addresses: the reconstruction of shared reality from the competing spreadsheets each function has brought to the room. By the time the group agrees on what the numbers actually are, there is barely time left for the decisions those numbers were supposed to inform. The important items get deferred to next week, when the numbers will have diverged again.
This post is about reclaiming that meeting. Not by shrinking it, the meeting itself is valuable, but by redesigning it around the work that actually needs to happen. The premise is simple: when the data is shared and authoritative, the meeting becomes a decision-making forum rather than a reconciliation forum. The time you currently spend on reconciliation is time you recover for decisions. And the decisions, done properly, make the rest of the week dramatically more productive.
What follows is the anatomy of the failure, the structural fix, and a concrete twenty-five-minute agenda template that replaces the sixty-minute ritual.
Sit in a typical weekly shipping review and observe what actually happens in the first half hour. The pattern is remarkably consistent across operations.
The meeting opens with a request for an update on the programme’s current state. Usually, a senior operational leader kicks off: “Where are we on the week?” What follows is not an answer. It is a negotiation.
The commercial team produces a view of expected shipments based on their workbook, which was updated late Friday after a customer call. The operations planner produces a view of the plan that reflects confirmed rail movements and vessel nominations but has not yet incorporated the commercial update. The quality manager has a view based on what the mine is producing and what the stockpiles can supply, which differs from both. The finance representative, trying to reconcile the rolling forecast, has a fourth view.
The first 15 minutes are spent identifying which views differ from one another. The next fifteen are spent resolving, or deferring, the differences. Nobody is arguing in bad faith; each view is a legitimate reading of the function’s own data. But until the group reaches a common picture, no decisions can be made, and the clock keeps running.
By minute thirty, the group has usually converged on an approximate shared view. At this point, the real meeting begins, the decisions about what to prioritise this week, how to handle specific issues, and what to escalate. But now there are 30 minutes left; the group is mentally drained from the reconciliation, and several items are rushed or pushed to next week.
This is not a failure of meeting discipline. The failure is in the data foundation that the meeting sits on. A well-chaired meeting with fragmented data still produces reconciliation-heavy meetings because reconciliation must occur before decisions are possible. The chair cannot discipline its way out of the structural problem.
Before redesigning the meeting, we should be specific about what the weekly shipping review is intended to accomplish in a bulk-commodity operation.
It is not for status updates. Status updates are a one-way communication that can occur asynchronously: in a shared dashboard, in an automated report, or in a daily stand-up. Each function runs independently. Using synchronous meeting time for status is an expensive waste.
This is not for catching up on last week’s items. Post-mortem conversations deserve their own space and are better served by a structured review process than by consuming time in the forward-looking meeting.
It is not for reconciliation. Reconciliation is a symptom that the underlying data is fragmented. Fixing the data layer is the right response, not repeatedly performing reconciliation in meetings.
The meeting is for three specific things:
Each of these three categories produces genuine value when done well. Each of them is systematically compromised when the meeting is also expected to produce reconciliation.
The redesigned meeting rests on a simple premise. The shared data view, the programme state, the KPI dashboard, and the exception list are produced in advance and are authoritative. All participants review the same data before the meeting starts. The meeting does not produce the data; it is the forum where decisions are made based on the data.
This is not an optional enhancement. It is the structural change that makes the rest possible. If the data is not shared and authoritative before the meeting, reconciliation remains the dominant use of meeting time, regardless of how well-structured the agenda is.
Producing shared data in advance requires the underlying systems to support it. This is the data architecture discussion: one authoritative record per domain, derived views for each function, automated propagation of changes. For a full treatment of how this is done in a bulk commodity operation, see our piece on one version of the truth. Without the data foundation, the meeting redesign described below will not hold.
Assuming the data foundation is in place, either because you have implemented it or because you are willing to invest to get there, the meeting redesign becomes straightforward.
Here is a concrete template for a redesigned weekly shipping review. Twenty-five minutes, four segments, no reconciliation. Please print it, bring it to next Monday’s meeting, and follow it.
The chair opens the meeting with a brief acknowledgement of the shared data view (which everyone has reviewed in advance, this is non-negotiable) and a scan of the agenda. Any urgent items that have arisen since the agenda was circulated will be added. Anything that does not require synchronous discussion gets moved to asynchronous follow-up. The group confirms the agenda.
Three minutes is plenty for this segment because there is no reconciliation to do. The shared data is the shared data. If you have a concern about the data’s accuracy, please address it after the meeting; we should not use shared time to raise it.
The chair walks through the active exception list: shipments at risk, commitments under threat, and issues that have escalated since the last meeting. For each exception, the group confirms whether it is still active. What is the current status? What is the next action and who owns it? By when?
The discipline here is brutal. Exceptions are discussed only to the extent necessary to agree on next steps. Detailed problem-solving happens after the meeting with the relevant subset of the group. The meeting is not the place to solve the problem; it is the place to assign clear ownership and a timeline.
Seven minutes is tight but achievable for a typical exception list of five to ten items, provided the group respects the discipline.
This is the strategic heart of the meeting. The chair walks through the next two to four weeks of the programme using the shared risk view, and the group addresses the specific decisions to be made.
Decisions might include: which customer gets priority if we cannot meet two overlapping windows; whether to accept a new commercial commitment given operational constraints; how to handle a surfaced quality concern before it impacts operations; what to do about a forecast weather event; and whether to escalate a customer issue to leadership.
Each decision is framed by the chair with specific options; the group discusses and makes a decision, or, if more information is needed, an owner is assigned to gather it by a specific deadline. No decision is left ambiguous; no action is left unassigned.
Ten minutes is enough for three to five substantive decisions when the group is disciplined. If more decisions are needed, the agenda was too large and should have been trimmed during the initial review.
The chair summarises: the decisions made, the actions assigned, the owners and deadlines. Any items that require escalation to senior leadership are explicitly flagged, and the owner responsible for the escalation is named. The group confirms understanding. The meeting ends on time.
Five minutes for closure feels long, but it is essential. The value of the meeting is captured in the decisions and actions, and the close is where those get crystallised in a form everyone leaves with. Shortcutting the close is the most common way value leaks out of an otherwise well-run meeting.
The twenty-five-minute meeting works only if participants arrive having completed the preparatory work. This requires a cultural shift that some organisations find harder than others.
These demands are more rigorous than most organisations currently impose on their weekly reviews. The payoff is a meeting that actually produces decisions, respects everyone’s time, and compounds value week after week.
If the old meeting was 60 minutes and the new one is 25, each participant recovers 35 minutes per week. For a meeting with ten attendees, that is almost six hours per week reclaimed. Over a year, that is 300 hours, almost two months of one full-time person’s time.
The time should not be idle. Please redirect the time to the work that the weekly review previously crowded out, such as:
The reclaimed time is not a gift to be absorbed by random work. It is a strategic resource, and how the organisation uses it determines whether the meeting redesign produces durable value.
Organisations that attempt this redesign run into predictable failure modes. Calling them out in advance makes them easier to avoid.
The shared data view is not actually shared. The meeting is set up to share data, but in Practise half the group is still looking at their own spreadsheets. The reconciliation creeps back into the meeting, disguised as clarification. Within a quarter, the meeting is sixty minutes again.
The fix is to be ruthless about the shared data view. If a participant is looking at their own spreadsheet during the meeting, that is a problem to be named. The shared view is the view.
Exception triage becomes exception solving. The chair lets the group drift into detailed problem-solving on an exception, because the problem feels urgent. Seven minutes become twenty. The rest of the agenda gets compressed or skipped.
The fix is to enforce the distinction between triage and solving. Triage is “who owns this and by when?” We will have a separate conversation with the relevant subset after the meeting. The chair’s job is to hold the line.
Decisions get deferred repeatedly. A decision comes up, the group needs more information, and an owner is assigned to gather it. Next week, the information is partial, so we will defer the decision again. And again. And again. The decision never gets made; the meeting loses its decision-making function.
The fix is to make deferrals explicit and visible. A decision deferred twice gets escalated to a specific resolution mechanism, often a small decision group outside the meeting. The weekly review is not a place to defer decisions.
Participants drift in and out. Some participants stop attending regularly. Others send substitutes who cannot make decisions. The continuity of the meeting erodes.
The fix is to treat attendance as a commitment, not a preference. Participants who cannot commit to the meeting are not the right participants. The meeting should have the right attendees, and they should prioritise it.
The preparation burden is not distributed. One person, often the operations leader, ends up doing the preparation work that was supposed to be automated by shared data. They become the bottleneck. The meeting’s timeliness depends on them.
The fix is to invest in the data infrastructure so that preparation is automated and to distribute the active preparation work, agenda-setting, exception curation, and decision framing across functions rather than concentrating them in a single role.
Catching these failure modes early keeps the meeting redesign sustainable across years, not just months.
The weekly shipping review does not exist in isolation. It sits within a broader operating rhythm that includes daily operational stand-ups, monthly commercial reviews, quarterly planning sessions, and annual strategic planning. Each layer has its own purpose, and the clarity between them matters.
The daily stand-up handles tactical coordination: what is happening today, what needs to happen tomorrow, who needs help. These are short, operational, and function-specific. They do not need cross-functional decision-making.
The weekly shipping review handles near-term decisions that require cross-functional judgment, such as the redesigned meeting described in this post. Forward-looking by two to four weeks, decision-oriented, structured.
The monthly commercial review addresses pattern-level issues, how the programme is performing against plan, emerging trends, and needed adjustments. Broader scope, more strategic framing, often with senior leadership.
The quarterly planning session covers strategic alignment, the programme shape for the coming quarter, commitments to the market, and the operational adjustments needed. Cross-functional, strategic, decision-focused.
When these layers are clear, and each is run with discipline, the operating rhythm becomes efficient. When they are muddled, weekly meetings that become tactical, monthly reviews that become reconciliation, quarterly sessions that become status updates, the rhythm becomes wasteful, and teams spend their week in meetings without the decision-making density that should emerge from them.
The redesigned weekly shipping review is one element of a broader operating rhythm. Getting it right enables the others to be simpler because each layer stops trying to do what another layer should do.
Focused meetings produce better commercial outcomes. The causal chain is simple.
Better decisions in meetings mean better operational outcomes. Better operational outcomes mean more reliable delivery to customers. More reliable delivery to customers means stronger relationships, better renewals, and higher willingness to pay. A higher willingness to pay means a better margin.
The connection from “meeting quality” to “commercial performance” is not direct but reliable. Operations that run decisive, focused reviews tend to have better delivery metrics. Operations with better delivery metrics tend to have stronger customer relationships. Operations with stronger customer relationships tend to win the renewals that matter.
For a view of how meeting quality ultimately shows up in customer retention, see our piece on why bulk commodity customers really leave. The accumulated disappointment that drives attrition is almost always, at root, a failure of internal decision-making to keep pace with commercial commitments.
If a redesigned weekly shipping review sounds attractive but far away, the starting point is small.
Pick the next weekly shipping review. Please commit to a thirty-five-minute version as a first step, with a structured agenda, a shared data view prepared in advance, and a decision-oriented approach.
Measure the outcome. How many decisions were made? How many actions were assigned? How clear are the next steps? Compare to the old sixty-minute version.
Get feedback from the participants. What worked? What did not? What would they change? The feedback informs the next iteration.
Iterate for a few weeks, gradually shortening toward the twenty-five-minute target, tightening the discipline, and building preparation habits. By the end of a quarter, the meeting should be a structurally different forum than it was at the start.
The full redesign requires the underlying data foundation described in our piece on one version of the truth. Without that, the meeting will improve but not transform. With it, the meeting becomes one of the most efficient uses of cross-functional time in the business.
The weekly shipping review is a microcosm. The way an organisation runs itself reflects how it makes decisions, uses data, and respects time. Improving the meeting is not just about recovering thirty-five minutes per week; it is about demonstrating that the organisation can run itself with the discipline and clarity that its scale deserves.
The teams that have made this transition describe the change in consistent language. The meetings are shorter and more productive. The rest of the week feels more deliberate. The pattern of firefighting is reducing. Decisions get made on time. Commercial commitments hold up in operational execution. Customers notice the improvement, even without being able to articulate why.
None of this is dramatic. All of it compounds. And the starting point is the next weekly shipping review, the one scheduled for next Monday, where you can decide whether to run it the old way or begin the redesign.
The teams that succeed with this redesign share one trait. They stop treating the weekly shipping review as sacred and start treating it as a tool. Tools can be redesigned. Sacred rituals cannot.
Treat the meeting as a tool. Please redesign it for the purpose it is meant to serve. Measure whether it is serving that purpose. Adjust when it is not. Repeat.
That is how operating discipline compounds. Not in any one change, but in the pattern of continuous thoughtful adjustment to the mechanisms by which the organisation runs itself. The weekly shipping review is a good place to start.
Nick Ogle has over 30 years of experience in Enterprise IT, spanning engineering, sales, and marketing roles across Australia, the USA, and APJ for various IT vendors.
Nick is passionate about entrepreneurship and Software innovation that drives positive change. Currently, he is the Sales & Marketing Manager at SCIAR Systems, a Newcastle-based SAAS startup, where he is helping commercialise their groundbreaking Bulk Commodity Logistics solutions.
For more information on Nick and to find articles that have been written on the IT sector in the past, feel free to look at his LinkedIn profile or browse some of the additional articles Nick has written for SCIAR.