Management reports: formula sheet

Key formulas

Cost-benefit test for a report

Benefit of improved decisions > Cost of producing and using the report

Cost includes data collection, processing, distribution and the manager's time reading it. Benefits are often hard to quantify, so argue qualitatively.

Qualities of good information (checklist)

Relevant, Accurate, Timely, Clear, Concise, Complete, Reliable, Cost-effective

Use as a checklist, but only discuss the qualities that matter in the scenario.

Variance for exception reporting

Variance = Actual − Budget (or standard); report if outside an agreed tolerance

The tolerance level is a management choice. State it as a judgement, not a fixed rule.

Tailoring rule

User → Decision → Content + Detail + Format + Timing

Use this as your answer structure. Always start from the user's decision, not from the data available.

Detail by level

Higher level = more summary, more strategic, more external and forward-looking; lower level = more detail, more operational, more frequent

This is a general tendency, not an absolute rule. Say so if the scenario points the other way.

Controllability principle

Report to managers only what they can control or influence, and separate uncontrollable items

Particularly important for divisional managers, where allocated head office costs distort performance.

Internal vs external

Internal: flexible, confidential, forward-looking, financial and non-financial. External: regulated, standardised, mainly historic

Voluntary external reports, such as sustainability reports, sit between the two.

Six capitals (integrated reporting)

Financial, manufactured, intellectual, human, social and relationship, natural

Use them to structure a value-creation discussion. Not every capital is relevant to every organisation.

Balanced scorecard perspectives

Financial | Customer | Internal business process | Innovation and learning

Each perspective asks a question and needs measures, targets and actions.

Variance to target

Variance = Actual − Target (state favourable or adverse)

Apply to financial and non-financial KPIs alike. For defects, a lower figure is favourable.

Percentage change

% change = (Current − Previous) ÷ Previous × 100

Useful for trend columns in a dashboard.

Data to information

Data + processing + context = Information

Use this to answer 'difference between data and information' questions. Add that information must be useful to a decision.

Big data characteristics

Volume, Velocity, Variety (plus Veracity and Value in extended lists)

Name the ones you use and apply each to the scenario, not just list them.

Types of analytics

Descriptive → Diagnostic → Predictive → Prescriptive

Moves from what happened to what should be done. Value and difficulty usually rise along the sequence.

Qualities of good information

Accurate, Complete, Timely, Relevant, Understandable, Cost-effective (and reliable source)

Many memory aids exist (such as ACCURATE). Any sensible, well-explained list earns credit.

Cost-benefit test

Value of better decisions > cost of obtaining the information

Applies to any new data source or system. Benefits are often hard to quantify.

Evaluation checklist

User → Decision → Relevance → Reliability → Timeliness → Clarity → Balance → Distortion

A memory aid, not a formula. Use it to structure the critique so no area is missed.

Critique structure

Point → Evidence from scenario → Effect on user → Improvement

Each weakness should follow this four-part pattern to earn application and evaluation marks.

Variance on report figures

Variance = Actual − Budget (state whether favourable or adverse)

Use it when recalculating figures to show a report hides or misstates performance. Check the sign carefully.

Quick revision

• A report must fit its user, purpose and decision. Start every answer from this test.
• Different stakeholders need different detail, frequency and format. Do not assume one report suits all.
• Good reports are relevant, reliable, timely, understandable and worth their cost.
• Financial measures show results but often look backwards. Non-financial measures can give earlier signals about future performance.
• Non-financial measures need clear definitions and links to strategy or they add noise.
• Too many measures can hide what matters. Focus on the few that drive decisions.
• Big data is usually described by volume, velocity and variety. Quality and reliability still decide its value.
• Analytics can describe the past, explain causes, predict outcomes or suggest actions. Know the difference.
• Check data quality: accuracy, completeness, timeliness, consistency and source.
• When critiquing, state the problem, explain the effect on the user, then give a specific recommendation.
• Tie every point to facts in the scenario. Generic points earn few marks.
• Use a format that suits the requirement, such as a memo or report, with a clear structure and suitable tone.

Common mistakes

• Listing the qualities of good information without applying them. Fix: Link each quality to a fact in the scenario and explain the effect on the user's decision.
• Ignoring who the user is. Fix: State the user's level first. Operational users need detail and frequency. Senior users need summaries and strategic links.
• Describing one generic report for everyone. Fix: Name each user, state their decision, and show how the report differs for each. Contrast is what the examiner wants.
• Giving the board too much detail. Fix: Recommend summaries, KPIs, exceptions and trends for the board, with detail available on request. Mention information overload.
• Listing generic KPIs with no link to the scenario. Fix: Tie each KPI to a stated CSF or strategy in the case and say why it suits that organisation.
• Calling non-financial measures better than financial ones. Fix: Argue balance. Each type has strengths and weaknesses, and non-financial KPIs should still link to financial outcomes.
• Writing a generic list of the Vs of big data with no link to the business. Fix: Define in one line, then apply each V to the scenario's data, such as velocity of live sales feeds in a retailer.
• Treating data and information as the same thing. Fix: State that information is processed, contextualised data useful for a decision, and show the processing step in your answer.
• Listing generic qualities of good reports without using the scenario. Fix: Tie every point to a fact, figure or person in the scenario. If a point has no scenario link, cut it or rework it.
• Identifying weaknesses but giving no improvements, or vague ones such as 'improve the data'. Fix: Pair each weakness with a concrete recommendation stating what changes, who does it and why it helps.

Exam tips

• Always name the user and purpose before discussing qualities. Markers reward application to the scenario.
• Pick the three or four qualities that matter most. A focused answer scores better than a full list.
• Make recommendations specific, such as exception reporting, a dashboard or shorter lead time, and add a cost-benefit point.
• Use the format requested, such as a report or briefing note, to earn professional skills marks for communication and structure.
• Link the report to strategy and non-financial measures when the scenario hints at them.
• Always name the user and their decision before describing the report. Examiners reward tailoring, not lists of report qualities.
• Use data from the scenario, such as a named division, a KPI or a complaint from a manager, to show application. This also earns analysis and commercial acumen marks.
• Match your answer format to the requirement. If asked for a memo or email, use that format and keep it concise for professional skills marks.