Skip to content
GREEN FUTURETECH.
Explore

Research libraryThe Compliance Frontier

Chapter 13 of 14 · Part IV · Draft web edition

The cost of evidence should be tested against the order it serves

A supplier needs a transparent cost model and a practical rehearsal rather than an assumed compliance premium.

Sections
7
Exhibits
4
Minutes
24
Sources
9
EX 56 · Request response: adds 21. Running total 120 illustrative cost units

The cloth is woven from this chapter's 4 exhibits: each weft is one exhibit's own data, normalised; each warp group is a section. The probe reads the exhibit's own value where it crosses. Procedural visualisation, not a measurement.

The chapter as a draft: 7 sections, 3 exhibit wefts, one shuttle.

Lead exhibit · 56ReconciliationillustrativeSetup and recurring evidence work have different cost drivers
050100150+18Product review+42System setup+15Initial training+24Periodic testing+21Request response+30Remediationreserve150Evidence pool

Read-outProduct review: adds 18. Running total 18 illustrative cost units

Method and source

Illustrative model only. Product review 18 + system setup 42 + initial training 15 = 75 setup units. Periodic testing 24 + request response 21 + remediation reserve 30 = 75 recurring units. Total evidence pool = 150 units. No market price, accounting treatment or actual incident is assumed.

Unit: illustrative cost units. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

The chapter's warpBar: share of the reading · square: an exhibit

Section 13.0 · Opening · 1 min · no exhibit of its own · one movement Go to section ↓

Overture · 1 min

An evidence system is worth funding when it lets a supplier release a lawful product, protect workers and answer a defined customer need at a cost the order can bear. The decision cannot start with an assumed compliance premium. It should start with an order model that separates setup from recurring work, states which units can legitimately ship and records the cost of delay without inventing a penalty forecast. A rehearsal then tests whether the supposed evidence system works under pressure. GFT recommends a bounded pilot on a real product and sales route, with measured hours, actual quotations and unresolved legal questions carried into the investment decision. This chapter provides an operating method, not legal, tax or investment advice.

¶ 01

The method has two disciplines. First, no favourable margin can cancel a critical product or worker-protection failure. Second, no administrative burden should be described as waste merely because it is inconvenient. Some evidence is necessary for safety, legal review or remedy. Other work may be duplicated, poorly specified or avoidable through reuse. The economics become useful only when those categories remain distinct.

¶ 02

13.13 min · 10 paragraphs · 1 exhibit

The model must distinguish recurring work from setup

Related · chapter 1210 paragraphs step it

Related exhibit 52 · chapter 12ReconciliationillustrativeAn added evidence request should be priced by its actual work
01002003004000Opening+60Technicalreview+140Laboratory+32Translation+50Workerengagement+30Portaladaptation312Total

Read-outOpening: total 0. Running total 0 illustrative cost units

Method and source

Illustrative arithmetic only: technical review = 6 hours x 10 cost units = 60; laboratory allowance = 140; translation = 4 hours x 8 = 32; worker-engagement preparation = 5 hours x 10 = 50; portal adaptation = 3 hours x 10 = 30. Total = 60 + 140 + 32 + 50 + 30 = 312. All rates and quantities are invented for the worked model, not market fees or a GFT cost baseline.

Unit: illustrative cost units. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

Read this exhibit in its chapter ↗
13.1 · Introduction · paragraph 1 of 10

A supplier should build the cost model around decisions, not around a software subscription or an annual audit line. The first decision is whether the product and sales route have been scoped correctly. Initial product review therefore sits beside legal applicability work, specification mapping and the design of batch records. These are setup activities because they create a reusable basis for later orders. Their treatment in this management model does not prescribe their accounting treatment.

System setup is a second block. It includes configuring record identifiers, access rights, evidence locations, review responsibilities and correction routes. Staff training belongs here when it establishes the initial operating capability. Refresher training after a material legal, product or process change may instead be recurring. The model should state the reason for each classification rather than forcing every invoice into a permanent category.

