How to Build a Decision-Grade Supply Chain Baseline: A Framework for Australian Businesses
The most expensive mistakes in supply chain transformation are made before the transformation itself begins. They are made in the baseline. A weak current state model leads to a flawed business case, which leads to a misaligned future state, which leads to a programme that overruns, underdelivers, and damages the credibility of the leadership team that sponsored it. The technology is rarely the problem. The baseline is.
Yet in our experience advising Australian organisations across retail, FMCG, hospitality, health and aged care, government, and 3PL, the baseline is also the most consistently underweighted piece of any transformation. Programme teams spend months on the future state, the technology, the change plan, and the implementation roadmap. They spend weeks, sometimes days, on the current state. The asymmetry shows up later in every business case argument, every executive decision review, and every variance conversation post go-live.
This guide is the framework for building a decision-grade supply chain baseline: one that survives board scrutiny, supports scenario modelling, and underpins the downstream decisions on network, technology, operating model, and investment. It covers what a baseline actually is, what "decision-grade" means in practice, the components that have to be in the model, the methodology to build it, how to handle the data gaps that exist in every Australian business, and the common pitfalls that turn a baseline exercise into wasted effort.
What is a supply chain baseline?
A supply chain baseline is the structured, defensible, quantified representation of the supply chain as it operates today. It is the answer to the question "what does our supply chain actually cost, how does it actually perform, and what does it actually look like" before anyone starts proposing what it should become.
A baseline is not a slide pack. It is a model. A working representation of the network, costs, service levels, inventory positions, and capability that the business can interrogate, stress-test, and use as the starting point for every transformation decision that follows.
There is a useful distinction between three terms that are often used interchangeably and should not be. A current state assessment is the exercise of investigating and documenting how the supply chain operates today. A baseline is the quantified model that comes out of that assessment. A diagnostic is the analytical interpretation of the baseline against benchmarks, peers, or future requirements. The assessment is the activity. The baseline is the artefact. The diagnostic is the insight.
The baseline is what survives. Years later, when the transformation is complete and the next one is being scoped, the diagnostic insights have aged and the assessment work has been forgotten, but the baseline model (if it was built properly) is still being refreshed and used.
Why decision-grade matters
Most supply chain baselines are not decision-grade. They are good enough to populate a slide deck but not good enough to defend against a sceptical CFO, a challenging board, or a transformation steering committee asking pointed questions about variance.
A decision-grade baseline meets three tests.
The defensibility test. Can the model be defended line by line under scrutiny from a sceptical executive? Can every cost be traced to a source system? Can every allocation be explained by the cost driver behind it? Can every service level be reconciled to operational records? If the answers are not yes, the baseline will fail at the first hard meeting and the transformation will lose credibility before it has started.
The operability test. Can an operator look at the baseline and recognise the business they actually run? A baseline that the operations team rejects as not reflecting reality is dead on arrival, regardless of how analytically elegant the model is. The baseline must be built with operational input, validated with operational stakeholders, and accepted as a fair representation of how the business actually works.
The scenario test. Can the baseline support scenario modelling? Can it be re-run with different assumptions to test future state options? Can it produce comparable cost, service, and capability views under different network configurations, demand patterns, or operating models? A baseline that cannot move is a snapshot, not a tool.
A baseline that passes all three tests becomes a permanent commercial asset. A baseline that passes only one or two is consumable: useful for the immediate purpose, but not durable enough to support the decisions that follow.
The five components of a decision-grade baseline
A baseline that is going to support real transformation decisions has five components. Models that omit any of them tend to produce conclusions that do not survive contact with the board.
Component one: the network baseline. A complete description of the physical supply chain: facilities (DCs, warehouses, cross-docks, manufacturing sites, retail nodes), flows (inbound, inter-site, outbound, returns), volumes (units, lines, cases, pallets, cubic metres), and the geographic structure that connects them. The network baseline is what every future state network design alternative is compared against.
Component two: the cost baseline. The full cost-to-serve picture covering inbound freight, warehousing and handling, outbound transport, last mile, returns, customer service, technology, and the share of overhead that genuinely scales with serving activity. The cost baseline must reconcile to the financial P&L within an acceptable tolerance. A cost baseline that cannot reproduce reported supply chain cost is not a baseline.
Component three: the service baseline. The current service performance picture: DIFOT, order accuracy, dock-to-stock time, dispatch lead time, perfect order rate, returns rate, customer satisfaction, and the service differentiation patterns (or absence of them) across customers, channels, and segments. Service is the constraint that bounds every cost decision. A baseline that ignores it produces commercially indefensible recommendations.
Component four: the inventory baseline. The current inventory position by SKU, location, and stock class. Holding, ageing, obsolescence, slow-moving, dead, in-transit, safety stock, and cycle stock. Inventory is the working capital lever and the service lever simultaneously, and the inventory baseline is what every future state working capital case is built on.
Component five: the capability baseline. The honest assessment of the organisation's current process maturity, system landscape, data discipline, and team capability. Capability is often the missed component. A transformation that the current organisation cannot execute will fail regardless of how good the future state design is. The capability baseline anchors the change programme.
The five components form an interconnected system. Network, cost, service, and inventory views all need to reconcile against each other. The capability view sets the speed limit on what the transformation can achieve.
The methodology: seven steps to a decision-grade baseline
The end-to-end methodology for building a decision-grade baseline breaks into seven steps. Each has its own data, validation, and governance discipline.
Step one: scope the baseline. Define the boundaries of the baseline before any data is gathered. Geography, business units, channels, time period, level of granularity. A baseline scoped too tightly cannot answer the questions the business actually has. A baseline scoped too broadly produces a model too large to maintain and too aggregated to act on. Scope to the decisions the baseline will support, not to the data that happens to be available.
Step two: define the data model. Specify the structure of the baseline upfront: dimensions, hierarchies, time grain, cost categories, service measures, and the link tables that allow the views to combine. A baseline built without a data model on day one ends up with structural inconsistencies that surface late and cost time to fix. Spend the design effort early.
Step three: gather and validate the data. Pull data from the source systems (finance, ERP, WMS, TMS, planning systems, payroll, customer service) and validate every input against the source. Where data is incomplete, mark it. Where data is questionable, flag it. Where data is missing, document the gap and decide whether to estimate, exclude, or commission a focused collection effort. Data integrity at this step is what makes the baseline defensible later.
Step four: model the current state. Build the working baseline model that reproduces actual cost and service performance within an acceptable tolerance. A baseline that cannot reproduce current-state costs to within an acceptable variance cannot be trusted to evaluate future-state scenarios. The tolerance varies by use case, but typical practice is reconciliation within 5 per cent at total level and within 10 per cent at segment level. Where the model cannot reconcile, the data has a problem, the allocation logic has a problem, or the business has an unexplained variance that itself is a finding.
Step five: stress-test the baseline. Walk the baseline through operational stakeholders. Test it against known facts. Test the outliers. Test the segments where the output looks counter-intuitive. Either the model is wrong, the data is wrong, or the business has a real insight it did not previously have. All three are valuable outcomes.
Step six: document everything. A decision-grade baseline is documented to a standard that allows anyone to interrogate any number. Data sources, allocation logic, assumptions, exclusions, and known limitations are all captured. The documentation is what makes the baseline durable and what allows it to survive personnel changes.
Step seven: hand over and maintain. A baseline that is built and then abandoned is half a baseline. The handover plan covers how the model is owned, who maintains it, what the refresh cycle is, and how it integrates with the ongoing planning and reporting rhythm of the business. A working baseline that is refreshed quarterly is worth more than a perfect baseline that is built once and shelved.
The full methodology typically runs eight to fourteen weeks for a mid-market Australian business, depending on scope, data quality, and the level of granularity required. Enterprise-scale or multi-business-unit baselines can run longer. The single biggest variable is the state of the data when the work begins.
How to handle data gaps
Every Australian business has data gaps. The decision-grade approach is not to pretend they do not exist. It is to handle them transparently.
Categorise the gap. Is it missing, incomplete, low-quality, or inconsistent across sources? Each category has a different remediation approach. Missing data may need to be collected. Incomplete data may need to be sampled and extrapolated. Low-quality data may need to be cleaned. Inconsistent data may need to be reconciled at source.
Quantify the materiality. A data gap that affects 0.5 per cent of total cost can be handled with a documented estimate. A data gap that affects 30 per cent of total cost is a project in itself. Materiality determines the level of remediation effort.
Use defensible proxies. Where data is genuinely unavailable, use industry-standard or operationally-validated proxies. Cost per kilometre for line haul. Cost per pallet-day for storage. Cost per line picked for warehouse labour. Document the proxy and its source. A proxy is defensible. A guess is not.
Mark data quality in the model. Every input in the baseline should carry a data quality flag: actual, calculated, estimated, or proxy. The model output should aggregate the data quality view alongside the cost and service view, so users can see which conclusions are most and least defensible.
Resist the urge to build the perfect baseline. Perfect is the enemy of decision-grade. A baseline that is 90 per cent complete with known gaps documented is more useful than a baseline that is still being built six months later. Decision-grade does not mean perfect. It means defensible.
How a baseline gets used downstream
A decision-grade baseline is not the deliverable. It is the foundation for the decisions that follow. Six downstream uses recur across Australian businesses.
Network design. Every network design alternative is evaluated against the baseline. The baseline answers "what does the current network cost and how does it perform". The network design exercise answers "what alternative configurations would deliver better cost-service trade-offs". Without a credible baseline, network design conclusions are unfalsifiable. The baseline feeds directly into our Strategy and Network Design practice work.
Business case development. Every transformation business case quantifies the value at stake against the current state. The baseline is what defines that current state. A weak baseline produces a soft business case that does not survive CFO scrutiny.
Operating model redesign. Future-state operating model decisions are evaluated against current-state operating cost and capability. Without a capability baseline, the change effort required is consistently underestimated.
S&OP and planning transformation. Planning maturity and forecast accuracy improvements are measured against the baseline. The baseline anchors the value case and the performance management cadence.
Cost-to-serve and customer profitability. Cost-to-serve analysis is one of the most valuable applications of the baseline. The cost baseline component feeds directly into CTS modelling and customer or channel profitability decisions.
Automation and technology investment. Automation business cases are built on baseline labour, accuracy, and throughput data. The baseline is what makes the savings case defensible.
A baseline that is built once and then used across all six downstream applications repays its cost many times over. A baseline that is built for one purpose and then redone separately for each subsequent decision is expensive and inconsistent.
Where baselines go wrong
In our experience advising Australian operations and finance leaders, baseline exercises underdeliver for five recurring reasons. All of them are avoidable.
Treating the baseline as a slide pack rather than a model. A 60-page current state report with no underlying working model dies on the day the next executive question is asked. The baseline must be a model the business owns, not a deliverable the consultant takes away.
Skipping the data quality discipline. A baseline that quietly absorbs bad data without flagging it produces conclusions that look authoritative until they are challenged. The defensibility comes from the data discipline, not from the polish of the output.
Building the baseline without operational input. A baseline built entirely in the analytical team without ground-truth from the operators is rejected on arrival. The operators have to recognise their business in the model. If they do not, the baseline is unusable regardless of how methodologically sound it is.
Failing the reconciliation test. A cost baseline that cannot reconcile to the P&L is not a baseline, it is a hypothesis. Reconciliation to financials is mandatory, not optional.
Building it once and never refreshing it. Supply chains move. A baseline that is not refreshed within twelve months has aged past usefulness. The maintenance plan is part of the baseline, not an afterthought.
The common thread is treating the baseline as a project artefact rather than as a permanent commercial asset. The businesses that get the most from their baselines are the ones that build them once, properly, and then keep them alive.
The 2026 context
The Australian environment in 2026 has made baselines more commercially important than at almost any point in the last decade.
Sustained cost pressure across inbound freight, energy, last-mile distribution, and labour means that supply chain cost is a permanent board-level conversation. The Deloitte 2026 Global Retail Industry Outlook reports that 95 per cent of retail executives surveyed expect global trade policies to push costs higher in the year ahead. Tariff volatility, including the 10 per cent baseline US tariff and higher rates on specific categories, has added cost uncertainty across import-exposed Australian businesses.
Channel and operating model change continues. Omnichannel fulfilment, ecommerce growth, and reverse logistics have rewritten the cost structures retailers and FMCG businesses operate against. Health and aged care reform has rewritten the workforce and logistics cost picture for those sectors. Government procurement and program review continues to push for value-for-money transparency that depends on credible cost baselines.
Transformation programmes are being scoped and approved at pace under that pressure. The risk is that they are being scoped against baselines that are weeks-old slide packs rather than living models. The cost of that asymmetry will show up over the next 24 months in transformation overruns, business case re-baselines, and post-investment reviews that struggle to demonstrate the value originally promised.
The baseline is the cheapest insurance in the transformation portfolio.
How Trace Consultants can help
Trace Consultants advises Australian organisations on supply chain current state assessments, baseline modelling, and the downstream decisions baselines support. Our positioning is deliberate: we deliver decision-grade models the business owns, not slide packs the consultant retains. We are vendor-agnostic, partner-led, and senior on every engagement.
Current state assessment and baseline modelling. We scope, build, validate, and hand over decision-grade baseline models that survive executive scrutiny. The deliverable is a working model the business can interrogate, refresh, and use across the downstream decisions that follow.
Network design and strategy. Where the baseline informs network design, our Strategy and Network Design practice translates the baseline into network footprint, DC role, and infrastructure decisions.
Operating model and capability. Where the baseline exposes operating model or capability gaps, our Planning and Operations and Organisational Design practices support the future-state design work.
Transformation programme delivery. Where the baseline anchors a transformation business case and programme, our Project and Change Management practice supports the delivery.
Procurement and supplier baselines. Where the baseline informs procurement or supplier strategy, our Procurement practice translates the baseline into category and sourcing decisions.
Explore our Strategy and Network Design services →
Where to begin
If you are early in this journey, start with three questions. What decisions is the baseline being built to support (network design, business case, operating model, S&OP transformation, cost-to-serve, automation investment)? What data is available in your source systems today and what would need to be collected or estimated? Who will own the baseline once it is built, and is there a maintenance cycle in place to keep it alive?
If those three questions point to a baseline exercise, scope it tightly to the decisions it will support, design the data model upfront, and treat the build as a programme rather than a project.
Frequently asked questions
What is a supply chain baseline? A supply chain baseline is the structured, defensible, quantified representation of the supply chain as it operates today. It is a working model of network, cost, service, inventory, and capability that the business can interrogate and use as the starting point for transformation decisions.
How is a baseline different from a current state assessment? A current state assessment is the activity of investigating and documenting how the supply chain operates today. A baseline is the quantified model that comes out of the assessment. The assessment is the exercise. The baseline is the artefact.
How long does it take to build a decision-grade baseline? A decision-grade baseline for a mid-market Australian business typically takes eight to fourteen weeks. The single biggest variable is the state of the data when the work begins. Enterprise-scale or multi-business-unit baselines can take longer.
What data do you need to build a baseline? At minimum: finance data covering supply chain cost categories, ERP transaction data covering volumes and flows, WMS and TMS operational data covering warehousing and freight, planning system data covering forecast and inventory positions, service performance data, and the organisational structure and headcount data covering capability. Data gaps are normal and managed transparently in the model.
What does decision-grade actually mean? A baseline is decision-grade when it is defensible to a board, executable by an operator, and useful for scenario modelling. Defensibility means every number can be traced to a source. Executability means the operators recognise the business in the model. Scenario usefulness means the model can be re-run with different assumptions to test future state options.
Does the baseline need to reconcile to the P&L? Yes. A cost baseline that cannot reproduce reported financial cost within an acceptable variance is not a baseline. Typical practice is reconciliation within around 5 per cent at total level and within around 10 per cent at segment level. Where reconciliation fails, either the data, the allocation logic, or the business has an unexplained variance, and that itself is a finding.
How is a baseline used after it is built? The most common downstream uses are network design, business case development, operating model redesign, S&OP and planning transformation, cost-to-serve and customer profitability analysis, and automation and technology investment cases. A single baseline can support all six.
How often should a baseline be refreshed? A working baseline used for ongoing commercial decision-making is typically refreshed quarterly or at minimum annually. Cost structures, channel mix, and operating model shift over time. A baseline that is not refreshed within twelve months has typically aged past usefulness.
Can a small or mid-market business build a decision-grade baseline? Yes. The methodology is scalable and the tooling required is well within mid-market reach. A small-to-mid-market baseline typically involves less data complexity than an enterprise-scale model and can be delivered in a tighter timeline.
Who should own the baseline once it is built? Ownership typically sits with the supply chain, operations, or transformation leadership team, with finance as a key partner for the cost reconciliation discipline. External advisors build the baseline. The business owns it.
A decision-grade supply chain baseline is one of the highest-leverage investments an Australian business can make before committing to a transformation programme. Built well, it survives years, supports every downstream decision, and pays back many times over. Built badly, it produces a slide pack that lasts a month and a business case that does not survive its first hard meeting.
If you are scoping a transformation, a network redesign, a business case, or an operating model change in 2026, the baseline is where the work begins.
Explore our Strategy and Network Design services →
Related reading: Strategy and Network Design · Planning and Operations · Project and Change Management · Organisational Design · Procurement · Insights
