Record tasks, not just impressions
Breaking an evaluation into specific tasks—startup preparation, core operations, cleaning and storage, and exception handling—provides more useful evidence than a single satisfaction score.
Separate requirements from preferences
Record safety- and workflow-critical requirements separately from interface and appearance preferences to support later decisions.
Create traceable conclusions
After the evaluation, record the owner of each issue, required supporting materials, and confirmation dates so verbal conclusions are not lost as the project progresses.