Purpose of the briefings

A briefing explains a defined development or technical question. It identifies the subject, jurisdiction and date relevant to the explanation. Readers should distinguish that context from the facts of their own product or activity.

Find a subject

Browse by technical topic and content type. Product requirements, quality methods, evidence and professional practice may involve different sources. A subject classification is a discovery aid, not a determination that a rule applies.

Read a briefing

The briefing record identifies its reference, source-check date and scope. Follow the original source for the authoritative status of a provision or document. Related material may explain implications or methods without having the same status as the source.

Standards and legislation

Legislation establishes legal obligations within its scope. Standards provide specified technical or other requirements and may have a particular relationship to legislation. The effect of that relationship depends on the applicable framework and the document's actual status.

Sources and review

Sources are selected for their relevance and authority on the point concerned. A proposed measure, a published measure and an implementation notice are distinguished. Changes in the source or context can require revision of the explanation.

Technical publications

Guides and reports may provide a fuller treatment of methods or evidence. They should be selected for the actual question and used with the applicable source documents.

Publications

Ask a focused question

Identify the source, passage, product or activity and the decision being considered. A question about applicability requires the relevant facts; a broad label such as European compliance is insufficient.

Technical enquiry

Next steps