Types of ASB Documents

Standard

A standard is a document that provides requirements and is written to establish objectively measurable requirements for a given topic or set of actions. It is aimed at the achievement of the optimum degree of order in a given context. A standard is established by consensus and approved by a recognized body. 

The requirements in a standard are expressed as imperative sentences or stated in ‘shall’ language and can be assessed by one or more forms of conformity assessment procedures. However, when writing a standard, the use of other verb forms, such as 'should', 'may' or 'can' are allowed only when their use is necessary to explain a secondary aspect of a requirement such as an operation. 

Keep in mind, the document is the standard. It is incorrect to describe a standard as containing or providing standards. A standard provides requirements.

Guideline

A guideline provides information and advice on processes and activities contained in a standard or best practice recommendation, or guides users on the implementation of a standard or series of standards. It may include recommendations but does not establish best practices. A guideline is written in ‘should’ language and is informative rather than directive. A guideline in and of itself is not appropriate for conformity assessment. 

Best Practice Recommendation

A best practice recommendation (BPR) identifies and sets forth the optimal way to carry out an action or actions. It may include choices and the variations between them as a means of demonstrating optimal choices in different circumstances. A BPR is written in ‘should’ language. Imperative or ‘shall’ language can be used in a secondary context when necessary to clarify a recommended action or approach.  

Technical Report

A technical report (TR) is an explanatory, information-only document. It provides scientific, technical, terminology, or operational information relevant to a standard, a field of activity, or a profession. These documents can also, for example, identify and discuss applications not yet standardized, and provide relevant research on emerging issues or technologies that may become suitable for standardization. TRs do not set requirements or recommendations and are not suitable for conformity assessment.

additional resources

• See ASB's Documents and Forms to view:
  • Manual and Style Guide for ASB Standards, Guidelines, Best Practice Recommendations, and Technical Reports 
  • ASB Supplemental Guide
• Walk through an ASB document.