B-CAP · June 2026
Nisala Garments — Complete Verbal Pitch Guide
5 Scenarios · Issue · Causes · Solutions · Full Rubric · Common Mistakes
B-CAP Verbal Pitch · June 2026

All 5 Scenarios —
Complete Preparation Guide

Everything you need for the verbal pitch in one place. For each scenario: a fully worked pitch with issue, causes, solutions, and sample script — plus the complete rubric showing exactly what Poor, Adequate, Good, and Excellent look like for each criterion, and the 3 most common mistakes students make on that scenario.

5
Scenarios · fully worked
20
Rubric bands per scenario
13
Short-term solutions
15
Common mistakes dissected
Scenario Area 01
Production Efficiency &
Capacity Utilisation
Sewing line inefficiency is Nisala's most visible operational weakness — with 78% line efficiency against an 85% target, the gap costs real output every single day. A pitch on this area sits at the heart of the Chapters A and B syllabus.
Lean / BottlenecksDowntime ManagementStyle ChangeoverLabour ProductivityChapter A
1

Slide 1 — What Is the Issue?

Issue definition · Business impact · Pre-seen evidence
The Issue: Nisala's sewing line efficiency stands at 78% against a target of 85% — a 7 percentage-point gap that, combined with 6–8% unplanned machine downtime, is eroding output capacity and driving excessive overtime costs during peak periods when efficiency falls further to an implied rate below standard.
⚠️
Why This Matters for Nisala: At LKR 2.2 billion revenue with 22% of COGS tied to direct labour, every hour of idle sewing time is a direct cost increase per unit. Overtime during peak periods increases labour input by 15% but only boosts output by 8.3% — meaning each peak-period unit costs proportionally more to produce. This compresses the already tight 29% gross margin.
📊
Pre-seen Evidence: Output per labour hour drops from 2.05 units (normal) to 1.93 units (peak). Capacity utilisation rises from 85% to 92% under overtime, but efficiency deteriorates. Three named root causes of downtime: style changes, minor machine adjustments, and delayed material transfer from cutting to sewing (Section 6.3).
2

Slide 2 — Why Is It Occurring?

Root causes · Fishbone categories · 5 Whys drill-down · Quantitative & qualitative
Root Cause 01 Quantitative

Style Changeovers Consume Excessive Productive Time

Each new style requires machine reconfiguration, thread changes, template updates, and operator retraining — taking 3–4 hours per changeover. As retailers demand smaller, more frequent collections, changeover frequency has increased. The original facility layout, designed for batch production not line-based runs, amplifies the disruption.

3–4 hrs per changeover · no standardised SMED protocol
Fishbone (Ishikawa) Analysis
Process
No pre-staging protocol — changeover setup begins after the previous run ends, not before
Facility layout (batch-designed) forces physical relocation of materials between each style
People
Operators must relearn settings for each style from memory — no standardised changeover card exists
No designated "changeover specialist" role — all operators stop production simultaneously
Management
Order scheduling does not group similar styles sequentially to minimise changeover frequency
No changeover time KPI tracked — therefore no management pressure to reduce it
5 Whys Drill-Down
Why 1
Why does sewing line efficiency drop during style changes?
Because the entire line stops for 3–4 hours while machines are reconfigured and operators prepare for the new style.
Why 2
Why does reconfiguration take 3–4 hours?
Because there is no pre-staged changeover kit — materials, templates, and settings are gathered reactively after production stops.
Why 3
Why are changeovers not pre-staged?
Because no changeover protocol or advance scheduling system exists to trigger preparation before the current run ends.
Why 4
Why has no protocol been established?
Because changeover time is not tracked as a KPI, so management has no visibility of its cumulative cost on daily output.
Why 5
Why is changeover time not tracked?
Because the production reporting system is manual and batch-oriented — it captures output quantities, not time lost to non-productive transitions.
Root cause identified: The absence of a changeover time KPI within the manual reporting system means the cumulative cost of unmanaged style transitions is invisible to management — so no pressure exists to standardise or reduce it.
Root Cause 02 Quantitative

Reactive Maintenance Causes Unplanned Machine Downtime

Machine maintenance is "periodic but not formally tracked" (Pre-seen). Without a scheduled preventive maintenance programme, minor faults accumulate into unplanned breakdowns. Recurring faults are not logged, analysed, or eliminated — resulting in 6–8% sewing machine downtime and ~5% cutting machine downtime.

6–8% sewing downtime · ~5% cutting downtime
Fishbone (Ishikawa) Analysis
Equipment
No machine-specific maintenance log — failure history not recorded per machine
Ageing machines operating beyond optimal service intervals without documented inspection
Management
No preventive maintenance schedule in place — maintenance triggered by breakdown, not calendar
Limited maintenance documentation explicitly named as a control weakness (Pre-seen Section 7.5)
People
Operators not trained to identify early warning signs — machine health is assessed visually, not systematically
No maintenance technician on permanent shift — repair response delays production restart
5 Whys Drill-Down
Why 1
Why do sewing machines break down unplanned during production?
Because maintenance is reactive — machines are only serviced after faults occur, not before they develop.
Why 2
Why is maintenance reactive rather than preventive?
Because there is no formal maintenance schedule — the timing of servicing is decided ad hoc by supervisors, not set in advance.
Why 3
Why does no formal maintenance schedule exist?
Because maintenance documentation is limited (Pre-seen Section 7.5) — without records of past failures, a data-driven schedule cannot be built.
Why 4
Why is maintenance documentation limited?
Because operators lack a simple logging tool and the habit of recording machine status — the culture treats maintenance as a crisis response, not a routine discipline.
Why 5
Why hasn't this habit been built?
Because there is no KPI linking downtime frequency to machine-level maintenance records, and therefore no accountability for supervisors to track and improve it.
Root cause identified: A cultural and systemic gap — maintenance is treated as crisis management, not operational discipline. Without machine-level logs and a downtime KPI, the accountability chain needed to shift from reactive to preventive maintenance does not exist.
Root Cause 03 Qualitative

Cross-Departmental Coordination Failure: Cut Panels Not Reaching Sewing On Time

The Pre-seen explicitly names delayed material transfer from cutting to sewing as a root cause of sewing machine downtime. This is a coordination failure — when cut panels are not staged and ready, sewing operators sit idle despite being available. The facility layout (originally designed for batch not line production) creates physical distance and ambiguous handover ownership between the two departments.

Cross-dept coordination gap · no handover protocol · layout mismatch
Fishbone (Ishikawa) Analysis
Process
No formal handover target — no agreed time by which cut panels must reach sewing at the start of each shift
No pull system — sewing does not signal cutting when capacity is ready, so mismatches accumulate
Environment
Facility layout designed for batch production — physical distance between cutting and sewing areas creates movement delay and unclear staging zones
Management
Cutting and sewing managed as separate departments with no shared daily output target linking them
No cross-departmental KPI — each supervisor is measured on their own section's output, not the handover efficiency
5 Whys Drill-Down
Why 1
Why do sewing operators sit idle waiting for cut panels?
Because cut panels are not ready in the buffer area when sewing lines are ready to begin — there is a timing mismatch between the two departments.
Why 2
Why is there a timing mismatch?
Because there is no agreed handover schedule — the cutting section does not know when sewing needs panels, and sewing does not communicate readiness to cutting.
Why 3
Why is there no handover schedule?
Because cutting and sewing are treated as independent departments — their daily plans are not synchronised as part of a single production flow.
Why 4
Why are they treated as independent departments?
Because the organisational structure places a separate supervisor over each section with no shared accountability metric — the system does not incentivise coordination.
Why 5
Why has this structural gap not been addressed as Nisala scaled?
Because the original batch production model tolerated inter-stage buffers — as Nisala transitions to line-based production at higher volumes, the coordination requirement intensifies but the structure has not evolved to match it.
Root cause identified: The organisational model has not kept pace with the production model transition. Batch production tolerated coordination gaps; line-based production at scale cannot. The structural disconnect — two separate supervisors with no shared KPI — is the enabling condition for sewing idle time.
3

Slide 3 — What Can Nisala Do?

2–3 short-term, realistic actions · Directly address the causes
Solution 01 → Addresses Cause 01

Implement SMED-Inspired Changeover Reduction for Top 3 Styles

Without major investment, Nisala can reduce changeover time by standardising pre-staging of materials, tools, and machine settings before production stops. A simple "changeover kit" prepared by a designated operator while the current style is finishing can cut idle time from 3–4 hours to under 2 hours. Starting with the top 3 most frequent style transitions makes this immediately actionable and measurable.

Low cost · Implementable within weeks
Solution 02 → Addresses Cause 02

Introduce a Basic Weekly Preventive Maintenance Schedule with Logbooks

A simple machine log tracking last service, noted faults, and next scheduled check — maintained by machine operators and reviewed weekly by the Production Manager (Ruwan Fernando) — can prevent minor issues from becoming downtime events. A one-page maintenance card per machine is a low-cost, high-impact control. This directly addresses the Pre-seen's identified gap of "limited preventive maintenance documentation."

Paper-based · Immediate implementation
Solution 03 → Addresses Cause 03

Establish a Daily Cutting-to-Sewing Handover Target with Supervisor Sign-Off

Introduce a simple daily production plan that specifies the number of cut panels the cutting section must deliver to sewing by a set time (e.g., by 9:00 AM for morning production). A brief end-of-shift handover log signed by both the cutting and sewing supervisors creates accountability without requiring system investment. This directly addresses the cross-departmental coordination breakdown identified in the Pre-seen.

Zero cost · Process change only
Integration of External Data — 20 Mark Criterion
  • Globally, competitive garment manufacturers target line efficiency above 85% as standard practice — Nisala at 78% sits below the industry threshold for sustainable margin performance.
  • Sri Lankan retailers' shift toward smaller, more frequent collections (a Pre-seen trend) directly increases changeover frequency — making SMED-type solutions an industry-recognised response to this market shift.
  • The apparel industry's SMED (Single Minute Exchange of Die) approach is well-documented as applicable to sewing line changeovers — even without automation, process-standardised changeovers in mid-sized factories typically achieve 30–40% time reductions.
  • UrbanThread Manufacturing (competitor) differentiates on fabric utilisation efficiency, while LankaStyle competes on capacity — improving line efficiency is a way for Nisala to build competitive advantage on both fronts simultaneously.
Sample Spoken Script — 5 Minutes
Slide 1 (~1:30)
"The issue I want to address today is Nisala's sewing line efficiency, which currently sits at 78% against a target of 85%. That 7-point gap may sound small, but at 4,800 garments per day capacity, it represents hundreds of units of lost daily output. More critically, when Nisala relies on overtime to recover this during peak periods, hours increase by 15% while output only grows 8.3% — meaning each unit costs more to produce at exactly the moment margins are under the most pressure."
Slide 2 (~2:00)
"Three causes are driving this. First, style changeovers — each one takes 3 to 4 hours of productive time, and as retailers demand more frequent new styles, these changeovers are happening more often. Second, machine downtime of 6 to 8%, driven by reactive rather than preventive maintenance — the Pre-seen explicitly notes that maintenance documentation is limited. And third — the one that's hardest to see from the sewing section alone — delayed material transfer from cutting to sewing. When cut panels aren't ready on time, sewing operators sit idle even though they're available to work. This is a coordination failure between two departments, not just a sewing problem."
Slide 3 (~1:30)
"Three practical actions Nisala can take immediately. One — implement pre-staged changeover kits for the top three style transitions. This can cut changeover time below two hours at minimal cost. Two — introduce a one-page weekly maintenance log per machine, reviewed by the Production Manager. Low cost, but it converts reactive maintenance into preventive practice. Three — establish a daily cutting-to-sewing handover target with supervisor sign-off. A simple paper protocol that creates accountability for panel delivery timing — no systems investment required. Together, these address all three causes and can meaningfully move efficiency toward the 85% target within the current quarter."
📋

