Research method

Define the research object

Record the product, configuration, intended users, setting and claim under examination. Separate the product supplied, the specimen assessed and the scope of the conclusion. A product family requires an explicit explanation of the differences between models.

Establish the publication identity

Copy the complete standard reference from the official record. Include the edition, amendments and corrigenda relevant to the analysis. Keep international publications, European adoptions and national implementations distinct. Similar numbers do not establish identical technical content.

Check the legal relationship

Identify the relevant legislation before relying on a harmonised reference. Check the citation act and later amendments, the exact edition, any conditions and the applicable dates. Do not infer citation from a publisher's status field or from an end date left blank in a summary list.

Read the evidence as a connected file

Connect every conclusion to an identified requirement, object, method, result and decision. Examine configuration tables, report coverage, component schedules, instructions and production changes together. An isolated report cover or certificate rarely explains all those relationships.

Distinguish the basis of analysis

• Bibliographic record: reference, title, publisher and official link.
• Legal source record: the source act, cited edition, dates and restrictions.
• Application study: original analysis of product scope and technical evidence.
• Technical conclusion: a conclusion supported by the relevant complete requirements and identified evidence.

Published studies identify their actual research scope. They do not claim clause-level examination where only public catalogue or legal source material was used.

Use product groups for discovery

The 28 product groups are an IESQ navigation taxonomy. Candidate references are matched using bibliographic titles, reference families and available ICS codes. A match helps a reader find a source; it is not a declaration that the standard applies. Read the official scope, exclusions and normative relationships.

Record change and uncertainty

Keep the research date, source identity and configuration with the conclusion. Record unresolved questions expressly in the technical file. A new edition, amended legal citation or product change can require review; none automatically determines which earlier conclusions remain supported.

To report a reference error, send the reference number, source link and the specific discrepancy through technical enquiries.