When we see the term “national standard” on a product or in technical documentation, it may create the impression that compliance with all national standards is legally mandatory. On the other hand, the term “voluntary standard” is sometimes used in a way that suggests the standard is less important or merely a recommendation. Neither interpretation alone provides an accurate picture of the subject.
For a manufacturer, importer, or engineering team, knowing the number and title of a standard is not enough. It must be clear what status the standard has, whether the product is subject to its mandatory application, what the scope of the standard is, and under what conditions and at what time the requirement becomes applicable to the product. This distinction is particularly important in the automotive industry, where a product may simultaneously be subject to national standards, technical regulations, type approval requirements, manufacturer Specifications, and various contractual Requirements.
What Is a Mandatory Standard?
Put simply, when compliance with a standard has been made mandatory by a legal authority for a product, service, or subject within its scope, meeting the relevant requirements is no longer merely a voluntary choice for the manufacturer. In such circumstances, a product or activity falling within the scope of mandatory implementation must meet the applicable requirements, and its production, importation, supply, or other related activities will be subject to the applicable regulations.
An important point is that the existence of a national standard is not the same as mandatory implementation of that standard. Many standards are developed and published, but their implementation status must be reviewed separately. Therefore, when encountering a standard number, the designation “Iranian National Standard” alone does not mean that its implementation is mandatory for every product and under all circumstances.
Furthermore, even if implementation of a standard has been made mandatory, it is still necessary to determine whether the product falls within its Scope of application. A standard may be defined for specific groups of vehicles, components, equipment, or conditions of use, while another product may fall outside its scope despite appearing similar. Therefore, the mandatory implementation status of a standard and its applicability to a particular product are two related but separate questions.
What Is a Voluntary Standard?
In contrast to standards subject to mandatory implementation, there are standards whose application has not been mandated through the general framework for mandatory standards for the relevant products or activities. These are commonly referred to as voluntary standards. Manufacturers and organizations may use such standards to improve quality, establish a common technical framework, meet customer needs, or demonstrate product conformity with a defined level of requirements.
However, the term “voluntary” should not be interpreted as meaning that such a standard is technically less important. A voluntary standard may contain highly detailed requirements, test methods, and acceptance criteria and may be widely used within an industry. The primary difference lies in the basis on which compliance becomes required, not in the technical rigor or engineering value of the document.
In fact, a voluntary standard may be highly important for a specific project. A customer may require compliance with it in a contract, a vehicle manufacturer may include it in a Supplier Specification, or a product development team may adopt it as a design Requirement. In such cases, although the standard may not be mandatory from the perspective of general regulatory implementation, compliance with it may become one of the requirements of that particular contract or project.
What Exactly Is the Difference Between Mandatory and Voluntary Standards?
The main difference lies in the source of the obligation to comply with the standard. For a standard subject to mandatory implementation, the obligation arises from the applicable legal and regulatory framework. For a voluntary standard, its use is not mandated through the same general mechanism, but a manufacturer or the parties to a project may choose to adopt it or make compliance a project requirement through contracts and technical specifications.
| Mandatory Standard | Voluntary Standard |
|---|---|
| Compliance is mandatory for products within its applicable scope under the relevant legal requirements | Its implementation is not mandated through the general framework for mandatory standards |
| Implementation status and scope are important | Its use may be voluntary or may arise from a contract or project Requirement |
| Non-compliance may have relevant legal or regulatory consequences | The consequences of non-compliance depend on how the standard is being used and the project obligations |
| Its Applicability to the product must still be assessed | It may still contain detailed technical requirements and specific test methods |
The distinction between the two should therefore not be reduced to “important standard” versus “unimportant standard.” Both may be technically rigorous; what distinguishes them is why and on what basis compliance with the standard is required for the particular product.
Are All Iranian National Standards Mandatory?
No. The designation “Iranian National Standard” indicates that the document has been developed or published within the national standardization system, but the designation itself does not mean that its implementation is necessarily mandatory. The implementation status of the standard must be checked against relevant and reliable sources and regulations.
This distinction is highly important in engineering work. If a project team receives only a list of standard numbers without understanding the status of each one, it may mistakenly treat a standard as a legal requirement or, conversely, overlook a requirement that actually applies to the product. Therefore, identifying the standard and determining its mandatory status should be treated as two separate steps when reviewing project Requirements.
Can a Voluntary Standard Be Ignored?
There is no absolute “yes” or “no” answer to this question. If a standard is not subject to mandatory implementation, that tells us only about its general regulatory status; it is still necessary to determine whether compliance with that standard has become mandatory for the project through another mechanism.
Suppose a component manufacturer is developing a product for a vehicle manufacturer and the project contract or Technical Specification requires compliance with a particular standard. Even if that standard is voluntary from the perspective of general implementation, the component manufacturer must comply with the relevant requirements within the framework of its contractual obligations in order to deliver the product in accordance with the contract. The same situation may arise in export projects, a vehicle manufacturer’s internal requirements, or product development programs.
From an engineering perspective, some voluntary standards can also be used as design references, test methods, or technical Benchmarks even when there is no direct contractual obligation. Therefore, the right question is not simply “Is this standard mandatory or voluntary?” but rather: What role does this standard have in my project?
What Is the Difference Between a Standard Being Mandatory and Being Applicable?
These two concepts should not be confused. Suppose implementation of a standard has been made mandatory; it is still necessary to determine whether the product in question falls within the standard’s scope of application. A requirement may apply only to a specific vehicle category, a particular mass range, a certain type of system, or a product equipped with a specific technology.
For example, in the automotive industry, classifications such as M and N and their subcategories are important in determining the Applicability of many requirements. Powertrain type, vehicle capacity, installed equipment, and other characteristics may also affect whether a standard applies. Therefore, the statement “this standard is mandatory” does not, by itself, answer whether this specific vehicle must comply with it.
In a proper technical assessment, the relevant standard or requirement should first be identified, its scope of application should then be compared with the product characteristics, and finally its implementation status and the date or conditions under which the requirement applies should be reviewed.
Why Do Implementation Status and Effective Date Matter?
The presence of a standard on a list of requirements does not necessarily mean that it has been implemented for all potentially applicable products from that same date. New requirements may have defined implementation schedules or conditions and may enter into force in different stages. This is particularly important in automotive projects because several years may pass between the start of product design and the point at which the product enters production or approval.
In such situations, the project team should not review only the requirements in force at the start of the project. It should determine which requirements will be applicable when the product enters the approval, production, or market introduction process. A requirement may not yet be in force when the project begins but may become applicable before the product is launched; overlooking such a requirement can lead to design changes or additional testing during the later stages of the project.
This topic is discussed in greater detail in the article “What Are the 122 Vehicle Standards? New Vehicle Standard Requirements in Iran”, including why new requirements do not necessarily take effect simultaneously and why Applicability and implementation timing should be assessed separately for each project.
How Are the 122 Vehicle Standards Related to This Topic?
The term “122 Vehicle Standards” may create the impression that there are 122 standards that every vehicle must comply with at the same time and in the same way. However, as we have seen in the discussion of mandatory standards, the situation is not that simple. The standard’s scope of application, vehicle category, installed equipment and technologies, and implementation status determine which requirements apply to a specific product.
In addition, some new requirements may have different implementation schedules or conditions. Therefore, for a vehicle manufacturer or importer, knowing that a standard appears in the list of 122 standards is only the starting point of the assessment. The next question should be: Does this requirement apply to my product, and what is its status at the relevant stage of the project?
To review standard titles, Iranian national standard numbers, equivalent regulations or standards, and implementation status, you can use the Table of 122 Vehicle Standards on the TAT website.
What Is the Difference Between a Mandatory Standard and a Contractual Requirement?
This distinction is particularly important for component manufacturers. A legal requirement arises from applicable laws, regulations, and formal processes, whereas a contractual Requirement arises from an agreement between the parties to a project. A vehicle manufacturer may require compliance with a standard in a component Specification even when that standard is not subject to mandatory implementation at the general regulatory level. In this case, the source of the obligation is different, but the component manufacturer must still comply with the relevant Requirement in order to deliver the product in accordance with the contract.
A project may also include a manufacturer’s internal standards, Corporate Standards, Drawing Requirements, and proprietary test methods in addition to legal requirements. Therefore, preparing a complete list of product requirements cannot be achieved simply by searching for the country’s mandatory standards. Regulatory Requirements and Customer Requirements must be considered together.
This distinction is also important in test planning. A component may require one evaluation to demonstrate conformity with a legal requirement and additional tests according to the vehicle manufacturer’s Specification for customer acceptance. The result of each evaluation or test should be interpreted within the context of the Requirement it was intended to assess.
Does Every Mandatory Standard Mean That a Mandatory Test Is Required?
Not necessarily in such a simple way. A standard may contain a range of different requirements, and the method used to demonstrate conformity depends on the content of the standard and the applicable process. Some requirements are evaluated through physical testing, while others may require measurement, document review, inspection, or other methods. Even where testing is required, the specimen type, test conditions, and acceptance criteria must be determined from the relevant reference.
For this reason, the title of a standard alone is not enough to determine exactly which specimen should be sent to a laboratory or which test is required. If the applicable standard and test have already been identified, you can use TAT’s Table of Available Tests to review testing services and related standards.
What Should You Do If the Status of a Standard Is Unclear?
In a real project, decisions should not be based on hearsay, outdated files, or lists whose date and source are unknown. First identify the exact standard number and title, then review its scope of application, implementation status, effective date or conditions, and, where relevant, the referenced version or amendment. If the product is part of an automotive project, the vehicle category and Configuration should also be considered when assessing Applicability.
This work is best carried out at the beginning of the project rather than when the specimen is already prepared for testing. Late identification of a Requirement can result in design changes, the need to build a new specimen, or repetition of part of the testing process. In projects where the applicable requirements have not yet been fully identified, reviewing the standards and preparing a Requirement List is one of the fundamental steps before test planning begins.
Mandatory or Voluntary: It Is the First Question, Not the Last
Knowing whether a standard is mandatory or voluntary is important, but this information alone is not sufficient for engineering decision-making. Once the status of the standard has been established, it is necessary to determine whether the product falls within its scope, when and under what conditions the requirement applies, which version is applicable, and whether the project contract or Specification defines additional requirements.
For this reason, in an automotive project, rather than creating a simple list with only two columns labeled “mandatory” and “voluntary,” it is better to identify the source of obligation, Applicability, technical reference, implementation status, and method of demonstrating conformity for each Requirement. This approach provides a much more accurate picture of the project’s actual obligations and helps transform standards from a simple list of numbers and titles into a manageable part of the product development and evaluation process.