No two standards are alike. Because there are certain characteristics of standards, there may be some overlap. Despite this, each must be unique. The basic requirements are:

1. A Standard Should be Suitable for Repetitive Use. A major requirement of a standard is that it can be used time and again. If a set of requirements is so specialized that it cannot and will not be applied repeatedly, it is not a standard.
2. A Standard Should Be Enforceable. A standard's requirement should be worded so that a person auditing its use or application can point out where it has been followed or where it has not been followed, or the extent to which it has or has not been followed.
3. A Standard Should be Definite. Requirements that are too general or which contain platitudes instead of workable instructions are impractical and often useless. Express requirements as specific instruction and never as explanations.
4. A Standard Should Be Realistic. Requirements should not be arbitrary but should be based on factors that are necessary to achieve the purpose of the standard. Do not include any more than are necessary, and don't make requirements or tolerances tighter than necessary. A standard that is too restrictive or too detailed imposes a burden on the user. Increasing the severity or detail of a requirement does not necessarily increase quality, but will always increase cost. Be ready to justify, in writing if necessary, every requirement of the standard, and be able to show the basis of each as a logical deduction from factual information about the item or practice in question.
5. A Standard Should Be Authoritative. Requirements should be technically correct and accurate and should cover only those properties which are subject to control or which are of legitimate use. Requirements should be reasonably consistent in the industry and be capable of being met by the user.
6. A Standard Should Be Complete. All areas open to question or interpretation (or conversely, to misinterpretation) should be covered. If requirements are specified in terms of, or by reference to, another standard, all areas of the referenced standard, which are open to question, or misinterpretation should also be covered. Leave nothing to the imagination of the user.
7. A Standard Should Be Clear. Express the requirements in simple, understandable language that is free from ambiguity. Language should be so precise that differences of interpretation are unlikely.
8. A Standard Should Be Consistent. Requirements should not be contradictory or incompatible with one another; similarly, the requirements of related and dependent standards should also be consistent with each other. Also, the requirements should be compatible with the requirements of documents referenced in the standard. Special (i.e., non-standard) sizes, shapes, or tests require special attention and extra time on the part of the user and therefore increase cost; they also inhibit maintenance and repair.
9. A S tandard Should Not Cover Too Broad a Scope. When too much is covered by one standard, its requirements become confused and watered-down, and the standard loses its flexibility. Users may be left wondering what parts of the standard apply to their work. Where the standard applies to a number of users, with different requirements for each, it is often more desirable to provide separate standards.