Skip to content
Free tool · no account

Sample feedback template

Turn "it is a bit too chunky" into something a factory can actually make. Measurements, one instruction per line, and the part everyone forgets · what to keep.

Sample feedback

What to change

One instruction per line. Give the measurement you have and the one you want · that is the difference between a correction and another guess.

What to keep

Ready to send

Why feedback fails

A sampling round takes between two and eight weeks. When one is wasted, it is almost never because the maker is bad · it is because the instruction could be read two ways. Three habits fix most of it:

The longer version, including how to name versions and photograph a sample, is in managing samples and prototypes.

Questions

Why not just send photos with arrows?

Do send them · an arrow on an image removes a whole exchange of emails. But a photo cannot carry a tolerance, and it cannot be ticked off line by line. Use both: this list as the instruction, images as the evidence, and reference the image number in the line.

What if I do not know the measurement?

Measure it. A caliper costs very little and removes most of the ambiguity in product development. Where it genuinely cannot be measured · a feel, a drape, a sound · say so explicitly and send the reference object alongside, rather than hoping an adjective travels.

Should I send this in the email body or as a file?

Body for short rounds, file for anything a factory will print and work from. Either way, keep a copy with the version number · in four months the thing you will need is not the sample, it is what you asked for between V2 and V3.

Is my product information sent anywhere?

No. Everything is built in your browser. No account, no upload, no request.

The round after this one

The template solves today. The problem is V5, when you need to know what you asked for at V2 and whether you got it. In Teseo, every version of a piece carries its own feedback and its own photos, in order, on the product itself.