What to bring to the review
- Product and intended use
- Operating cycle and electrical load
- Available space and mounting
- Charging and host interfaces
- Environment and destination markets
- Project stage, volume estimate and open decisions
Describe the operating cycle
Explain how the product starts, works, idles and shuts down. State the expected runtime and whether that includes standby. If measured current traces exist, include the operating conditions and how the data was captured.
A single average-current value can hide short events that matter to the design. Identify startup, acceleration, communication activity or other peak loads, including their duration and repetition when known.
Record constraints and preferences separately
A fixed enclosure is a constraint; a preferred connector may still be negotiable. Mark which dimensions, mass limits, interfaces and charging conditions are fixed, and which can be reviewed. This prevents an early preference from becoming an accidental design requirement.
- Use a drawing for usable space, mounting points and access clearance.
- Identify the host’s allowed input range and any shutdown behavior.
- State whether charging happens inside the product, externally or through a removable pack.
Define what a successful evaluation means
List the operating conditions in which the prototype will be assessed. Include the host configuration and the person or team responsible for each review. Certification requirements should be identified by application and destination market, then confirmed during engineering review; listing a standard in a brief does not establish compliance.
Use a revision identifier for the brief. When a requirement changes, record the reason and which earlier test or design decision may need to be revisited.