Full Rubric — Scenario 1: Production Efficiency

All 4 criteria · All 4 bands · What each level looks like for this specific scenario
🎯
The Excellent unlock: Identifying that Root Cause 3 (cutting-to-sewing delay) is a cross-departmental coordination failure — not a sewing problem. This single insight separates Good from Excellent on Analytical Insight and demonstrates integrated business thinking that examiners specifically reward.
🔍 Analytical Insight 35 marks
Poor
0–14

"Production is inefficient." No metric. Causes are "workers need training." No Pre-seen engagement. No link to the 78%/85% figures or the 85% target.

Adequate
15–21

78% efficiency mentioned. Style changeovers identified. Solutions generic — not mapped to causes. Pre-seen Section 6.3 not cited. Cross-departmental cause missed entirely.

Good
22–28

78% vs 85% stated with overtime cost disproportionality articulated (+15% hours, +8.3% output). All three Pre-seen causes identified. Each solution explicitly maps to a cause.

Excellent
29–35

Cutting-to-sewing delay framed as a cross-departmental coordination failure, not a sewing problem. Output-per-hour drop (2.05→1.93) interpreted as evidence overtime is financially inefficient. Solutions reference specific managers and are graded by implementation speed.

🗂️ Communication Clarity 25 marks
Poor
0–10

Slide 1 lists background facts. Causes and solutions mixed across slides. No opening hook. Student reads statistics without framing their significance.

Adequate
11–15

Three-slide structure followed. Issue stated but without financial framing on Slide 1. Transitions abrupt. Cross-departmental cause buried in a bullet rather than highlighted.

Good
16–20

Opens with "78% vs 85% — hundreds of lost units daily." Transitions signal movement. Each solution sentence states what it does and why it's feasible. Closes with a summary sentence.

Excellent
21–25

Root Cause 3 introduced with 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 ties efficiency target back to Slide 1.

🎙️ Persuasion & Presence 20 marks
Poor
0–8

Reads efficiency statistics from slides. No emphasis on the financial implication of the 7-point gap. Recommendations presented as possibilities ("could consider").

Adequate
9–12

Mostly from memory. Numbers stated without urgency. "We should improve changeovers" rather than a specific time-bound recommendation with a feasibility justification.

Good
13–16

Opens confidently with the 78%/85% contrast as a daily cost. Solutions presented as recommendations. "I am recommending three actions that address all three root causes within this quarter."

Excellent
17–20

Pause after 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."

🌐 Integration of External Data 20 marks
Poor
0–8

No industry benchmarks. Entirely internal analysis. No reference to what competitive manufacturers achieve or what the Sri Lankan market demands.

Adequate
9–12

"Efficient production is important in the garment industry." Generic — no specific benchmark, no named competitor, no connection to Nisala's competitive position specifically.

Good
13–16

85% global efficiency benchmark used in Slide 1. Retailer trend (smaller, more frequent collections) drives changeover frequency. LankaStyle and UrbanThread named with their competitive differentiation noted.

Excellent
17–20

Places Nisala within Pre-seen Section 3.1's framework — competitive manufacturers already do this, Nisala doesn't yet. SMED as an industry-standard term. Retailer trend directly linked to changeover cause — external context justifies urgency, not just provides background.

⚠️

Common Mistakes — Scenario 1

Errors students consistently make on Production Efficiency pitches
✗ Weak version
"Nisala has production inefficiency problems which affect output and costs." The issue is stated too broadly — "production inefficiency" covers everything and analyses nothing. No specific metric, no impact figure, no Nisala context.
Analytical Insight: Poor → Adequate
✓ Strong version
"Sewing line efficiency at 78% against the 85% target means Nisala is losing hundreds of units of daily output — and recovering it through overtime that costs 15% more hours for only 8.3% more units." Specific metric, specific gap, financial consequence linked.
Why it matters: The rubric rewards "sharp issue framing" and "insightful use of Pre-seen." A vague issue statement signals you haven't studied the numbers — examiners notice immediately.
✗ Weak version
Only addressing sewing-side causes — recommending operator training or machine investment — while missing entirely that the cutting-to-sewing transfer delay is one of the three named Pre-seen causes of downtime. The analysis stays within one department.
Analytical Insight: caps at "Good" — misses key Pre-seen insight
✓ Strong version
Explicitly identify the cross-departmental coordination failure — "Root cause 3 is not a sewing problem, it's a planning and handover problem between cutting and sewing." This is the analytically sophisticated insight that separates Good from Excellent.
Why it matters: The Pre-seen names this explicitly in Section 6.3. Spotting a cross-functional root cause demonstrates integrated business thinking — exactly what the Analytical Insight criterion at 35 marks is testing.
✗ Weak version
"Nisala should invest in automated sewing machines and a new ERP production monitoring system." Technically valid ideas — but completely disproportionate for a mid-sized garment company scaling from batch to line production. Signals no understanding of Nisala's SME constraints.
Persuasion & Presence + Integrity: Poor — "grand strategy" flag
✓ Strong version
Solutions are zero or low cost, process-based, and implementable within weeks — changeover kits, paper maintenance logs, supervisor sign-off protocols. The Pre-seen says technology should be adopted "selectively" — solutions must respect that qualifier.
Why it matters: The official guidance explicitly warns against "grand strategy" solutions. Recommending ERP for a company with manual documentation culture is not just unrealistic — it signals you're writing a generic answer, not one grounded in Nisala's reality.
Scenario Area 02
Fabric Utilisation &
Cost Control
Fabric accounts for 58% of Nisala's COGS — the single largest cost driver. Any movement in fabric wastage directly flows through to gross margin. With margin already at 29% and under pressure from currency-driven import costs, this is the most financially material scenario.
Fabric = 58% COGSMarker PlanningUsage VarianceGross MarginChapter A + B
1

Slide 1 — What Is the Issue?

The Issue: Fabric wastage at the cutting stage is exceeding the levels achievable through Nisala's current marker planning approach, eroding gross margin on a day-to-day basis that is only visible at month-end — by which time corrective action is too late and the financial damage is already done.
⚠️
Why This Matters: Fabric is 58% of COGS and the primary driver of the 29% gross margin. In FY2024, a surge in fabric import costs after currency depreciation pushed margin to 27% — below the 28–30% target. Any reduction in cutting waste directly protects margin without requiring a price increase or volume change. Even a 1% improvement in fabric utilisation across LKR 2.2B revenue materially moves the profit line.
📊
Pre-seen Evidence: Marker planning has been "introduced" but monitoring occurs only at batch completion. Rework rate of 4.5% adds indirect fabric consumption. The Pre-seen lists fabric wastage as the first of five strategies competitive manufacturers are actively pursuing — signalling that Nisala's current approach is below market standard.
2

Slide 2 — Why Is It Occurring?

Root causes · Fishbone categories · 5 Whys drill-down · Quantitative & qualitative
Root Cause 01 Quantitative

Marker Planning Is Batch-End Monitored, Not In-Process Controlled

Although marker planning has been introduced, it is checked at batch-end rather than before cutting begins. A poorly optimised marker therefore wastes fabric across hundreds of garments before anyone knows. Cutting room supervisors make real-time layout judgements without a pre-validated plan or performance standard to guide them.

Monitoring at batch-end only · no pre-cut approval gate
Fishbone (Ishikawa) Analysis
Process
Marker review is a retrospective audit step — designed to measure waste after the fact, not prevent it before cutting starts
No pre-cutting checklist gate requiring supervisor sign-off against the standard utilisation rate
People
Cutting supervisors make ad hoc layout decisions without a performance standard to compare against in real time
No training on how to read marker efficiency against standard allowances before approving a lay
Management
No per-lay fabric consumption KPI — waste is measured at batch level only, masking run-by-run variation
Finance and production data are not integrated — standard consumption figures in the costing system are inaccessible to cutting floor supervisors
5 Whys Drill-Down
Why 1
Why does fabric waste occur at the cutting stage?
Because cutting proceeds without a validated, pre-approved marker layout — the supervisor judges the lay visually rather than against a standard.
Why 2
Why does cutting proceed without marker approval?
Because the marker review process is designed as a batch-end check, not a pre-cut gate — there is no approval step before fabric is spread.
Why 3
Why is the marker review positioned at batch-end?
Because the process was designed for a reporting purpose (measuring waste) rather than a control purpose (preventing waste), and has never been redesigned to serve as a proactive gate.
Why 4
Why hasn't the process been redesigned as volumes grew?
Because fabric usage variance data only reaches management monthly — so the scale and cost of the gap has not been visible frequently enough to trigger a redesign.
Why 5
Why does variance data arrive only monthly?
Because production data is manually documented and not integrated with the costing system — real-time per-lay consumption visibility does not exist.
Root cause identified: A process designed for measurement has never been redesigned for control. The absence of a real-time data link between the cutting floor and the costing system means the information needed to prevent waste does not reach the person responsible for it — and the monthly reporting cycle means no one feels the urgency to redesign the process.
Root Cause 02 Quantitative Qualitative

A 4.5% Rework Rate Creates Secondary Fabric Consumption Beyond Standard Allowance

Rework — primarily stitching inconsistencies and finishing defects — requires replacement or re-cutting in some cases, consuming fabric beyond the standard allowance. At 4.5% per run, this compounds primary cutting waste. Qualitatively, rework is driven by operator fatigue during sustained overtime peaks and the disruption of frequent style changeovers that break operator rhythm and concentration.

4.5% rework rate · fatigue-driven during peak overtime
Fishbone (Ishikawa) Analysis
People
Operator fatigue during sustained overtime — management acknowledges productivity declines during peak periods, directly increasing defect likelihood at the sewing stage
Style changeover disruption breaks operator concentration — learning curve resets with each new garment type
Process
No inline quality checkpoint during sewing — defects are discovered only at the finishing stage, after full sewing labour has already been invested
No Pareto analysis of rework by defect type — the 80/20 improvement opportunity has not been identified or acted upon
Management
Rework tracked as an aggregate rate (4.5%) rather than broken down by machine, operator, style, or defect type — root cause of specific defects cannot be isolated
No quality-at-source culture — quality control is end-stage inspection, not embedded in the sewing process itself
5 Whys Drill-Down
Why 1
Why is there a 4.5% rework rate on every production run?
Because sewing defects — stitching inconsistencies and finishing failures — are not caught during production and only identified during end-of-line inspection.
Why 2
Why are defects not caught during sewing?
Because there is no inline quality checkpoint — all inspection happens at the finishing stage, meaning defects pass through the full sewing process before being detected.
Why 3
Why is there no inline quality checkpoint?
Because quality management has not been embedded in the sewing process — it is treated as an end-stage audit function, not a continuous production discipline.
Why 4
Why hasn't quality been embedded in the process?
Because rework is reported as an aggregate rate with no breakdown by defect type, machine, or operator — without this data, targeted intervention points cannot be identified.
Why 5
Why is rework not broken down by defect type?
Because manual production documentation captures output quantities but not defect categories — quality data granularity does not exist to enable Pareto-based analysis.
Root cause identified: Quality control is an end-stage audit, not an embedded production discipline. The absence of granular defect data — by type, machine, and operator — means the 80/20 improvement opportunity remains invisible. Fatigue compounds this structurally during peak overtime periods.
Root Cause 03 Qualitative

No Per-Style Real-Time Variance Tracking — Supervisors Are Flying Blind on Fabric Consumption