Recurring evidence work begins once the product family is operating. Periodic testing, specification review, evidence retrieval, buyer responses and controlled disclosure recur by batch, period, request or change event. Worker engagement and remedy need their own lines. A reserve for remediation is a planning provision, not evidence that harm occurred and not a substitute for immediate protective action. Legal advice, internal process change, product redesign and buyer-specific administration also need separate labels. Combining them would hide the decision that management can actually take.

The Commission's ecodesign working plan says that analysis will consider the reliability and cost of associated verification mechanisms. That confirms verification cost is a policy design question. It does not provide a cost curve for a garment supplier.[S13] Likewise, the Commission presents its voluntary SME reporting standard as a way to reduce administrative burden when smaller companies answer sustainability-information requests. It does not establish the saving a particular factory will realise.[S05]

Exhibit 56 shows a purely illustrative cost build-up. It uses cost units rather than a currency so that no market fee, wage rate or vendor quotation is implied. The setup block contains product review, system setup and initial training. The recurring block contains testing, request response and a remediation reserve. The model deliberately leaves production cost, revenue and financing outside the evidence subtotal.

The illustrative total of 150 cost units is not a budget recommendation. Its purpose is to expose the allocation question. Setup may serve several orders, while a buyer-specific portal charge may serve only one. Testing may be triggered by a changed dye recipe rather than by elapsed time. Remedy may be urgent and non-deferrable even when the order has no remaining headroom. Each line therefore needs a driver, an owner and an approval rule.

A useful cost card records the activity, cost object, driver, payer, evidence output and reuse potential. The cost object may be a product family, batch, site, customer or order. The driver may be a changed specification, a test sample, a request field or an hour of qualified work. Reuse potential should be marked as unproved until the same evidence has actually answered a subsequent need without equivalent rework.

The model should also distinguish cash cost from internal effort. An external laboratory invoice is visible immediately. Hours spent by production, human resources or quality staff often remain hidden inside ordinary payroll. Both belong in the pilot log, but they should not be added without a stated valuation basis. Internal hours can first be reported as hours, then converted with a user-supplied loaded rate in a clearly labelled scenario.

Finally, setup allocation is not permission to smooth away a cash constraint. An order model may spread reusable setup across a defined eligible volume for comparison. The cash plan still needs the actual payment timing. A supplier can show a positive allocated margin while lacking the cash to complete required tests before shipment. The investment review needs both views.

13.23 min · 9 paragraphs · 1 exhibit

A comparable unit cost needs a consistent denominator

Exhibit 579 paragraphs step it

Exhibit 57Control mapillustrativeCost per unit changes with volume and duplicated work
Recurring 30Recurring 60Recurring 90500 eligible2102703301,000 eligible1051351652,000 eligible52.567.582.5

Read-out500 eligible: Recurring 30 210, Recurring 60 270, Recurring 90 330 (illustrative cost units per 1,000 eligible shipped units)

Method and source

Illustrative sensitivity, not observed costs or volumes. Formula: (75 allocated setup units + recurring evidence units) / eligible shipped units × 1,000. Rows are eligible volumes of 500, 1,000 and 2,000. Columns use recurring totals of 30, 60 and 90 units. Values are exact model outputs.

Unit: illustrative cost units per 1,000 eligible shipped units. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

13.2 · Introduction · paragraph 1 of 9

The proposed unit measure is evidence cost per eligible shipped unit. Its numerator is allocated setup plus recurring evidence cost attributed to the order. Its denominator is the number of units that have passed the applicable release checks and are contractually available to ship. Production volume, ordered volume and invoiced volume are not automatic substitutes. Each answers a different question.

The word eligible is a control, not a marketing description. Product-safety rules apply to products sold in the EU regardless of where they were made, and businesses in the supply route have responsibilities under the applicable legislation.[S33] REACH restrictions can apply to imported articles as well as domestic production.[S16] A unit should not enter the denominator while a critical requirement within the order's verified scope remains unresolved. The precise release checklist still depends on the product, role and destination.

