Monk Fruit SweetHENGLIYUAN / SAMPLE WORKSHEET
Sweetener sample comparison.
Same question. Clearer feedback.
Keep the sample version and test conditions with your observations.
Free to use · No login
Save your record before closing.
Record sweetener sample feedback in your actual application. Create coded tasting sheets, compare observations and prepare a revision brief without signing in. One evaluator and one round per sheet. The completed record supports a sample discussion; production approval remains separate.
FROM TRIAL TO REVISION
Keep the version with the feedback.
Use the same record when discussing which sample is closest to the target, what should change first and what should remain unchanged. Keep separate sheets for repeats and other evaluators.
Prepare an OEM project brief- Record the actual dose, base, preparation and serving conditions.
- Save the code key separately; use codes in the tasting view.
- Describe differences and the first adjustment to discuss.
- Confirm the exact sample version and evaluation scope before commercial review.
How to read the worksheet
Overall fit is your own 1–5 assessment against the target you wrote. Optional observations use their own labeled scales: intensity describes how strong a sensation is, while sweetness describes its difference from your target. These dimensions are not added together or ranked automatically.
This worksheet does not verify a formula, nutrition claim, shelf life or finished-product specification. It records one person's observations under the stated conditions. Refreshing or closing the page clears the entries, so save the report and code key you need.
USEFUL ANSWERS
Before the next round.
What should I record before tasting?
Use the actual application or base, sample versions, reference target and first improvement priority. Record the dose with units, base quantity, preparation and serving conditions, and observation time. The worksheet does not prescribe a universal dose or test method.
How does the coded view work?
A preparer enters sample identities, receives unique three-digit codes and a shuffled presentation order, then labels the samples. Save the separate code key before opening the evaluator view. Only codes appear in the tasting questions. The preparer should not act as an unaware evaluator; identities remain in the page's memory, so this is not secure multi-user blinding.
Do all samples need the same preparation?
Use a consistent basis for the comparison you intend to make. If a sample needs different preparation, record that difference in its notes and consider whether the results still answer the same question. The tool does not correct for differences in dose, temperature, base or processing.
What do the scores mean?
Overall fit runs from 1 (poor) to 5 (very good) against your own stated target. Optional bitterness, lingering taste and cooling observations describe intensity, not goodness. Sweetness is relative to your target. These are worksheet scales, not a validated sensory test or a statistical result.
Can several people use this as a panel test?
Each sheet records one evaluator and one round. Keep separate records for other evaluators or repeats. This version does not pool panel data, balance presentation orders across a panel or calculate significance.
Does a preferred sample approve production?
No. Use the record to discuss the closest sample, what to adjust first and what to keep unchanged. Formula and sample version, agreed evaluation scope, packaging, specifications and commercial terms need separate confirmation.
Where are my entries saved?
Entries stay in the current page and clear on refresh. You can copy the record or use Print / save PDF to save the record and its separate code key in the company document layout. No login or contact information is required, and nothing is automatically sent to Hengliyuan.
Built with the SurveyJS Form Library under the MIT license.
