Input evidence
Mapped before scope
Brief, references, constraints and current files are mapped before scope is recommended.
Prototype planning
Prototype Route Planner
The wrong prototype can look impressive and still answer the wrong question. The route should match what the team needs to learn next.
Visual context
What this checklist should support
A checklist is useful only when it connects to project evidence that a buyer, engineer or supplier can review.
Structure evidence
Supplier-ready handoff
3D structure, assembly logic and exploded views make supplier handoff easier to review.
Prototype evidence
Prototype learning path
Sample route, fit checks and revision notes show what the next prototype should prove.
Production evidence
Pilot risk control
DFM notes, supplier questions and pilot gates reduce late surprises before tooling or launch.
Checklist
What this resource helps clarify
Use the table as a project-preparation checklist before sharing files or requesting a first development path.
| Area | What to prepare | Why it matters |
|---|---|---|
| Looks-like | Useful for form, CMF, investor visuals and retail conversations. | Keeps appearance feedback separate from engineering proof. |
| Works-like | Useful for fit, ergonomics, mechanisms, electronics and assembly checks. | Finds functional problems before production-intent spend. |
| Production-intent | Useful before DFM, supplier quoting, pilot approval or tooling decisions. | Connects prototype evidence to manufacturing risk. |
Send for review
Turn the checklist into a next-step recommendation
A short product description is enough to start. Sensitive technical, supplier and prototype files can wait until NDA terms are agreed.
Plan the right sample route
Send product type, current stage, target market and the context you can safely share now.