The Rubric —
Fully Decoded
The official rubric has four criteria and four bands. This tool unpacks exactly what Poor, Adequate, Good, and Excellent look like — in general, per criterion, and specifically for each of the five Nisala scenarios. Use this to calibrate your own pitch before submission.
Analytical Insight
Does your reasoning demonstrate genuine understanding of Nisala's business?This is the core intellectual test. It asks: have you correctly identified a specific, significant operational issue? Have you traced its causes to root level (not surface symptoms)? Does your cause-effect chain hold together logically? Does your use of the Pre-seen show genuine understanding rather than repetition of facts?
Communication Clarity
Is your pitch organised, flowing, and easy to follow — with slides that support, not replace, your words?This tests both structural organisation and slide quality. A pitch should flow as a coherent story — Issue → Causes → Solutions — with clear transitions between sections. Slides must amplify your message, not duplicate your speech or present walls of text. Examiners are assessing whether someone unfamiliar with your work could follow your argument in real time.
Persuasion & Presence
Does your delivery feel confident, credible, and professionally compelling?This criterion is about how you come across — not whether you're a naturally gifted speaker. Confidence, pacing, eye contact with the camera, and a tone that treats the examiner as a business audience (not a teacher) all contribute. The key word in the Excellent descriptor is "professional presence" — you are presenting as a finance executive, not as a student reciting notes.
Integration of External Data
Does your pitch connect Nisala's situation to the broader industry, market, and commercial context?This criterion tests commercial awareness — the ability to situate Nisala's internal problems within their external context. This includes Sri Lankan apparel industry dynamics, global benchmarks, competitor comparisons, buyer expectations, ESG pressures, and economic factors. External data must be clearly connected to your analysis — not dropped in as decoration at the end.
Analytical Insight
Issue framing · Root cause logic · Pre-seen integration · Managerial judgementIssue is either not stated, stated so broadly it has no meaning, or is factually wrong. Reasoning is absent or circular. No cause-effect chain. Pre-seen data either ignored or misquoted.
Issue is identifiable but vague or incompletely framed. Some correct reasoning present but logic chain has gaps. Pre-seen facts referenced but not interpreted. Integration between slides is partial.
Issue clearly defined with business impact articulated. Causes are genuine root causes with clear logical links. Solutions directly address identified causes. Pre-seen evidence used purposefully throughout.
Sharp framing that goes beyond naming the issue to interpreting its implication. Cross-functional or systemic root causes identified. Solutions show understanding of feasibility and trade-offs. Pre-seen data is interpreted, not just cited.
Communication Clarity
Structure · Flow · Transitions · Slide quality · ConcisenessDisorganised content with no clear narrative thread. Examiner cannot follow what is being argued. Slides are cluttered, text-heavy, or actively contradict the spoken content.
Basic structure present — issue, causes, solutions are identifiable. Flow is uneven with some abrupt transitions. Slides partially support the argument but have excess text or unclear layout.
Well-organised with a clear narrative from opening to close. Transitions signal movement between slides. Slides are concise and support the argument. Explanations are direct and free of jargon.
Highly coherent narrative where every sentence serves the argument. Slides feel purposefully designed — each one could stand alone as a clear visual summary of its section. Polished pacing, no unnecessary words.
Persuasion & Presence
Confidence · Engagement · Pacing · Tone · Professional credibilityDelivery is visibly hesitant or monotone. Student reads from slides or notes entirely. No eye contact. Examiner is not engaged. Argument is not presented persuasively — it is recited.
Delivery is understandable with reasonable pace. Some engagement with the examiner. Student occasionally glances at notes. Argument is presented rather than read, but without conviction.
Confident and credible delivery. Student speaks with authority about the subject. Argument is clearly persuasive — the examiner understands why action is needed. Professional tone maintained throughout.
Strong professional presence — delivery feels like a genuine boardroom presentation, not an exam performance. Compelling tone, varied pacing, and a pitch structure that builds naturally to a persuasive conclusion. The examiner is convinced.
Integration of External Data
Industry benchmarks · Market context · Commercial awareness · Nisala vs. sectorNo external reference at all. Analysis treats Nisala as if it exists in isolation — no awareness that the Sri Lankan garment industry, global benchmarks, or buyer dynamics are relevant to any of the issues raised.
Some external points mentioned but they feel like add-ons rather than integrated reasoning. References are generic ("garment industry faces cost pressures") without being specific or connected to the issue being analysed.
Relevant external insights clearly connected to the analysis. At least one specific benchmark, industry trend, or competitive reference that directly supports the issue or recommendation being made.
Well-chosen industry and contextual cues that enhance every dimension of the analysis. External data is not an afterthought — it is woven into the issue framing, cause analysis, and solution justification.
Scenario 1 — Production Efficiency & Capacity Utilisation
Analytical Insight · 35 marks"Nisala has production problems." Issue not quantified, no metric cited. Causes listed include "workers need training" and "buy better machines" — generic fixes with no Pre-seen grounding. No link to the 78% efficiency figure or the 85% target.
Mentions "sewing line efficiency below target" with some reference to downtime. Identifies style changeovers as a cause. Solutions are generic (train operators, schedule maintenance) but not connected explicitly to root causes. Pre-seen Section 6.3 not cited.
States 78% vs 85% target with financial impact (overtime cost disproportionate to output gain). Identifies all three Pre-seen root causes: changeovers, reactive maintenance, and cutting-sewing transfer delays. Each solution clearly traces to a cause.
Explicitly identifies Root Cause 3 (cutting-to-sewing delay) as a cross-departmental coordination failure — not a sewing problem. Interprets the 2.05→1.93 output-per-hour drop as evidence that overtime is financially inefficient, not just operationally stretched. Solutions reference specific managers (Ruwan Fernando) and are graded by implementation speed.
Scenario 2 — Fabric Utilisation & Cost Control
Analytical Insight · 35 marks"Nisala wastes fabric." No mention of the 58% COGS weighting. Recommends "introduce marker planning" — contradicting the Pre-seen which already states marker planning has been introduced. Shows no engagement with the actual Pre-seen content.
Identifies cutting waste as the issue with a general cost reference. Mentions marker planning exists but doesn't diagnose the gap (batch-end check vs. pre-cut approval). Rework noted as a quality issue but not linked to secondary fabric consumption.
Anchors issue in the 58% COGS figure and FY2024 margin dip to 27%. Identifies the monitoring gap (batch-end only) and 4.5% rework as a secondary fabric cost driver. Solutions are Pre-seen grounded and zero-cost oriented.
Connects all three causes into a coherent system: marker planning is retrospective → waste happens mid-run → no real-time variance data means no correction → rework compounds the damage. Interprets the FY2024 margin recovery as evidence of what's possible when fabric control improves, creating a forward-looking financial argument for the solutions.
Scenario 3 — Real-Time Costing & Data Visibility
Analytical Insight · 35 marksSlides explain what standard costing is and how variance analysis works — pure textbook content with no Nisala application. The issue of the timing lag is never stated. Recommends "implement ERP immediately" as the solution without addressing the process gap.
Correctly identifies that variance data arrives late. References "manual systems" as a cause. Solutions mention weekly reporting but don't specify how it would work in practice. Misses the supervisor capability gap entirely — focuses only on the systems dimension.
States the 4–5 week lag clearly and its consequence. Identifies both systems gap (manual disconnected data) and reporting design (monthly cadence not fit for operational use). Pre-seen Section 7.5 control weaknesses explicitly referenced. Solutions are realistic and escalating.
Identifies the dual gap — systems (no live data link) AND behavioural (supervisors have no mechanism to use cost data even if available). Interprets this as a design failure, not a technology gap. Solutions therefore address both dimensions: weekly reporting AND a per-style cost card to build supervisor habit. Frames the pilot as generating proof-of-concept data for Sandun Perera's investment decision.
Scenario 4 — Working Capital & Financial Sustainability
Analytical Insight · 35 marks"Nisala has working capital problems." No distinction between inventory days (rising), receivable days (stable), and payable days (stable). Recommends invoice factoring as the primary solution — financing the symptom rather than fixing the operational cause.
Identifies inventory as the pressure point. States inventory days are rising but doesn't trace this to procurement behaviour. WIP accumulation mentioned as a production issue but the cash-conversion implication not articulated. Solutions address receivables (stable metric) rather than inventory (the actual problem).
Correctly isolates inventory days (101.6, worsening) as the specific driver. Links to over-procurement and WIP build-up as operational causes. Three-year trend data used. Solutions are operationally grounded — reorder point, Kanban WIP limit — with a commercial receivables lever.
Makes the cross-scenario link explicit: WIP accumulation between cutting and sewing (identified in Scenario 1 as a production problem) is also a cash problem — cut panels awaiting sewing are cash committed to inventory that cannot be invoiced. Interprets the FY2025 cash recovery to LKR 85m as partial — "still below the LKR 90m FY2022 baseline, despite revenue growing 33%." This reframes the issue from a short-term blip to a structural trend.
Scenario 5 — Ethics, Workforce & Community
Analytical Insight · 35 marksPure ethical argument with no business data. "Nisala must treat its workers better." No reference to the overtime productivity data, rework rate connection, or compliance risk. Recommends generic CSR initiatives (community donations, sustainability report) entirely disconnected from the overtime issue.
Identifies overtime as the issue and notes worker fatigue. References the +15% hours / +8.3% output data. Causes include "no planning ahead" but misses the narrow upskilling gap and the welfare monitoring absence. Solutions focus on overtime limits but without a structural fix for peak demand.
Frames issue as dual financial and ethical. All three causes identified: overtime as default capacity lever, narrow upskilling limiting flexibility, and absent welfare monitoring. Solutions address structural demand (smoothing), workforce flexibility (cross-training), and formal welfare protocol. Integrity-skills dimension explicitly acknowledged.
Connects the 4.5% rework rate directly to overtime fatigue — framing rework as a measurable financial consequence of welfare failure, not just an operations metric. Identifies that the upskilling programme, though positive, is a precondition for cross-training that hasn't been completed yet. Frames the welfare protocol as generating documented evidence for retail buyer audits — a commercial argument, not just an ethical one.
All 5 Scenarios — Communication Clarity Band Descriptors
The same structural principles apply across all scenarios — what varies is the specific narrative coherence expected per scenario typeNo discernible flow. Examiner cannot tell what the issue is until slide 2 or 3. Slides filled with dense text. Student reads from slides verbatim. Causes appear on slide 1, issue on slide 3. No transitions.
Three-slide structure identifiable. Issue, causes, solutions appear in correct sequence. Flow is choppy — jumps between ideas without bridging. Slides have 3–4 bullets each. Some spoken content not on slides and vice versa.
Clear narrative from opening to close. Each slide has a dominant headline element. Verbal transitions signal movement between slides. Student speaks to examiner, uses slides as visual anchors. Time is well-managed across three sections.
Highly coherent narrative where every sentence earns its place. Slides and speech feel co-designed. The closing sentence of slide 3 resolves the problem stated in slide 1 — the pitch has a complete arc. No sentence could be removed without weakening the argument.
Persuasion & Presence — Band Descriptors with Scenario Notes
Delivery principles are universal; what "convincing" sounds like varies by scenario typeReading slides. Visible nerves. Monotone delivery. No eye contact. Argument not made persuasively — it is reported. Examiner not engaged. For Scenario 5 specifically: dry recitation of ethical facts without any sense of genuine concern for the workforce.
Mostly delivered from memory. Reasonable pace. Some engagement. For financial scenarios (1–4): the numbers are stated but their significance isn't emphasised. For Scenario 5: welfare concern is present but the business case isn't articulated alongside it.
Confident, credible delivery. Student speaks with authority. For financial scenarios: key numbers are emphasised with a brief pause. For Scenario 5: the dual financial-ethical framing is delivered with conviction — showing the student believes both arguments simultaneously.
Strong professional presence. Compelling tone and pacing. The opening line creates immediate engagement. For all scenarios: the closing sentence is delivered with total conviction and lands cleanly. For Scenario 5: the argument for worker welfare sounds genuinely felt, not performed.
Scenario 1 — External Integration by Band
No external reference. Analysis treats production efficiency as a purely internal matter with no competitive or market context.
"The garment industry is competitive and efficient operations are important." Generic. Not connected to 78% vs 85% gap or to a specific competitor.
References the 85% global efficiency benchmark. Notes Sri Lankan retailers shifting to smaller, more frequent collections (Pre-seen trend) as the driver of more frequent changeovers. Mentions one named competitor.
Places the efficiency gap within Section 3.1's list of five strategies competitive manufacturers already use — framing Nisala's 78% as below the global competitive floor. Uses SMED as an industry-recognised response. Notes LankaStyle and UrbanThread competitive differentiation as context for why line efficiency matters specifically for Nisala's market position.
Scenario 2 — External Integration by Band
No market context. Fabric waste treated as a purely internal cost issue without acknowledging the currency depreciation dynamic that makes it more urgent for Sri Lankan importers specifically.
Mentions "rising fabric costs" in the industry without connecting to the LKR depreciation mechanism or explaining why this specifically compounds Nisala's import-dependent cost structure.
Explicitly links the FY2024 margin dip to LKR depreciation and imported fabric costs. Notes UrbanThread differentiates on fabric utilisation efficiency — making this a competitive priority. References digital marker planning software as the global benchmark Nisala's manual approach falls short of.
Frames fabric efficiency as the intersection of an internal control gap AND an external currency risk — Nisala cannot control import prices but can control utilisation. The double-squeeze argument (currency raises fabric cost while tightening margins) is uniquely Sri Lankan and highly commercially aware. Connects UrbanThread's competitive position to a specific commercially observable threat for Nisala.
Scenario 3 — External Integration by Band
No external context at all. The costing lag is analysed entirely as an internal technical problem with no reference to how competitors or industry benchmarks address real-time data.
Mentions "modern businesses use ERP" without connecting this to Nisala's SME context or the "selective technology" qualifier the Pre-seen places on automation recommendations.
Uses Pre-seen Section 3.1 — real-time production monitoring is Strategy 4 that competitive manufacturers already use — to position Nisala's monthly reporting cycle as a competitive disadvantage. References affordable SME ERP options in Sri Lanka's apparel sector.
Frames the data lag as simultaneously a competitive gap (vs global benchmarks) AND a compliance risk (delayed visibility means Nisala cannot prove cost control to buyers conducting supplier audits). Connects the cost performance card solution to management accounting best practice — positioning it as what any professionally-managed apparel firm of Nisala's size would already have.
Scenario 4 — External Integration by Band
Working capital analysis has no market or industry context. The LKR interest rate environment, retail payment norm dynamics, or inventory management benchmarks are not referenced anywhere.
Notes that retailers typically pay slowly without contextualising this against the Sri Lankan retail sector's concentration and payment norms. Kanban mentioned but not placed in an industry context.
References Sri Lankan retailer concentration as the leverage dynamic — Nisala's growing volume gives it increasing bargaining power that has not yet been exercised on payment terms. Notes rising post-2022 interest rates as amplifying the cost of the LKR 200m short-term borrowings.
Connects the working capital problem to Nisala's growth phase specifically — as a company scaling from SME to mid-market, the cash conversion cycle naturally stretches unless proactively managed. References that Kanban-based WIP management is the standard operational finance tool in garment manufacturing globally, making Nisala's absence of it a measurable gap against industry practice rather than an unusual recommendation.
Scenario 5 — External Integration by Band
Ethical argument presented without any external standards, industry norms, or commercial context. No reference to buyer codes, ILO standards, or ESG trends in the Sri Lankan retail sector.
Mentions "ethical sourcing is increasingly important" without citing specific standards, buyer requirements, or quantifying the commercial risk of non-compliance for a company in Nisala's market position.
References that retailers are increasingly monitoring ethical sourcing (Pre-seen stated trend) and that Nisala currently meets only local legal minimums — creating a future compliance gap. Cites ILO research connecting sustained overtime to measurable defect rate increases. Notes 40% lower turnover in companies with strong ethical practices.
Frames ethical workforce management as a commercial necessity, not just a moral choice — using SDG 8 (Decent Work), WRAP certification, and evolving buyer audit requirements to show that what is currently legally compliant may become commercially disqualifying. Connects the welfare protocol solution specifically to buyer audit documentation requirements — the protocol isn't just the right thing to do, it is what retail buyers are beginning to require as evidence.
Capacity Utilisation
Analytical Insight
"Production is inefficient." No metric. Causes are "workers need training." No Pre-seen evidence used. Solutions invented rather than drawn from company context.
78% efficiency mentioned. Style changeovers identified as a cause. Solutions present but not mapped to specific causes. Pre-seen Section 6.3 not referenced. Cross-departmental cause missed entirely.
78% vs 85% target stated with overtime cost disproportionality articulated. All three Pre-seen causes identified and each solution explicitly maps to a cause. Issue is financially anchored.
Cutting-to-sewing delay framed as a cross-departmental failure. Output-per-hour drop (2.05→1.93) interpreted as evidence overtime is financially inefficient, not just operationally stretched. Solutions reference specific managers and are graded by ease of implementation.
Communication Clarity
Slide 1 lists background facts. Causes and solutions appear mixed across slides. No opening hook. Student reads efficiency statistics without framing their significance.
Three-slide structure followed. Issue stated but without financial framing on Slide 1. Transitions between slides are abrupt. Key insight (cross-dept cause) buried in a bullet rather than highlighted.
Opens with "78% vs 85% — hundreds of lost units daily." Transitions signal movement: "Now let me explain why." Each solution sentence explains what it does and why it's feasible. Closes with a summary sentence.
Root Cause 3 (the cross-dept failure) is introduced with a deliberate pause and emphasis: "And third — the one that's hardest to see from the sewing section alone…" This framing makes the structural insight land as a revelation, not a list item. Closing sentence ties efficiency target back to slide 1 problem.
Persuasion & Presence
Reads efficiency statistics from slides. No emphasis on the financial implication of the 7-point gap. Recommendations presented as possibilities ("could consider") rather than confident recommendations.
Mostly delivered from memory. Numbers stated without emotional or business urgency. "We should improve changeovers" rather than "Changeover standardisation can cut downtime by 40% in 4 weeks — the fastest available efficiency gain."
Opens confidently with the 78%/85% contrast framed as a daily cost. Solutions presented as recommendations with justifications. "I am recommending three actions that together address all three root causes within this quarter."
Uses pause after the cross-departmental insight to let it register. Closes with conviction: "These steps move Nisala toward 85% — the competitive threshold — without capital investment. I recommend we act on all three this quarter." Sounds like a boardroom recommendation, not an exam answer.
Integration of External Data
No industry benchmarks. Analysis is entirely internal. No reference to what competitor manufacturers achieve or what the Sri Lankan market demands.
"Efficient production is important in the garment industry." Generic. No specific benchmark, no named competitor, no connection to Nisala's competitive position specifically.
85% global efficiency benchmark used in Slide 1. Retailer trend (smaller, more frequent collections) drives changeover frequency — a Pre-seen trend made external. LankaStyle and UrbanThread named with their competitive differentiation noted.
Places Nisala's gap within Pre-seen Section 3.1's framework — competitive manufacturers already do this, Nisala doesn't yet. SMED used as an industry-standard term that signals commercial knowledge. The retailer trend to smaller collections is linked directly to the changeover cause — external context justifies urgency, not just provides background.
Cost Control
Analytical Insight · 35 marks
"Nisala wastes fabric." No COGS weighting cited. Recommends introducing marker planning — contradicts the Pre-seen. Shows student has not read the material.
58% COGS mentioned. Marker planning gap identified as "not used effectively." Rework treated as a quality issue only — the secondary fabric consumption link is missed. Solutions not mapped to specific causes.
58% COGS and FY2024 margin dip anchor the financial case. Three causes correctly identified — monitoring gap, rework as secondary waste, no real-time variance data. Solutions are zero-cost and process-based.
Causes linked as a system: retrospective monitoring enables waste, which combines with rework to exceed standard allowances, and no variance tracking means no correction is possible mid-batch. FY2024 margin recovery used as evidence of what better control achieves — a forward financial argument for the solutions.
Communication Clarity · 25 marks
Slide 1 explains what fabric cost is. Actual issue (monitoring gap) not stated until slide 2. No financial hook in the opening.
Correct structure but the 58% COGS significance is mentioned as a fact rather than used as a financial hook. Rework and marker planning treated as separate issues on slide 2 rather than as linked causes.
"Fabric is 58% of COGS — the single largest cost driver. When we waste it, the margin loss is direct and immediate." Causes presented as three distinct mechanisms. Solutions each get one sentence of justification.
Three causes flow as a system narrative in slide 2 — the student doesn't list them, they connect them: "Marker planning is checked too late, so waste happens uncorrected; rework then compounds that waste; and no real-time tracking means neither problem is visible during production." The system framing makes slide 2 memorable.
Persuasion & Presence · 20 marks
Fabric cost statistics read from slide. No sense of urgency. The FY2024 margin story not used as a compelling opening hook.
Issue and causes delivered correctly but without conviction. "Nisala could improve fabric monitoring" rather than "We need to close this monitoring gap before the next peak season or we risk another margin dip."
Opens with the FY2024 margin dip as a live risk: "In FY2024 we saw what happens when fabric cost control slips — margin fell below target. The underlying monitoring gap is still there." This creates urgency and positions the student as commercially aware.
"These three solutions cost nothing to implement and can be running by the end of this week. The question isn't whether Nisala can afford to do them — it's whether Nisala can afford not to, given that UrbanThread is already competing on exactly this dimension." Confident, commercially specific, and memorable.
Integration of External Data · 20 marks
No market context. Fabric waste treated as internal only — the currency depreciation amplifier not mentioned.
"Fabric costs are rising globally." Generic — not connected to LKR depreciation or to Nisala's specific import-dependency structure.
LKR depreciation named as the amplifier of fabric waste cost. UrbanThread's fabric utilisation differentiation cited as a competitive context. Digital marker planning software referenced as the global benchmark.
The double-squeeze framing: "Nisala cannot control import prices — but it can control utilisation. In a market where the LKR depreciation raises fabric costs and UrbanThread already differentiates on this metric, fabric utilisation efficiency is not an optional improvement — it is the primary cost lever available to management." Highly commercially specific and integrated throughout all three slides.
Data Visibility
Analytical Insight · 35 marks
Slides define standard costing and variance analysis concepts. The timing lag is never stated as the issue. "Implement ERP" as the solution — without addressing any process gap first.
Monthly reporting lag identified. "Manual systems" named as a cause. Misses the supervisor capability gap — solutions focus on IT systems only, not on building supervisors' ability to use cost data operationally.
4–5 week lag stated with its consequence (damage is irreversible by then). Both systems gap and reporting design named. Pre-seen Section 7.5 control weaknesses cited. Solutions are process-first, technology-later and escalating.
Dual gap: systems (no live link) AND behavioural (no mechanism for supervisors to use data). Solutions therefore address both — weekly tally changes the data flow, per-style cost card builds supervisor habit. Frames the tablet pilot as generating a business case for Sandun Perera, not just a technology experiment.
Communication Clarity · 25 marks
Slide 1 is a definition of standard costing. The actual business issue (the lag and its consequence) is on slide 2. No financial hook.
Correct structure. Monthly lag stated on Slide 1 but not translated into a concrete consequence ("weeks after" without specifying what that means for a typical production run).
"By the time the Finance Manager sees an adverse variance, the run generating it is complete and the damage is locked in." This sentence translates the lag into a business consequence that is immediately understandable.
Solutions in Slide 3 are presented in escalating order of investment — "First, zero cost. Second, one week of Finance time. Third, a low-cost pilot." This sequencing makes the pitch feel actionable and proportionate, and directly responds to the "short-term" constraint the question imposes.
Persuasion & Presence · 20 marks
Accounting terminology delivered flatly. The audience — if positioned as a business executive — is not engaged by slides that explain variance analysis methodology.
Lag stated as a fact without a business framing. "The variances are monthly" rather than "we are always correcting yesterday's problem — never preventing today's."
"We have good controls — but they tell us what went wrong last month, not what's going wrong right now." This reframes the issue positively (good foundation) while clearly identifying the gap — more persuasive than pure criticism.
Closes with a forward-looking recommendation that references the pilot: "In six weeks, we can have data from one line that tells us whether real-time visibility actually changes supervisor behaviour. The cost is negligible. The upside — closing a control gap the Pre-seen identifies explicitly — is significant." Confident, specific, and grounded.
Integration of External Data · 20 marks
No external context. Costing lag treated as a purely internal technical problem.
"Modern companies use ERP" — too generic. Not calibrated to Nisala's SME status or the "selective technology" Pre-seen qualifier.
Pre-seen Section 3.1 Strategy 4 (real-time monitoring) used as the benchmark. Mid-tier Sri Lankan manufacturers adopting affordable ERP modules noted as context showing Nisala is becoming an outlier.
Frames the data lag as a compliance risk — buyers conducting supplier audits increasingly require cost control evidence, and monthly variance reports do not provide the granularity needed. This elevates the issue from an internal efficiency gap to a commercial and compliance imperative.
Financial Sustainability
Analytical Insight · 35 marks
"Nisala has working capital problems." No distinction between the three WC ratios. Recommends factoring as primary solution — financing the symptom, not fixing the operational cause.
Inventory identified as the pressure point. Over-procurement mentioned. WIP accumulation treated as a production issue without articulating the cash-conversion implication. Solutions address receivables (stable metric) rather than inventory (rising).
Correctly isolates inventory days (101.6, worsening trend) as the driver. Over-procurement and WIP accumulation identified as operational causes. Reorder-point solution and Kanban WIP limit are operationally grounded. Early payment discount addresses receivables lever.
WIP accumulation explicitly linked to cash conversion: "Cut panels in the buffer are cash committed but uninvoiceable." FY2025 cash recovery reinterpreted as still below FY2022 baseline despite 33% revenue growth — structural trend, not a blip. Kanban framed as simultaneously an operations and a finance intervention.
Communication Clarity · 25 marks
Working capital ratios listed on slide 1 without narrative. Examiner cannot distinguish which metric is the problem until slide 2. No opening hook that frames why this matters now.
Inventory days trend stated. Cash fall noted. But receivable and payable stability not contrasted — examiner cannot tell the student has diagnosed which metric is the actual problem.
"Receivable days and payable days are stable. The pressure is specifically in inventory days — rising from 96 to 101.6 over three years. That is where the cash is being consumed." This sentence does the diagnostic work clearly and concisely.
Opens with the cash story arc: "Cash fell from LKR 90m to 60m as revenue grew. It partially recovered — but only to 85m. We're 5% below our 2022 cash position despite a 33% revenue increase. That tells us working capital efficiency is not keeping pace with growth." This narrative makes the financial stakes vivid and immediate.
Persuasion & Presence · 20 marks
Balance sheet ratios read from slides. No sense of urgency. Financial recommendations presented as finance-department suggestions rather than operational priorities.
Correct content delivered with neutral tone. The connection between rising inventory and short-term borrowings not emphasised as an escalating cost risk.
Connects the inventory problem to interest costs: "Every extra day of inventory is funded by LKR 200m of short-term borrowings at current rates. Reducing inventory days directly reduces that financing cost." Makes the solution financially compelling, not just operationally tidy.
"The early payment discount offer to our top two accounts could release LKR 30–50m in cash — that's more than the 1–2% discount cost. We're currently paying interest on borrowings to fund credit we're extending for free. That arithmetic doesn't work." Specific, financially precise, and delivered as a recommendation that the examiner can act on.
Integration of External Data · 20 marks
No market context. Working capital analysis entirely internal. Interest rate environment or retail payment norms not referenced.
Notes retailers pay slowly as a generic fact. Kanban mentioned without placing it in an industry context as a standard practice.
Sri Lankan retailer concentration cited as the leverage argument for payment term renegotiation. Post-2022 interest rate environment noted as amplifying borrowing costs. Kanban referenced as industry-standard WIP management.
Growth-phase framing: "Companies scaling from SME to mid-market face this working capital stretch predictably — it is a known transition risk in the manufacturing sector. The solution set — reorder points, WIP limits, payment incentives — is standard practice at Nisala's target scale. We are not inventing new solutions; we are implementing what the next stage of growth requires." Commercially sophisticated and contextually grounded.
Community Responsibility
Analytical Insight · 35 marks
"Nisala must treat its workers better." Pure moral argument, no business data. No reference to overtime productivity loss, rework rate connection, or compliance risk. Recommends CSR initiatives entirely disconnected from the overtime issue.
Overtime identified as issue. +15%/+8.3% data cited. Causes include "no planning ahead" but the narrow upskilling gap and welfare monitoring absence are missed. Solutions focus on overtime limits without addressing the structural demand peak that forces overtime in the first place.
Dual financial and ethical framing. All three causes identified and solutions address all three: demand smoothing (structural), cross-training (flexibility), welfare protocol (safeguards). Integrity Skills dimension explicitly acknowledged in slide 3.
Connects 4.5% rework directly to overtime fatigue — making rework a measurable financial consequence of welfare failure. Identifies upskilling as a precondition for cross-training not yet completed. Frames welfare protocol as buyer audit documentation — a commercial argument. Solutions therefore have both operational and commercial justifications.
Communication Clarity · 25 marks
Slide 1 is a values statement. No business data. Examiner cannot connect the ethical argument to Nisala's operational reality. Slides read like a corporate social responsibility brochure.
Correct structure. The dual financial-ethical framing is present but the connection between them is not clearly articulated on Slide 1. Examiner must infer the link between overtime hours and rework rate.
Opens with both arguments in one sentence: "Nisala's reliance on overtime to meet peak demand is not just a welfare concern — the +15% hours that deliver only +8.3% more output is also a financial inefficiency." This single sentence makes the dual case immediately and clearly.
Solutions in slide 3 are explicitly layered: "Solution 1 reduces the need for overtime structurally. Solution 2 increases the flexibility to absorb peak demand without overtime. Solution 3 protects workers when some overtime remains unavoidable." This layering shows the pitch has been designed — not assembled — to address the issue at every level.
Persuasion & Presence · 20 marks
Ethical argument delivered flatly as a duty statement. No genuine conviction. Business data absent so the argument feels theoretical rather than grounded.
Welfare concern articulated with some warmth but the business case is weak or absent. Sounds like an ethics lecture rather than a management recommendation.
Both financial and ethical arguments delivered with conviction. The student sounds as if they genuinely believe both: "This isn't just the right thing to do — the rework rate tells us fatigued workers produce worse output. Managing welfare well is managing operations well."
Closes with a line that integrates both dimensions: "Nisala has 320 people depending on this company for their livelihoods. Managing their welfare responsibly is not a cost — it is what protects the quality of output, the loyalty of a skilled workforce, and the commercial relationships that depend on ethical sourcing. I am recommending we formalise this — this week, at zero cost." Conviction, specificity, and genuine professional presence.
Integration of External Data · 20 marks
No external standards, buyer requirements, or ESG trends referenced. Argument is based entirely on internal moral obligation without commercial context.
"Ethical sourcing is increasingly important" without specifying which buyers, which standards, or what the consequence of non-compliance would be for Nisala specifically.
Pre-seen stated trend (retailers monitoring ethical sourcing) cited explicitly. ILO overtime-fatigue research connected to Nisala's 4.5% rework rate. 40% lower turnover statistic in ethical companies cited as a Gampaha District workforce retention argument.
Frames ethical management as commercially necessary through buyer audit evolution: "SDG 8, WRAP certification, and evolving retail codes of conduct are moving in one direction. What meets legal minimum today may fail buyer audit tomorrow. Nisala currently has no documented welfare protocol — that is the gap this recommendation closes, at zero cost, before it becomes a commercial liability." External data is not added for marks — it is the commercial argument that justifies the urgency of action.