Practise turning financial analysis into decisions through twenty original written tasks and sixty substantive lessons integrating E2, P2 and F2. The tasks simulate Finance Manager communications, with self-contained facts, model answers and assessable rubrics. This representative preview follows the May 2025 syllabus blueprint applicable to May, August and November 2026 and February 2027; it is not a full mock or official question set. Each core activity receives four tasks and twelve concepts here, while official activity weights remain 15–25% each. Suggested practice times are instructional. Source s1 establishes syllabus relevance and format; it does not independently verify every technical explanation. IFRS treatments use the stated scenario assumptions.
What this guide covers
Twenty written finance-manager tasks and 60 focused lessons for CIMA's 2026 Management Case Study syllabus.
Evaluate opportunities to add value
1. NPV starts with incremental cash flows
Net present value discounts the cash flows that change because an investment is accepted, then subtracts the initial investment. Include opportunity costs, incremental operating cash flows, working capital movements and disposal proceeds. Exclude sunk costs and allocations that do not alter total cash spending. A positive NPV indicates value above the required return under the assumptions. Interest is normally excluded from project cash flows when financing cost is already captured by WACC. Match cash-flow timing, tax treatment and inflation assumptions to the discount rate.
Worked example: A testing machine costs $90,000 and releases annual net cash savings of $30,000 for four years. At a supplied annuity factor of 3.170, savings have present value $95,100, giving NPV of $5,100 before any additional terminal proceeds.
Common mistake: Including allocated headquarters costs merely because they appear in the project budget can reject an investment without identifying any additional cash expenditure.
Official syllabus reference: [1]
2. IRR can misrank mutually exclusive investments
Internal rate of return is the discount rate at which project NPV equals zero. It expresses a return percentage, whereas NPV expresses value created. For mutually exclusive investments, different scale or cash-flow timing can make the higher-IRR project produce less value at the appropriate required return. NPV should guide value-maximising selection when funding and risk assumptions are comparable. Non-conventional cash flows can produce multiple IRRs or no useful unique result. IRR is therefore a supplementary explanation of return, rather than a universal ranking rule.
Worked example: Project Birch has a 28% IRR and $40,000 NPV; mutually exclusive Project Cedar has a 20% IRR and $95,000 NPV at the same suitable discount rate. With sufficient funding and comparable risk, Cedar creates more value despite its lower percentage return.
Common mistake: Selecting the highest percentage return automatically ignores investment scale, timing differences and the possibility that NPV rankings better reflect shareholder value.
Official syllabus reference: [1]
3. Equivalent annual cost compares replacement cycles
Equivalent annual cost converts the present value of an asset's lifetime costs into a constant annual amount by dividing by the corresponding annuity factor. It helps compare alternatives with unequal lives when they provide equivalent service and can be replaced on comparable terms. Include maintenance, purchase and disposal cash flows consistently. The lower annual cost is preferred only after confirming equivalent capacity, quality and risk. If technology or replacement conditions will change substantially, an explicit common planning horizon may be more informative than assuming repeated identical replacement cycles.
Worked example: Two machines provide identical service. Their lifetime cost present values are $120,000 over three years and $170,000 over five years. With supplied annuity factors of 2.487 and 3.791, annual costs are approximately $48,251 and $44,843, favouring the longer-lived machine.
Common mistake: Comparing total lifetime cost alone can favour a short-lived asset that must be replaced more frequently to deliver the same service.
Official syllabus reference: [1]
4. Real options value managerial flexibility
A real option is the ability to change an investment decision as uncertainty resolves. Options include delaying commitment, expanding successful capacity, switching inputs or abandoning an unsuccessful project. Flexibility has value when new information can influence a feasible future action; uncertainty alone does not establish option value. Decision trees can represent staged choices and contingent cash flows without requiring a traded-option formula. Compare the flexibility benefit with pilot costs, delay costs and competitive effects. Avoid adding an option value already included in the forecast's conditional decisions.
Worked example: A manufacturer can pay $25,000 to reserve extra production capacity for six months. Reservation may be valuable when confirmed orders will arrive before commitment, allowing expansion only if demand supports it; its value depends on avoided losses and reservation cost.
Common mistake: Calling every uncertain project a valuable option overlooks whether management actually retains a practical right to change its later commitment.
Official syllabus reference: [1]
5. Digital-data provenance protects investment forecasts
Investment forecasts built from digital data depend on provenance: where records originated, how they were transformed and whether they represent the decision population. Transaction records, customer telemetry and external market data answer different questions. Check completeness, duplicate events, timestamps, consent or contractual permissions, and changes in definitions. A model may predict behaviour accurately within its training sample yet fail in a new segment. Reconcile digital measures to operational and financial records, and distinguish predictive association from evidence that the proposed investment causes an improvement.
Worked example: An app reports 50,000 monthly events, but duplicate retries account for 15,000 and staff testing for 5,000. A subscription forecast based on events as unique customers overstates its market; identity reconciliation and representative conversion evidence are needed before appraisal.
Common mistake: A large dataset does not remove selection bias, duplicated records or the gap between a recorded event and a paying customer.
Official syllabus reference: [1]
6. Price elasticity informs contribution decisions
Price elasticity describes the responsiveness of demand to a price change, commonly expressed as percentage quantity change divided by percentage price change. State the percentage convention used when calculating from two observations. Pricing decisions still require contribution analysis because revenue and profit need not move together. A price rise may reduce units and revenue while improving profit if the contribution per remaining unit rises sufficiently. Forecasts should address competitor responses, customer segments and longer-term retention. An elasticity estimated over one price interval need not apply to much larger changes.
Worked example: Using base-period percentages, price rises from $50 to $55 while demand falls from 10,000 to 9,000 units, giving elasticity of negative one. With variable cost $30, contribution rises from $200,000 to $225,000, despite fewer units being sold.
Common mistake: Using elasticity to predict revenue and then treating that prediction as a profit conclusion leaves variable costs and customer economics unexamined.
Official syllabus reference: [1]
7. Skimming and penetration target different economics
Price skimming begins with a relatively high price to capture willingness to pay among early customers, often where differentiation or scarce capacity supports it. Penetration pricing begins lower to build adoption, scale or network participation. Neither strategy is appropriate merely because a product is new. Assess imitation speed, capacity, switching costs and whether future contribution can recover acquisition expenditure. Low introductory prices may create reference-price expectations that make later increases difficult. Segment-specific offers can sometimes capture willingness to pay without applying one introductory price to every customer.
Worked example: A patented specialist sensor with limited launch capacity may support skimming among customers valuing early access. A collaborative maintenance platform may favour penetration in one region because customer value increases when sufficient installers and equipment owners participate together.
Common mistake: Assuming penetration pricing guarantees market share ignores competitor reactions, customer switching costs and the possibility of attracting persistently unprofitable demand.
Official syllabus reference: [1]
8. The Business Model Canvas tests internal coherence
The Business Model Canvas links customer segments, value propositions, channels, relationships, revenue streams, key resources, activities, partnerships and cost structure. Its value comes from testing whether those elements support one another. A subscription promise requires continuing delivery capabilities and a revenue model that covers service obligations. The canvas describes how value is created and captured; it does not establish financial viability by itself. Translate major assumptions into measurable unit economics, capacity requirements and cash forecasts. Revisit connected elements when one major assumption changes, such as channel ownership or partner incentives.
Worked example: A sensor company promises guaranteed uptime to small factories. Its canvas exposes a missing capability: weekend field support. Adding a service partner changes key partnerships, costs and customer relationships, requiring the subscription price and service promise to be reconsidered together.
Common mistake: Completing nine labelled boxes without testing their connections produces a description rather than evidence that the business model can operate profitably.
Official syllabus reference: [1]
9. Platform network effects require participation design
A platform coordinates interactions between participant groups. Cross-side network effects arise when participation by one group increases value for another, such as more installers attracting equipment owners. This creates a coordination problem when neither group joins before the other. Focused geographic launches, anchor participants or temporary subsidies can establish sufficient participation. More users do not automatically create value: congestion, poor matching and low-quality suppliers can weaken the platform. Assess who pays, who receives incentives, how quality is governed and whether participants can readily transact outside the platform.
Worked example: A nationwide repair platform has many registered customers but too few nearby technicians. Launching one city with committed workshops and sufficient customers can improve successful matches, whereas additional remote registrations may add little usable network value for either group.
Common mistake: Treating registered-user growth as proof of network value overlooks match quality, local coverage and whether participants actually complete useful transactions.
Official syllabus reference: [1]
10. Circular models change lifecycle responsibilities
Circular business models seek value through product durability, repair, reuse, remanufacture or material recovery. Leasing or product-as-a-service can give the supplier an incentive to reduce lifetime resource consumption because it retains ownership and maintenance responsibility. The model requires reverse logistics, condition information and a viable secondary use or recovery route. Environmental and financial benefits must be evaluated across the lifecycle; collection and refurbishment can consume resources too. Compare retained residual value, servicing cost, utilisation and customer outcomes rather than assuming that recurring billing alone creates circularity.
Worked example: A device supplier retains ownership and refurbishes returned units after three years. A credible appraisal includes collection, testing, replacement parts, second-life revenue and unusable returns, rather than counting the original device's full sales value again on every refurbishment cycle.
Common mistake: Describing a rental contract as inherently sustainable confuses a payment arrangement with demonstrated reductions in lifecycle resource use and waste.
Official syllabus reference: [1]
11. WACC combines market-weighted financing costs
Weighted average cost of capital combines the required returns on finance using appropriate market-value weights. In a simple debt-and-equity structure, WACC equals the equity weight times cost of equity plus the debt weight times after-tax debt cost, when interest tax relief is available. More borrowing can raise both lenders' and shareholders' required returns. Corporate WACC is suitable for projects only when operating risk and financing assumptions are sufficiently comparable. Use consistent nominal or real cash flows and avoid subtracting interest again from cash flows discounted at WACC.
Worked example: A business financed 70% by equity costing 11% and 30% by debt costing 5% before a 20% tax benefit has WACC of 8.9%. That rate needs reconsideration for an unrelated speculative venture with materially different operating risk.
Common mistake: Using the cheapest individual funding source as the project discount rate ignores the required return on the rest of the capital supporting investment.
Official syllabus reference: [1]
12. Acquisition synergy must survive integration costs
Acquisition value depends on incremental cash flows available to the acquirer, including credible synergies and integration costs. Separate the target's standalone value from benefits that arise only through combination. Cost savings may require restructuring expenditure, while revenue synergies depend on customer acceptance and operational delivery. Avoid counting the same benefit in both the target forecast and a separate synergy valuation. Compare combined value with the purchase price and associated transaction expenditure. Accounting goodwill is a reporting residual; it is not an independent demonstration that an acquisition creates economic value.
Worked example: A target is worth $8 million independently. Integration creates $2 million present value of savings but costs $700,000. Paying $9.6 million destroys $300,000 of value before other transaction costs, despite the presence of genuine operating synergies.
Common mistake: A positive synergy estimate does not justify any acquisition premium; the price can transfer all benefits, and more, to the seller.
Official syllabus reference: [1]
Implement senior management decisions
13. Project governance separates sponsorship from delivery
The project sponsor owns the business justification, secures organisational support and resolves issues beyond the project manager's authority. The project manager coordinates delivery within agreed scope, schedule, cost and quality boundaries. Governance should specify approval gates, delegated tolerances and escalation triggers. A project charter establishes authority and objectives, while the business case explains expected benefits and their costs. Benefits ownership may continue after implementation. A technically successful system can still fail commercially if no operational manager is accountable for changing processes and realising the forecast benefits.
Worked example: A billing system goes live on time, but staff continue using spreadsheets. The project manager delivered the software; the sponsor and operational benefits owner must ensure process adoption and verify that collection improvements actually appear after implementation.
Common mistake: Assigning every project responsibility to the project manager leaves strategic trade-offs, resource conflicts and post-launch benefit ownership without sufficient organisational authority.
Official syllabus reference: [1]
14. Work breakdown structures define deliverable scope
A work breakdown structure decomposes project scope into manageable deliverables and work packages. It establishes what must be produced before detailed scheduling and resource allocation. Each package needs an owner, acceptance criteria and a sufficiently clear boundary to prevent omissions or duplication. A WBS is not itself a chronological schedule: dependencies and durations are added through further planning. Control scope changes by assessing their effects on cost, time, benefits and risk. Unrecorded additions create scope creep even when each individual request appears small and reasonable.
Worked example: A customer migration package is divided into data cleansing, mapping, trial conversion and signed reconciliation. Explicit acceptance criteria reveal that historical-balance validation was absent from the original estimate, allowing the team to resource it before release rather than after failure.
Common mistake: Listing departments or broad activities without deliverables can conceal missing work and make completion impossible to assess consistently across teams.
Official syllabus reference: [1]
15. Critical paths distinguish duration from float
Critical path analysis links activity dependencies and durations to establish the earliest project completion. A forward pass finds earliest times; a backward pass finds latest times compatible with completion. Total float is the difference between latest and earliest start, or finish. Critical activities normally have zero total float under the baseline network. Shortening a non-critical activity does not reduce completion until it changes the controlling path. Resource shortages, uncertain durations and revised dependencies can alter the network, so the calculated path must be updated when circumstances change.
Worked example: One route through a project takes twelve weeks and another takes ten. Removing one week from the ten-week route leaves completion unchanged. Removing one week from the twelve-week route reduces completion to eleven weeks, provided the required resources are available.
Common mistake: Treating every important activity as critical confuses commercial importance with the specific dependency relationship that determines the project's earliest finish date.
Official syllabus reference: [1]
16. PERT makes duration uncertainty explicit
The traditional PERT approximation uses optimistic, most likely and pessimistic activity durations to estimate expected time as (optimistic + four times most likely + pessimistic)/6. Its variance approximation is the square of (pessimistic − optimistic)/6. These are modelling conventions, not guarantees about actual distributions. Combining variances assumes suitable independence, and uncertain durations can change which path is critical. Use estimates to expose uncertainty and discuss contingency, rather than presenting one expected completion date as certain. Shared suppliers or resources can create correlations that simple aggregation overlooks.
Worked example: A configuration activity has optimistic duration two weeks, most likely four and pessimistic eight. PERT gives expected duration 4.33 weeks and variance one week squared. A supplier delay affecting several activities would require more than independent activity calculations.
Common mistake: An expected duration is not a delivery promise, and adding activity variances mechanically can understate risk when delays share a common cause.
Official syllabus reference: [1]
17. Earned value separates spending from progress
Earned value expresses completed work at its budgeted cost. Compare earned value with actual cost to assess cost performance and with planned value to assess progress against the baseline. Cost performance index is earned value divided by actual cost; schedule performance index is earned value divided by planned value. Values below one indicate adverse performance under these conventions. Measures require reliable completion evidence and a credible baseline. Schedule indices are expressed in budget-value terms, so they do not directly establish the number of weeks late or identify the critical path.
Worked example: Planned value is $120,000, earned value $90,000 and actual cost $100,000. CPI is 0.90 and SPI 0.75. Spending is below the original plan, yet completed work is both behind schedule and more expensive than its budgeted value.
Common mistake: Reporting underspending as good performance without measuring completed work can hide delay and adverse cost efficiency within an apparently favourable budget variance.
Official syllabus reference: [1]
18. RACI clarifies decision and execution roles
A RACI matrix distinguishes those responsible for performing work, accountable for its outcome, consulted before decisions and informed afterwards. It is useful where functional boundaries create gaps or duplicated approvals. Normally give each defined deliverable a clear single accountable owner, while several people may perform tasks. Accountability requires enough authority to resolve issues or escalate them. The matrix should be agreed by participants and linked to acceptance criteria. It cannot replace technical procedures, resource commitments or a decision process when genuinely conflicting objectives require sponsor intervention.
Worked example: For opening-balance migration, an analyst performs reconciliations, the Financial Controller owns approval, IT is consulted on conversion errors and Sales receives completion updates. This prevents Finance and IT each assuming that the other has authorised the final balances.
Common mistake: Marking everyone accountable avoids a difficult conversation but usually recreates the ambiguity that the responsibility matrix was intended to remove.
Official syllabus reference: [1]
19. Risk registers connect threats to responses
A useful project risk register records an uncertain event, its cause, potential effect, owner, response and indicators that trigger action. Distinguish a risk from an issue: a risk may occur, while an issue already requires management. Responses include avoidance, reduction, transfer and acceptance, chosen according to exposure and response cost. Ownership means responsibility for managing the response, not personal blame if the event occurs. Reassess residual risk after treatment because insurance, supplier contracts or controls rarely remove every consequence. Review interdependencies rather than treating each entry as isolated.
Worked example: A migration risk is that incomplete customer identifiers cause failed matching. The data lead owns cleansing and sample tests; an error-rate trigger initiates additional validation. Once the trial conversion fails, the team records an issue and executes the agreed response.
Common mistake: A register containing only red, amber and green labels provides little control when it omits causes, owners and specific response actions.
Official syllabus reference: [1]
20. Switching values expose appraisal fragility
Sensitivity analysis changes an input to determine its effect on an investment result. A switching value identifies the change that reduces NPV to zero, holding specified other assumptions constant. For a proportional reduction in a positive cash-flow stream, divide current NPV by that stream's present value. The result measures tolerance, not the probability of failure. One-variable sensitivity can miss combinations and correlations, such as lower prices occurring alongside weaker volumes. Use switching values to prioritise evidence gathering, then examine coherent scenarios where linked assumptions move together.
Worked example: A project has NPV of $24,000 and discounted sales receipts of $600,000. If all other assumptions remain fixed, a 4% reduction in receipts eliminates NPV. Whether that exposure is acceptable depends on demand evidence and interactions with variable costs.
Common mistake: Calling the smallest switching percentage the most likely risk confuses the project's sensitivity to an assumption with uncertainty about that assumption.
Official syllabus reference: [1]
21. Decision trees value conditional project choices
Decision trees distinguish management choices from uncertain outcomes and place them in the order information becomes available. Work backwards: calculate probability-weighted values at chance nodes and choose the best feasible action at decision nodes. Include research costs and time-consistent discounted cash flows. Information has value when it enables a better subsequent action. Imperfect signals require conditional probabilities rather than treating a favourable test as certain success. Expected value supports decisions across uncertain outcomes, but funding limits, downside tolerance and one-off consequences may justify additional analysis.
Worked example: A pilot costs $10,000 and reveals whether expansion would earn $100,000 or lose $60,000. With equal state probabilities and perfect revelation, conditional expansion has expected value $40,000 after pilot cost, compared with $20,000 for immediate expansion.
Common mistake: Averaging the best outcome from each branch without respecting when information arrives grants management knowledge it does not actually possess.
Official syllabus reference: [1]
22. Debt and equity allocate different claims
Debt creates contractual payments and may impose security and covenant conditions; equity provides a residual claim and usually affects ownership or voting influence. Interest tax relief may make debt attractive, but affordability depends on cash timing and downside resilience. Compare funding over the asset's economic life and include arrangement costs, repayment profiles and refinancing exposure. Equity has a required return even without mandatory dividends. The preferred mix depends on risk, control objectives, funding access and flexibility. A lower quoted interest rate alone cannot establish the lowest overall financing burden.
Worked example: A five-year project generates uneven cash flows, with little cash in its first year. A loan with heavy immediate repayments may be less suitable than staged equity or a repayment profile matching later cash generation, despite offering a lower headline rate.
Common mistake: Treating equity as free because dividends are discretionary ignores investors' required returns, ownership dilution and possible changes in control rights.
Official syllabus reference: [1]
23. Funding maturity should fit asset cash generation
Maturity matching seeks to avoid financing long-lived commitments with funding that must be renewed before the asset generates sufficient cash. Short-term borrowing can appear cheaper while creating refinancing and interest-rate exposure. Leases can spread payments and transfer some residual-value risk, but may impose usage, maintenance or termination conditions. Compare complete after-tax cash flows where relevant, including deposits, purchase options and ownership benefits. Financing suitability also depends on flexibility: an uncertain technology project may not justify an inflexible long-term asset commitment even when scheduled payments appear affordable.
Worked example: A production line generates cash over seven years, but a proposed credit facility expires after twelve months. Management should assess committed longer-term funding or a suitable lease, rather than assume annual renewal will remain available on unchanged terms throughout the asset's life.
Common mistake: Matching the first year's instalment to forecast cash does not address refinancing risk or obligations continuing after the asset becomes obsolete.
Official syllabus reference: [1]
24. Tuckman stages explain team development tensions
Tuckman's forming, storming, norming and performing stages describe common patterns as teams establish relationships and working methods; adjourning recognises closure. The model helps distinguish productive disagreement about roles from persistent destructive conflict. Leaders can clarify purpose during forming, facilitate working rules during storming and support autonomy as reliable coordination develops. Stages are a heuristic rather than a compulsory linear sequence: membership changes or new tasks can reopen earlier issues. High performance also requires psychological safety, complementary capability and accountability, so labelling a stage does not itself solve the problem.
Worked example: Finance and Operations dispute approval rights after joining a new automation team. A facilitated agreement on responsibilities and escalation rules can convert the disagreement into workable norms; telling members simply to behave like a performing team leaves the underlying conflict unresolved.
Common mistake: Assuming storming must be suppressed immediately can prevent the constructive discussion needed to establish clear responsibilities and sustainable team working.
Official syllabus reference: [1]
Manage performance and costs to create sustainable value
25. Controllability shapes responsibility-centre assessment
Responsibility centres classify managerial authority over costs, revenues, profits or investment. Evaluate a manager using measures consistent with decisions they can influence, while separately reporting the centre's full economic performance. An allocated corporate expense may matter to organisational profitability without being controllable by a local manager. Distinguish managerial performance from divisional performance to avoid distorted incentives. Controllability is rarely absolute: managers may influence shared costs without owning them completely. State responsibility assumptions and include relevant quality or service measures so cost reduction does not simply transfer problems elsewhere.
Worked example: A depot manager controls overtime and route scheduling but cannot choose the corporate property lease. Report total depot profit for commercial decisions, while assessing the manager primarily on controllable operating performance and delivery quality rather than unexplained lease-allocation changes.
Common mistake: Removing an uncontrollable cost from a manager's appraisal does not mean the cost disappears from the organisation's assessment of divisional viability.
Official syllabus reference: [1]
26. Residual income corrects a common ROI incentive
Return on investment divides accounting profit by the relevant investment base. Residual income subtracts a capital charge from profit. An investment can exceed the company's required return but reduce a division's existing ROI, encouraging a manager rewarded only on ROI to reject it. Residual income recognises the additional surplus above the charge and can improve goal congruence. However, absolute residual income is affected by divisional size, and both measures depend on accounting policies and asset ages. Neither replaces discounted cash-flow analysis of a project's complete economic life.
Worked example: A division earns $300,000 on $2 million, or 15%. An additional $500,000 produces $60,000, or 12%. With a 10% capital charge, the proposal adds $10,000 residual income even though combined ROI falls to 14.4%.
Common mistake: Rejecting every project below the division's historical ROI can sacrifice investments that earn more than the organisation's actual required return.
Official syllabus reference: [1]
27. Activity-based management targets resource drivers
Activity-based costing assigns resource costs to activities and then to products or customers using drivers that explain consumption. Activity-based management uses that information to change the processes causing cost. Batch setups, order handling and support contacts may explain overhead better than production volume alone. Distinguish a driver rate from an avoidable cash cost: reducing activity does not necessarily remove committed resources immediately. Investigate practical capacity and cost behaviour before claiming savings. The objective is better resource use and profitability, including customer value, rather than merely reallocating the same overhead more precisely.
Worked example: Two products use similar machine hours, but one requires frequent short production runs. A setup-based allocation reveals its greater resource demand. Combining orders may reduce setups, while actual cash savings depend on whether overtime, consumables or staffing commitments can change.
Common mistake: An allocated cost reduction does not automatically become a cash saving when the people, equipment or contracts supporting that activity remain committed.
Official syllabus reference: [1]
28. Target costing translates market price into design limits
Target cost equals an achievable selling price less the required profit. It starts with the market and works backwards into product and process design. A cost gap is the excess of forecast cost over target cost. Value engineering examines how required functions can be delivered more economically without removing benefits customers value. Profit expressed as a margin on selling price differs from a markup on cost, so calculate the target consistently. Concentrate improvement before design commitments lock in expenditure, and include quality, reliability and lifecycle effects rather than pursuing purchase-cost reductions alone.
Worked example: A product can sell for $400 and requires profit of 25% of selling price. Target cost is $300. A forecast cost of $335 creates a $35 gap; redesigning an overcomplicated housing may close part of it without reducing customer-valued accuracy.
Common mistake: Applying a 25% cost markup when the requirement is a 25% sales margin produces the wrong allowable cost and profit target.
Official syllabus reference: [1]
29. Lifecycle costing reveals costs beyond manufacture
Lifecycle costing measures costs across development, production, use-related obligations and withdrawal, rather than concentrating on the manufacturing period. Design decisions often commit substantial future spending before production begins. Include relevant warranty, support, decommissioning and disposal obligations within a clearly stated perspective. Supplier lifetime profitability and customer total ownership cost are related but different measures. A cheaper component may increase failures and service spending enough to worsen lifetime economics. Use discounted cash flows where timing is material, and avoid double counting provisions and the underlying expected cash expenditure in one analysis.
Worked example: A cheaper seal saves $8 per device but increases expected warranty visits by $12 per device over its life. For the supplier's lifecycle profit, the substitution loses $4 per device before considering customer dissatisfaction or additional administration.
Common mistake: A favourable factory unit cost can conceal larger warranty and end-of-life commitments that were caused by the original design choice.
Official syllabus reference: [1]
30. Cost of quality separates prevention from failure
Quality costs are commonly grouped into prevention, appraisal, internal failure and external failure. Prevention seeks to avoid defects; appraisal detects them; internal failure occurs before customer delivery; external failure occurs afterwards. The classification helps test whether early investment reduces more expensive downstream consequences. A higher prevention budget can lower total quality cost. Interpret reductions carefully because recorded failure costs may omit reputation damage or customer effort. Quality measures should include defect frequency and severity, not simply expenditure, since cutting inspection can reduce reported cost while allowing more failures to reach customers.
Worked example: An extra $20,000 of supplier training reduces rework by $15,000 and warranty spending by $18,000. Total measured quality cost falls by $13,000, even though prevention expenditure rises and the organisation spends more before production starts.
Common mistake: Treating every increase in quality expenditure as inefficiency ignores the possibility that prevention substitutes for more expensive internal and external failures.
Official syllabus reference: [1]
31. Lean and JIT depend on reliable flow
Lean management seeks to remove activities that consume resources without adding customer value, including waiting, excess movement, rework and overproduction. Just-in-time arrangements reduce inventories by synchronising supply and production with demand. Low inventory exposes process weaknesses but also reduces the buffer against supplier disruption. Reliable quality, short setup times and dependable deliveries support implementation. Do not equate lean with indiscriminate capacity cuts: resilience and customer service remain valuable. Evaluate total system effects because a local efficiency measure, such as maximising batch size, can increase waiting and inventory elsewhere.
Worked example: A factory reduces changeover time from two hours to twenty minutes, making smaller batches economical. Inventory and waiting fall without forcing staff to run large batches for apparent machine efficiency, while selected safety stocks remain for an unreliable imported component.
Common mistake: Removing inventory before improving supply reliability can expose customers to disruption without achieving the stable process flow that JIT requires.
Official syllabus reference: [1]
32. Benchmarking compares processes on equivalent terms
Benchmarking compares performance or processes with a reference such as another business unit, a competitor or a functionally similar organisation. Its purpose is to identify the practices explaining a gap, not merely produce a league table. Normalise differences in scale, service mix, quality and measurement definitions. A lower unit cost may reflect a narrower service promise rather than superior efficiency. Process benchmarking can reveal transferable methods even outside the industry. Set improvement targets only after determining whether the reference process is feasible and valuable in the organisation's operating conditions.
Worked example: One repair centre closes tickets twice as quickly as another, but excludes time awaiting parts. After aligning definitions, much of the gap disappears. The remaining difference is traced to better diagnostic triage, providing a specific process improvement to test.
Common mistake: Copying the best reported number without aligning definitions can impose an unrealistic target or reward a reduction in the service actually delivered.
Official syllabus reference: [1]
33. Leadership style should fit the task and team
Directive leadership specifies methods and decisions; participative leadership involves staff in choices; delegation gives suitable decision authority; transformational leadership builds commitment to a broader purpose. These approaches can coexist rather than form a single permanent personality choice. Match direction and support to task novelty, competence, urgency and consequences of error. Experienced employees may benefit from discretion, while new staff may require demonstration and coaching. Participation is useful when distributed knowledge improves decisions, but consultation without genuine influence can undermine trust. Reassess the approach as capability and circumstances change.
Worked example: During an unfamiliar system cutover, a leader assigns clear roles and escalation steps. After staff demonstrate reliable competence, routine exception decisions are delegated. The change preserves accountability while preventing temporary implementation controls from becoming unnecessary permanent supervision.
Common mistake: Assuming one leadership style is universally best ignores differences in task risk, employee capability and the amount of coordination required.
Official syllabus reference: [1]
34. Expectancy theory diagnoses weak incentive systems
Vroom's expectancy theory links motivation to expectancy, instrumentality and valence. Employees must believe effort can improve performance, performance will produce the promised outcome, and that outcome is valuable to them. A weakness in any link can undermine an incentive scheme. Training and tools support expectancy; consistent reward rules support instrumentality; understanding employee preferences supports valence. The model helps diagnose behaviour without assuming money motivates everyone equally. Targets must also avoid rewarding gaming or outcomes outside employees' influence, since credible rewards can still drive the wrong organisational behaviour.
Worked example: Technicians value a bonus but believe obsolete diagnostic equipment makes the target unattainable. Increasing the bonus may have little effect. Better tools and achievable task standards address the expectancy problem, while consistent payment rules preserve confidence in the reward.
Common mistake: Increasing reward size alone will not repair an incentive system when employees doubt their ability to achieve the required performance.
Official syllabus reference: [1]
35. Empowerment requires authority and usable information
Empowerment gives employees meaningful discretion over decisions affecting their work, supported by capability, information and accountability. Delegation should specify outcomes, decision limits, available resources and escalation conditions. Retaining approval for every routine choice can make nominal empowerment ineffective. Conversely, assigning responsibility without authority transfers blame rather than decision power. Financial controls can be designed around risk-based limits and exception review instead of universal pre-approval. Evaluate results using quality and customer outcomes as well as speed, and develop competence before expanding discretion over more consequential decisions.
Worked example: Service agents may authorise replacement parts up to a defined budget when diagnostic evidence meets agreed criteria. Exceptions go to a specialist. Agents receive cost and warranty information, and managers review patterns afterwards instead of approving every ordinary replacement.
Common mistake: Telling employees to take ownership while withholding decision rights and relevant information creates responsibility without the practical means to act.
Official syllabus reference: [1]
36. Expected loss and tail exposure answer different questions
Expected loss weights each possible loss by its probability and sums the results. It is useful for comparing recurring exposures but can conceal a rare outcome that threatens liquidity or continuity. Present the distribution or selected adverse scenarios alongside the average. Value at risk describes a loss quantile over a stated horizon and confidence level; it does not describe the severity of all losses beyond that point. Expected shortfall addresses average loss in the specified tail. All such measures depend on assumptions, data and treatment of correlated events.
Worked example: A process has a 99% chance of no loss and a 1% chance of a $5 million loss. Expected loss is $50,000, but a business with only $400,000 available liquidity must separately assess whether it can survive the adverse event.
Common mistake: An affordable expected loss does not establish that the organisation can finance the largest plausible loss or continue operating after it.
Official syllabus reference: [1]
Measure performance
37. DuPont analysis connects margin and asset use
A basic DuPont relationship decomposes return on capital employed into operating profit margin multiplied by capital turnover, provided definitions are consistent. Margin shows profit earned per sales unit; turnover shows revenue generated per capital unit. The decomposition helps distinguish pricing and cost problems from inefficient capital deployment. Use comparable periods and preferably suitable average capital figures. Asset age, revaluation, leasing and acquisitions can distort comparisons. A higher return may arise from underinvestment or a temporary disposal, so interpret the components alongside service capability and sustainability of the underlying performance.
Worked example: A business earns a 10% operating margin and generates sales equal to twice capital employed, producing 20% ROCE. If margin falls to 8% while turnover stays at two, ROCE falls to 16%, pointing investigation toward sales profitability.
Common mistake: Comparing ROCE without examining margin and turnover can hide whether the underlying issue concerns operating profitability or the amount of capital deployed.
Official syllabus reference: [1]
38. The cash conversion cycle explains working-capital pressure
The cash conversion cycle approximates the time between paying for operating inputs and collecting customer cash. It combines inventory days plus receivables days less payables days. Use cost of sales for inventory and, where suitable purchase data are unavailable, a clearly stated approximation for payables; use credit revenue for receivables. Average balances generally improve interpretation, while seasonal closing balances can mislead. A longer cycle can absorb cash even during profitable growth. Reducing it must preserve supplier relationships, stock availability and commercially appropriate customer credit rather than simply shifting pressure elsewhere.
Worked example: Inventory is held for 50 days, customers pay after 45 days and suppliers are paid after 35 days. The cycle is 60 days. Reducing customer collection time by ten days releases cash without changing profit, assuming sales and other conditions remain unchanged.
Common mistake: A profitable business can still face a cash shortage when inventory and receivables expand faster than supplier funding and cash reserves.
Official syllabus reference: [1]
39. Gearing and interest cover reveal different exposures
Gearing measures dependence on debt relative to a stated capital base, while interest cover compares an earnings measure with interest expense. Definitions vary, so specify whether gearing uses debt/equity or debt/(debt plus equity), and whether values are book or market based. High gearing increases exposure to financial commitments, while falling cover signals reduced earnings capacity to meet interest. Neither measure directly proves cash affordability. Examine maturity, variable interest rates, covenant definitions and cash conversion. There is no universal safe ratio independent of the business model and financing terms.
Worked example: Operating profit of $900,000 and interest expense of $300,000 give three times interest cover. That figure does not reveal a $1 million principal repayment due next month, so liquidity and the debt maturity schedule still require separate assessment.
Common mistake: Applying a memorised gearing threshold without checking the ratio definition, industry cash stability or contractual terms can produce an unsupported risk conclusion.
Official syllabus reference: [1]
40. Balanced scorecards link leading and lagging indicators
The balanced scorecard commonly links financial, customer, internal-process, and learning-and-growth perspectives. It translates strategy into connected objectives, measures, targets and initiatives. Financial outcomes are often lagging indicators, while capability and process measures may signal future results. Proposed causal links must be tested rather than assumed: more training hours do not necessarily improve service. Include clear definitions and owners, and avoid excessive measures that dilute priorities. Sustainability objectives can be embedded where strategically relevant, with both absolute and intensity measures when they reveal different effects.
Worked example: A service strategy links diagnostic competence to first-time repair, then customer retention and contract margin. Measuring assessed competence is more informative than training attendance alone, and the company should verify whether improved repair outcomes actually predict retention in its customer base.
Common mistake: A dashboard with many unrelated indicators is not a strategic scorecard merely because it contains both financial and non-financial numbers.
Official syllabus reference: [1]
41. Scenario analysis differs from stress testing
Scenario analysis explores coherent combinations of assumptions, such as demand, input prices and exchange rates under different economic conditions. Stress testing examines performance under a specified adverse event or severe condition. Neither requires assigning probabilities unless an expected-value conclusion is intended. Define the performance measure, horizon and management actions explicitly. Reverse stress testing starts with an unacceptable outcome and asks what circumstances could cause it. These methods complement single-variable sensitivity by showing interactions and practical resilience, but their conclusions remain conditional on the scenarios selected.
Worked example: A distributor tests simultaneous weak demand, slower customer payments and higher import costs. A separate reverse stress asks what sales decline would exhaust its cash facility after planned mitigations. Both analyses address resilience that a single expected-profit figure would conceal.
Common mistake: Presenting a stressed outcome as an expected forecast confuses conditional severity analysis with a probability-weighted estimate of future performance.
Official syllabus reference: [1]
42. Business-model risk mapping follows dependencies
Business-model risk analysis traces how value creation depends on customers, suppliers, technology, partners and revenue mechanisms. A subscription model, for example, may depend on retention, uptime and a cloud provider rather than shipment volume alone. Identify concentrations and common dependencies that can cause several failures together. Link each risk to an operational indicator and a financial consequence, then assess feasible responses. Diversification is effective only if alternatives are genuinely independent and usable. A backup supplier relying on the same critical subcomponent may leave the underlying concentration largely unchanged.
Worked example: A monitoring service has two branded hosting suppliers, but both use the same regional data centre. Mapping the dependency reveals a common outage exposure, prompting evaluation of a genuinely separate recovery location rather than assuming two contracts provide resilience.
Common mistake: Counting suppliers without tracing shared infrastructure can create a false impression of diversification and understate the financial effects of one common failure.
Official syllabus reference: [1]
43. IFRS 15 allocates revenue to performance obligations
IFRS 15 recognises revenue through identifying the contract, identifying performance obligations, determining transaction price, allocating that price and recognising revenue as obligations are satisfied. Distinct goods and services generally receive allocation using relative standalone selling prices, subject to relevant exceptions. Recognition follows transfer of control at a point in time or over time when the applicable criteria are met. Billing and cash receipt do not determine performance. Bundled equipment and support can therefore generate immediate equipment revenue and a contract liability for unperformed service. Explain assumptions before applying simplified calculations.
Worked example: A $90,000 package contains equipment priced separately at $80,000 and service at $20,000. Relative allocation gives $72,000 and $18,000. If equipment control transfers immediately but service lasts twelve months, the service amount is recognised as that obligation is satisfied.
Common mistake: Recognising an entire prepaid package on delivery overlooks any distinct service obligation that remains to be performed after the equipment transfers.
Official syllabus reference: [1]
44. IFRS 16 separates lease liability and asset consumption
Under IFRS 16, a lessee generally recognises a right-of-use asset and lease liability for a lease, subject to applicable exemptions and scope requirements. The liability initially reflects the present value of relevant unpaid lease payments; subsequent accounting includes interest and payment reductions. The asset is depreciated under the applicable requirements and assessed for impairment. This often replaces a single operating lease expense with depreciation and interest, affecting reported EBITDA and leverage. A lease does not create new cash merely through recognition, so explain accounting changes separately from financing affordability and contractual obligations.
Worked example: A qualifying lease begins with a $100,000 liability, a 5% annual discount rate and a $30,000 year-end payment. First-year interest is $5,000 and closing liability is $75,000, while depreciation of the right-of-use asset is calculated separately.
Common mistake: An EBITDA increase after lease recognition does not by itself show improved cash generation; the contractual lease payments still require funding.
Official syllabus reference: [1]
45. IAS 38 distinguishes research from qualifying development
Research expenditure is expensed under IAS 38. Development expenditure is capitalised only from the date all applicable criteria are demonstrated, including technical feasibility, intention and ability to complete or use or sell, probable future benefits, adequate resources and reliable measurement. Previously expensed expenditure is not reinstated merely because the project later qualifies. Capitalised costs must be attributable to preparing the asset for use; training and promotional expenditure are not automatically included. Amortisation begins when available for use for a finite-life asset, with impairment considered under the relevant requirements.
Worked example: A software project incurs $60,000 before development recognition criteria are demonstrated and $140,000 afterwards. Only the qualifying later expenditure enters the intangible asset. If available for use on 1 December, amortisation begins then even if marketing delays the commercial launch.
Common mistake: Later technical success does not permit management to capitalise research or development expenditure that was correctly expensed before the recognition criteria were met.
Official syllabus reference: [1]
46. IAS 36 compares carrying amount with recoverable amount
An impairment arises when an asset's carrying amount exceeds recoverable amount. Under IAS 36, recoverable amount is the higher of value in use and fair value less costs of disposal. Value in use reflects discounted cash flows within the standard's measurement boundaries, using assumptions consistent with the asset and discount rate. When independent cash inflows cannot be identified for one asset, assessment uses an appropriate cash-generating unit. Impairment recognition affects profit and carrying values without itself creating a cash payment. Goodwill impairment has particular allocation requirements and is not subsequently reversed.
Worked example: An asset carries at $500,000. Its value in use is $430,000 and fair value less disposal costs is $460,000. Recoverable amount is $460,000, so impairment is $40,000 rather than the $70,000 difference from value in use alone.
Common mistake: Using the lower of the two recovery measures overstates impairment because recoverable amount reflects the better available route to recovering value.
Official syllabus reference: [1]
47. IAS 37 separates obligations from future operating plans
A provision requires a present legal or constructive obligation from a past event, a probable outflow of resources and a reliable estimate under IAS 37. Measure the best estimate of settlement, discounting where the time value effect is material. A future operating intention or expected trading loss does not itself create a present obligation. A contingent liability generally receives disclosure unless outflow is remote, subject to the standard's requirements. Distinguish uncertain timing or amount from an absence of obligation. Recognition should reflect evidence, rather than management's desire to smooth future profits.
Worked example: Products already sold carry warranty obligations. Expected repair expenditure can support a provision using suitable evidence. A plan to replace next year's production equipment does not create a provision merely because management considers replacement commercially necessary and has prepared a budget.
Common mistake: Budgeting a future expenditure does not create a liability unless a past event has already established the required present obligation.
Official syllabus reference: [1]
48. IAS 21 distinguishes monetary and historical-cost balances
Foreign-currency transactions are initially translated into functional currency using the transaction-date exchange rate, with appropriate approximations where permitted. Monetary items such as receivables and payables are generally retranslated at the reporting-date closing rate, with exchange differences generally recognised in profit or loss. Historical-cost non-monetary items retain the transaction-date rate. Functional currency reflects the primary economic environment rather than management preference. Distinguish transaction remeasurement from translating a foreign operation for consolidation, where different requirements and other comprehensive income may apply. Always state how the exchange rate is quoted.
Worked example: A company records a €10,000 payable when one euro costs $1.10, giving $11,000. At year-end one euro costs $1.15, so the payable becomes $11,500 and an exchange loss of $500 is recognised under the ordinary monetary-item treatment.
Common mistake: Retranslating every foreign-currency balance at the closing rate ignores the distinction between monetary liabilities and non-monetary assets measured at historical cost.
Official syllabus reference: [1]
Manage internal and external stakeholders
49. IFRS 10 control depends on power and returns
Control under IFRS 10 requires power over an investee, exposure or rights to variable returns, and the ability to use power to affect those returns. Voting ownership is important but does not settle every case: contractual rights, dispersed holdings and substantive decision rights may change the analysis. Protective rights alone do not confer power over relevant activities. A controlled subsidiary is generally consolidated from the date control is obtained, combining assets, liabilities, income and expenses before eliminations. Assess the substance of decision-making arrangements rather than relying solely on the investment's legal label.
Worked example: An investor holds 45% of voting rights while the remaining shareholders are widely dispersed and rarely participate. It may control the investee, but the conclusion requires evidence about practical decision power and relevant activities rather than assuming that any minority percentage prevents consolidation.
Common mistake: Treating ownership above or below 50% as the entire control assessment overlooks substantive contractual rights and other relevant power arrangements.
Official syllabus reference: [1]
50. Goodwill depends on acquisition measurement choices
In a straightforward business combination, goodwill equals consideration transferred plus recognised non-controlling interests, less the fair value of identifiable net assets acquired. More complex acquisitions can require additional elements, such as a previously held interest. Eligible NCI may be measured at fair value or proportionate share of identifiable net assets, producing full or partial goodwill respectively. Acquisition-date fair value adjustments can change future depreciation and tax balances. Goodwill is not amortised under IFRS but is subject to impairment requirements. Acquisition-related professional fees are generally expensed rather than included in goodwill.
Worked example: An acquirer pays $2.4 million for 80% of a business with identifiable net assets worth $2.5 million. If NCI fair value is $600,000, full goodwill is $500,000. Proportionate NCI of $500,000 would instead produce goodwill of $400,000.
Common mistake: Assuming goodwill always equals purchase price less the parent's share of net assets ignores the effect of the selected NCI measurement basis.
Official syllabus reference: [1]
51. Intragroup inventory profit waits for external sale
A group cannot earn profit by selling inventory to itself. Eliminate intragroup sales and purchases, and remove profit remaining in closing inventory so inventory reflects group cost. Convert markup on cost carefully: a 25% markup is profit of 25/125 of selling price. For an upstream sale by a subsidiary, the unrealised-profit adjustment reduces that subsidiary's result and can affect NCI. For a downstream parent sale, the profit adjustment belongs to the parent. Distinguish current-year unrealised profit from the release of previous-year adjustments when inventory is later sold externally.
Worked example: A subsidiary sells goods to its parent for $150,000 at a 20% markup on cost. One third remains unsold. Total profit is $25,000 and unrealised profit is approximately $8,333, reducing group inventory and the subsidiary profit used for NCI allocation.
Common mistake: Applying a markup percentage directly to transfer revenue treats markup as margin and overstates the profit requiring elimination from closing inventory.
Official syllabus reference: [1]
52. Associates use significant influence and equity accounting
An associate is an investee over which the investor has significant influence rather than control or joint control. IAS 28 includes a rebuttable presumption associated with holding 20% or more voting power, but actual influence must be assessed. Under the equity method, the investment starts at cost and is adjusted for the investor's share of subsequent profit, other comprehensive income and distributions, with relevant acquisition and impairment adjustments. Dividends reduce the carrying amount rather than create a second recognition of the same earnings. Associates are not consolidated line by line as subsidiaries.
Worked example: An investor pays $900,000 for a 30% associate. Ignoring acquisition adjustments and impairment, the associate's subsequent $200,000 profit adds $60,000 to the investment, while $50,000 total dividends reduce it by $15,000, producing a $945,000 carrying amount.
Common mistake: Recognising both the share of associate profit and dividends as income double counts earnings that the equity method has already recognised.
Official syllabus reference: [1]
53. Transfer-price floors include opportunity cost
For an internal supply decision, the selling division's economic minimum transfer price is incremental cost plus the contribution sacrificed from the best alternative use of capacity. With genuine spare capacity and no displaced business, opportunity cost may be zero. At full capacity, foregone external contribution matters, adjusted for costs avoided on internal trade. The buying division's ceiling usually reflects its best feasible external alternative, allowing for quality and logistics differences. A negotiating range exists when the seller's minimum does not exceed the buyer's maximum. Separate internal managerial prices from jurisdiction-specific tax requirements.
Worked example: A component costs $30 to make and sells externally for $50 with $4 avoidable distribution cost. At full capacity, minimum internal price is $46. If the buyer can source externally for $53, the internal negotiating range is $46–$53.
Common mistake: Using variable production cost alone at full capacity ignores the external contribution sacrificed when internal demand displaces a profitable customer order.
Official syllabus reference: [1]
54. Dual pricing can resolve divisional incentive gaps
A transfer-pricing system should support group decisions, fair performance assessment and appropriate divisional autonomy. Negotiated prices can share gains when both divisions have credible alternatives and sufficient information. Cost-based prices may be practical without external markets but can transfer inefficiency or distort incentives. Dual pricing credits the seller and charges the buyer on different bases, with a central reconciliation, to encourage beneficial trade. It can improve local incentives but complicates measurement and may weaken cost discipline. Use it transparently and distinguish managerial adjustments from consolidated profit, where internal transfers are eliminated.
Worked example: A seller needs a full-cost-based credit to support its performance target, while charging that amount would cause the buyer to reject a group-beneficial order. Dual pricing can bridge the gap centrally, provided management explains the reconciliation and retains pressure to improve inefficient costs.
Common mistake: Different internal credits and charges do not create extra group profit; they change divisional incentives and require a transparent central reconciliation.
Official syllabus reference: [1]
55. Integrated reporting connects six capitals to value creation
Integrated reporting explains how strategy, governance, performance and prospects create, preserve or erode value over time. The six capitals commonly considered are financial, manufactured, intellectual, human, social and relationship, and natural. Organisations need not treat every capital as equally material or force all effects into monetary values. The essential task is to explain connections, dependencies and trade-offs within the business model. A concise integrated report should connect resource use and stakeholder relationships with future prospects, rather than append disconnected sustainability statistics to financial statements. It does not replace applicable statutory reporting obligations.
Worked example: Automation improves manufactured capability and financial margins but requires retraining and changes employees' roles. An integrated explanation connects investment, human-capital development, service reliability and future cash generation, while acknowledging temporary disruption and resource consumption rather than reporting each metric in isolation.
Common mistake: Listing all six capitals without explaining dependencies and trade-offs misses the connected value-creation account that integrated reporting is intended to provide.
Official syllabus reference: [1]
56. ISSB and GRI use different materiality perspectives
ISSB standards focus on sustainability-related risks and opportunities that could reasonably affect an entity's prospects and inform primary users of general purpose financial reports. GRI focuses on an organisation's significant impacts on the economy, environment and people. These perspectives can overlap and complement each other, but their materiality assessments are not interchangeable. Jurisdictional adoption determines mandatory application; publication of a framework does not establish a universal legal requirement. Explain reporting boundaries, methods and governance, and distinguish absolute impacts from intensity indicators. Avoid claiming full compliance from a small collection of selected metrics.
Worked example: Water scarcity may be financially material because it threatens a factory's production, while the factory's withdrawals may also materially affect local communities. Reporting can address both perspectives, using consistent evidence while explaining the different reasons the issue matters to users.
Common mistake: Calling one sustainability topic material for one framework does not automatically establish the same reporting conclusion under every other framework.
Official syllabus reference: [1]
57. Stakeholder mapping guides communication choices
Stakeholder mapping identifies affected parties and assesses factors such as influence, interest, needs and vulnerability. A power-interest matrix can help prioritise engagement, but low formal power does not remove a stakeholder's legitimate interests or exposure to harm. Tailor content, channel and timing to the decision and audience. Directors may need options and financial implications; operational staff need responsibilities and procedures; customers need clear service information. Communication is a process requiring feedback and confirmation of understanding. Protect confidential information and avoid giving inconsistent factual accounts simply because audiences have different preferences.
Worked example: For a repair-policy change, directors receive cost and risk options, technicians receive diagnostic rules and escalation routes, and customers receive accessible explanations of coverage. Feedback from technicians reveals an ambiguous exception before conflicting messages reach customers in daily service interactions.
Common mistake: Sending the same detailed finance paper to every stakeholder can obscure practical instructions and does not demonstrate that recipients understand the change.
Official syllabus reference: [1]
58. BATNA and reservation values define bargaining limits
A BATNA is the best alternative to a negotiated agreement. It informs the reservation value beyond which accepting a deal is worse than taking that alternative. The zone of possible agreement exists where the parties' acceptable terms overlap. Analyse total terms, including quality, timing, risk and payment, rather than price alone. Distinguish underlying interests from opening positions so trades can create value. Relative bargaining power depends partly on credible alternatives and dependence. Ethical negotiation requires accurate representation of material facts and realistic authority to commit, rather than inventing competing offers.
Worked example: A buyer can obtain equivalent equipment elsewhere for $80,000 but would incur $5,000 installation costs. A supplier offering installation can be competitive above $80,000. Both parties should compare total alternatives before assuming that the quoted purchase prices define the bargaining limit.
Common mistake: An ambitious opening position is not the same as a reservation value, which should reflect a credible alternative and complete deal terms.
Official syllabus reference: [1]
59. Thomas–Kilmann modes distinguish conflict responses
The Thomas–Kilmann framework describes competing, collaborating, compromising, avoiding and accommodating using different degrees of assertiveness and cooperation. Collaboration seeks a solution addressing underlying interests; compromise exchanges concessions; competing may suit urgent non-negotiable decisions. Avoidance can provide time for evidence gathering, while accommodation may preserve a relationship where the issue matters more to the other party. No mode is universally best. Diagnose whether conflict concerns facts, goals, resources, roles or relationships, then choose a proportionate response. Collaboration takes time and requires willingness to share information, not merely a meeting invitation.
Worked example: Sales and Operations disagree over delivery promises. Collaboration examines demand uncertainty and capacity to create differentiated service tiers. A compromise that simply halves the requested lead-time reduction may leave promises infeasible and fails to address the underlying scheduling problem.
Common mistake: Calling every negotiated midpoint collaboration confuses sharing concessions with developing a solution that addresses the parties' underlying interests and constraints.
Official syllabus reference: [1]
60. Ethical reporting requires identifying and addressing threats
Professional ethics includes integrity, objectivity, competence and due care, confidentiality, and professional behaviour. Threats such as self-interest, intimidation, familiarity, advocacy and self-review can compromise compliance. Identify the specific threat, evaluate its significance and take action that removes or reduces it appropriately, following applicable professional requirements. A manager's request does not justify misleading reporting. Verify facts, explain the reporting consequence, seek correction and use appropriate governance channels where needed. Document significant judgments and protect confidential information. The objective is a defensible, truthful professional response, not merely recording disagreement while issuing misleading information.
Worked example: A manager whose bonus depends on margin asks Finance to exclude recurring support costs from a supposedly complete profitability report. Finance explains the distortion, offers a clearly labelled supplementary measure, and seeks correction or appropriate escalation if the misleading presentation remains.
Common mistake: Adding a private note of disagreement does not make a knowingly misleading report acceptable when users still receive the distorted information.
Official syllabus reference: [1]