Institute of European Standards and Quality 
From requirements to practice
Requirements have to be applied to real products, processes and evidence. Technical guidance addresses the practical questions that arise in doing so: selecting an approach, recording assumptions, judging evidence and explaining a conclusion.
Forms of guidance
A technical guide explains a subject in depth. A practice note addresses a specific task. A technical report presents an investigation or method. A position paper sets out a considered view on a defined issue. The document record identifies which type a reader is using.
Technical basis
Guidance identifies its sources and distinguishes requirements from explanatory advice. References to European or international standards retain the status of the original documents. The applicable edition and the context in which a reference is used matter to the interpretation.
Development and review
A work item defines the question, audience and expected output. Authors prepare the material within that scope. Technical review considers the method, evidence, terminology and limitations before the document proceeds through its approval arrangements.
Finding a document
The publication record brings together the abstract, intended audience, reference, edition and access arrangements. Related documents and replacement editions are linked where relevant. Readers should establish that the document addresses their particular task.
Contribute to guidance
Contributions may begin with a work proposal, expert participation or comments on a consultation. A useful contribution identifies the technical issue and gives a reasoned basis for the proposed treatment.
Use and permissions
A publication's own terms govern its use. Permission to read a guide does not necessarily include permission to reproduce it or to distribute an external standard cited within it. For reuse or translation, identify the document and intended use.