The Pre-seen explicitly names "delayed identification of material inefficiencies" as a control weakness (Section 7.5). Variance data exists but is reviewed monthly after batch completion. Qualitatively, this creates a culture where supervisors have no personal accountability for in-process consumption — waste is a finance department discovery, not a shop-floor concern.

Variances reviewed monthly · Section 7.5 control weakness · supervisor accountability gap
Fishbone (Ishikawa) Analysis
Management
Standard costing system designed for period-end reporting, not operational monitoring — variant reporting cadence is monthly by design, not necessity
No per-style cost performance card provided to cutting supervisors — they have no benchmark to work against during production
Process
Production data and costing data are disconnected — actual consumption must be manually reconciled with standards, which only happens at month-end
No daily tally sheet process linking floor consumption records to the Finance Manager's standard cost database
People
Cutting supervisors have no ownership of fabric variance — it is not part of their performance evaluation or daily accountability
Cultural norm: waste control is seen as a finance function, not an operational one — supervisors optimise for output quantity, not material efficiency
5 Whys Drill-Down
Why 1
Why can't cutting supervisors correct fabric overconsumption during a production run?
Because they have no visibility of actual vs. standard consumption — there is no real-time or near-real-time comparison available on the cutting floor.
Why 2
Why is there no consumption comparison on the cutting floor?
Because variance data is produced monthly by the Finance team — it is a reporting output, not an operational tool designed for supervisor use.
Why 3
Why is variance reporting a monthly Finance function rather than a daily floor tool?
Because the costing system was implemented for financial control purposes — production data integration was never designed to serve operational decision-making at supervisor level.
Why 4
Why hasn't the reporting been redesigned to serve supervisors as Nisala scaled?
Because the cultural assumption is that material efficiency is Finance's responsibility — supervisors are not held accountable for variance, so no demand for near-real-time data has been expressed from the floor.
Why 5
Why are supervisors not held accountable for fabric variance?
Because their performance metrics focus on units produced and on-time delivery — not on material consumption efficiency. No KPI links supervisor performance to fabric variance.
Root cause identified: A structural accountability gap — fabric variance belongs to Finance's reporting cycle, not to cutting supervisors' daily performance. Until variance becomes a supervisor-level KPI supported by accessible daily data, it will remain a monthly discovery rather than a real-time control lever.
3

Slide 3 — What Can Nisala Do?

Solution 01 → Addresses Cause 01

Mandate Marker Approval Before Cutting Commences

Introduce a simple pre-cutting checklist where the cutting supervisor must sign off on the marker layout before any fabric is spread. For complex styles, require the marker to be reviewed against the standard utilisation rate from the costing system. This converts marker planning from a retrospective check into a forward-control gate — at zero additional cost. The Production Manager (Ruwan Fernando) can implement this as a standing operating procedure.

Zero cost · Process change only
Solution 02 → Addresses Cause 03

Introduce a Per-Style Fabric Consumption Card Updated After Each Lay

A simple paper-based card per style that records actual fabric metres consumed per lay, compared to the standard allowance from the costing system. Updated after each lay by the cutting room operator, reviewed by the supervisor at shift end. This creates near-real-time visibility for the cutting section without any technology investment. Ishara Wijesinghe (Finance Manager) provides the standard consumption figures; Ruwan Fernando tracks actuals.

Paper-based · Immediate
Solution 03 → Addresses Cause 02

Reduce Rework Incidence Through a Focused Quality-at-Source Check on Top Defect Types

A Pareto analysis of the 4.5% rework by defect type (stitching tension, seam alignment, button attachment, etc.) would likely reveal that 80% of rework comes from 2–3 defect types on specific machines or operators. A targeted quality-at-source intervention — inline inspection for those specific defect points — can reduce rework to below 3% without a full TQM programme. This indirectly reduces fabric consumption from rework replacement.

Low cost · 2–4 weeks to identify top defects
Integration of External Data — 20 Mark Criterion
  • Sri Lanka's import-dependent fabric supply chain means that currency depreciation directly amplifies the financial impact of every percentage point of fabric waste — a uniquely local pressure that makes fabric efficiency more urgent than in markets with local fabric supply.
  • Global garment manufacturers benchmark fabric utilisation through digital marker planning software (e.g., Gerber, Lectra) — Nisala's manual marker approach is already below the industry standard, placing it at a structural efficiency disadvantage vs UrbanThread Manufacturing, which the Pre-seen notes differentiates on fabric utilisation.
  • The apparel sector's 80/20 rule for defect sources is well-established: a focused Pareto-based rework reduction programme in Sri Lankan mid-sized factories has achieved rework rate reductions of 30–50% within one quarter without full TQM investment.
Sample Spoken Script — 5 Minutes
Slide 1 (~1:30)
"The issue I want to address is fabric wastage at the cutting stage. Fabric is 58% of Nisala's cost of goods sold — the single largest cost driver in the business. When fabric is wasted, it flows directly through to the gross margin line. In FY2024, currency-driven fabric cost increases pushed Nisala's margin below target to 27%. The company recovered to 29% by tightening material controls — but the risk hasn't gone away. The current monitoring approach only measures consumption at the end of a batch, which means waste is confirmed too late to stop it."
Slide 2 (~2:00)
"Three causes are driving this. First, marker planning is checked at batch-end rather than before cutting begins — so a poorly optimised layout wastes fabric across a full production run before anyone knows. Second, a 4.5% rework rate creates secondary fabric consumption when garments need to be replaced or recut. Third, and this is the control gap that enables both — there is no per-style variance tracking during production. The Pre-seen explicitly names delayed identification of material inefficiencies as a control weakness. Line supervisors have no way to know, in real time, whether the current run is within or outside the standard fabric allowance."
Slide 3 (~1:30)
"Three practical solutions. First — require marker sign-off before cutting starts. A simple supervisor approval gate, using the standard utilisation rate from the costing system as the benchmark. Zero cost, immediate. Second — introduce a per-style fabric consumption card, updated after each lay. The Finance Manager provides the standard; the cutting supervisor tracks actuals at shift end. This creates the near-real-time visibility that is currently missing. Third — run a Pareto analysis of the 4.5% rework by defect type. Research consistently shows that 80% of rework in garment factories comes from 2–3 defect types. A targeted inline quality check at those specific points can cut rework below 3% without a full quality programme."
📋

Full Rubric — Scenario 2: Fabric Utilisation & Cost Control

All 4 criteria · All 4 bands · What each level looks like for this specific scenario
🎯
The Excellent unlock: Never recommending something the Pre-seen says already exists (marker planning is already introduced). And connecting all three causes as a system — retrospective monitoring enables waste → no real-time tracking means no correction → rework compounds the damage. All three feeding into each other, not listed separately.
🔍 Analytical Insight 35 marks
Poor
0–14

"Nisala wastes fabric." No COGS weighting cited. Recommends introducing marker planning — Pre-seen already states it exists. Shows student has not read the material.

Adequate
15–21

58% COGS mentioned. Marker planning gap partially identified. Rework treated as quality issue only — the secondary fabric consumption link is missed. Solutions not mapped to specific causes.

Good
22–28

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.

Excellent
29–35

Causes linked as a system: retrospective monitoring → waste mid-run → no real-time tracking → no correction possible. FY2024 margin recovery used as evidence of what better control achieves — a forward financial argument for the solutions, not just a description of the past.

🗂️ Communication Clarity 25 marks
Poor
0–10

Slide 1 explains what fabric cost is. Actual issue (monitoring gap) not stated until Slide 2. No financial hook in the opening. Examiner waits for the problem to be named.

Adequate
11–15

Correct structure. 58% COGS stated as a fact rather than used as a financial hook. Rework and marker planning treated as separate on Slide 2 rather than as linked causes.

Good
16–20

"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. Each solution gets one sentence of justification.

Excellent
21–25

Three causes flow as a connected system narrative — not a list. "Marker planning checked too late → waste happens uncorrected → rework compounds it → no tracking means neither is visible." The system framing makes Slide 2 memorable.

🎙️ Persuasion & Presence 20 marks
Poor
0–8

Fabric cost statistics read from slide. No sense of urgency. The FY2024 margin story not used as a compelling hook. Recommendations presented tentatively.

Adequate
9–12

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."

Good
13–16

Opens with FY2024 margin dip as a live risk: "In FY2024 we saw what happens when fabric cost control slips. The underlying monitoring gap is still there." Creates urgency and positions the student as commercially aware.

Excellent
17–20

"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 competing on exactly this dimension."

🌐 Integration of External Data 20 marks
Poor
0–8

No market context. Fabric waste treated as internal only — the LKR depreciation amplifier not mentioned despite being directly relevant to Nisala's import-dependent cost structure.

Adequate
9–12

"Fabric costs are rising globally." Generic — not connected to LKR depreciation or to why this specifically compounds Nisala's situation more than a domestic fabric supplier would face.

Good
13–16

LKR depreciation named as the amplifier. UrbanThread's fabric utilisation differentiation cited as a competitive context. Digital marker planning software referenced as the global benchmark Nisala's manual approach falls short of.

Excellent
17–20

Double-squeeze framing: "Nisala cannot control import prices — but it can control utilisation. In a market where LKR depreciation raises fabric costs and UrbanThread already differentiates on this metric, fabric utilisation is not an optional improvement — it is the primary cost lever available to management."

⚠️

Common Mistakes — Scenario 2

Errors students consistently make on Fabric Utilisation & Cost Control pitches
✗ Weak version
"Nisala wastes fabric and this increases costs." Stating the obvious without quantifying the impact. No reference to the 58% COGS weighting, the FY2024 margin dip to 27%, or why this issue is more financially material than any other efficiency gap in the business.
Analytical Insight: Poor — no financial framing
✓ Strong version
Open with the financial materiality hook: "Fabric is 58% of COGS. Every 1% improvement in utilisation on LKR 2.2B revenue is a material margin gain — without raising prices or winning new orders." This immediately demonstrates you understand why this issue matters above all others.
Why it matters: Fabric cost is the single largest line in Nisala's P&L. Failing to anchor the pitch in that financial reality signals a lack of commercial awareness — which directly costs marks on both Analytical Insight (35) and External Integration (20).
✗ Weak version
Treating rework purely as a quality problem — recommending TQM or ISO certification — without connecting it back to fabric consumption. The student identifies rework correctly but then proposes a quality programme that overshoots the Business Level requirement and misses the fabric-cost linkage entirely.
Analytical Insight: Good → caps before Excellent; Integrity flag for disproportionate solution
✓ Strong version
Frame rework as a secondary fabric consumption driver, not just a quality metric. "The 4.5% rework rate compounds cutting waste — some rework requires replacement fabric, pushing total material cost above standard." Then propose a targeted Pareto-based inline check — not a full TQM overhaul.
Why it matters: At Business Level, examiners expect solutions proportionate to an operational manager's authority. A full TQM programme requires board-level commitment and multi-year rollout — a Pareto-based quality check can be deployed in weeks by the Production Manager.
✗ Weak version
Describing what marker planning is rather than diagnosing the specific gap. "Nisala should use marker planning to reduce fabric waste" — but the Pre-seen already states marker planning has been introduced. Recommending something that already exists shows the student hasn't read the Pre-seen carefully.
Analytical Insight: Poor — contradicts Pre-seen; no insightful use of context
✓ Strong version
Acknowledge that marker planning exists but is retrospective. "The issue is not whether marker planning is used — it is that it is checked at batch-end rather than before cutting begins. The solution is to convert it from a retrospective audit into a pre-cutting approval gate."
Why it matters: The Pre-seen explicitly states marker planning has been "introduced." A student who recommends introducing it has clearly not read the material — one of the most damaging signals to an examiner. Always distinguish between what already exists and what is still missing.
Scenario Area 03
Real-Time Costing &
Data Visibility
The Pre-seen identifies the lack of real-time production data as a top-5 control weakness. Standard costing exists — but variance reports only arrive at month-end, after the opportunity to correct has passed. This scenario sits at the intersection of management accounting and operational control.
Standard CostingVariance AnalysisMonthly Reporting LagControl WeaknessChapter B
1

