Email is the default for collecting feedback because it is already open on everyone's screen. It is also, quietly, the single biggest source of avoidable chaos in creative projects. The problems are not occasional — they are structural, baked into how email works, and they get worse with every extra reviewer.
Feedback gets detached from the work
In email, feedback and the file it refers to live apart. Someone writes 'the second image feels off' in a message while the image sits in an attachment or a link somewhere else. You become a translator, mapping words back onto the work and guessing which 'second image' they mean. Feedback that is not attached to the exact spot is feedback you have to decode.
Reply-all turns into a maze
Add three reviewers and email fractures into parallel threads. One replies only to you, another replies-all, a third starts a new thread, and a fourth forwards it to someone you have never met. There is no single place where all the feedback lives, so you spend real time just assembling what everyone actually said before you can act on any of it.
Versions get hopelessly confused
Email has no concept of versions. You send v2, someone replies to the v1 email with notes, and now you genuinely cannot tell which version a comment applies to. Multiply that across a few rounds and the thread becomes an archaeological dig. Nobody can say with confidence what the current version even is.
There is no record of approval
The most costly gap: email approval is mush. 'Looks good!' in a thread is not a decision you can rely on or point to later. When a client disputes what was signed off, a buried email is weak evidence. A proper review tool replaces all of this with feedback pinned to the work, one place for every comment, clear versions, and a documented approval.
“Email's problems with creative feedback are not occasional — they are structural. Feedback detaches from the work, threads fracture, versions blur, and approval is never really recorded.”
Why email fails at feedback
- Comments live apart from the file they describe
- Reply-all fractures feedback across parallel threads
- There is no version tracking, so notes attach to the wrong cut
- No consolidated place where all feedback lives
- Approval is vague and unenforceable
Frequently asked questions
Why is email bad for creative feedback?
Email detaches feedback from the work, fractures it across reply-all threads, has no version tracking so comments attach to the wrong draft, and produces no reliable record of approval. The problems are structural and worsen with every extra reviewer.
What should I use instead of email for feedback?
A review tool where feedback is pinned to the exact spot on the file, every comment lives in one place, versions stack clearly, and approval is captured with a name, version, and timestamp — solving each of email’s structural gaps.
What is wrong with "looks good" in an email?
It is not an enforceable approval. If a client later disputes what was signed off, a vague line buried in a thread is weak evidence. A documented approval tied to a specific version protects both sides.
Related resources
FileFeedback
Struggling with client feedback on your projects?
FileFeedback lets clients leave frame-accurate, timestamped comments directly on your videos and images — no more email chains, no more confusion about which version they mean.
Try FileFeedback free