DC

Insights

15 findings, ordered by commercial weightEvidence from the live BC tenant, 11 Aug 2026
Replaces: the audit deck nobody opens twice, and the spreadsheets built around it
4,500item locations priced below cost or with no cost at allRead the finding
1.5%of the forecasting engine's buying advice reaches an orderRead the finding
41.5average days late across 400 released ordersRead the finding
0 of 5approval workflows running, since June 2025Read the finding
Ask the findingsOne question, answered from the figures on this page and nowhere else.15 findings, all cited
The answer is built only from the figures above, each of which names the file and row it came from. Where the page does not hold an answer it says so rather than reaching for one, and no figure is ever estimated, extrapolated or rounded for effect.

What the evidence says is going wrong, ordered by what it costs, each with the action that closes it. Every number names the file it came from.

06Order to cashHigh impact

Four hundred released orders are running weeks behind and nobody in the business can say whether that is a real backlog or stale data. That is the finding.

400released orders showing as delayed
41.5average days of delay
99showing ready to ship
50showing simply open
The sales role centre, as it stood on 11 Aug 2026Delayed400Ready to ship99Open50Role centre cues, 11 Aug 2026. The audit recorded its confidence as medium: the count is observed, the interpretation is open.
Why it matters

A released order is one the customer believes is coming. If it is stale data instead, the board is being shown a backlog that does not exist.

What to do

Put the delayed queue on a screen with a name against every line and triage it once.

Why it ranks 06

Ranked sixth: revenue promised, costed and not yet billed.

Source · msc-bc-audit/pain-points-and-opportunities.csv row PP-009 (400 sales orders released not shipped, average days delayed 41.5, confidence medium, count observed and interpretation open); functionality-register.csv row SAL-002 (cues: 50 open, 99 ready to ship, 400 delayed, avg days delayed 41.5).
13Order to cashModerate

The open quote cue reads at its ceiling, which is where the counter stops rather than where the quotes stop. Nobody is closing them.

999+open quotes, a ceiling not a count
Dailynew quotes raised, series last used 11 Aug 2026
Feb 2025last purchase quote, that side is retired
Why it matters

Either it is real pipeline nobody is chasing or it is noise in the forecast, and the business cannot tell which. The sales director asked during the audit and it is still open.

What to do

Give quotes an expiry and a follow up queue, then decide the cutover cleansing rule before migration rather than after.

Why it ranks 13

Ranked thirteenth: a doubt over the pipeline rather than a measured loss.

Source · msc-bc-audit/functionality-register.csv row SAL-001 (S-QUO last used 11/08/2026, Sales Quotes Open cue 999+, open quote count suggests quotes not closed or cleaned); risks-blockers-and-open-questions.md line 41; data-migration-inventory.csv row 9 (999+ open quotes, decide cutover cleansing); used-unused-matrix.csv row 8 (purchase quotes rare, last 03/02/2025).
What it adds up toIf you read one thing on this page
Stop the leak

A margin floor checked at the point of sale. Highest value change on this page, and it is a rule, not a rebuild.

Show the price

Name the winning level on every line. Thirteen levels of precedence stop being a liability and start being the asset they should be.

Buy what the engine says

Moving stock MSC already own between two sites they run is the cheapest service fix available. Today none of it happens.

Bill sooner, prove control

Late orders, uncounted quotes and stalled approvals all fix the same way: the work goes back on a screen with a name against it.

Where these figures come fromIncluding how the order was decided

Two sources, and every card names its own. The pricing work already built at gitlab.personify.tech/msc/msc-data-project, read directly, file and line quoted. And the read only audit of the live MSUPPLY LIVE Business Central tenant of 11 Aug 2026, the Netstock UI audit of the same day, the AL source read from the tenant's own extensions, and Product Scope chapter 14.

The data project publishes rules, not results. Its findings tables are declared and never written, its seed creates nothing and every count it shows is computed live and discarded, so what it contributes here is its thresholds, its comparison rules and its own record of what is still to build. Its mock fixtures are never shown as findings.

Two caveats travel with the audit numbers and both stand on their cards. The 999 plus open quotes is a display ceiling, so a floor rather than a count. The 400 delayed orders was recorded at medium confidence. The 650,000 price lines is the data project's own working figure for the size of the job, written to size a page cap, not a verified count.

The order is a commercial judgement, not a measurement. Each finding states the basis for its placing, built only from the figures cited on it. No pound value is attached to a finding the source did not price.