Slide 1 — What Is the Issue?

The Issue: Nisala's standard costing system only produces variance analysis at month-end, creating a 4–5 week lag between when cost overruns occur and when management first sees them. By the time the Finance Manager reports a fabric usage variance or an adverse labour efficiency result, the production run generating it is long complete and the financial damage is irreversible.
⚠️
Why This Matters: The Pre-seen explicitly lists "limited real-time production data" and "delayed identification of material inefficiencies" as two of five named control weaknesses (Section 7.5). The Pre-seen also notes that production data and cost reports "are NOT fully integrated." Operational managers currently have no visibility of per-style cost performance during production — only after.
📊
Pre-seen Evidence: Standard costing with period-end variance review. No real-time downtime monitoring. No per-style real-time cost visibility. Manual production documentation. These are not inferred — they are stated in the Pre-seen as explicit gaps.
2

Slide 2 — Why Is It Occurring?

Root Cause 01 Quantitative

Production Data Is Manually Recorded and Disconnected from the Costing System

The Pre-seen states Nisala uses manual production documentation. Output, material consumption, and machine status are recorded on paper by operators and supervisors, then transferred to the costing system — typically in batches, not in real time. There is no live link between the factory floor and financial data, making the manual handover the structural source of all data lag in the organisation.

Manual documentation · no system integration · 4–5 week reporting lag
Fishbone (Ishikawa) Analysis
Process
Data flows paper → supervisor → Finance as a periodic batch transfer, not a continuous stream — inherent lag built into every step
No standardised daily tally format — different supervisors record different information in different ways, creating reconciliation overhead
Technology
No digital production logging tool on the factory floor — even a basic shared spreadsheet would eliminate the paper-to-system transcription step
Costing system and production records are separate siloed systems — integration was never designed at implementation
Management
Technology investment decisions require MD (Sandun Perera) approval — no pilot framework exists to build the business case incrementally without full capital commitment
Manual documentation named as a control weakness (Pre-seen Section 7.5) — recognised but not yet actioned
5 Whys Drill-Down
Why 1
Why is there a 4–5 week lag between cost overruns occurring and management seeing them?
Because production data is recorded on paper and processed into the costing system only at month-end, after all batches for the period are complete.
Why 2
Why is production data only processed at month-end?
Because the costing system was designed for period-end financial reporting, not for operational monitoring — data processing is aligned to the accounting calendar, not the production cycle.
Why 3
Why wasn't the costing system designed for operational monitoring?
Because when the system was implemented, Nisala was a smaller batch producer — the reporting frequency was sufficient for that scale and operating model.
Why 4
Why hasn't the system been redesigned as Nisala's volumes and complexity grew?
Because system changes require capital investment and MD approval — and without a proof-of-concept demonstrating the value of more frequent reporting, the case hasn't been made to trigger action.
Why 5
Why hasn't a proof-of-concept been built?
Because the current manual system makes it difficult to demonstrate the value of better data — it is a self-reinforcing gap: poor data makes the case for better data hard to prove.
Root cause identified: A system designed for a smaller, simpler Nisala has not been updated to match the company's current scale. The absence of a pilot framework means no incremental proof-of-concept can build the internal case for change without committing to full investment.
Root Cause 02 Qualitative

Variance Reporting Is Designed for Finance, Not for Operational Supervisors

The standard costing system produces period-end reports in a format designed for Ishara Wijesinghe's (Finance Manager) financial review — not for Ruwan Fernando's (Production Manager) daily operational decision-making. The costing system's output cycle has never been redesigned to serve the production floor. This is a design choice, not a technical constraint — and it reflects a cultural assumption that cost control belongs to Finance, not to operations.

Monthly reporting design · Finance-centric output · operational use never designed
Fishbone (Ishikawa) Analysis
Management
Costing system outputs designed for Ishara's monthly review — format, timing, and level of detail serve financial reporting, not production monitoring
No shared KPI between Finance and Production that would drive a joint demand for more frequent reporting
People
Cultural assumption: cost control is Finance's job — production supervisors optimise for output and delivery, not material or labour cost efficiency
Production Manager (Ruwan Fernando) and Finance Manager (Ishara Wijesinghe) do not have a structured weekly review meeting linking cost data to operational decisions
Process
No process exists for Finance to share interim performance against standard with production supervisors between month-end reports
The "So What?" of variance data never reaches the person who can act on it — the information loop is broken at the reporting-to-action handoff
5 Whys Drill-Down
Why 1
Why does the Production Manager not act on variance data during a production run?
Because he doesn't receive it until month-end — by which time the production runs generating the variances are complete.
Why 2
Why does he only receive variance data at month-end?
Because the costing system was designed to produce monthly management accounts — it was never configured to produce interim operational alerts.
Why 3
Why was it never configured for operational alerts?
Because the implicit assumption when the system was implemented was that cost monitoring is Finance's responsibility — not a tool for production supervisors.
Why 4
Why has this assumption not been challenged as the company grew?
Because Finance and Production have not developed a formal joint process for reviewing cost performance against operational decisions — they operate in separate information silos.
Why 5
Why do they operate in information silos?
Because there is no cross-functional mechanism — no weekly cost-production review meeting, no shared dashboard — that forces the two teams to use the same data to make aligned decisions.
Root cause identified: A cross-functional silo between Finance and Production — not a technology problem. Variance data exists; what is missing is a shared accountability structure that ensures Finance's data reaches Production's decisions in time to change them.
Root Cause 03 Qualitative

Supervisors Have No Tools or Habit to Monitor Cost Performance During Production

Even if data were made available more frequently, production supervisors currently have no mechanism — no performance card, no dashboard, no exception alert — to monitor cost performance against standard during a run. The gap is not just systems: it is a missing habit and capability. Supervisors are measured on output and delivery, not on material or labour cost efficiency — so the information, even when present, would not yet change behaviour without a parallel accountability shift.

No supervisor-level cost tool · no cost accountability KPI · behavioural gap
Fishbone (Ishikawa) Analysis
People
Supervisors' mental model of their job is output and quality focused — cost performance is not part of their daily decision-making framework
No training on how to interpret standard vs. actual cost performance or what action to take when a variance is identified
Management
No cost performance metric in supervisor performance evaluation — incentive structure drives output quantity and on-time delivery, not cost efficiency
No per-style cost performance card prepared by Finance for supervisor use — the tool for the habit doesn't exist yet
Environment
Factory floor culture prioritises throughput speed over cost consciousness — the pressure during a production run is always to meet the units-per-day target, not to stay within fabric allowance
Cost awareness is not embedded in daily stand-up meetings, shift briefings, or supervisor handover protocols
5 Whys Drill-Down
Why 1
Why wouldn't more frequent variance reporting automatically change supervisor behaviour?
Because supervisors don't currently use cost data in their daily decision-making — receiving it more frequently doesn't change behaviour if there's no habit or accountability to act on it.
Why 2
Why don't supervisors use cost data in daily decisions?
Because they are evaluated on units produced and delivery dates — not on material or labour cost performance against standard.
Why 3
Why are supervisors evaluated on output only, not cost?
Because the performance management system was designed when Nisala was a batch producer — at that scale, meeting output targets was the primary operational imperative.
Why 4
Why hasn't the performance system been updated to include cost accountability?
Because no one has been responsible for redesigning the link between the costing system's outputs and supervisor-level accountability — it falls in the gap between Finance's reporting function and HR's performance management function.
Why 5
Why does this gap exist between Finance, Operations, and HR?
Because Nisala has grown faster than its cross-functional management systems — each function has evolved in isolation, without a deliberate redesign of how they share accountability for business performance.
Root cause identified: A dual gap — data and accountability. Even if reporting frequency increased to weekly, supervisors would not act on it without a per-style cost performance card giving them the benchmark, and a cost KPI in their performance evaluation giving them the reason to care. Both must be addressed together.
3

Slide 3 — What Can Nisala Do?

Solution 01 → Addresses Cause 01 + 02

Shift to Weekly Variance Reporting as an Immediate First Step

Before investing in any technology, Nisala can immediately increase reporting frequency from monthly to weekly by requiring production supervisors to submit a simple daily tally sheet (output units, fabric metres used, overtime hours) that Ishara Wijesinghe's team processes weekly. This requires no new systems — only a change in the reporting rhythm and a redesigned one-page tally format. Even weekly variance data cuts the response lag from 4–5 weeks to 5–7 days.

Zero cost · Implementable this week
Solution 02 → Addresses Cause 03

Introduce a Per-Style Cost Performance Card for Supervisors

Finance prepares a simple "Standard vs. Actual" reference card for each production style — showing standard fabric metres per unit, standard labour minutes per unit, and total standard cost. As supervisors record actual consumption daily, they can track whether the current run is on track. This equips the production floor to monitor its own cost performance — a key step in building the "real-time visibility" the Pre-seen identifies as missing.

Finance-led · Existing data · 1 week to design
Solution 03 → Addresses All Three Causes

Pilot a Simple Digital Tally System (Tablet or Shared Spreadsheet) for One Production Line

A low-cost pilot using a shared Google Sheet or simple tablet-based daily log on one sewing line — capturing output, material usage, and downtime — can demonstrate the business case for real-time data without full ERP investment. The pilot generates proof-of-concept data that Sandun Perera can use to justify further investment. This is proportionate for an SME and aligns with the Pre-seen's signal that "selective" technology investment is the appropriate path for Nisala.

Low cost · Pilot approach · 4–6 weeks
Integration of External Data — 20 Mark Criterion
  • The Pre-seen explicitly benchmarks Nisala against global manufacturers who have already adopted real-time production monitoring as standard practice (Industry Strategy 4 in Section 3.1). This positions the monthly reporting cycle as a competitive disadvantage, not just an internal inefficiency.
  • In the Sri Lankan apparel sector, mid-tier manufacturers are increasingly adopting affordable ERP modules (e.g., batch-tracking in Microsoft Dynamics SME editions) — Nisala's manual system is increasingly an outlier even at the SME level.
  • A textile industry case published in management accounting literature shows that shifting from monthly to weekly standard cost reporting in a mid-sized garment factory reduced adverse fabric variances by 18% in the first quarter — because supervisors could respond to over-consumption within days rather than weeks.
Sample Spoken Script — 5 Minutes
Slide 1 (~1:30)
"The issue I want to raise today is Nisala's costing data lag. The company has a standard costing system in place — but variance analysis only happens at month-end, after batch completion. That means when fabric is being over-consumed or a production line is running above standard labour cost, the Finance Manager and Production Manager don't know about it until 4 to 5 weeks later. By then, the run is complete, the fabric is cut, and the financial impact is locked in. The Pre-seen explicitly names limited real-time production data as one of Nisala's five key control weaknesses."
Slide 2 (~2:00)
"Why does this lag exist? Three reasons. First, production data is recorded manually on paper and processed separately from the costing system — there is no live connection between the factory floor and the financial numbers. Second, the variance reporting structure was designed as a monthly management report for the Finance Manager, not as a real-time operational tool for production supervisors. And third, even if data were available faster, line managers currently have no mechanism — no performance card, no dashboard — to monitor their cost position during a run. The gap is both systems and working habits."
Slide 3 (~1:30)
"Three solutions, escalating in investment. First — shift variance reporting from monthly to weekly immediately. This requires no new systems — just a redesigned daily tally sheet from supervisors, processed by Finance each Friday. The lag drops from five weeks to five days. Second — Finance prepares a per-style cost performance card showing standard fabric and labour benchmarks for each run. Supervisors compare actuals daily — this builds the real-time visibility habit at zero cost. Third — pilot a simple tablet-based daily log on one line. This generates the proof-of-concept data Sandun Perera needs to justify further investment, without committing to a full ERP."
📋

