Educators consistently say that it is difficult to trust product claims and to compare the quality of edtech products. While products make claims about their qualities and features, without an unbiased third-party to verify, how could the information be trusted?
|Educators and administrators, drawing from student experiences, identify a high-priority edtech product feature or design element (e.g., research-based design, learner variability, etc.).|
|Content experts, including educators, researchers and product designers, co-create certification and criteria.|
|Using Digital Promise’s competency-based framework, an application for edtech tools is developed.|
|The certification is piloted with product developers to ensure it is valid and reliable.|
|The certification is launched publicly as a signal to educators that a demonstration of the product’s features have been formally verified.|
Product Certifications articulate discrete criteria, prioritized by educators and administrators. Edtech applicants provide specific evidence to demonstrate that the tool meets the criteria.
Each Product Certification development process engages educators and administrators in defining the criteria and undergoes multiple rounds of testing with products to ensure a meaningful signal to consumers and a streamlined process for product applicants.
Products can start and continue their Product Certification journeys on their own time, without deadlines. Applications remain open permanently.
Product Certifications are Open Badges which can be displayed on product websites and edtech procurement platforms.