The operator dashboard for a volatile quarter

The World Bank's 2026 update combines weaker momentum, renewed inflation pressure and tight finance. GSMA's 2026 report shows a large mobile usage gap despite coverage. TechCabal's H1 funding review shows similar capital value spread across fewer disclosed deals. Different sectors share one management problem: aggregates can look stable while operating distribution deteriorates.

A weekly dashboard should show the next decision, not decorate the previous month.

Due in seven days: cash

Show unrestricted cash by bank and currency, committed available facilities and daily obligations through the next payroll or supplier cycle. Separate restricted money.

Add the lowest projected balance in 13 weeks under base and downside. Preserve last week's forecast and explain movement.

List the three largest payments requiring approval, currency or documentation. Assign owner and deadline.

Bank concentration and unavailable routes belong beside balance. Cash in a frozen channel is not ordinary liquidity.

Due in fourteen days: collections

Show invoiced, due, overdue, disputed and promised cash by customer cohort. Highlight largest exposures and receipts the base forecast needs.

Record collection probability from history and case evidence, not salesperson confidence. Keep pipeline out of receivables.

Disputes need root cause: delivery, quality, invoice, tax, approval or customer cash. Each has a different owner.

Report cash collected against due, not revenue booked.

Due before the next quote: price

For major products, show current price, replacement variable cost, realised contribution, discount and quote validity. Mark imported or index-linked inputs.

Add volume and mix. Margin percentage can improve because low-margin volume disappeared.

List contracts approaching reset and customers outside the new price. Revenue weighted by old terms shows exposure.

Exceptions need owner, expiry and expected relationship value.

Due before foreign payment: currency

Show committed foreign payments and reliable foreign receipts by currency and week. Do not net across dates.

Add executable rate, approved stress and local cash required. Identify documentation and provider.

Inventory cover should show which foreign order can be delayed and which stops operation. A broad purchasing freeze can damage cash later.

Record hedges or fixed quotes with counterparty and maturity.

Due before service breaks: capacity

Show the operating bottleneck: fleet availability, production uptime, support backlog, network completion or another process measure. Include demand and capacity in the same unit.

A GSMA coverage figure or national growth rate cannot replace company throughput. Use actual transactions, orders or hours.

List incidents and overdue maintenance. Cutting maintenance can improve this week's cash and weaken next month's service.

People capacity needs critical roles, absence and unsafe workload, not a general headcount target.

Due before financing closes: runway

Show fundraising or lending stages with documentary milestone, earliest cash date and dependency. An investor meeting is not liquidity.

Add financing cost, dilution, security and action dates if the process slips. TechCabal's fewer H1 deals support planning for selection, not predicting failure.

Existing investors and lenders need stated capacity and approvals. Verbal interest remains labelled.

The no-financing plan belongs on the page before the bank balance forces it.

Omit the vanity total

Do not lead with registered users, downloads, gross merchandise value or announced partnerships unless one connects to cash, capacity or an obligation. The metric can remain in a product report.

A dashboard has limited attention. Every prominent number should support an action, threshold or investigation. Removing a vanity metric is a design decision.

Growth can still matter. Show active paying cohort, contribution and retention when they connect to forecast cash.

Do not reward teams for manipulating the dashboard denominator.

Attach thresholds and owners

Each measure needs definition, source, refresh time and owner. Set thresholds from covenant, cash requirement, service promise or approved risk, not red colour preference.

A threshold triggers a named action or meeting. If no one acts, remove or redesign it.

Preserve corrections and system failures. Manual data can be useful when labelled. False automation confidence is worse.

Limit access to sensitive customer and employee data. The board needs aggregate decision evidence, not unrestricted records.

Run the meeting from deadlines

Start with decisions due before the next meeting. Record owner and date. Move unresolved data gaps into actions.

Compare forecast with actual and ask which assumption failed. Do not spend the meeting narrating every chart.

End with cash date under the approved case and the conditions that change it. Circulate minutes and updated actions.

The volatile quarter will generate more numbers than management can use. The dashboard earns its place by removing the ones that cannot change a decision in time.

Audit the dashboard itself

Once a month, select several displayed numbers and trace them to source records. Confirm definition, period, exclusions and refresh. A dashboard can become polished and wrong when an upstream field changes or a manual adjustment remains.

Review metrics that no longer trigger action. Remove them or move them to a specialist report. Add a new measure only with an owner and retirement condition; otherwise volatility produces an expanding wall of charts.

Ask users which decisions changed because of the dashboard and which arrived too late. This is not a satisfaction survey. It is an operating test of whether the reporting cycle matches the company's clocks.

Sources

• World Bank, 8 April 2026: Africa Economic Update April 2026
• GSMA, 16 June 2026: The Mobile Economy Africa 2026
• TechCabal Insights, 3 July 2026: $1.44 Billion Raised in the First Half of 2026