How to Map a Supply Chain on One Page (SCOR-Lite)

The Ninety-Minute Map: Five Links, Real Names, One Number Each

The map takes ninety minutes and a whiteboard, or one slide, which photographs better. Draw five boxes left to right: Plan, Source, Make, Deliver, Return. Fill each with real names: the planner's name and method for Plan; each supplier with location, lead time and promise reliability for Source; the manufacturing or branding arrangement for Make; the DC, the 3PL, the forwarder and the channels for Deliver; and, honestly, whatever actually happens today for Return, even if the honest answer is "an unlocked cage". The discipline that separates a map from wall art: one exposing number per arrow, computed from your own data, with its formula written beside it. The SCOR-Lite map is the working version of the Supply Chain Operations Reference model, the five links your chain actually runs on.

Learning how to map a supply chain is mostly learning what to leave off. No maturity models, no swim lanes, no twenty-metric dashboards, five links, real names, one number each. The map's job is not documentation; it is making weak links visible and ownership arguments arithmetical in a single artifact the whole room can hold in view at once.

The Exposing Number: One Per Arrow, No Exceptions

The exposing number is the link's vital sign, the one that moves when the link is broken and ignores the rest. The table below is the standard set with healthy bands and the data trap each one hides. If you cannot compute an arrow's number from data you can pull this week, write "unmeasured", that is the map's first finding, and it is usually the arrow nobody owns.

The unmeasured arrow is a finding

Treat every "unmeasured" as a scheduled reveal: the arrow nobody can compute is almost always the arrow with no owner, and the conversation about why is worth more than the number would have been. Log it on the map in plain text, assign it a month, and clean one arrow per cycle. Chains that follow this rule have a complete map within a quarter; chains that wait for perfect data are still waiting, with the same weak links, a year later.

The Four Numbers Underneath: Compute Before You Judge

The map shows structure; the four baseline numbers show health, and they deserve the same rigor as the arrows. Fill rate, order lines shipped complete from stock, is the customer number; at 3.1 turns versus a 5-6 benchmark, a $4M chain has roughly $1.3M asleep on shelves; OTIF is the number retail buyers actually score, where a punctual truck carrying 800 of 1,200 units is a failure with a chargeback attached; and the cash conversion cycle is the oxygen number, days between paying suppliers and getting paid. The table below is the version we hand out on Day 1.

The bias test for the Plan arrow

MAPE alone hides the most expensive forecasting failure, so add the bias test: compute signed error, and if it runs consistently above a third of MAPE, the forecast is pointing, systematically high or low, which is a mechanism problem, not a math problem. Pointing forecasts starve or flood buffers on schedule, which is why the bias test belongs on the map beside the error number. The fix is usually an information path: the promotion calendar that never reached planning, the distributor orders that double-count demand.

Why Mapping Stopped Being Optional

The resilience numbers made the map a leadership artifact rather than an operations one. McKinsey's 2020 survey found 93% of supply chain leaders planning resilience actions, McKinsey Global Institute estimates companies lose roughly 45% of one year's profits over a decade to disruptions, and Gartner's survey found only 21% of supply networks rated highly resilient. Plans without a map of where the chain actually breaks are budgets without addresses, the map is what gives the 93% a target.

The 45% number is the one to sit with. Losses of that size accumulate through precisely the weak links the map exposes: the single-source arrow, the lead-time lie, the return cage nobody owns. A chain that maps quarterly is not immune, it is simply the only kind of chain that can see the loss forming while there is still time to move.

The Six-Habit Audit: From Structure to Behavior

A map on a wall proves nothing by itself, so the audit scores the behaviors that keep it alive. Score each habit 0-5 on evidence: zero means it does not exist, three means it exists but depends on one person's memory and would not survive their vacation, five means it is written, owned and survivable. The gap between your score and five is the work queue, and the two lowest scores point at the two weak links your roadmap should attack first. The six-habit audit is the map's pulse check.

• Single-map habit, does one page exist with all five links and one number per arrow, updated quarterly? "In my head" scores zero, not five
• Four-number habit, are fill rate, turns, OTIF and cash cycle computed weekly from real data and posted where the team sees them?
• Weak-link habit, is the worst link reviewed on a cadence with a named owner and a fix in flight, or does it top the list every quarter with new adjectives?
• Target habit, does every number carry a target with a reading day? Targets without dates are wishes
• Evidence habit, is every claim in reviews attached to a number anyone can recompute?
• Return habit, do returns have a policy, a recovery path and an aging report? The cage nobody owns is where margin dies quietly

