Value Leakage: Reports
Objective. Open Reports and produce a leakage summary that preserves the capacity-vs-cash separation and the confidence discount, so the output is a defensible ledger, not an inflated slide.
This screen answers 'how do we communicate leakage and recovery to leadership and finance without inflating it?' Reports packages the ledger for sharing while keeping the honesty rules intact.
See it in the demo
What this screen answers
Leaders and finance ask 'give me the summary I can take to the board.' Reports answers it by packaging findings, categories and recovery into a shareable view. The whole point of the app is that this summary stays honest - sized by confidence, with capacity and cash kept apart - so a Sales or CSM person uses Reports to show the customer a business case finance will actually trust.
The task
Open Reports at the cited route. Read what the report groups - by category, by owner, by recovery status - and build a short summary of one or two findings. Keep capacity and cash as separate lines in anything you present, and keep the confidence discount visible. Do not quote the seeded figures externally and do not invent export controls or formats you have not confirmed with product.
How to read it
A report is only as honest as the rules it preserves. The misread to avoid: a report that rolls everything into a single headline 'savings' number - that silently sums capacity and cash and drops the confidence discount, which is precisely the inflation the app exists to prevent. Read a report as a ledger: detected and sized value, who owns it, and what is Verified-with-evidence as recovered, with capacity and cash on their own lines. If a report blends them, correct it before it reaches the customer's finance.
Honest limits
This screen proves a report can be produced on seeded demo data. It does not prove the customer's real figures, and it must not be used to generate an external number that has not been validated. Which report formats, exports and groupings exist, and whether they can be shared externally, are customer-specific and SME-validation-pending - confirm with product. The figures remain seeded until the customer's rates, quantities, recoverable share and verification evidence are agreed with their finance.
Interpretation check
A leakage report must preserve the capacity-vs-cash separation and the confidence discount; a single blended 'total savings' headline is the exact inflation the app exists to prevent, so never present or quote one.
Practical task
Open Reports, build a short summary of one or two findings, and present it with capacity and cash on separate lines, the confidence basis stated, and recovery status shown - then note one way a careless report could inflate the number and how you would correct it.
Self-check
A report shows one big 'total savings' figure. What is wrong with it?
It almost certainly sums capacity and cash and hides the confidence discount - the two things the app exists to prevent. Insist on separate capacity and cash lines and a visible confidence basis before it goes to finance.
What makes a leakage report defensible to a CFO?
Confidence-discounted values, no overlap double-counting, named owners, and recovery that is Verified-with-evidence - with capacity and cash kept on separate lines. That is a ledger, not a vendor claim.
Can you share a report's figures externally after the demo?
No. They are seeded demo numbers. External figures need the customer's agreed rates, measured quantities, recoverable share and verification evidence, and the available formats/exports are SME-validation-pending - confirm with product.
What three things should any shared summary keep visible?
The confidence discount, the capacity-vs-cash separation, and recovery status (what is only Open versus Verified-with-evidence). Drop any of these and the summary inflates.
Verified vs demo. Screen is live in the demo at /#/reports; exact controls and figures are SME-validation-pending.