This denominator prevents a common modelling error. If a supplier divides evidence cost by every garment sewn, it can make the unit cost look low while counting goods that cannot lawfully or contractually be shipped. If it divides by the first small pilot order only, it can overstate the long-run burden of reusable setup. Neither result is a reliable return calculation. The model should show ordered, produced, eligible and shipped quantities as separate fields, with reasons for each difference.

Setup allocation needs an explicit population. A product-review cost may be allocated across the orders that use the unchanged specification and evidence design. A site-wide access-control setup may need a broader allocation. A buyer-specific schema mapping should not be spread across customers that cannot use it. When the useful life or reuse population is uncertain, the chapter recommends sensitivity ranges rather than a single amortisation assumption.

Exhibit 57 illustrates the arithmetic with an allocated setup pool of 75 cost units and three recurring-cost scenarios. The recurring total rises from 30 to 60 to 90 illustrative cost units as duplicated response work rises. Eligible volume varies across 500, 1,000 and 2,000 units. Cost per eligible unit equals allocated setup plus recurring evidence cost, divided by eligible units. The chart multiplies that ratio by 1,000 for readable labels.

At an illustrative eligible volume of 1,000 units, the displayed cost rises from 105 to 165 cost units per 1,000 eligible units as recurring work increases. This is the difference between 0.105 and 0.165 cost units per eligible unit. At the lowest recurring scenario, moving from 500 to 2,000 eligible units reduces the displayed measure from 210 to 52.5 cost units per 1,000. These are arithmetic results from declared assumptions, not measured economies of scale.

The sensitivity reveals two separate management questions. Can reusable setup serve a larger eligible population without losing validity? Can recurring work be reduced without removing necessary evidence? A smaller unit cost created merely by shipping more units with unresolved failures would be a false improvement. A reduction in recurring effort created by reusing a reviewed answer may be genuine, provided the product, period and request purpose remain comparable.

The model should stop short of a composite return unless the other inputs have their own evidence. Revenue, customs duties, tax, labour productivity, financing and production losses require separate models and source boundaries. Adding them here would create an apparently precise answer from incompatible assumptions. The evidence model instead supplies a bounded cost input to the order decision, while product release and worker protection remain gates rather than monetary adjustments.

A denominator review should accompany every comparison. The reviewer checks whether the same product family, unit definition, release population and period are used in each scenario. If the denominator changes because the buyer cancels part of the order, that is a commercial volume effect. If it changes because goods fail release, that is an eligibility effect. Combining the two would obscure the corrective action required.

13.33 min · 9 paragraphs · read with a related exhibit

Request reuse should be measured rather than credited in advance

Reuse is a hypothesis until a second request arrives. A supplier may reasonably expect a controlled product record or voluntary reporting template to reduce work, but the saving belongs in the base case only after comparable observations. Before that point, the model should show the full effort and a separate sensitivity for possible reuse. This prevents an anticipated efficiency from concealing an under-resourced response process.

The Commission's VSME description supports the direction of travel: a common voluntary standard is intended to make responses to large-company and financial-institution requests easier for SMEs.[S05] It does not show that every buyer will accept the same extract, that every field fits a product order or that translation and review disappear. The supplier should therefore measure its own workflow rather than converting the policy objective into a promised saving.

¶ 02 · 1 source

S05

A pilot log should capture collection, translation, technical checking, approval, portal entry and rework as separate activities. It should record the request purpose, product and period, number of fields, evidence already held, missing evidence and the recipient's response. Hours should be assigned to the activity where they occur. A quality specialist interpreting a test result is not doing the same work as an administrator uploading a file, and the distinction matters for both cost and control.

¶ 03

The basic comparison is response hours before reuse minus response hours after reuse. A monetary saving requires a further input: the appropriate loaded rate for each role, multiplied by the comparable hours avoided. The rate is a user-supplied planning input until payroll and overhead policy support it. No saving should be booked when the later request is narrower, concerns a simpler product or arrives with better buyer instructions. Those changes are alternative explanations.

¶ 04

A matched-request protocol makes the comparison fairer. Select requests with the same purpose and substantially the same evidence boundary. Record differences in product mix, order size, reporting period, buyer schema and required language. Where a perfect match is unavailable, keep the observations as separate cases rather than manufacturing a trend. A small pilot can reveal failure modes without establishing a general cost curve.

