Water / accepted unit
Energy / accepted unit
Now passingAccepted release
Material flowBatch evidenceAccepted-unit gate
Conceptual animation, not factory data. Gauges are not readings.
Capabilities / Sustainability measurement and traceability
Water, energy and material claims begin with a boundary, an accepted denominator and an unbroken evidence chain.
Illustrative tokens, not readings.Withdrawal = consumption + discharge + unresolved. Illustrative proportions, not readings.
A footprint becomes auditable when accepted output, process perimeter and evidence rules are explicit. Use this selector to inspect the accounting question before reporting a result.
Boundary instrument
Boundary 01 of 04
The denominator is accepted garments at a named quality gate. Rejects and work in progress stay outside that count, while their water, energy and rework loads remain inside the boundary numerator.
Intensity = boundary load ÷ accepted garments; absolute load remains visible beside it.
Boundary 02 of 04
Accepted units inherit their batch genealogy. Splits, merges, subcontracted operations and rework resolve to the same reporting gate, so numerator and denominator describe the same population.
Batch genealogy + accepted-unit register + process loads within the declared perimeter.
Boundary 03 of 04
Define where measurement begins and ends, the operations between those gates and the treatment of outsourced work. Exclusions remain visible rather than disappearing into a seemingly lower intensity.
Included operations, excluded operations, transfers and allocation rules are stated together.
Boundary 04 of 04
Metered withdrawal enters the site account. Derive consumption and discharge only where the water balance supports them, recording return destination, quality evidence, recycling and unresolved losses.
Withdrawal ≠ consumption ≠ discharge; each term needs its own evidence and boundary.
Loads: boundary water and energy stay in the numerator.Accepted garments: only units through the release gate count below the bar.Rejects and WIP: their load stays above the bar, their units stay out.
This illustrative method control is not a measured footprint or live factory connection. It changes the accounting question, not an environmental result.
Sector context
Cameroon programme evidence frames why local measurement matters, but does not establish site water, energy or traceability performance. Sector context and operational evidence remain separate.
About 95%
Cotton fibre exported rawR06 programme-annex estimate, not a current verified baseline.
About 5%
Cotton fibre processed locallyR06 programme-annex estimate, kept distinct from seed cotton.
50% by 2030
Local-processing policy targetR07 policy ambition, not installed capacity or a delivered result.
No value
Factory baselineSite records, meter coverage, accepted-output definitions and batch histories are needed before this frame can be filled. The programme annex provides none of them.
One strand = 5 percent of cotton fibre; R06 shares are approximate. The target gate is a policy ambition (R07), not installed capacity.
Gap arithmetic, illustrative scrubber
45points between a 5% local share (R06) and the 50% target (R07)50 minus 5 = 45
Hypothetical share for the arithmetic only. It is arithmetic, not a forecast, and not factory data.
R06 reports a cotton sector dominated by raw fibre export, with a small share processed locally. R07 restates a national local-processing target. Both are programme-annex sources with qualifications, not independently verified measurements of present factory activity.
These figures can motivate a measurement architecture; they cannot populate its meters. A defensible baseline needs site records, accepted-output definitions, meter coverage, water balances, batch histories and documented gaps. No site saving, live traceability or certification is asserted.
R06 and R07 support sector context only. They provide no water or energy quantities, product footprints, site savings, chain-of-custody coverage or certification evidence.
Measurement contract
A credible account joins physical measurements to production events without hiding the judgements between them. Fix the time window, process boundary, accepted-unit gate and exception rules before analysis.
Variance open on 2 of 3 rows0 of 3 rows unexplained, 1 estimate flagged
Meter A · Direct
Direct reading, calibrated interval
Batch X · Dyeing
Accepted and rework units counted
Meter B · Shared
Shared bus, needs an allocation rule
Batch Y · Cut & sew
Split across two active batches
Meter C · Manual
Interval estimate, flagged in ledger
Batch Z · Rework
Same genealogy, added process load
Contract diagram 01 · Meter ledger architecture
Contract diagram 02 · Batch genealogy & yield
Contract diagram 03 · Catchment water balance
Contract diagram 04 · Dual reporting pair
Early in the run: absolute load and intensity per accepted garment both sit near their starting points.Mid-run: absolute load has climbed while intensity per accepted garment has begun to fall.Full output: absolute load is highest while intensity per accepted garment is lowest. Report both.
Measurement contract term 01 of 04 · Meter ledger
Record meter identity, location, unit, reading interval, calibration status and process served. Shared meters need an allocation method. Keep estimates distinct from direct readings, and append corrections rather than replacing original entries.
Measurement contract term 02 of 04 · Batch ledger
Link receipts, lot issue, machine runs, quality release and dispatch through stable batch identifiers. Record work in progress, rejects, rework and yield loss so loads cannot be divided by a more favourable production population.
Measurement contract term 03 of 04 · Water account
Withdrawal enters the defined system. Consumption is not returned to the same catchment or system within the account. Discharge leaves through a named route. Each needs suitable metering and reconciliation, with quality evidence where relevant.
Measurement contract term 04 of 04 · Reporting pair
Per-unit water and energy can fall while total withdrawal or energy use rises with output. Report both forms for the same period and boundary, beside accepted volume and mix. Efficiency language cannot conceal an opposing absolute trend.
Allocation, gap estimates and normalisation change interpretation. Publish each rule with the result and test whether a reasonable alternative changes the decision.
Reconciliation sequence
The review follows material and meters together. Each sticky step changes the batch-chain drawing, keeping exceptions visible until resolved or allowed to limit the claim.
Chain of custody
A certificate file or supplier reference cannot follow material through a factory. Chain of custody must preserve identity as lots are received, combined, divided, processed, repaired and released.
If a garment cannot be followed backwards, its footprint cannot be explained forwards.
Backward trace progress: 4 of 5 nodes verified · 1 exception quarantinedIllustrative chain and records. Not a real product history.
Each custody event identifies the lot, actor, location, time, quantity, process and resulting batch. Transformations record inputs and outputs; transfers record responsibility changing hands. Source documents support events rather than substituting for them. Carried-forward attributes need rules for splits, merges and losses.
Missing events break the chain. Use an exception state, bounded reconstruction where evidence permits, or an unverified segment, never an invented clean passage. Rework rejoins the same genealogy with added meter loads and process events intact. Release the accepted unit once while every resource-consuming attempt remains visible.
Custody record · Step 01 · illustrative
Source documents support the event. They do not replace it.
Custody record · Step 02 · illustrative
A transfer records responsibility changing hands.
Custody record · Step 03 · illustrative
Use an exception state or bounded reconstruction. Never invent a clean passage.
Custody record · Step 04 · illustrative
Meter loads attach to the run, not to the paperwork.
Custody record · Step 05 · illustrative
Release once, while every resource-consuming attempt stays visible.
Operating review
A review dial directs attention to coverage, exceptions and unresolved decisions. It is a governance grammar, not live monitoring.
72%Meter coverage
Open custody gaps
Unresolved rework
Claim withheldCoverage is below the illustrative floor. 2 custody gaps lack a disposition. 1 rework segment is unresolved.
Coverage
Review unmetered processes, shared utilities, manual readings and outsourced work. Assign a remedy rather than treating absent data as zero load.
Exceptions
Classify missing events, suspect readings and broken identities. Hold affected claims until evidence supports closure, recording the reason for any override.
Rework
Track repeated processing against the same batch and accepted output, exposing resource use without confusing added work with saleable units.
A governance grammar, not live monitoring. All values here are illustrative controls. The ochre tick marks an illustrative release floor.
Reduction-project governance
A project proposal is not a saving. Separate expected effect, measured change and an approved public claim. Freeze the baseline before work starts. Release only the effect the evidence supports.
Read the shared measurement approachAbsolute load channelWater & energy reported on their own
Intensity per accepted garmentReported beside accepted volume & mix
Claim status
Claim withheldNext: pass the baseline gate. Tick its evidence in the panel.Gate 01 of 03
Approve the counterfactual, measurement coverage and normalisation before work begins.
Before implementation, freeze the baseline, boundary, accepted-output definition and measurement plan. Record the intervention, affected meters, production conditions and possible burden shifting. A project cannot pass by shifting load outside the perimeter or benefiting from quieter production.
0 of 3 evidence items ticked
Gate 02 of 03
Reconcile accepted output, meter evidence, rework, water balance and absolute load.
After implementation, verify meter quality, normalisation, chain integrity and absolute and per-unit results over a justified window.
0 of 5 evidence items ticked
Gate 03 of 03
Publish only the supported effect, with its period, boundary, limitations and evidence owner.
Independent review should confirm persistence and disclose adverse effects. Keep inadequately supported findings internal and provisional.
0 of 4 evidence items ticked
Demonstration only. Nothing is recorded, approved or sent.
Water per accepted unit
Energy per accepted unit
Accepted release gateIllustrative gauges settle at the release gate. Not factory readings.
Continue through the evidence
These routes extend the accounting, product and programme questions. The closing chain keeps provenance attached to each door.
Active hover read-out 01 / 06 · Paper
Examine the process loads behind an accepted-unit account.
/library/water-dye-and-energy-per-unit/
Paper. Open route in this build.
Follow this threadActive hover read-out 02 / 06 · Paper
Explore identity, custody and evidence across transformations.
/library/traceable-by-design/
Paper. Open route in this build.
Follow this threadActive hover read-out 03 / 06 · Paper
Carry boundary discipline into product carbon accounting.
/library/carbon-per-garment/
Paper. Open route in this build.
Follow this threadActive hover read-out 04 / 06 · Tool
Interrogate a footprint through explicit inputs and assumptions.
/tools/footprint/
Tool. Open route in this build.
Follow this threadActive hover read-out 05 / 06 · Tool
Inspect the provenance events a product history requires.
/tools/trace-a-garment/
Tool. Open route in this build.
Follow this threadActive hover read-out 06 / 06 · Programme
Connect measurement governance with the wider performance method.
/programmes/cameroon-textile/performance-system/
Programme. Open route in this build.
Follow this thread