A claim register makes a company statement easier to evaluate. For SPG research, it should connect the actual wording to a source, date and defined scope before the statement is repeated in a headline or comparison.
SPG’s official homepage publishes company, capability and sustainability statements. Read the source.
Give every claim a traceable row
Use separate fields for the statement, publisher, relevant period and supporting record. Label first-party descriptions as such. A paraphrase should not broaden a statement from one product or site to the whole group, and a retrieval date should not become a new event date.
The register should also explain what is still unknown. If a claim would require a test report, methodology or transaction record to assess, identify that document rather than guessing the result. A research question is useful when it is specific enough for a source holder to answer.
Questions to put in the file
- What exact proposition is being assessed?
- Who published it and on what date?
- Does it concern a product, facility, group or reporting period?
- What supporting record would be needed for a stronger conclusion?
A practical evidence worksheet
| Field | What to retain |
|---|---|
| Claim | Exact proposition and publisher |
| Scope | Product, site, group and period |
| Support | Available record and unresolved question |
Worked example
A reader records a broad capability statement from the homepage. Before applying it to a proposed package, the reader asks which specification and test evidence address the product and route in question. The claim remains attributed to the company until the separate project evidence is reviewed.
What the record can establish
A claim register preserves attribution and scope. It helps readers identify the next useful document without turning uncertainty into an allegation.
Sources and scope
Public sources reviewed November 1, 2026. Company statements remain attributed descriptions, not independent certification. Examples are hypothetical. No private files, original interviews or authenticated leaks were used for this explainer. Technical or legal decisions require the relevant records and qualified review.