¶ 05

Buyer turnaround needs the same care. The supplier controls internal retrieval and approval time, but not the time a recipient takes to review or reject a submission. The log should separate elapsed waiting time from active supplier work. Faster portal acknowledgment does not prove acceptance. A request closed without further questions may reflect a satisfactory answer, a changed buyer priority or an abandoned order.

¶ 06
Note

The counterfactual should remain visible in the management account. If a buyer reduces its questionnaire while the supplier introduces reusable evidence, the whole time reduction cannot be attributed to the supplier's system. If order volume doubles, total response work may rise even while work per request falls. If a new product needs additional tests, higher cost may indicate broader coverage rather than worse administration.

¶ 07

The practical output is not a single savings claim. It is a library of observed response routes with their effort and limitations. Management can then decide which fields deserve a controlled canonical answer, which need product-specific work and which require clarification before staff begin collecting data. Reuse becomes an operating result when the evidence shows it, not a discount granted to the project business case in advance.

¶ 08

Interlude · the cloth half-woven

4 exhibits carry this chapter's argument.

Woven: sections 13.0 to 13.3Still to weave: 13.4 to 13.7

  1. 56Setup and recurring evidence work have different cost driversReconciliation
  2. 57Cost per unit changes with volume and duplicated workControl map
  3. 58A hold-cost range depends on declared funding and time inputsReview bands
  4. 59A drill tests decisions rather than a readiness scoreRegister
Hover or focus an exhibit to light its weft; select it to jump to it.

13.43 min · 9 paragraphs · 1 exhibit

A shipment hold creates cash exposure rather than a forecast fine

A hold is first an operational and cash event. Goods remain unfinished, undispatched or otherwise unavailable for sale while teams preserve records, investigate, retest, correct labels or protect affected people. The financial model should represent those observable consequences. It should not invent a probability of enforcement or a universal penalty and call the result expected compliance value.

The forced-labour product framework illustrates why this distinction matters. The Commission describes separate assessment, dialogue, investigation, decision and enforcement stages, while also stating that the regulation itself introduces no audit or reporting obligations.[S10] A supplier precautionary hold is not the same event as an authority decision. The internal model must name which state it represents and which actor authorised it.

¶ 02 · 1 source

S10

A narrow working-capital calculation can still be useful. The planning formula is inventory value under hold, multiplied by the annual funding rate and hold days, divided by the declared day-count basis. It estimates the funding cost of value tied up for that period. It does not include every consequence and does not predict the hold duration. Inventory value, funding rate and days are user inputs, not facts supplied by the regulation.

¶ 03

Exhibit 58 applies that formula to an illustrative inventory value of 120,000 currency units. The low and high bounds use annual funding rates of 8 percent and 16 percent, with a midpoint of 12 percent. Hold durations of 15, 30 and 60 days are planning scenarios on a 365-day basis. The exhibit is deliberately labelled illustrative because none of these inputs is an observed supplier or enforcement figure.

¶ 04

Exhibit 58 applies that formula to an illustrative inventory value of 120,000 currency unitsillustrative

Exhibit 58
Exhibit 58Review bandsillustrativeA hold-cost range depends on declared funding and time inputs
01,0002,0003,0004,00015-day hold30-day hold60-day hold

Read-out15-day hold: low 395, central 592, high 789 (illustrative currency units)

Method and source

Illustrative scenarios only. Inventory value under hold = 120,000. Formula = inventory value × annual funding rate × hold days / 365. Low, mid and high rates = 8%, 12% and 16%. Values rounded to the nearest whole currency unit. No enforcement probability, statutory deadline or actual supplier funding rate is implied.

Unit: illustrative currency units. Status: illustrative. Illustrative figures are teaching examples, not measured factory results.

The midpoint for an illustrative 30-day hold is 1,184 currency units after rounding: 120,000 multiplied by 12 percent, multiplied by 30, divided by 365. The corresponding low and high values are 789 and 1,578 currency units. This range describes sensitivity to the declared funding rate only. It is not a statistical confidence interval, and the midpoint is not a forecast mean.

