Describe your samples, scoring attributes, and participants. Makeform turns the brief into a taste test form for blind ratings, preferences, and comments.
Send taste test responses to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a tasting setup, adapt its prompt, or send it to the editable Makeform builder.
Audience
Consumer panelists comparing three coded samples
Format
Repeated sensory scales plus final preference
Prompt size
255 chars
Example form structure
Repeated sensory scales plus final preference
Confirm the sample code
Rate appearance, aroma, and flavor
Rate texture, aftertaste, and overall liking
What did you like or dislike?
Rank the three samples
Suggested routing tags
Completed panel
Preference winner
Follow-up comments
Use neutral three-digit sample codes and repeat the same scale for every sample so the product name and question order do not influence ratings.
Step 1
Code
label samples without revealing brands or recipes
Step 2
Taste
serve in a planned order under consistent conditions
Step 3
Rate
repeat identical scales for every sample
Step 4
Compare
review preferences, attributes, and comments together
Why structured tasting matters
A casual “Did you like it?” hides why a sample worked. A structured form captures consistent attributes, scales, and context.
Repeat identical attribute questions so every sample can be compared without translating mismatched answers.
Use coded dropdowns instead of product names while keeping responses tied to the correct recipe.
Pair rankings with comments to identify a leading sample and what to preserve or revise.
Useful tasting formats
Choose a format for an overall winner, attribute diagnosis, or quick restaurant feedback.
Put two versions side by side, repeat identical attribute questions, then ask which sample is preferred and why.
Measure how much participants like each sample overall and by attribute with clearly labeled endpoints.
Let participants order three or more coded samples, then capture the reason behind the top and bottom choices.
Keep the mobile form short: core sensory scores, likelihood to order, price range, and one actionable comment.
Build the tasting workflow
Define the decision, repeat the tasting path, and keep sample identity attached to each response.
Name the samples, participants, attributes, and whether you need liking, preference, or purchase intent.
Choose labeled endpoints, repeat one block per code, and add follow-ups where answers need explanation.
Share the link, assign serving order, and have participants confirm each code before rating.
Review submissions or send them to Google Sheets with codes, order, ratings, preferences, and comments together.
Choosing a collection method
Preserve sample identity, use consistent questions, and keep responses ready to compare.
Field guide
Six compact blocks capture what product, culinary, or research teams need without exhausting participants.
Participant context
Use an anonymous code when names are unnecessary. Add only segments the analysis will use, such as age range or category familiarity.
Session controls
Attach the session, serving order, and product condition to ratings. Record temperature or batch when those variables matter.
Sample identity
Start every repeated block with a required code dropdown. Neutral codes reduce brand cues and controlled choices prevent typos.
Sensory attributes
Choose attributes appropriate to the product. Label both scale endpoints and keep their direction consistent across samples.
Preference and intent
Ratings can be close despite a clear favorite. Add a final ranking, then measure purchase intent separately from sensory liking.
Diagnostic comments
Ask what to keep, reduce, increase, or change. Conditional follow-ups can explain extreme scores without lengthening every path.
Related tools
Pair the taste test with sensory evaluation, product research, customer feedback, and food operations forms.
Create a deeper sensory scorecard for trained panels evaluating detailed product attributes.
Open toolCollect broader usability, concept, and product-performance feedback beyond flavor alone.
Open toolExplore category habits, decision factors, and stated preferences before choosing test concepts.
Open toolGather service, atmosphere, menu, and return-intent feedback from café customers.
Open toolDocument routine handling, storage, cleaning, and preparation checks for food operations.
Open toolOpen a general feedback channel for customers after a product launch or menu release.
Open toolFAQ
Answers for food brands, restaurants, and researchers planning a tasting.
It is a questionnaire completed while evaluating food or drink. It links each coded sample to consistent sensory ratings, preference, and comments.
Start with participant and sample codes. Add relevant sensory attributes, overall liking, preference or ranking, purchase intent when useful, and focused comments.
Use neutral codes that hide brand or recipe. Put valid codes in a dropdown, confirm one before each block, and keep the product key outside the participant form.
Choose a scale with labeled endpoints. Use liking scales for acceptance and just-about-right choices for intensity. Keep direction and labels consistent.
Yes. Repeat one rating block per sample with a required code. Keep attributes and scale order identical, then ask for preference after all blocks.
Hide product identity, use neutral codes, standardize serving conditions, and rotate tasting order when needed. Collect individual ratings before group discussion.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse a taste test form without a response cap. The paid tier removes the Makeform badge.
Review submissions in Makeform or send them to Google Sheets. Keep codes, order, ratings, preference, and comments as structured fields for comparison.
Make every sample earn a clear score.
