The Executive Brief: Turning ERP Metrics into Board-Ready Narratives

Boards do not need more ERP dashboards. They need a short narrative that answers three questions: Are we on track? If not, why? What decision do you need from us? The executive brief is how you translate operational ERP metrics — cash conversion cycle, on-time in full (OTIF), gross margin bridges, inventory days, project margin — into that story without dumping fifty green tiles and a PDF of exports.

This guide is a practical map from system numbers to board-ready language. It covers which ERP metrics answer which board questions, how to structure a one-page brief, sample narratives for cash, margin, and delivery, and the monthly versus quarterly cadence that keeps directors focused on strategy rather than data archaeology. If you are still building the business case for the system itself, pair this with how to justify ERP to the board — that piece is about the investment ask; this one is about the operating narrative once the data exists.

What directors actually want from ERP metrics

Research and practitioner reporting on executive packs converge on a blunt diagnosis: most “executive reports” are data dumps dressed as insight. ClearPoint Strategy’s performance-reporting guidance puts it plainly — leaders want answers, exceptions, and actions, not archives of every metric the organisation can measure (https://www.clearpointstrategy.com/blog/performance-reporting-for-executives). Preferred CFO’s board-KPI guidance makes the same point from the finance chair: context, forward-looking insight, and simplicity beat memorised numbers (https://preferredcfo.com/insights/financial-kpis-every-ceo-must-master). Domo’s executive reporting guide separates monitoring dashboards from reporting workflows that include variance commentary and board-ready packages (https://www.domo.com/learn/article/the-ultimate-guide-to-creating-executive-level-reporting-dashboards).

Translate that into ERP practice:

• Answers, not exports. “Revenue was $4.2M” is a fact. “Revenue hit 98% of plan; the $120K miss is enterprise sales cycle stretch; Q2 pipeline is +12% and we recommend accelerating mid-market methodology training” is an answer.
• Exceptions, not everything. Green metrics need a status, not a paragraph. Red and amber metrics need root cause, impact, response, and a decision request.
• Actions, not status theatre. Every off-track KPI should end with what management is doing and what, if anything, the board must approve (capital, policy, risk appetite, priority trade-off).

Secret CFO’s widely shared KPI process, distilled from a large multi-unit group, reinforces the operating discipline underneath the brief: start from strategy and a short hero-metric set, document definitions the way finance documents GAAP, set targets in the budget cycle, anchor on a monthly scorecard, and spend meeting time on performance management rather than reconciling sources (https://x.com/SecretCFO/status/1850657824835264579). ERP is valuable here only when it makes that loop faster and more trustworthy — not when it multiplies charts.

Map ERP metrics to board questions

Do not start with the chart library. Start with the questions directors already ask, then pull the few ERP-sourced measures that answer them.

Liquidity and working capital — “Can we fund the plan without surprise?”

• Cash conversion cycle (CCC) = days inventory outstanding (DIO) + days sales outstanding (DSO) − days payable outstanding (DPO), as defined in standard working-capital teaching (https://corporatefinanceinstitute.com/resources/accounting/cash-conversion-cycle/).
• Free cash flow and operating cash flow trends after close.
• Working capital as a percentage of revenue, and absolute cash tied in inventory and receivables.

Board language: “CCC moved from 62 to 71 days because DIO rose eight days on slow-moving SKUs in product line B; that ties roughly $X more cash. We are cutting safety stock on the bottom 15% of SKUs and tightening credit on three accounts driving DSO.”

Profit quality — “Is growth real margin or just volume?”

• Gross margin percentage and absolute gross profit versus plan and prior year.
• Gross margin bridge: price, volume, mix, cost (materials, labour, overhead absorption), and FX where relevant.
• Contribution margin by product family or customer segment when the ERP cost model supports it.

Board language: “Gross margin is −120 bps versus plan. Price held; volume was flat; mix shifted to lower-margin channel C (−80 bps); material cost inflation on alloy X (−40 bps). Mitigations: surcharge on alloy-heavy SKUs from next month; sales incentives reweighted toward channel A.”

Customer promise and capacity — “Are we delivering what we sell?”

• OTIF (on-time in full): share of orders delivered both on the agreed date and complete. Formula: OTIF deliveries ÷ total deliveries. Industry guidance typically treats roughly 95–99% as excellent and below about 85% as a structural problem (https://www.mrpeasy.com/blog/on-time-in-full-otif/; retail-facing logistics sources often cite 98% customer targets such as Walmart-style OTIF programmes — https://www.fourkites.com/blogs/maximizing-on-time-in-full-otif-in-the-supply-chain/).
• Fill rate, backlog, and late-order aging as supporting diagnostics — not as peer metrics on the same page as OTIF unless definitions are crystal clear.
• Capacity utilisation or order cycle time when capacity is the strategic constraint.

Board language: “OTIF is 91% against a 96% target. On-time is the problem (93%); in-full is 98%. Root cause is production scheduling on Line 2 and two supplier OTIF failures on critical components. Customer risk is concentrated in three key accounts. Decision requested: approve dual-source for component Y ($Z tooling, 10-week lead).”

Project and services margin — “Are we earning on delivery, not only on booking?”

• Project margin (WIP, estimated cost to complete, write-ups/write-downs).
• Utilisation and realisation for professional services models.
• Deferred revenue and milestone completion for long-cycle work.

Board language: “Three projects above $500K are below 20% forecast margin at completion. Two are scope-creep without change orders; one is a fixed-price bid miss. Action: freeze scope on Project Atlas pending change-order approval; reforecast Q3 services margin −$180K.”

Control and close — “Can we trust the numbers?”

• Days to close, number of manual journal entries, reconciling items aged past threshold.
• Audit findings open, segregation-of-duties exceptions, inventory accuracy (cycle count).

Board language: “Close completed in six business days (target five). Two material reconciling items remain in intercompany; both owned and dated. Inventory accuracy 97.2% on ABC cycle counts.”

Keep the board pack to roughly 4–7 primary KPIs on the scorecard face, with deeper bridges in appendices. Domo’s role-based guidance clusters strategic packs around a small set (revenue growth, gross margin, cash, initiative progress); ClearPoint flags packs with more than about 15 metrics as losing executive focus. More charts are not more governance.

Anatomy of a one-page executive brief

Constraint forces clarity. A board-useful brief fits one page (or a two-page spread) and uses a stable structure every period so directors spend cognition on content, not layout.

1. Headline (three sentences max)

What changed, why it matters, what you recommend. Example: “Q2 cash conversion lengthened nine days on inventory, tying ~$1.1M incremental working capital. Gross margin held within 20 bps of plan. Recommend approving the dual-source and SKU rationalisation package so CCC recovers by Q4.”

2. Scorecard (4–7 KPIs)

For each: actual, plan, prior period or prior year, trend (improving / stable / declining), RAG status, and a one-line note only when not green. Use colour as signal only — green / amber / red — not decoration.

3. Bridges and narratives (the “so what”)

Only for exceptions and strategic themes. Prefer one gross margin bridge and one cash or OTIF narrative over ten sparkline cards.

4. Initiatives and decisions

Five to eight strategic initiatives maximum: name, status, percent complete, blocker, owner. Explicit decision list: what needs board approval this meeting versus management-only actions for information.

5. Outlook and risks

Next-period milestones, known constraints, and the two or three risks that would change the story if they materialised.

This structure mirrors the four-section executive report pattern (summary, scorecard, initiatives, resource outlook) described in contemporary performance-reporting practice, adapted to ERP-sourced operating metrics rather than pure strategy software.

Sample narratives you can reuse

Inventory and cash conversion

ERP sources: inventory valuation and aging, COGS, open sales orders, purchase receipts, AP and AR subledgers.

Narrative pattern:

• State CCC and the component that moved (DIO, DSO, or DPO).
• Quantify cash impact (days × daily COGS or revenue, as appropriate).
• Name the SKU families, plants, or customers driving the move.
• Separate intentional build (pre-season, promotion, risk stock) from leakage (obsolete, forecast error, MOQ bloat).
• End with owners, dates, and any capital or policy decision.

Weak: “Inventory days increased.” Strong: “DIO +8 days; $X cash; 60% of the rise is finished-goods SKU family Z with 4+ months cover; plan is freeze replenishment and run a 90-day sell-down with sales incentives.”

Gross margin bridge

ERP sources: invoiced revenue, COGS by element, standard vs actual cost, sales order discounts, product hierarchy.

Narrative pattern:

• Start and end margin (plan and actual).
• Walk price → volume → mix → cost → other.
• Call out whether cost variance is purchase price, usage, or overhead absorption.
• Tie actions to commercial (pricing, discount authority) and operations (yield, scrap, supplier).

Boards trust bridges more than a single margin percentage because bridges show which lever management owns.

Customer OTIF

ERP / WMS / TMS sources: promised date, ship date, delivered quantity versus ordered quantity, reason codes.

Narrative pattern:

• Overall OTIF and split on-time versus in-full (they fail for different reasons).
• Concentration: which customers, lanes, or product lines.
• Root cause ladder: supply → production → warehouse → carrier → master data (wrong promise dates).
• Customer commercial risk (penalties, chargebacks, churn risk) where real.
• Decision: inventory policy, capacity, dual source, or promise-date policy change.

McKinsey’s consumer-sector OTIF work stresses definition discipline — quantity and schedule against the order — because case-fill and OTIF are not interchangeable (https://www.mckinsey.com/~/media/McKinsey/Business%20Functions/Operations/Our%20Insights/Defining%20ontime%20infull%20in%20the%20consumer%20sector/Defining-on-time-in-full-in-the-consumer-sector.pdf). Put the definition in the KPI manual once so the board meeting is not a debate about the formula.

Project margin (make-to-order / services)

ERP sources: project accounting, timesheets, PO commitments, billing milestones, estimates at completion.

Narrative pattern:

• Booked margin versus forecast margin at completion.
• Drivers: scope, productivity, subcontract, change-order lag.
• Cash: billed versus cost incurred (underbilling / overbilling).
• Governance: which projects need executive or board visibility thresholds.

Cadence: monthly operating truth, quarterly board story

Not every audience needs the same depth.

Weekly (ops leadership, optional one-pager): early-warning only — OTIF, backlog, production throughput, cash receipts if stressed. Exceptions and alerts. Five to ten minutes to read.

Monthly (executive team + deep board packs when the board meets monthly): full scorecard, bridges for reds, initiative status, reforecast if material. This is the workhorse where ERP close quality matters. Domo’s reporting workflow is useful here: aggregate after close → refresh KPIs → variance analysis → commentary → leadership review → distribute (https://www.domo.com/learn/article/the-ultimate-guide-to-creating-executive-level-reporting-dashboards).

Quarterly (board / investors): fewer metrics, more strategy. Trend over four to eight quarters, capital allocation, risk register, and progress on multi-year initiatives. Use monthly data as the source of truth so the quarterly story does not invent a parallel reality.

Rule of thumb from executive reporting practice: monthly for course correction; quarterly for governance and capital. Do not make the board re-litigate every operational amber every week.

Visualisation rules that survive the boardroom

• Five-second rule. A director should grasp the headline and RAG state in seconds (Domo’s executive dashboard guidance).
• One primary chart per story. A waterfall for margin, a stacked trend for CCC components, a simple OTIF trend with target line — not three competing visuals for the same point.
• Definitions footnoted once. “On-time = delivered by promised date on sales order; In-full = shipped qty ≥ ordered qty within tolerance X%.”
• No decorative dashboards in the pack. Live operational screens belong to plant and warehouse managers. The board pack is a decision document.
• Reconcile to the financials. ERP operational metrics that cannot be tied back to the management accounts destroy trust. If OTIF improves while returns and credit notes spike, show both.

Make the ERP the source of narrative, not the excuse

Board narratives fail when definitions drift, extracts disagree, and every meeting starts with “which system is right?” Fix the plumbing:

1. KPI dictionary (your “KPI-GAAP”). Name, formula, source tables or reports, owner, refresh cadence, target, and red/amber thresholds. Secret CFO’s framing is right: document the answers so the room debates performance, not the denominator.
2. Single close calendar. Operational metrics that depend on unposted inventory or open periods will lie. Align cut-offs with finance close.
3. Ownership. Each Tier-1 KPI has one accountable executive. ERP can automate calculation; it cannot own the story.
4. Exception workflows. When OTIF or margin crosses a threshold, the system (or a lightweight process on top of it) should trigger the narrative owner before the pack is compiled.
5. Implementation and integration quality. Fragmented CRM, WMS, and finance stacks force manual bridges. If your board pack is still a three-day Excel project, that is a systems and process design problem as much as a storytelling problem — the kind of work addressed in structured ERP implementation and system integration programmes, not in more slide templates.

AI can draft first-pass variance commentary from structured KPI feeds; humans still own root cause, risk framing, and the decision request. Treat generated prose as a draft, never as the board minute.

Common failure modes (and fixes)

• Too many metrics. Fix: force a one-page scorecard; park the rest in an appendix nobody presents unless asked.
• Red without a plan. Fix: no red KPI ships without why / impact / response / decision.
• Metric churn. Fix: change the Tier-1 set only at planning cycles, not every quarter for novelty.
• OTIF theatre. Fix: separate customer OTIF from supplier OTIF; publish definitions; avoid celebrating OTIF while expedite costs explode.
• Margin without bridge. Fix: never present a single margin number as the whole story when price, mix, and cost moved.
• Cash ignored until a crunch. Fix: CCC and FCF sit next to EBITDA every month; profitable-and-illiquid is a board-level failure mode.
• IT metrics that only IT understands. Fix: translate system uptime and ticket volumes into business outcomes (close time, OTIF, order cycle) unless the board is explicitly reviewing technology risk.

How this differs from “justify ERP to the board”

How to justify ERP to the board is the capital and risk conversation: cost of inaction, TCO, phased investment, execution controls. This executive brief is the after — the recurring operating language that proves the system is earning its keep and that management can govern the business from one truth. Use the justification piece when you are asking for money; use this structure every month when you are asking for attention, priority, or a decision on the back of live metrics.

FAQ

How many KPIs belong on a board ERP scorecard? Four to seven primary KPIs on the face of the pack is the practical range used in modern executive reporting guidance. Ten to fifteen is a hard upper bound for a CEO dashboard; beyond that, you have an operations manual, not a board brief.

Should the board see the same dashboard as the plant manager? No. Operational dashboards optimise for real-time action and many process metrics. Board packs optimise for strategic outcomes, variance narrative, and decisions on a monthly or quarterly rhythm. Same data platform; different aggregation and story.

What is a good OTIF target? Context-specific. Many industrial and distribution teams treat mid-to-high 90s as excellent; large retail customers may impose contractual targets near 98%. Below roughly 85% usually signals structural supply, planning, or logistics failure rather than noise. Always publish the definition of “on-time” and “in-full” with the number.

How do we calculate cash conversion cycle from ERP? CCC = DIO + DSO − DPO. DIO uses average inventory and COGS; DSO uses receivables and credit sales or revenue; DPO uses payables and COGS (or purchases), each scaled to days in the period. Use the same calendar and close status as the financial statements so the narrative reconciles.

Monthly or quarterly for the board? Track monthly inside the company; present full narrative depth at the board’s actual meeting cadence (often quarterly for non-executive boards, monthly for active investor boards). Never invent a separate quarterly dataset that disagrees with the monthly management accounts.

Who owns the executive brief? Usually finance or a performance-management function, with metric owners in operations, sales, and supply chain writing exception commentary. The CEO owns the headline and the decision list. ERP and BI teams own data pipelines and definitions, not the strategic story.

Can AI write the board narrative from ERP? It can draft variance text and flag outliers. It should not invent root causes, obscure bad news, or replace accountable sign-off. The board is buying management judgment, not a language model summary.

Closing

ERP metrics become board-ready when they are few, defined, bridged, and attached to decisions. Start from the questions directors already ask — cash, margin quality, customer promise, project economics, control — and force every number through the headline → scorecard → narrative → decision pattern. Do that consistently and the board stops asking for “more data” and starts spending time where it belongs: trade-offs, risk appetite, and capital allocation.

If your numbers still live in irreconcilable spreadsheets, or your close cannot support a trustworthy monthly scorecard, the constraint is often process and platform design rather than slide craft. Flectic helps mid-market teams turn Odoo and Microsoft Dynamics environments into reliable operating systems — from discovery and process mapping through ERP implementation, integration, and ongoing optimisation — so the executive brief is grounded in one operational truth, not a heroic export the night before the meeting.