¶ 01

The midpoint for an illustrative 30-day hold is 1,184 currency units after roundingillustrative

Note

A complete hold account needs those separate lines because they have different owners and cash timing. Storage may accrue daily. Testing may require an external quotation before work begins. Rework may consume materials and capacity. Lost sales depend on the contract and subsequent buyer decision. Worker remedy must be determined by the harm and the affected person's needs, not capped by the remaining order margin.

¶ 02

Legal and advisory costs also need careful treatment. A scope review may resolve which evidence is necessary and prevent irrelevant work. It should not be presented as a fine avoided. Likewise, a shipment hold can protect against a worse outcome without proving that the alternative would have been an enforcement action. The decision record should state what the hold achieved, what remains unresolved and who may release the goods.

¶ 03

A hold can also distort the unit-cost denominator. Goods under critical review are not eligible shipped units. Moving them out of the denominator increases the measured evidence cost per eligible unit, but that increase is not the main reason to act. The primary question is whether the product and people are protected. Cash exposure helps management resource the response; it does not decide the legal or ethical release condition.

¶ 04

13.52 min · 7 paragraphs · read with a related exhibit

A shared-service approach has benefits and concentration risks

Evidence work can be organised inside the supplier, bought from specialists or supported through a buyer-shared service. Each route changes more than the invoice. It changes who defines the record, who can retrieve it, who corrects it and what happens when the commercial relationship ends. The cheapest visible service fee may not be the lowest total cost once portability and continuity are included.

An internal evidence team keeps process knowledge close to production and worker-management systems. It can connect batch events, specification changes and corrective action without sending every question through an intermediary. Its costs include training, supervision, cover for absence and independent review where needed. Internal control does not remove the need for competent laboratories, legal advice or specialist safeguarding support.

¶ 02

External specialists can provide expertise that would be inefficient to maintain for occasional work. The buyer of those services still needs a clear scope, competence check, confidentiality terms and usable output. A report locked inside a consultant's format may answer one questionnaire while leaving the supplier unable to reconstruct the evidence later. Procurement should therefore test data export, source access and correction rights alongside price.

¶ 03

A buyer-supported common portal may reduce repeated formatting and make request purposes clearer. It can also concentrate dependency. If several customers use different schemas, the supplier still needs a canonical internal record and mapping layer. If the buyer changes portal, access terms or hosting arrangements, the evidence must remain retrievable. A shared platform does not replace product-specific testing, worker engagement or the supplier's own release decision.

¶ 04

Personal information adds a sharper boundary. Where the GDPR applies, its principles include purpose limitation and collecting only the personal data necessary for that purpose.[S23] The EDPB separately explains cumulative criteria for transfers to organisations outside the EEA and conditions that apply in addition to other GDPR rules.[S24] These questions depend on the actors and data direction. A common portal is not automatically unlawful, but convenience alone does not answer necessity, access or transfer review.

¶ 05 · 2 sources

S23S24

The commercial comparison should therefore include exit cost and service continuity. Can the supplier export every record with its version history and evidence links? Can a worker's restricted information be withheld from a broad product extract? Will the service remain available during an incident, and who pays for urgent retrieval? These are operating requirements, not technical accessories.

¶ 06

A mixed model is often the most testable starting point. The supplier retains the canonical evidence register and decision rights. Specialists provide bounded analysis. Buyer portals receive controlled extracts. The pilot can then price each interface and observe where duplication remains. No vendor should be described as regulator-approved unless that specific status and scope are independently evidenced.

¶ 07

13.63 min · 9 paragraphs · 1 exhibit

The tabletop drill should expose failure modes

A cost model describes intended work. A tabletop drill tests whether people can perform that work when several problems arrive together. The exercise should use a fictional order, controlled records and a fixed decision table. It is not a simulation of authority enforcement and should not produce a readiness score. Its purpose is to expose missing evidence, unclear authority and actions that could harm a worker or release an unreviewed product.

