As standards are developed, code sprints iteratively test the work.

Code sprints are venues that test draft standards and software solutions that implement against them. Standards-based solutions are put through real-world scenarios to document their use in a context understandable by the wider community. 

Compliance tests are run to ensure that software and systems are reliable and interoperable through adherence to OGC standards.

There are three types of standard: 

1. Encoding standards provide rules that determine how to organize information, typically sent by a service provider, or produced by an application. 
2. Interface Standards provide rules that determine the operations between service providers and service requesters. Together, these standards define interoperable approaches to geospatial data organization, access, processing, visualization, and discovery. 
3. Conceptual Model Standards describe common concepts and their relationships to facilitate exchange of information between parties within a specific domain.. 

There are three levels of standard: 

1. Community Standard: This is a document, developed by communities external to the OGC, that OGC members wish to bring into the OGC process. The key consideration for a Community Standard submission is that there is very strong evidence of implementation. 
2. Draft Standard: This is a document developed by the OGC membership for which there is no evidence of implementation. Members seek to approve it as an official OGC document in order to have developers and organizations implement the Draft Standard and provide feedback. A Draft Standard becomes a Standard once evidence for implementation is provided. 
3. Standard: This is a mature OGC Standard for which there is evidence of implementation.