A construction kit arrives with a promising claim: it helps children understand engineering. The box shows a finished bridge. The instructions show how to assemble it. What remains unclear is what the child can investigate, which decisions belong to the child, and what evidence supports the learning claim.
For a manufacturer preparing a STEM product for evaluation, that gap is a useful place to begin. A reviewer needs a clear account of the product learners actually receive and the educational experience it makes possible. More enthusiastic wording will not resolve an unclear claim. A well-documented example can.
This guide shows how to organize that account, using an illustrative bridge-building kit. The preparation suggestions are STEM.org editorial guidance, not a substitute for the current submission requirements or a prediction of an evaluation result.
Define the product before describing its promise
Start with a scope record: product name, model or SKU, version, intended age range, included materials, and the instructions supplied with it. For a digital tool, note the software version, supported devices, account requirements, and which learning activities depend on a paid tier or internet connection. Date the record so later changes can be traced.
A starter kit and a classroom bundle may share a name while offering different experiences. One might include enough parts for a single model; the other might support group investigations. Describe those differences rather than assuming that a shared brand establishes equivalent educational value. If proposing a product family, identify its members and ask which scope can be evaluated together.
Keep the sample, packaging, manual, product webpage, and evidence consistent. If an instructional activity uses extra materials, identify them and explain who supplies them. A reviewer should be able to distinguish the product’s included experience from an optional lesson developed around it.
Connect each claim to something a learner does
“Builds problem-solving skills” names an ambition. “Learners compare two support arrangements, observe what changes, and revise their design” describes an opportunity the product may provide. The second statement gives a reviewer something to examine without claiming an outcome that has not been measured.
For each important learning claim, record the task, the learner’s decisions, the feedback available, and the supporting material. A photograph of a bridge shows what was built. Instructions showing alternative supports explain what can be changed. A learner’s account of why one design behaved differently provides another kind of evidence. Label each source according to what it actually establishes.
This approach reflects STEM.org’s emphasis on learner agency: tools should leave meaningful reasoning with the learner. Assistance can make participation possible. Identify where an adult introduces a technique or supports assembly, and where the learner predicts, compares, explains, or revises.
Illustrative worked example
A bridge kit: from a broad claim to an inspectable activity
This fictional example demonstrates evidence organization. It is not an evaluated product, an official rubric, or a passing submission.
- Proposed learning claim
- The kit gives learners an opportunity to investigate how support placement affects a model bridge.
- Activity and learner decision
- Build two arrangements across the same gap using the same parts. Choose where to place the supports, predict a difference, and compare what happens under the same teacher-approved test conditions.
- Materials that make the claim inspectable
- The parts list, the relevant instruction pages, photographs of both arrangements, and a sample observation sheet. Mark what is included in the box and what the facilitator supplies.
- What an observation could show
- A learner changed support placement and described a difference during this activity. Record the assistance provided and any difficulty using the parts or instructions.
- What it does not establish
- A single demonstration does not establish lasting engineering knowledge, transfer to a different task, or improved school achievement. Those are separate claims requiring appropriate evidence.
Make supporting evidence easy to inspect
Organize existing materials around the claims they support. A short evidence index can name the claim, link to the relevant file or instruction page, describe the context, and state its limit. Use descriptive filenames and working links. Avoid requiring a reviewer to search a large marketing presentation for one useful activity.
If you have pilot observations, distinguish what was observed from what participants reported. Note the product version, setting, task, and assistance involved. A teacher’s report that children enjoyed a kit is useful feedback about that experience; it does not independently show a gain in conceptual understanding. Product-specific research should be identified as such, with its methods and limitations available.
Research about a teaching approach can explain a design choice without proving the effectiveness of every product using it. If a claim exceeds the available evidence, narrow the wording or identify the question that remains open. Use appropriately permissioned, privacy-respecting records rather than including identifiable learner information simply to make a submission look persuasive.
Show the conditions that make the activity usable
A learning opportunity depends on access to the task. Check the reading level of instructions, the visibility of diagrams, how parts connect, the space required, and the preparation expected of an adult. For digital products, explain setup and accessibility features that actually exist. Describe known limitations plainly.
Try following the included instructions with someone who did not write them. Notice where a missing step, unexplained symbol, or unreliable connection interrupts the intended investigation. An adult completing every difficult action can produce an attractive model while concealing an unusable learner experience.
Document improvements with version dates. If you revise a diagram or add an alternative activity, keep clear which materials belong to the submitted product and which remain proposals. A credible evidence record makes the current experience understandable, including the circumstances in which it needs support.
Use the right evaluation pathway
STEM.org Authenticated™ concerns specific products. Its current process asks applicants to identify the product or product family, provide product information and learning claims, and submit supporting documentation and requested evidence. The review examines educational alignment, learning value, usability, applicable hands-on learning, and support for the claims made.
Begin through the linked registration pathway and confirm the requested materials for your submission. Clarification may be needed. Payment starts the applicable review; it does not guarantee recognition. Use the official service page for current process details rather than treating this article’s illustrative evidence record as a mandatory checklist.
If the main subject is published curriculum or educational media, consult our guide to product evaluation and curriculum review before selecting a pathway. STEM.org Reviewed™ addresses published educational content. The distinction helps keep an application focused on the work actually being submitted.
Keep educational evaluation and safety records distinct
An educational claim and a safety claim answer different questions. Demonstrating that learners can investigate a mechanism does not establish that its materials or construction satisfy applicable safety requirements. Keep the relevant compliance records with the product’s documentation, clearly labelled for their purpose.
In the United States, the Consumer Product Safety Commission’s toy-safety guidance explains applicable testing and certification responsibilities, including third-party testing for toys intended primarily for children 12 and under. Manufacturers should follow the requirements that apply to their product and market. STEM.org educational recognition is not a replacement for that work.
Prepare for accurate communication after a decision
If recognition is issued, use its exact awarded scope and approved assets. Check that product names and identifiers match the credential. Do not extend a product award to an entire company or a later version without confirming coverage. Link buyers to credential verification so the claim can be checked directly.
Discovery is a separate function. The independent STEM.org Product Registry can help people find learning products; a listing alone does not establish STEM.org Authenticated™ or Best In STEM™ recognition. Keep discovery descriptions, verified credential information, and claims about learning outcomes distinct.
Our Product Registry walkthrough shows how families and educators move from a search to a specific product profile and its verification records. Use that reader journey to make your product description precise and useful.
Begin with one claim and one activity
Choose the educational claim most central to your product. Identify the learner action behind it, gather the materials that make it inspectable, and record what remains unknown. Then consult the current STEM.org Authenticated™ evaluation pathway to prepare your submission.