The proposed scenario combines a changed dye recipe, missing upstream records, a worker allegation and an excessive reporting request. Each event has a different decision path. REACH restrictions can apply to imports, so a changed material or finish should trigger product-specific scope and evidence review rather than an administrative assumption that the old test still covers the new state.[S16] The reviewer must determine the actual substance question, sample and batch relationship from the operative requirements.

¶ 02 · 1 source

S16

Missing upstream records require containment and reconstruction. The team should identify affected input lots, processing events and finished batches, preserve the available record and name what cannot be established. A missing record is an evidence gap, not proof of abuse. It is also not a zero-risk answer. The forced-labour framework's distinct assessment and investigation stages reinforce the need to separate a concern, an internal review and an authority finding.[S10]

¶ 03 · 1 source

S10

The worker allegation changes the priority. Protection, confidential intake and escalation outside the production deadline must come before evidence packaging. The ILO and IOE handbook uses forced-labour indicators to help companies identify and assess risks in practice.[S09] An indicator starts enquiry; it does not license a public accusation. The drill should record who can take safeguarding action, how the affected person can confirm remedy and which information must remain restricted.

¶ 04 · 1 source

S09

The reporting request tests a separate control. The team should ask its purpose, check what can be reused and distinguish product evidence from corporate reporting. The adopted amending text gives protected undertakings a right, subject to its conditions, to decline information beyond the voluntary standards for specified sustainability-reporting requests.[S35] That mechanism should not be stretched into a refusal to supply necessary safety or investigation evidence. National implementation and the applicable standard version remain review dependencies.

¶ 05 · 1 source

S35

Exhibit 59 sets out the rehearsal register. Its result cells deliberately state that the drill has not been run. Retrieval times, decision quality and remediation effectiveness must be recorded only during an actual exercise. A completed template is not a completed drill.

Exhibit 59RegisterillustrativeA drill tests decisions rather than a readiness score
Scenario
Changed dye recipe
Evidence to retrieve
Specification, change notice, batch link and test scope
Decision required
Hold release pending product-specific review
Result
Not run

Read-outScenario: Changed dye recipe. Evidence to retrieve: Specification, change notice, batch link and test scope. Decision required: Hold release pending product-specific review. Result: Not run

Open the full register (4 rows)
Changed dye recipeSpecification, change notice, batch link and test scopeHold release pending product-specific reviewNot run
Missing upstream recordInput lot, processing site and affected finished batchesPreserve evidence and contain the affected scopeNot run
Worker allegationRestricted intake, protective action and remedy recordProtect the person and escalate independentlyNot run
Excessive reporting requestRequest purpose, reusable answers and standard mappingClarify purpose and route a proportionate responseNot run
Method and source

Illustrative scenarios and proposed actions. Sources support parts of the decision context, not any observed drill result. All result cells remain Not run. No actual allegation, product failure, legal conclusion or measured retrieval time is claimed.

Unit: illustrative rehearsal protocol. Status: illustrative. Sources: S09, S10, S16, S35. Illustrative figures are teaching examples, not measured factory results.

A facilitator should introduce the events in sequence and preserve the decisions made at each point. The changed recipe may reduce the eligible batch before the worker allegation arrives. The reporting request may distract staff while the upstream record remains missing. This interaction is the useful stress: the drill shows whether urgent protection and product control retain owners when administrative work competes for the same people.

¶ 01

The observation sheet should record elapsed retrieval time, active work, unresolved evidence, decision-maker and protective action. It should also note false starts, inaccessible records and ambiguous instructions. Those observations become pilot costs and design changes. They must not be backfilled with target values after the exercise. If no retrieval occurred because a record was absent, the honest entry is unavailable, not an unusually fast response.

¶ 02

Closure requires more than a meeting. Each gap needs an owner, resources and a review condition. A corrected template addresses an administrative defect only if the revised route works on the next exercise. A worker-related action needs appropriate confirmation and recurrence review. A product hold needs an authorised release decision based on the actual evidence. The drill budget should include these follow-up actions, otherwise the exercise becomes a performance without operational change.

