Define the sample before the test
Record the sample identifier, firmware, source files, settings and accessories. Choose the same tasks for all devices. An observation belongs to that sample and condition; avoid extending it to production units, all readers or every document without supporting evidence.
Leave runtime unresolved
No battery duration, charging speed, refresh rate or stylus latency has been measured here. If those matter, agree a protocol that names document activity, lighting, connectivity, starting state and stop condition. Publish the conditions beside the result when a real test is eventually performed.
Request market documentation
Ask for applicable material, electrical, transport and market documents from a real supplier before procurement. This studio does not certify any product or determine which rules apply. Keep certificate identity, sample identity and document scope in the review rather than assuming a badge proves the whole instrument.
A practical sample set
- 01
Sample and software identifier
- 02
Repeatable source task and settings
- 03
Measured result with conditions
- 04
Document scope and remaining questions
What evidence would change the shortlist before a purchase decision?
Record it as unresolved. A future sample or document should provide the answer before a purchasing decision.
Add context to the local brief