Reading the Map: Where Weak Links Actually Hide

A mapped chain with honest numbers almost always surprises its own management, in three recurring places. Source surprises first: the supplier defended by unit price is exposed by the arrow's number, 71% on-time means every buffer downstream is starving, and the landed-cost table usually shows the "cheap" quote carrying a 20-30% hidden premium in freight, rejects, expedites and pipeline days. Plan surprises second: the forecast measured at the flattering grain prints half the error of the decision-grain truth, and the bias test reveals a pointing problem with a mechanism. Deliver surprises third: the fill-rate gap concentrates in specific SKUs and weeks, which the flat-buffer rule and the review cadence explain in an afternoon.

Each surprise has a named tool elsewhere in the library: the buffer math lives in the safety stock guide, the supplier correction lives in the supplier scorecard build, and the delivery levers live in our guide to reducing lead time. The map is the diagnostic; those are the treatments, and the sequence is always map, baseline, then treat the two weakest links.

The Political Function: Publish Before You Converse

The map's political function is its most valuable feature: publish it internally before any cross-department or supplier conversation. The first argument should happen inside your own house, in daylight, with numbers, because weak links are ownership arguments, and the map is what turns them into arithmetic. The warehouse cannot absorb blame for a returns process nobody owns once the cage is on the map; the supplier cannot coast on charm once the OTD number is on the arrow with their name on it.

Suppliers perform differently for chains that measure predictably; so do departments. The map is not an accusation, it is the shared fact that lets professional people be professional about a weak link, which is why the quarterly refresh is a better meeting than the annual blame retrospective the map replaces.

What Measured Chains Return

The performance numbers complete the case. Accenture's analysis found 94% of Fortune 1000 companies experienced pandemic-era disruptions, 75% reporting negative business impact, and Deloitte's long-cited research found 79% of organizations with high-performing supply chains achieve above-average revenue growth. The difference between the two groups is not luck or scale; it is measured visibility, the habit the map builds in ninety minutes and compounds every quarter after.

The wider benchmark set, and the numbers worth arguing with, is collected in the supply chain statistics briefing, which pairs every figure with its source and its caveats. Bring it to the same meeting as the map; the two documents answer different questions and the room needs both.

Keeping the Map Alive: Quarterly Refresh and the Capstone Re-Run

A map is a living instrument, not a one-time exercise. Refresh it quarterly: the same five links, the same exposing numbers, recomputed, with the previous quarter's numbers beside them, so direction is proven rather than narrated. The refresh takes an hour once the baseline formulas exist, and it is where improvement becomes visible: fill rate moving with the buffer rework, supplier OTD responding to the scorecard, MAPE falling as the bias mechanisms get fixed. Numbers that did not move stay on the map with their mechanisms and reading days, honest lag builds more credibility than curated wins.

This is exactly how the fifteen-day Supply Chain & Logistics Optimization program uses the map: Day 1 draws it and computes the baseline, Days 2-14 install the mechanisms that move the arrows, and Day 15 re-runs it with fresh evidence as the capstone. If you want the map built with AI assistance, the free supply chain course day includes the SCOR-Lite Map Builder prompt and the four-number baseline calculator, the founding artifact set in one morning, with your real names on every arrow.

Your 90-Day Mapping Plan

Here is the quarter that turns the map into the chain's operating document. Days 1-30: draw the map with real names, compute every arrow you can, mark the rest unmeasured with an owner and a month, and compute the four baselines from your own exports. Days 31-60: run the six-habit audit, publish the map internally, and attack the weakest link with one designed change. Days 61-90: hold the first quarterly refresh with last quarter's numbers beside the new ones, and put the four baselines on the leadership one-pager. The full sequence, with prompts and feedback on every artifact, is the Supply Chain & Logistics Optimization program.

For workshops and planning offsites, the ready-made supply chain case studies books and coaching toolkits carry the same map template, baseline calculators, and audit sheets into the room offline. Ninety days of that rhythm will not make your chain perfect; it will make it legible, mapped, measured, and argued about in numbers rather than adjectives, which is the only condition under which weak links ever actually get fixed.

• One page, five links, real names, photographed, not laminated, because you will edit it
• One exposing number per arrow, formula written beside it, "unmeasured" treated as a finding
• Four baselines computed from your own exports, with the data traps you hit written down as findings
• Six-habit audit scored on evidence, with the two lowest habits named as the work queue
• Quarterly refresh on the calendar with last quarter's numbers beside the new ones

Frequently asked questions