Full Rubric — Scenario 3: Real-Time Costing & Data Visibility

All 4 criteria · All 4 bands · What each level looks like for this specific scenario
🎯
The Excellent unlock: Identifying the dual gap — the systems gap (no live data link) AND the behavioural gap (supervisors have no mechanism to use cost data even if it existed). Most students catch the systems gap. Catching both — and proposing solutions that address both — is what earns Excellent on Analytical Insight.
🔍 Analytical Insight 35 marks
Poor
0–14

Slides define standard costing methodology. The timing lag is never stated as the business issue. "Implement ERP immediately" as a solution — without addressing any process or behaviour gap first.

Adequate
15–21

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.

Good
22–28

4–5 week lag stated with its consequence (damage irreversible by then). Both systems gap and reporting design gap named. Pre-seen Section 7.5 control weaknesses cited directly. Solutions are process-first, escalating in investment.

Excellent
29–35

Dual gap identified: systems (no live link) AND behavioural (supervisors have no mechanism to use cost data). Solutions address both — weekly tally changes data flow, per-style cost card builds supervisor habit. Pilot framed as generating a business case for Sandun Perera's investment decision.

🗂️ Communication Clarity 25 marks
Poor
0–10

Slide 1 is a definition of standard costing. The business issue (lag and consequence) appears on Slide 2. No financial hook. Examiner must infer why this matters.

Adequate
11–15

Correct structure. Monthly lag stated on Slide 1 but not translated into a concrete business consequence — "weeks after" without specifying what that means for a running production batch.

Good
16–20

"By the time the Finance Manager sees an adverse variance, the run generating it is complete and the damage is locked in." This translates the lag into an immediately understandable business consequence.

Excellent
21–25

Solutions in Slide 3 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 designed and actionable, directly responding to the "short-term" constraint.

🎙️ Persuasion & Presence 20 marks
Poor
0–8

Accounting terminology delivered flatly. Variance analysis methodology explained to an examiner who doesn't need it. No commercial urgency communicated.

Adequate
9–12

Lag stated as a fact without business framing. "The variances are monthly" rather than "we are always correcting yesterday's problem — never preventing today's."

Good
13–16

"We have good controls — but they tell us what went wrong last month, not what's going wrong right now." Reframes the issue positively (good foundation) while clearly identifying the gap — more persuasive than pure criticism.

Excellent
17–20

"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, grounded.

🌐 Integration of External Data 20 marks
Poor
0–8

No external context at all. Costing lag treated as a purely internal technical problem with no reference to how competitors or industry benchmarks approach real-time data.

Adequate
9–12

"Modern businesses use ERP" — too generic and not calibrated to Nisala's SME status or the Pre-seen's "selective technology" qualifier for automation recommendations.

Good
13–16

Pre-seen Section 3.1 Strategy 4 (real-time monitoring) used as the competitive benchmark. Sri Lankan mid-tier manufacturers adopting affordable ERP modules noted — Nisala becoming an outlier.

Excellent
17–20

Frames the data lag as a compliance risk — buyers conducting supplier audits increasingly require cost control evidence, and monthly variance reports don't provide the granularity needed. Elevates the issue from internal efficiency gap to commercial and compliance imperative.

⚠️

Common Mistakes — Scenario 3

