Updating Declarations: Change Triggers and Version Discipline

The declaration stays true only while the packaging it describes stays the same. Change events therefore route through a declaration assessment: does this change affect anything the declaration states or the file evidences? The standard triggers: material or formulation changes in any component; supplier changes for composition-relevant inputs; process changes at conformity control points; revised assessments (a new grade, a new content figure, a new substance finding); standards and criteria updates that change the route a requirement was met by; labelling changes; and identity changes (names, designations, manufacturing sites). Each trigger event gets a recorded disposition: re-issue the declaration, amend the file with the declaration standing, or no action - with the reasoning in the change record.

The discipline's failure mode is not refusal; it is silence - changes absorbed by production while the declaration describes a product that no longer exists.

The assessment asks three questions of any change. Does it touch a declared property - composition, content, grade, substance position, label, identity? Does it touch the evidence - would any report, certificate or calculation in the file cease to describe the product? Does it touch the route - has a standard, criterion or legal requirement the declaration relies on itself changed? A yes to any question re-opens the file at that point; three noes, each considered rather than assumed, close the event with a note. The questions are deliberately property-based rather than size-based: a two-percent formulation change in a coating can matter more than a twenty-percent change in a dimension, and change boards trained on size alone misjudge both directions.

The trigger system sees only the changes it is told about, and the dangerous changes are the unannounced ones - the supplier's quiet reformulation, the contractor's site move, the resin grade substituted under an unchanged trade name. Defences are layered: contractual change-notification with audit and sampling rights (exercised, per the production-control guide); incoming-goods verification sensitive enough to notice (identity checks on critical inputs, periodic fingerprint testing on the highest-risk materials); and market-signal attention (a competitor's finding, a scheme's alert) routed to the file owner. When an unannounced change is discovered, the assessment runs retrospectively over the placings it may have touched - the incident the corrective-action duties were written for, handled by the nonconformity loop's rules.

Half the declaration's change load arrives not from the factory but from the legal calendar the timeline station maintains: criteria acts adopting (the recyclability route changes), methodologies finalising (content calculations re-based), harmonised standards cited or superseded, labelling specifications landing. Each legal milestone should generate declaration assessments across the affected families automatically - the acts calendar and the declaration register joined by a standing agenda item. Businesses that run the join find regulatory change administratively boring, which is the highest state a compliance system can achieve.

Keep every disposition - re-issues, amendments, no-actions with their reasoning - in the change register permanently, beyond the file's own retention where possible. The register becomes the business's memory of its own conformity reasoning: why this grade route, why that supplier change mattered, why the 2028 criteria act re-issued forty declarations in a month. Successors inherit judgement instead of folklore, and auditors meet an institution rather than a person. In a self-assessment regime, institutional memory is not an administrative nicety; it is the asset the whole system compounds.

Legal milestones and portfolio-wide input changes arrive as batch events: a criteria act re-basing grades across the estate, a group-wide resin change, a standards citation update touching every file that cited it. Batch events need programme handling - the affected set generated from the registers (which is why the registers cite standards and inputs as fields), a re-assessment template per family pattern, and a completion report with the exceptions named. Handled ad hoc, batch events leave a residue of un-updated declarations that surface for years; handled as programmes, they are the system's most visible proof of life. Diary the known batch events from the acts calendar now - several are already dated.