A useful template reduces drafting drift across product lines.
The template should pull information from the control and release workflow, not invent it at the last minute.
Structured answer sets in this page tree.
Cited legal and guidance references.
The best statement template is one that only uses approved product identifiers, support-period values, and compliance conclusions taken from the product evidence file. That avoids the common failure where the statement and the product website describe different support periods or different security positions. It is also important to confirm that the product is actually using the section 9 statement route rather than the newer Schedule 2A deemed-compliance route.
Start with the exact product identity, model references, and the manufacturer identity relevant to the UK route to market. Schedule 4 requires the product type plus any batch or serial number needed to identify the product, the manufacturer's name and address, and any authorised representative's name and address. If there are multiple manufacturers, the template must support the joint preparation position allowed by the Act.
This is the anchor for every other statement field.
SSOT can take PSTI Statement of Compliance Template from reusing this material inside a governed evidence system to a reusable workflow inside Sorena. Teams working on PSTI Statement can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from PSTI Statement of Compliance Template and keep documents, evidence, and control records in one governed system.
Review your current process, evidence gaps, and next steps for PSTI Statement of Compliance Template.
The template should identify the applicable security requirements and record the defined support period exactly as the customer-facing materials state it. Schedule 4 also requires the declaration that, in the manufacturer's opinion, the applicable security requirements have been complied with and that the support-period statement was correct when the manufacturer first supplied the product.
Do not let teams type this freehand from memory.
The template should also support the internal approval path and retention calculation. Schedule 4 requires the name, function, and signature of the person signing, plus the place and date of issue. That means the template should capture the issue date and any links needed for later retrieval by the manufacturer and importer.
A statement that cannot be version-controlled will eventually break the retention model, and if the product is on a Schedule 2A route the template should not be used as a substitute for checking those separate conditions.