Supply Chain Spreadsheet Risks usually reside in a single file. Somewhere in your operation, there is a workbook. It has a name you probably do not say in public: shipping_programme_MASTER_v7_final_final.xlsx, or something like that. It lives on a shared drive, or in the logistics manager’s personal OneDrive, or in an email chain that the last five versions have been forwarded through. It is open on somebody’s screen almost every hour of the working week.
That workbook is running hundreds of millions of dollars of cargo a year.
It holds the fixture list. It holds the nomination plan. It holds the blend ratios. It holds the rail consist forecast. It holds the berth sequence. It holds the demurrage log. It holds the customer contact list. It holds the account manager’s notes. It holds, in small tabs in the back that nobody but the author remembers exist, the calculations that determine which product goes to which customer on which vessel, the most important commercial and operational decisions in the business.
And it is a spreadsheet. Maintained by one person, mostly. Backed up in the informal sense that copies of it exist in various inboxes. Tested in the sense that it has not obviously failed yet. The Supply Chain Spreadsheet Risks built into that arrangement are the subject of this post.
This post is not a dunk on spreadsheets. Excel earned its place in your operation. It was free, flexible, faster than anything IT would have built, and the person who created it understood the business. The problem is not that it exists. The problem is that it has scaled to a role it was never designed for, a role in which its structural limitations are no longer a nuisance but a material risk to the business. This post walks through seven specific Supply Chain Spreadsheet Risks hiding within that workbook, explains why each of them remains invisible until it matters, and offers a respectful, staged path to reducing the risk without destroying the institutional knowledge the workbook represents.
Version drift is the first of the Supply Chain Spreadsheet Risks because it is the most basic. It is the risk that the version of the truth you are looking at is not the version someone else is looking at. In workbook-run operations, it is the most common source of small errors that compound into expensive ones.
The shape of version drift is familiar. Somebody emails a copy of the master workbook on Friday afternoon for the commercial team to review over the weekend. The logistics coordinator updates the master on Saturday with a weekend berth swap. The commercial team, looking at the Friday copy on Monday, raises a concern about the berth sequence. An hour of email ensues before anyone realises the two teams are looking at two different versions of the same document.
In a workbook-run operation, there is no mechanism that prevents this. Every email attachment is a branch. Every OneDrive sync is a potential conflict. The master is whichever copy the logistics manager designates as the master, and that designation is a social agreement rather than a technical fact. Most of the time it works. Occasionally, it fails, and when it does, the failure results in a small loss, a demurrage event, a wrong nomination, or a customer update referencing yesterday’s ETA.
Individually, the version drift losses are modest. In aggregate, across a year of a busy programme, they are not. One operation I sat down with found, after some honest bookkeeping, that roughly one in twelve demurrage events they had experienced in the preceding twelve months could be traced to a version-drift root cause: someone acted on information from an out-of-date copy of the workbook.
The structural fix is a system of record, a single, authoritative view that does not get emailed. The workbook becomes a working copy at best; the source of truth lives somewhere that cannot drift.
The second of the Supply Chain Spreadsheet Risks lives in the formulas themselves. The workbook is full of them. Some are visible; most are not. The logistics manager who built the blend calculation three years ago knew what every cell did. The logistics manager who inherited it a year ago mostly knows. The coordinator who joined last month knows about 40 per cent of it and has learned not to touch the rest.
Opaque formulas are the risk that the business is making decisions based on calculations that nobody currently in the room can explain. The calculations were correct when they were written. They may still be correct. They may also not be correct, because the contract structure they referenced has changed, or the commodity quality profile has evolved, or a rounding convention that once did not matter now matters at a different scale.
Spotting an opaque-formula risk is hard precisely because the formula is producing an answer. If the answer looks plausible, the team will trust it. The symptom is not a wrong numbers error; it is numbers that have been slightly wrong for longer than anybody realises. A two-per-cent systematic bias in a blend calculation, applied to hundreds of shipments, accumulates into a real margin leak without ever producing a visible alarm.
The fix is not to rebuild the formulas in a different system. The fix is to move the calculations out of the workbook and into a system that provides each calculation with documentation, ownership, a test case, and a change log. The math is probably right. The durability of the math, as the operation moves through people and time, is what is at risk.
This is the Supply Chain Spreadsheet Risk that most workbook-run operations understand instinctively but avoid naming. The workbook is maintained, fundamentally, by one person. Sometimes two. When that person is in the office, the workbook is a productive tool. When that person is on leave, the workbook becomes fragile. When that person resigns, the workbook becomes a hostage; the operation cannot run at its usual pace until a successor has absorbed the tacit knowledge behind the explicit formulas.
The common response is to create documentation. It rarely works. Documentation of a living workbook is never complete, never current, and never a substitute for the pattern recognition of the person who runs it. Even well-intentioned documentation efforts tend to capture the what, what the cells do, and miss the why, which of the many possible calculations the business chose, and under which circumstances the choice should be revisited.
The fix is structural, not documentary. The institutional knowledge needs to live in a system, not a workbook. The system captures not only the calculation but also the ownership, the last updated date, the circumstances under which the calculation should be reviewed, and the change log of how it reached its current state. The operator’s expertise is then amplified by the system rather than replaced by it.
Audit exposure is one of the fastest-growing Supply Chain Spreadsheet Risks because customer expectations are outpacing most workbook-run operations. When a customer’s procurement team conducts a supplier audit, they increasingly ask about the systems that support quality, safety, and delivery, not only the policies. For many buyers, particularly Japanese and Korean steel and utility customers, the audit is not a pass-fail; it is a ranking exercise that feeds directly into the allocation of preferred suppliers for the following cycle.
A workbook-run operation presents poorly in this audit. The audit team asks how do you know which cargo was loaded against which contract, with which quality parameters, through which chain of custody, and the honest answer is that we have a workbook, and the logistics manager would be able to reconstruct it for any specific shipment you name, but we cannot show you the chain as a system. The audit team records that. The conversation about next year’s allocation reflects it.
This is not a hypothetical future risk. It is already driving allocation decisions in several commodity categories and is moving into the rest. Operations that cannot produce a system-backed chain of custody are already losing volume to operations that can, even when their underlying product quality is identical. The workbook is not the sole cause of that exposure, but it is usually the most visible indicator of it.
The fix is not to build a separate audit system. The fix is to ensure that the system of record for the operation is also the system of evidence, that the quality data, the chain of custody, and the decision log are artefacts of the same platform rather than a separate exercise in audit preparation.
A workbook does not remember what it looked like yesterday. When somebody changes a cell, the old value is gone. This is fine for a working document. It is not fine for an operational system of record, and it is one of the Supply Chain Spreadsheet Risks that compounds most quietly.
The consequence is that the team loses the ability to detect a class of errors that only show up over time. A formula edited three months ago by someone who no longer works on the team produced a small, systematic shift in the blend calculation, and that shift has been invisibly baked into every cargo since. A change to the contract reference for a customer was made in haste and never reviewed. A manually entered ETA contained a typo, and the dependent nomination was built around the wrong date.
Change-blindness is insidious because it does not produce obvious alarms. It produces a slow accumulation of small drifts, any one of which might cause the next off-spec event or demurrage dispute, and none of which can be traced after the fact because the workbook does not remember its state when the change occurred.
The fix is a system that records state changes with timestamps, authors, and the previous value. This is not exotic technology; it is how every modern operational system works. It is the single feature workbooks do not have that would, on its own, eliminate an entire class of recurring incidents.
There is a volume at which a workbook-run operation stops scaling, and the symptoms are predictable. The workbook now takes 15 seconds to open. Filtering a table freezes the laptop for a minute. A coordinator working on the file accidentally overwrites a cell, and the resulting error ripples through three tabs before somebody spots it. As the logistics team grows, the second and third people on the team cannot work in the workbook simultaneously, so they work in their own copies and merge changes by hand. This is when the Supply Chain Spreadsheet Risks stop being theoretical and start showing up as daily friction for the team.
This ceiling tends to hit operations at a specific moment, often when a mine expansion goes live, a second product line is added, or a merger brings a new trade flow into the programme. The scale of the operation has grown, but the tool’s scale has not. The team is doing their normal job badly for a few months, while nobody is quite sure why everything feels harder.
The structural fix is not a bigger workbook. It is a tool built for the scale the operation has moved to. The discomfort of the scalability ceiling often drives operations to finally make the platform decision, but the cost in disruption and missed margin during the months of discomfort can be significant. Operations that anticipate the ceiling and move before they hit it tend to avoid that cost.
The last of the Supply Chain Spreadsheet Risks is the one with the broadest blast radius. A workbook does not integrate with anything else. It can export and import files, but it cannot participate in real-time data flows with the rail operator’s system, the port scheduler’s system, the customer’s EDI, or the mine’s dispatch platform. Every integration between the workbook and the rest of the operation is a human, usually the logistics coordinator, copying data from one system into another.
This has two consequences. First, the workbook is always slightly behind reality, because the human integration layer does not operate in real time. Second, every new counterparty or system the operation adds increases the copy-paste burden linearly. The operation scales by adding coordinator hours rather than by adding system capacity.
The cost shows up in three places. On the coordinator’s job satisfaction, the work is repetitive and error-prone. On the timeliness of decisions, the workbook lags the physical operation by hours or days. And on the commercial agility of the operation, new trade flows, new customers, new stakeholders take longer to onboard than they should, because every one of them requires a new column, a new tab, a new copy-paste habit.
The fix is a system built to integrate. Not every integration needs to happen on day one; the system just needs to be built so that integrations can be added without rebuilding anything. This is the difference between a workbook and a platform, the workbook does one thing well, and the platform is designed to do more things as the operation grows.
It is important to clearly say that the workbook is not stupid and that the people who built it are not wrong. The workbook is, in most operations, a genuinely impressive feat of domain expertise. It encodes decades of operational intuition into a tool that a small team has used to run a substantial business. The first thing a thoughtful conversation about Supply Chain Spreadsheet Risks does is acknowledge that.
The problem is not that Excel is the wrong tool. The problem is that it was the right tool for the operation at an earlier scale, but the operation has outgrown it. The same logic that tells you not to keep a five-year-old laptop as your primary machine, it was a great laptop once, and now the workload has moved on, applies to the master workbook. Respecting its history and moving past it are not in conflict.
The worst way to make this transition is to treat the workbook as an enemy. The team that built it will reasonably feel defensive. The operational continuity that depends on it is real. The right posture is an honest engineering conversation. Here is what this tool does well, what it cannot do at our current scale, and how we carry forward the parts that matter into something more durable.
The best platform conversations I have seen begin with the logistics manager who built the workbook as the lead designer of its successor. That person knows the operation better than any consultant ever will. The platform conversation is about amplifying their expertise, not replacing it.
The pattern that works for retiring Supply Chain Spreadsheet Risks is a staged one. The workbook does not disappear on day one. The platform earns its place before the workbook is retired.
The first stage is to identify the two or three highest-risk functions in the workbook and replicate them in a system that structurally addresses the risks. Usually, this is the fixture list and nomination plan, because those are the most version-drift-prone. The system runs in parallel with the workbook for a period. The logistics team uses both. The system is the system of record; the workbook is a working copy that the manager keeps open for their own convenience.
The second stage is to migrate the blend calculations and the quality chain into the system. These are the highest-value calculations and also the most opaque. Moving them exposes the logic, which is often the point; the calculations become reviewable for the first time in years, and the team finds a couple of small issues that have been quietly there the whole time. The fixes pay back the migration cost.
The third stage is to connect the external systems, the rail operator, the port scheduler, and the customer EDI directly to the platform. The coordinator’s copy-paste load drops. The timeliness of decisions improves. The integration, once built for one counterparty, is easier to replicate for the next.
The fourth stage is cultural. The weekly shipping review starts running from the platform rather than the workbook. The workbook is archived. The platform becomes the default place people go to find out the state of the programme. At this point, the platform has earned its place, and the transition is complete.
Across these four stages, typically six to twelve months of elapsed time, the operation has moved from a workbook-run model to a platform-run model without any week in which the programme stopped working. The institutional knowledge is preserved because the person who owned it led the migration. The team’s day-to-day work feels mostly the same, which is the point; good platform transitions are boring on the surface.
The workbook has never actually failed us. This is the most interesting objection because the person saying it is almost certainly right. The workbook has produced occasional bad days but not a catastrophic failure. The Supply Chain Spreadsheet Risks are probabilistic, not guaranteed. The question is not whether the workbook has failed; it is what happens when it does, and how much of that failure mode the business is currently exposed to. The business case for change is rarely this will definitely break: it is when it breaks, the cost will be higher than the cost of preventing it.
A platform is more expensive than the workbook. Yes, a platform has a cost; the workbook does not. The apples-to-apples comparison is not platform cost versus workbook cost; it is platform cost versus the annualised cost of the seven risks. The second number is hard to calculate, which is why the comparison usually gets abandoned. The 90-minute audit at the bottom of this post is a tractable way to estimate it.
We do not have the capacity to do this migration. Often true in the short term. The best response is usually a phased approach that uses the platform vendor’s implementation team to do the heavy lifting, with the internal team reviewing and guiding rather than building. A good vendor engagement is designed around this. A bad vendor engagement asks the customer to build most of the integration themselves, which is where most workbook-to-platform transitions fail.
Specifics make the Supply Chain Spreadsheet Risks concrete. Three quick stories, names changed, mechanics real.
A mid-tier iron ore producer lost a two-year offtake extension with a Japanese trading house in late 2023. The technical pretext was a series of minor on-time delivery misses in the final quarter of the contract; the underlying cause, as the procurement team eventually explained in a candid conversation, was that the supplier could not produce a coherent chain-of-custody narrative at the annual audit. The workbook-based documentation was judged insufficient against a newly formalised ESG sourcing policy. The allocation moved to a competitor whose quality data was equivalent on paper but whose operational evidence was platform-backed. The commercial impact was in the eight-figure range over the life of the contract. Nothing about the physical product had changed.
A metallurgical coal exporter discovered during an internal audit that a demurrage calculation in the master workbook had been systematically understating laytime allowance by 0.3 days per Capesize for about eighteen months. The formula was correct in itself; it had been written against an older charter party template and had not been updated when the standard template changed in a minor revision. The understatement had resulted in a cumulative six-figure overpayment to the counterparty, which was then contested and partially recovered. The audit was triggered by an unrelated matter; without it, the leak would have continued indefinitely.
A base metals miner went through a ten-week period during which the logistics manager was on medical leave, the deputy had left for another role three months earlier and had not been fully replaced, and the workbook became effectively unmaintainable. The business continued to ship, but with elevated quality claim rates, several missed nominations, and a board-level conversation about organisational resilience that nobody in the company had expected to have that quarter. The workbook survived the period; the operation’s reputation took longer to recover.
None of these is a horror story. None of them involved catastrophic failure, fraud, or incompetence. They are the predictable, survivable, quietly expensive consequences of running serious operational processes on tools not designed for them. The cumulative effect across an industry of operations carrying these Supply Chain Spreadsheet Risks is substantial and largely invisible in aggregated numbers, because each individual incident appears to be bad luck rather than structural exposure.
The question of what should replace the workbook is the one workbook owners most want answered, and the one most platform vendors answer badly. The answer is not a bigger spreadsheet. It is a system designed around the realities the workbook was quietly papering over: a single source of truth, reviewable, ownable calculations, automatic change history, first-class integrations, and audit evidence as a by-product rather than a project. A good successor closes each of the seven Supply Chain Spreadsheet Risks structurally, and does so without asking the team that built the workbook to feel like the work they did never mattered. It mattered. It got the operation here. The next chapter is about getting it to the scale it has already grown into.
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.