¶ 03

13.72 min · 7 paragraphs · read with a related exhibit

An export decision needs evidence of value and of readiness

The final decision should compare accepting, conditionally accepting, repricing or declining the order. Acceptance requires both economic headroom and a clear release path. Conditional acceptance may be appropriate when evidence work, buyer clarification or product review has a funded owner and a feasible completion point. Repricing may address identifiable incremental work. Declining may be necessary when the route cannot meet critical conditions or the commercial terms cannot fund the required response.

A positive contribution never overrides a critical failure. Product safety, applicable chemical restrictions and worker protection are not optional enhancements to be traded against price. The order model should therefore present two outputs side by side: an economic calculation and a gate register. A high margin beside an unresolved critical gate means do not release. A low administrative cost beside complete evidence does not, by itself, prove that the order is attractive.

¶ 02
Note

The illustrative case shows why negotiation should focus on the work driver. Removing duplicated administration improves the scenario without claiming to reduce necessary testing or remedy. Repricing can be evaluated against the same transparent lines. Yet if the changed dye recipe still lacks the required release evidence, neither version authorises shipment. The financially preferable route remains conditional on the gate.

¶ 03

The investment memorandum should attach actual buyer terms, the verified scope decision, external quotations, internal-hour observations and the drill register. Assumptions should remain in separate sensitivity cells. A premium can be included only as a buyer-supported commercial input, not as a reward automatically generated by compliance. Financing approval, EU market access and buyer acceptance are separate decisions that this model cannot promise.

¶ 04
Note

The decision record should close with the unresolved questions as well as the recommendation. Who confirmed the legal scope? Which evidence remains missing? Which costs are quotations and which are estimates? What did the rehearsal fail to retrieve? What must change before the next order? Those answers make the economics answerable to the order rather than making the order serve a predetermined compliance story.

¶ 05

Check the record

The chapter keeps its sources within reach.

Every knot is a source this chapter cites; select one to read its record, or filter the register by grade. Publication dates and inherited-source limits stay explicit. Read the paper's full evidence summary.

9 sources · 21 citation marks on this pageMost cited: S05, 3 times

Grade AGrade BGrade CKnot size: citations on this page

All 9 records shown

c13-S05 · Grade A

European Commission, DG FISMA

Commission presents voluntary sustainability reporting standard to ease burden on SMEs

The Commission has today adopted a recommendation on voluntary sustainability reporting for small and medium-sized companies (SMEs).

2025-07-30. Register access date: 2026-10-30. Source provenance is supplied by the paper evidence register.

Open the recorded source ↗
Chapter source notes

S13 European Commission. 2025-04-16.

S05 European Commission, DG FISMA. 2025-07-30.

S33 European Union, Your Europe. 2026-08-19.

S16 European Commission, DG GROW. n.d..

S10 European Commission, DG GROW. n.d..

S23 European Commission. n.d..

S24 European Data Protection Board. n.d..

S09 International Labour Organization and International Organisation of Employers. 2025-11-26.

S35 European Parliament and Council of the European Union. 2026-02-24.

Keep the thread · chapter 13 of 14

Chapter 14 picks up the thread.

Move the shuttle along the rack to preview any chapter: its sections, exhibits and reading time. Draft web edition. This research is not investment, legal or tax advice; illustrative models are not measured factory results.

The paper's rack · 14 boltsBolt length: reading time

14Part IV: Operate the evidence system and fund its upkeep

GFT would measure whether the system prevents harm and answers for the product

The roadmap begins with scope and current duties, then proves repeatable evidence and adapts to later rules.

  • 14.1Start by approving the route, roles and current-law register
  • 14.2Make worker protection and current product duties the first gate
  • 14.3Prove a reusable pack on a bounded product family
  • 14.4Add future requirements through a controlled change process
Reading time
25 min
Exhibits
4
Sections
7
Continue to chapter 14
← Previous: chapter 12, Contracts should fund evidence and remedy rather than transfer slogansContinue the threadChapter 14 · GFT would measure whether the system prevents harm and answers for the product

Find a thread.

Type to search.