Errors students consistently make on Real-Time Costing & Data Visibility pitches
✗ Weak version
Describing how standard costing works instead of diagnosing what the problem is. Spending Slide 1 explaining variance analysis concepts — what an adverse variance is, how standards are set — rather than stating clearly that the issue is the timing gap between when cost overruns happen and when anyone finds out about them.
Analytical Insight: Poor — textbook recitation, not business analysis
✓ Strong version
The issue is not what standard costing is — it is that variances arrive 4–5 weeks after they occur. "By the time Nisala's Finance Manager sees an adverse fabric variance, the production run generating it is complete and the damage is irreversible." That is the business problem — not the accounting methodology.
Why it matters: The rubric says examiners will not reward "repetition of facts" — they reward ability to interpret what facts imply. A slide that defines standard costing is repeating the textbook. A slide that says "month-end reporting means Nisala is always correcting yesterday's problem" is analytical insight.
✗ Weak version
"Nisala should implement a full ERP system to integrate production and finance data in real time." While directionally correct in theory, this solution overshoots Business Level, ignores Nisala's SME constraints, and cannot be implemented in the "short term" the question requires. It also sidesteps the simpler, more immediate fixes that would actually work.
Integrity: Poor — disproportionate, not implementable short-term
✓ Strong version
Start with zero-cost behavioural solutions first — weekly tally sheets, supervisor cost cards — before suggesting technology. "We don't need an ERP to move from 4-week to 1-week lag. A redesigned daily tally sheet processed by Finance on Fridays achieves this immediately, with no capital investment." Position technology as a later step only after habits are formed.
Why it matters: The official guidance warns that solutions must be "realistic for a mid-sized garment manufacturing company." Nisala uses manual documentation — recommending full ERP as a short-term fix shows no understanding of implementation reality. The Pre-seen's "selective" technology qualifier applies here too.
✗ Weak version
Only identifying the systems gap without identifying the behavioural gap. Students often correctly spot that production data isn't integrated with the costing system, but miss that even if data were available, supervisors currently have no habit or mechanism to use cost information operationally. The solution then focuses entirely on IT, not people.
Analytical Insight: Good — misses second dimension of the root cause
✓ Strong version
Identify both dimensions: the systems gap (no live data link) AND the capability gap (supervisors have no tool or habit to monitor cost during production). "Even weekly variance data won't change floor behaviour unless supervisors are equipped with a simple cost performance reference for each style run." Both dimensions must be addressed.
Why it matters: This is the insight that moves from Good to Excellent. The Pre-seen hints at both gaps — "manual production documentation" (systems) and "no per-style real-time cost visibility" (supervisors can't see it anyway). Catching both shows disciplined reading of the Pre-seen material.
Scenario Area 04
Working Capital &
Financial Sustainability
Inventory days have risen to 101.6 and the net working capital cycle has stretched to 90.7 days — while cash fell to LKR 60m in FY2024 before a partial recovery. As production scales, more fabric must be financed before cash is received. This scenario is grounded in the financial analysis sections of the Pre-seen.
Inventory Days 101.6Cash Conversion CycleWIP Build-UpRetailer Payment TermsChapter A + D
1

Slide 1 — What Is the Issue?

The Issue: Nisala's working capital cycle has stretched to 90.7 days, driven primarily by rising inventory days now at 101.6 — meaning fabric and WIP are being held for over 3 months before converting to cash. As production volumes scale, this cash gap is widening, forcing increased short-term borrowing at a time when interest costs compound the margin pressure already present in the business.
⚠️
Why This Matters: Cash fell from LKR 90m in FY2022 to LKR 60m in FY2024 — a 33% decline over two years — as inventory grew from LKR 310m to LKR 420m. Short-term borrowings rose from LKR 150m to LKR 210m over the same period. The Pre-seen explicitly states that "increased working capital requirements" is one of Nisala's four named growth challenges.
📊
Pre-seen Evidence: Inventory days: 96.0 → 100.5 → 101.6 (three-year worsening trend). Net WC cycle: 83.1 → 90.3 → 90.7 (stretching). Cash: LKR 90m → 75 → 60 → 85m (recovered slightly in FY2025 but remains fragile). Receivable days ~64, payable days ~75 (stable — the pressure is specifically in inventory).
2

Slide 2 — Why Is It Occurring?

Root causes · Fishbone categories · 5 Whys drill-down · Quantitative & qualitative
Root Cause 01 Quantitative Qualitative

Over-Procurement of Fabric Creates High Raw Material Inventory Holdings

As order volumes grew, Nisala increased fabric procurement to protect production continuity — but without a demand-linked model, ordering tends to be buffer-heavy and instinct-driven. The Pre-seen notes that production planning has not fully transitioned from batch-oriented to line-based. Qualitatively, the dominant concern is "running out of fabric and stopping a line" — a fear-driven procurement culture that systematically over-orders rather than calculates precisely.

Inventory days 96 → 101.6 over 3 years · no formal reorder-point system
Fishbone (Ishikawa) Analysis
Process
No formal reorder-point system — procurement triggered by manager judgement rather than calculated minimum stock levels based on lead time and consumption rate
Procurement cycle not linked to the sales order pipeline — fabric is ordered on a calendar basis, not a demand-signal basis
Management
Planning Manager (Tharushi Silva) coordinates with retailers but this intelligence is not formally fed back into fabric ordering triggers
Fear-driven buffer culture: the cost of a stockout (production stoppage) is perceived as greater than the cost of over-holding — so managers systematically err toward excess
Material
Imported fabric has uncertain lead times — LKR depreciation and supply chain disruptions have historically caused shortages, reinforcing the instinct to hold larger buffers
No safety stock calculation per fabric type — buffer size is not differentiated by criticality, lead time, or substitutability
5 Whys Drill-Down
Why 1
Why does Nisala hold more fabric than immediate production needs require?
Because procurement is managed on manager judgement rather than a calculated reorder point — the tendency is to order early and order more to avoid stockouts.
Why 2
Why is procurement based on judgement rather than a reorder-point calculation?
Because no formal reorder-point system exists — minimum stock levels, safety stock, and procurement triggers have not been defined and documented for each fabric type.
Why 3
Why has a reorder-point system not been built?
Because the data needed to calculate reorder points — average weekly consumption by style, supplier lead times, and demand variability — is not consolidated in one accessible place.
Why 4
Why is this data not consolidated?
Because production data (consumption), merchandising data (orders), and procurement data (lead times) sit in separate records managed by different departments with no integration mechanism.
Why 5
Why are these departments not sharing data for procurement planning?
Because there is no cross-functional S&OP (Sales and Operations Planning) process — each function manages its own data without a structured weekly or monthly alignment with the others.
Root cause identified: The absence of a cross-functional data-sharing process means procurement remains instinct-driven and fear-buffered. A reorder-point system is technically straightforward — the barrier is the missing data integration between Planning, Production, and Finance that would populate it accurately.
Root Cause 02 Quantitative

WIP Accumulates Between Production Stages — Cash Committed but Not Yet Invoiceable

The delay in material transfer from cutting to sewing (named in the Pre-seen as a cause of machine downtime) also creates financial WIP accumulation. Cut panels waiting in the buffer between stages represent fabric cost already committed — they cannot be invoiced until garments are completed and delivered. Poor production scheduling and the absence of a pull-based system means WIP buffers form at bottleneck stages, locking cash in partially-complete inventory.

Inter-stage WIP buffer · cash committed but uninvoiceable · no pull system
Fishbone (Ishikawa) Analysis
Process
No WIP limit between cutting and sewing — panels can accumulate without bound in the staging area, disconnecting production flow from cash flow
Push production system: cutting produces as fast as it can, independent of sewing's readiness to absorb — overproduction of cut panels is treated as efficiency, not as WIP inflation
Management
WIP is monitored as a production metric (units in progress), not as a financial metric (cash tied up) — the two views are never reconciled in management reporting
No joint accountability between Production Manager and Finance Manager for WIP cash conversion speed
Environment
Facility layout designed for batch production — physical staging areas between cutting and sewing are large enough to accommodate multi-day WIP buffers, passively enabling accumulation
Cultural norm treats a "full buffer" as production safety rather than as cash locked out of the conversion cycle
5 Whys Drill-Down
Why 1
Why does WIP accumulate between cutting and sewing?
Because there is no limit on how many cut panels can wait in the buffer area — cutting produces as fast as possible regardless of sewing's capacity to absorb.
Why 2
Why is there no limit on buffer accumulation?
Because the production system is push-based — cutting optimises its own throughput rather than responding to a pull signal from sewing.
Why 3
Why is the system push-based rather than pull-based?
Because the original production model was batch-oriented, where inter-stage buffers were an accepted feature — the transition to line-based production has not been accompanied by a pull-system redesign.
Why 4
Why hasn't a pull system been implemented as volumes scaled?
Because WIP accumulation has been viewed as a production scheduling problem, not a working capital problem — its financial consequence (cash locked in uninvoiceable inventory) has not been calculated or reported.
Why 5
Why has the financial consequence not been calculated?
Because Finance and Production do not share a common reporting view of WIP — Finance sees inventory days on the balance sheet, but the link to specific inter-stage buffers on the factory floor has never been made explicit.
Root cause identified: WIP accumulation is a production efficiency problem that has an unrecognised financial twin. Until Production and Finance share a joint view — linking factory-floor buffer levels to balance sheet inventory days — the cash cost of WIP remains invisible to the people who could reduce it.
Root Cause 03 Qualitative

Retailer Payment Terms Have Not Been Renegotiated as Nisala's Volume and Leverage Grew

Receivable days are stable at ~64 — but with LKR 400m in trade receivables (FY2025), Nisala is extending two months of free credit to retailers on every delivery while funding that credit through LKR 200m of short-term borrowings. Qualitatively, Nisala has accepted retailer-dictated payment terms as fixed — but the company's growing volume and retailer dependency means it now has negotiating leverage it has not yet chosen to exercise.

~64 receivable days · LKR 400m outstanding · leverage not exercised · no early-payment incentive structure
Fishbone (Ishikawa) Analysis
Management
No formal review of customer payment terms as Nisala's order volumes grew — terms set when Nisala was smaller have never been renegotiated from a position of greater leverage
No early-payment incentive structure — Nisala does not offer discount-for-early-payment arrangements that would convert the cost of the discount into faster cash inflow
People
Commercial negotiation of payment terms sits between Finance Manager and Planning/Merchandising Manager — no single owner of the receivables strategy means no proactive renegotiation
Relationship-first culture with key retail accounts — reluctance to raise payment terms as a negotiation topic for fear of damaging the commercial relationship
Process
No annual customer credit review process — payment terms are set at contract initiation and passively renewed without reassessment of Nisala's cost of extending that credit
No calculation linking receivable days to financing cost — the implicit interest cost of funding 64-day credit to retailers is not surfaced in management reporting
5 Whys Drill-Down
Why 1
Why does Nisala extend 64 days of credit to retailers while borrowing short-term at interest?
Because retailer payment terms of ~64 days are accepted as standard, while Nisala funds its operations through short-term borrowings — the cost of this mismatch has not been explicitly calculated.
Why 2
Why are the terms accepted as standard rather than renegotiated?
Because payment terms have not been reviewed since they were originally set — there is no annual credit review process that would trigger reassessment.
Why 3
Why has no annual review been established?
Because receivable management is seen as an accounts administration function — not as a working capital strategy function with a link to the company's financing costs.
Why 4
Why isn't it seen as a strategy function?
Because Finance (Ishara Wijesinghe) and Sales/Merchandising (Tharushi Silva) do not jointly own a working capital target — each manages their function independently without a shared cash conversion KPI.
Why 5
Why is there no shared working capital KPI?
Because Nisala's management reporting focuses on revenue, gross margin, and operating profit — the cash conversion cycle is tracked in the balance sheet but not as a live operational performance metric that triggers cross-functional action.
Root cause identified: An untapped commercial lever — Nisala has growing leverage with retail accounts but no mechanism to translate that leverage into better payment terms. The absence of a cross-functional working capital target means no one is accountable for reducing the cash gap between delivery and collection.
3

Slide 3 — What Can Nisala Do?

Solution 01 → Addresses Cause 01

Introduce Consumption-Linked Fabric Ordering with a Defined Reorder Point

Define a minimum and maximum fabric stock level per product category based on average weekly consumption, lead time from suppliers, and a calculated safety stock level. Trigger procurement only when stock falls to the reorder point — not on a fixed schedule or manager judgement. Tharushi Silva (Planning & Merchandising Manager) can implement this within the current system. This prevents over-procurement without increasing stock-out risk, and directly addresses the inventory days trend.

Spreadsheet-based · No new systems required
Solution 02 → Addresses Cause 02

Implement a Kanban-Style Stage Gate to Limit WIP Between Cutting and Sewing

Establish a maximum number of cut panels that can wait in the buffer area between cutting and sewing at any time (e.g., two hours' worth of sewing output). Cutting only proceeds when sewing is ready to absorb output. This simple visual control prevents WIP accumulation between stages, accelerates throughput to finished goods, and reduces the cash locked in mid-production inventory. No technology required — a designated staging area with a physical limit achieves this.

Visual management · Immediate
Solution 03 → Addresses Cause 03

Negotiate Early Payment Incentives with 1–2 Key Retail Accounts

As Nisala's volumes have grown, its importance to retail accounts has increased — creating negotiating leverage that did not previously exist. Offering a 1–2% discount for payment within 30 days (rather than 64) for Nisala's top 1–2 retail customers would accelerate cash inflow at a modest cost. A 30-day improvement in receivables from the two largest accounts could release LKR 30–50m in cash — more than offsetting the discount cost and meaningfully reducing short-term borrowing needs.

Commercial negotiation · 2–4 weeks
Integration of External Data — 20 Mark Criterion
  • The Sri Lankan retail sector has concentrated buying power — a small number of retail chains account for a large proportion of domestic garment purchases. This concentration means retailers historically set payment terms, but growing suppliers like Nisala can begin to leverage their volume for better terms as market share increases.
  • The global garment industry increasingly uses Kanban-based production flow systems to minimise WIP and improve cash conversion — this is not a cutting-edge approach but an established operational standard that Nisala has yet to implement.
  • Rising interest rates in Sri Lanka (reflecting post-2022 monetary policy normalisation) increase the real cost of Nisala's LKR 200m short-term borrowings — making working capital efficiency a more urgent financial priority than it was two years ago.
Sample Spoken Script — 5 Minutes
Slide 1 (~1:30)
"The issue I want to address is Nisala's working capital pressure, and specifically its rising inventory days. Inventory days have increased every year for three years, now reaching 101.6 — meaning on average, fabric and WIP sit in the business for over 100 days before converting to cash. Over the same period, Nisala's cash balance fell from LKR 90m to a low of LKR 60m, while short-term borrowings rose from 150 to 210 million. The Pre-seen explicitly identifies increased working capital requirements as one of four growth challenges facing the company. As volumes continue to scale, this problem will worsen unless addressed directly."
Slide 2 (~2:00)
"Three causes. First, fabric procurement is not demand-linked — the company is ordering more than immediate production needs to ensure supply continuity, but without a formal reorder system, the result is over-stocking. Second, WIP accumulates between cutting and sewing because there is no limit on how many cut panels can wait in the buffer area — panels sit between stages, consuming cash without progressing. Third, retailer payment terms of 64 days lock significant cash in trade receivables — LKR 400 million by FY2025 — and these terms haven't been renegotiated as Nisala's volumes and bargaining position have grown."
Slide 3 (~1:30)
"Three solutions. First — introduce consumption-linked fabric ordering. Define a reorder point based on weekly usage and supplier lead time. Tharushi Silva can implement this in a spreadsheet within days. This stops the over-procurement cycle. Second — implement a Kanban-style WIP limit between cutting and sewing. Cutting only proceeds when sewing is ready to absorb output. A physical staging limit — no technology required — prevents inter-stage WIP build-up. Third — offer a small early payment discount to Nisala's top two retail accounts. A 1–2% discount for 30-day payment could release LKR 30–50 million in cash, more than covering the cost of the discount and reducing short-term borrowing meaningfully."
📋

Full Rubric — Scenario 4: Working Capital & Financial Sustainability

All 4 criteria · All 4 bands · What each level looks like for this specific scenario
🎯
The Excellent unlock: Making the WIP-to-cash-conversion link explicit — cut panels sitting between cutting and sewing are cash committed to inventory that cannot be invoiced until delivery. This cross-scenario insight connects operational flow directly to financial consequence, and is the mark of an integrated thinker.
🔍 Analytical Insight 35 marks
Poor
0–14

"Nisala has working capital problems." No distinction between the three WC ratios. Recommends invoice factoring — financing the symptom rather than fixing the operational cause.

Adequate
15–21

Inventory identified as the pressure point. Over-procurement mentioned. WIP accumulation treated as a production issue without the cash-conversion implication articulated. Solutions address receivables (stable) rather than inventory (rising).

Good
22–28

Correctly isolates inventory days (101.6, worsening trend) as the driver. Over-procurement and WIP accumulation identified as operational causes. Three-year trend data used. Solutions are operationally grounded with a commercial receivables lever.

Excellent
29–35

WIP 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
Poor
0–10

WC ratios listed on Slide 1 without narrative. Examiner cannot tell which metric is the problem until Slide 2. No opening hook that frames why this matters now.

Adequate
11–15

Inventory days trend stated. Cash fall noted. But the contrast with stable receivable and payable days is not made — examiner cannot tell the student has diagnosed which metric is the actual problem.

Good
16–20

"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." Concise, diagnostic, and clear.

Excellent
21–25

Opens with the cash story arc: "Cash fell from LKR 90m to 60m as revenue grew 33%. It partially recovered — but only to 85m. We're 5% below our 2022 cash position despite being a third larger. Working capital efficiency is not keeping pace with growth."

🎙️ Persuasion & Presence 20 marks
Poor
0–8

Balance sheet ratios read from slides. No sense of urgency. Financial recommendations presented as finance-department suggestions rather than operational priorities requiring immediate action.

Adequate
9–12

Correct content with neutral tone. The connection between rising inventory days and increasing short-term borrowing costs not emphasised as an escalating cost risk.

Good
13–16

"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.

Excellent
17–20

"The early payment discount could release LKR 30–50m. That's more than the 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, delivered as a boardroom recommendation.

🌐 Integration of External Data 20 marks
Poor
0–8

No market context. Working capital analysis entirely internal. Interest rate environment, retail payment norms, or WC benchmarks not referenced anywhere.

Adequate
9–12

Notes retailers pay slowly as a generic fact without contextualising against Sri Lankan retail sector concentration, payment norms, or Nisala's improving bargaining position.

Good
13–16

Sri Lankan retailer concentration cited as the leverage dynamic for payment terms. Post-2022 interest rate environment noted. Kanban referenced as industry-standard WIP management practice.

Excellent
17–20

Growth-phase framing: "Companies scaling from SME to mid-market face this working capital stretch predictably. 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."

⚠️

Common Mistakes — Scenario 4

Errors students consistently make on Working Capital & Financial Sustainability pitches
✗ Weak version
Treating "working capital pressure" as the issue rather than diagnosing which specific element of working capital is the problem. Students often state the WC cycle is 90.7 days without identifying that inventory days are the culprit — receivable and payable days are actually stable. The analysis stays surface-level and vague.
Analytical Insight: Adequate — identifies symptom, not root location
✓ Strong version
Pinpoint the specific driver: "Receivable days are stable at 64 and payable days at 75 — the working capital pressure is almost entirely from inventory days rising from 96 to 101.6 over three years. That is where the cash is being consumed." This demonstrates you've actually analysed the balance sheet data, not just stated the headline.
Why it matters: The Pre-seen provides three years of working capital ratios precisely so students can distinguish between stable and deteriorating metrics. An examiner looking for "insightful use of Pre-seen" expects you to identify that inventory, not receivables, is the specific driver. Generic "working capital is under pressure" misses that entirely.
✗ Weak version
Recommending factoring or invoice discounting as the primary solution. While technically a valid working capital tool, recommending external financing solutions as the first response signals a preference for borrowing over fixing the operational root cause — and ignores that Nisala's short-term borrowings have already risen from LKR 150m to 200m. More debt is not the solution when the problem is operational inefficiency.
Integrity: Poor — financing a symptom rather than fixing the cause
✓ Strong version
Prioritise operational fixes first — reorder-point procurement (stops over-buying fabric), WIP Kanban limit (frees cash stuck between stages) — before any financing conversation. Financing is a last resort when the operational leak hasn't been fixed. "We reduce the cash need first, then if a gap remains, we can discuss how to bridge it."
Why it matters: This is fundamentally an operations management scenario, not a corporate finance one. The causes are operational — over-procurement, WIP accumulation. A pitch that goes straight to factoring or overdraft extension has misdiagnosed the problem at the root level.
✗ Weak version
Missing the WIP-to-WC connection. Students discussing WIP accumulation often frame it purely as a production bottleneck (Scenario 1 territory) without making the financial link explicit — that WIP sitting between cutting and sewing is cash locked in partially completed inventory that cannot be invoiced until garments are delivered. The financial and operational dimensions of the same problem are not joined up.
Analytical Insight: Good — correct observation but incomplete integration
✓ Strong version
Make the financial consequence explicit: "Every cut panel waiting in the buffer between cutting and sewing represents fabric cost that has been consumed but cannot yet be invoiced — it is cash committed to WIP. A Kanban WIP limit doesn't just improve production flow; it accelerates the conversion of raw material cost into completed goods that can be delivered and invoiced."
Why it matters: Scenario 4 rewards students who connect operations to finance. The same WIP bottleneck appears in Scenario 1 — but here the analytical insight required is the financial consequence, not just the production consequence. Failing to make that link keeps the answer in "Good" territory.
Scenario Area 05
Ethical Scaling, Workforce
Sustainability & Community
This scenario demands that you demonstrate Integrity Skills as much as analytical ones. The issue here is not just about operational efficiency — it is about the responsible management of people and community during a period of rapid production growth. Examiners will reward practical, balanced solutions over either idealism or cold profit-logic.
Overtime FatigueWorker WelfareESG / Retailer StandardsSustainabilityChapter A + D + E
1

Slide 1 — What Is the Issue?

The Issue: As Nisala scales production to meet growing retailer demand, it is relying on a sustained overtime model that is simultaneously eroding worker productivity, increasing the risk of safety incidents, and creating a growing misalignment between the company's workforce practices and the ethical sourcing standards that its retail customers are increasingly applying to their suppliers.
⚠️
Why This Matters: The Pre-seen explicitly states that "management acknowledges that excessive overtime leads to declining productivity and worker fatigue." This is simultaneously a financial risk (output per hour drops from 2.05 to 1.93 during peak), a welfare concern for 250+ production workers, and a reputational risk — the Pre-seen notes that retailers are increasingly monitoring ethical sourcing standards, and Nisala's current compliance is to local legal minimums only.
📊
Pre-seen Evidence: Peak overtime: +15% hours for only +8.3% output. The company has basic upskilling programmes but no formal overtime welfare safeguards. 320 employees — a significant Gampaha District employer with community responsibility. Compliance is to local law only, with retailer expectations potentially exceeding legal minimums (noted as a future compliance risk).
2

Slide 2 — Why Is It Occurring?

Root causes · Fishbone categories · 5 Whys drill-down · Quantitative & qualitative
Root Cause 01 Quantitative Qualitative

Production Scheduling Treats Overtime as the Default Capacity Lever, Not a Last Resort

Capacity utilisation reaches 92% during peak periods — achieved only by adding 15% extra labour hours for 8.3% more output. Overtime has become a planned, structural response to demand peaks rather than an emergency measure. Qualitatively, the production scheduling culture is reactive: demand spikes are met by extending the working day rather than by planning ahead, cross-deploying staff, or smoothing order intake across a longer window.

+15% hours → +8.3% output · scheduling not redesigned since batch era
Fishbone (Ishikawa) Analysis
Process
Production scheduling has not been redesigned since Nisala was a batch producer — no forward demand smoothing protocol exists to spread peak volume across a longer window
No advance production start triggered by confirmed orders — production begins close to the delivery window, leaving overtime as the only recovery option
Management
Planning Manager (Tharushi Silva) coordinates retailer orders but this intelligence is not formally used to trigger early production starts ahead of peak periods
Overtime approved reactively by HR (Chamara Jayasekara) on request — no proactive capacity planning meeting between Production, Planning, and HR before peak season
People
Overtime has become culturally normalised — workers and supervisors accept it as "how things work during peak" rather than flagging it as an operational design failure
No incentive for Production Manager to avoid overtime — performance is measured on units delivered, not on labour cost efficiency or overtime hours consumed
5 Whys Drill-Down
Why 1
Why does Nisala rely on overtime to meet peak demand every season?
Because production scheduling does not begin early enough — peak orders arrive, capacity is insufficient, and overtime is the only available response.
Why 2
Why doesn't production begin earlier to spread the peak load?
Because confirmed advance orders from retailers are not routinely used to trigger early production starts — the planning process is reactive to delivery deadlines, not proactive on order confirmation.
Why 3
Why is planning reactive rather than forward-looking?
Because the Planning Manager's role is focused on order coordination and delivery scheduling — not on proactively redesigning the production window to absorb demand more evenly.
Why 4
Why hasn't the planning role been expanded to include demand smoothing?
Because there is no cross-functional S&OP process involving Planning, Production, and Finance — each function operates within its own horizon without a joint capacity plan.
Why 5
Why is there no cross-functional capacity planning process?
Because Nisala's management structure has not evolved to match the complexity of its current order volumes — the batch-era operating model is still in place even though the production model has scaled significantly.
Root cause identified: An operating model mismatch — Nisala's scheduling and planning processes are calibrated for a smaller, batch-oriented business. As order volumes grew, the gap between planning capability and operational complexity widened, and overtime filled the space. Until a proactive S&OP process is built, overtime will remain the structural response to every peak.
Root Cause 02 Qualitative

The Upskilling Programme Is Stage-Specific — It Creates Competence, Not Workforce Flexibility

The Pre-seen confirms that basic upskilling programmes exist for sewing operators, covering sewing techniques, quality awareness, and machine handling. Qualitatively, this programme builds competence within a single stage — it does not create cross-trained, multi-stage operators who can be redeployed when demand shifts between cutting, sewing, and finishing. The result is a workforce that is skilled but inflexible: when one section is overloaded, the only option is overtime, not internal redeployment.

Upskilling confirmed but stage-specific · no cross-stage certification · no flexible deployment pool
Fishbone (Ishikawa) Analysis
People
Workers trained in one stage only — no multi-stage certification exists that would allow redeployment between cutting, sewing, and finishing
Workers may be willing to cross-train but have not been given the opportunity or incentive — the programme was not designed with flexibility as an outcome
Management
HR Manager (Chamara Jayasekara) manages training as a welfare and compliance function — not as a workforce flexibility planning tool linked to production capacity management
No "flexible worker" designation or premium in the HR system — cross-trained workers are not formally recognised or rewarded for their broader capability
Process
Training programme designed in isolation from production capacity planning — no feedback loop between which stages face peak pressure and which skills are trained
No structured job rotation programme that would naturally build multi-stage familiarity as a byproduct of normal operations
5 Whys Drill-Down
Why 1
Why can't Nisala redeploy workers from underloaded stages to overloaded stages during peak periods?
Because most workers are trained in one production stage only — they cannot competently perform cutting, sewing, and finishing interchangeably.
Why 2
Why are workers trained in only one stage?
Because the upskilling programme was designed for competence within a single stage — multi-stage training was not included in its scope or objectives.
Why 3
Why was multi-stage training not included?
Because the programme was designed primarily as a quality and welfare initiative — not as a workforce flexibility strategy linked to capacity management.
Why 4
Why wasn't flexibility considered as an objective of the training programme?
Because HR and Production did not jointly design the programme — it was developed by the HR Manager without a production capacity input that would have highlighted the peak flexibility gap.
Why 5
Why did HR design training without a Production input?
Because there is no cross-functional workforce planning process at Nisala — HR manages training and welfare, Production manages scheduling and output, and the two functions do not have a shared capacity planning agenda.
Root cause identified: The training programme was designed by HR for a welfare and quality purpose — a good outcome in itself. But it was not co-designed with Production as a capacity flexibility tool. This is a cross-functional planning gap that has made the programme less useful for peak capacity management than it could be with minor redesign.
Root Cause 03 Qualitative

No Formal Welfare Monitoring Framework During Peak Periods — Compliance Is to Legal Minimum Only

HR Manager Chamara Jayasekara oversees overtime approvals — but the Pre-seen gives no evidence of structured welfare monitoring during sustained peak periods: no fatigue assessments, no shift rotation protocols, no maximum consecutive overtime thresholds beyond legal minimums. Qualitatively, this reflects a compliance mindset rather than a welfare leadership mindset — Nisala meets the letter of labour law but has not built the formal systems that ethical sourcing auditors increasingly expect to see documented.

HR oversight exists · welfare monitoring absent · compliance-only posture · no documented welfare protocol
Fishbone (Ishikawa) Analysis
Management
No formal welfare protocol document — welfare management during peak periods is informal, discretionary, and undocumented
HR Manager manages overtime approvals reactively — no proactive peak-period welfare plan is prepared before each season
People
Workers may be experiencing fatigue but have no formal channel to report welfare concerns — no anonymous feedback mechanism, no welfare check-in at shift end
Supervisors incentivised for output — worker fatigue signals are interpreted as productivity problems to be managed, not welfare signals to be addressed
Environment
Compliance culture rather than welfare-leadership culture — the minimum required by Sri Lankan labour law is the ceiling, not the floor, of welfare management
No documented evidence of welfare protocols means buyer audit requests for ethical sourcing documentation cannot be satisfied — a growing commercial risk as retailer audit standards evolve
5 Whys Drill-Down
Why 1
Why do workers not have formal welfare protections beyond legal minimums during peak overtime periods?
Because no formal welfare protocol has been written — welfare management during peaks is handled informally by individual supervisors without a documented standard.
Why 2
Why has no formal protocol been written?
Because Nisala's welfare management posture is compliance-oriented — the legal minimum is treated as the standard, and no commercial or ethical pressure has yet triggered a more proactive approach.
Why 3
Why has no commercial or ethical pressure triggered a more proactive approach yet?
Because Nisala sells to domestic retailers who have not yet formally required ethical sourcing documentation as a contract condition — but the Pre-seen signals this is changing.
Why 4
Why haven't retailer expectations been anticipated and prepared for in advance?
Because there is no function or person at Nisala monitoring the evolution of retailer ethical sourcing requirements — commercial compliance is tracked reactively, not monitored proactively.
Why 5
Why is commercial compliance monitored reactively?
Because Nisala's governance structure focuses on operational and financial performance — ESG and ethical compliance are not formally integrated into the business planning process or the management team's accountabilities.
Root cause identified: A compliance ceiling rather than a welfare floor — Nisala meets legal requirements but has not built the formal welfare management systems that ethical sourcing leadership requires. The commercial risk is that what is legally sufficient today may become commercially disqualifying as retailer audit standards evolve faster than Nisala's governance keeps pace.
3

Slide 3 — What Can Nisala Do?

⚖️
Integrity Principle: Solutions here must balance operational efficiency with genuine worker welfare — not sacrifice one for the other. Recommendations that only serve profit without addressing worker wellbeing will score poorly on the Integrity Skills dimension. Show that you understand the dual obligation.
Solution 01 → Addresses Cause 01

Implement a Forward Demand Smoothing Protocol — Spread Peak Volume Across a Longer Window

Work with Tharushi Silva (Planning & Merchandising) to begin peak-season production earlier, using confirmed advance orders from retail accounts to front-load production in the weeks before peak demand. This reduces the intensity of the peak period, lowers the overtime requirement, and improves output quality by avoiding the fatigue-driven efficiency drop. Many garment manufacturers in Sri Lanka use 6-week rolling production schedules to achieve this — it requires retailer collaboration, which Nisala's growing volume now makes possible to negotiate.

Planning-led · Retailer coordination needed · 4–8 weeks
Solution 02 → Addresses Cause 02

Expand Upskilling to Create a Cross-Trained Flexible Workforce Pool

Identify 15–20 versatile operators who can be certified to work across two or more production stages. This creates a flexible deployment pool that can be redirected to the highest-pressure stage during peak periods — reducing the need for across-the-board overtime. The Pre-seen notes that basic upskilling already exists for sewing operators — extending this to cutting and finishing familiarisation is a natural next step. Cross-training also improves worker employability and job satisfaction, directly addressing the welfare dimension.

Low cost · 6–8 weeks to certify · Builds on existing programme
Solution 03 → Addresses Cause 03

Introduce a Simple Peak-Period Welfare Protocol with Maximum Consecutive Overtime Limits

Chamara Jayasekara formalises a written welfare protocol covering: maximum consecutive overtime shifts before a mandatory rest day, a voluntary overtime roster (not compulsory), and a brief end-of-shift check-in for workers on extended hours. This protocol costs nothing to implement, demonstrates genuine care for the 250 production workers, and provides documented evidence of ethical workforce management — exactly the kind of record that retail buyer audits increasingly require. This directly addresses the future compliance risk the Pre-seen flags.

HR-led · Document-based · Immediate
Integration of External Data — 20 Mark Criterion
  • Sri Lanka's garment export sector, competing for international buyer contracts, has faced increasing pressure from WRAP (Worldwide Responsible Accredited Production) and other ethical certification bodies — and domestic retailers are now beginning to adopt similar standards as ESG awareness grows among Sri Lankan consumers (a Pre-seen trend).
  • The ILO's research on garment worker fatigue consistently shows that sustained overtime above 10 hours per day for more than 3 consecutive days produces measurable increases in defect rates and incident frequency — precisely the pattern observable in Nisala's 4.5% rework rate during peak periods.
  • Companies with strong ethical practices experience, on average, 40% lower employee turnover — particularly relevant in Gampaha District, where Nisala competes with other garment employers for skilled sewing operators. Reducing turnover has direct cost benefits via lower recruitment and retraining costs.
  • The UN Sustainable Development Goals (particularly SDG 8: Decent Work) are increasingly referenced by Sri Lankan retailers in supplier codes of conduct — framing ethical workforce management as a commercial as well as moral imperative for Nisala.
Sample Spoken Script — 5 Minutes
Slide 1 (~1:30)
"The issue I want to address today sits at the intersection of operational performance and workforce welfare. Nisala is growing — revenue is up, orders are increasing — but that growth is being sustained, in part, by a reliance on overtime that management itself acknowledges is causing declining productivity and worker fatigue. During peak periods, Nisala adds 15% more labour hours to achieve only 8.3% more output. Output per hour drops. Rework rates rise. And meanwhile, the 250 production workers bearing this burden are doing so without formal welfare safeguards — creating a growing gap between Nisala's practices and the ethical sourcing standards that its retail customers are beginning to apply."
Slide 2 (~2:00)
"Three causes. First, overtime has become the default capacity buffer — production scheduling has not been redesigned since Nisala was a smaller batch producer, and demand peaks are met by adding hours rather than planning ahead. Second, the upskilling programme, though a positive foundation, only covers sewing operators in sewing tasks — it doesn't create cross-trained workers who can flex between stages, so when one section is overloaded, there's no internal redeployment option. Third — and this is the integrity gap — there is no formal welfare protocol during high-intensity periods. No maximum consecutive shift limits, no voluntary overtime roster, no fatigue monitoring. The Pre-seen explicitly flags this as a future compliance risk."
Slide 3 (~1:30)
"Three solutions that address both the operational and the ethical dimension. First — implement forward demand smoothing. Work with the Planning Manager to begin peak production earlier, using confirmed advance orders, so overtime is spread over more weeks rather than concentrated. Second — extend the upskilling programme to cross-train 15 to 20 versatile operators across two stages. This creates a flexible deployment pool for peak periods — reducing overtime and improving worker development simultaneously. Third — Chamara Jayasekara formalises a simple peak-period welfare protocol: maximum consecutive overtime shifts, a voluntary roster, and brief end-of-shift check-ins. This costs nothing, demonstrates genuine care for Nisala's people, and creates the documentation that retail buyer audits are now beginning to request."
📋

Full Rubric — Scenario 5: Ethics, Workforce & Community

All 4 criteria · All 4 bands · What each level looks like for this specific scenario
🎯
The Excellent unlock: Framing ethical workforce management as a commercial necessity, not just a moral obligation. The welfare protocol earns marks not only because it's the right thing to do — but because retail buyer audit requirements are evolving and Nisala currently has no documented evidence of ethical management. Both arguments together are Excellent; either alone is only Good.
🔍 Analytical Insight 35 marks
Poor
0–14

Pure moral argument with no business data. "Nisala must treat workers better." No reference to overtime productivity loss, rework rate connection, or compliance risk. Generic CSR recommendations disconnected from the overtime issue.

Adequate
15–21

Overtime identified. +15%/+8.3% data cited. Causes include "no planning ahead" but narrow upskilling gap and welfare monitoring absence are missed. Solutions focus on overtime limits without a structural fix for the demand peak.

Good
22–28

Dual financial and ethical framing. All three causes identified. Solutions address all three: demand smoothing (structural), cross-training (flexibility), welfare protocol (safeguards). Integrity Skills dimension explicitly acknowledged in Slide 3.

Excellent
29–35

4.5% rework directly connected to overtime fatigue — rework as a measurable financial consequence of welfare failure. Upskilling identified as a precondition for cross-training not yet completed. Welfare protocol framed as buyer audit documentation — a commercial, not just ethical, argument.

🗂️ Communication Clarity 25 marks
Poor
0–10

Slide 1 is a values statement. No business data. Examiner cannot connect the ethical argument to Nisala's operational reality. Reads like a CSR brochure, not an analytical pitch.

Adequate
11–15

Correct structure. Dual framing present but connection between financial and ethical dimensions not clearly articulated. Examiner must infer the link between overtime hours and rework rate.

Good
16–20

Opens with both arguments in one sentence: "Nisala's reliance on overtime is not just a welfare concern — the +15% hours that deliver only +8.3% more output is also a financial inefficiency." The dual case made immediately and clearly.

Excellent
21–25

Solutions in Slide 3 explicitly layered: "Solution 1 reduces the need for overtime structurally. Solution 2 increases the flexibility to absorb peaks without overtime. Solution 3 protects workers when some overtime remains unavoidable." Shows the pitch was designed, not assembled.

🎙️ Persuasion & Presence 20 marks
Poor
0–8

Ethical argument delivered flatly as a duty statement. No genuine conviction. Business data absent so the argument feels theoretical rather than grounded in Nisala's actual situation.

Adequate
9–12

Welfare concern articulated with some warmth but business case weak or absent. Sounds like an ethics lecture rather than a management recommendation with operational justification.

Good
13–16

Both arguments delivered with conviction. "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."

Excellent
17–20

"Nisala has 320 people depending on this company. Managing their welfare responsibly is not a cost — it is what protects output quality, workforce loyalty, and the commercial relationships that depend on ethical sourcing. I am recommending we formalise this — this week, at zero cost."

🌐 Integration of External Data 20 marks
Poor
0–8

No external standards, buyer requirements, or ESG trends referenced. Argument based entirely on internal moral obligation with no commercial context.

Adequate
9–12

"Ethical sourcing is increasingly important" without specifying which buyers, which standards, or what the commercial consequence of non-compliance would be for Nisala specifically.

Good
13–16

Pre-seen stated trend (retailers monitoring ethical sourcing) cited. ILO overtime-fatigue research connected to Nisala's rework rate. 40% lower turnover statistic cited as a Gampaha District workforce retention argument.

Excellent
17–20

"SDG 8, WRAP certification, and evolving retail codes 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."

⚠️

Common Mistakes — Scenario 5

Errors students consistently make on Ethics, Workforce & Community pitches
✗ Weak version
Treating this as purely an ethics/values pitch with no financial anchor. Students go straight to "Nisala has a moral obligation to its workers" without connecting the welfare issue to business performance data. The pitch feels like a corporate values statement rather than a business analysis — and scores poorly on Analytical Insight because the financial consequence is never quantified.
Analytical Insight: Adequate — ethical framing without business grounding
✓ Strong version
Lead with the dual financial and welfare consequence: "Overtime that adds 15% hours for 8.3% more output isn't just ethically questionable — it's financially inefficient. Output per hour drops, rework rises to 4.5%, and the cost per unit increases at exactly the moment margins are under pressure." The financial and ethical cases reinforce each other — use both.
Why it matters: Analytical Insight carries 35 marks. Even in Scenario 5, the examiner is testing business reasoning, not moral conviction. A pitch that only makes the ethical case will cap out at "Adequate" on the highest-weighted criterion. The financial and ethical arguments are genuinely aligned here — make both.
✗ Weak version
Recommending broad CSR initiatives disconnected from the specific operational issue. Suggestions like "Nisala should publish a sustainability report," "donate to community schools," or "achieve ISO 14001 certification" are not solutions to overtime-driven workforce welfare — they are generic CSR actions that ignore the specific problem entirely and signal the student has not focused their analysis.
Analytical Insight: Poor — solutions don't address the diagnosed causes
✓ Strong version
Solutions must directly address the overtime dependency: demand smoothing to reduce peak intensity, cross-training to create deployment flexibility, and a welfare protocol to formalise safeguards. These are operational and HR interventions, not brand exercises. Every solution should trace back to one of the three named root causes.
Why it matters: The official guidance is explicit — solutions must "directly address the causes you identified." CSR programmes that don't reduce overtime or protect workers during peaks don't address the causes at all. This is one of the most common ways students lose marks on Scenario 5 specifically.
✗ Weak version
Ignoring the compliance risk angle entirely. Many students frame Scenario 5 purely as an internal welfare question — "Nisala should care for its workers because it's the right thing to do" — without connecting it to the commercial reality that retailers are increasingly auditing supplier labour practices, and Nisala currently meets only local legal minimums. The commercial urgency of the issue is missed.
External Integration: Adequate — misses the commercial dimension of the ethical risk
✓ Strong version
Explicitly frame the commercial compliance risk: "The Pre-seen notes that retailers are increasingly monitoring ethical sourcing standards, and that Nisala currently meets only local legal minimums. As buyer audit requirements evolve, what is legally compliant today may become commercially disqualifying tomorrow — making a welfare protocol not just ethically right, but commercially necessary."
Why it matters: This is the insight that earns strong marks on External Integration (20). Connecting Nisala's internal welfare practices to the external commercial risk from evolving buyer standards demonstrates genuine commercial awareness — exactly what the rubric's "well-chosen industry/contextual cues" and "strong commercial awareness" descriptors are looking for.