Frames and timecode: how to review video without ambiguous feedback
What a video frame is and how to identify the version, timecode, problem, and expected result when reviewing video.
A frame is each individual image that makes up a video. When many frames play every second, we perceive movement. In post-production, a frame helps identify an exact moment: “version 03, 00:18:12” is much more useful than “change the part after the logo.”
Timecode alone does not complete a review. An actionable comment needs the version, moment, problem, and expected result.
Frame, frame rate, and timecode are different
- Frame: one image in the sequence.
- Frame rate: the number of frames displayed each second, such as 24, 25, or 30 fps.
- Timecode: a time address usually written as hours, minutes, seconds, and frames.
Two exports with different introductions or frame rates may show different timecodes for the same scene. Every comment must therefore refer to an identified version as well.
The formula for useful feedback
Use this structure:
Version + timecode + element + problem + expected result.
Ambiguous:
The music is too loud when she speaks.
Actionable:
In
spot_v03, from 00:18:12 to 00:23:05, the music masks the second sentence. Lower it so the voice is clear without changing the rest of the mix.
The second comment defines the work. The editor does not have to guess which voice, which version, or how much material should change.
A review protocol for agencies and clients
1. Freeze the version
Do not silently replace a file while people are reviewing it. Every export needs an unmistakable identifier. If an urgent correction appears, close the round or explain which comments must be transferred.
2. Review the same playback
Whenever possible, everyone should view the same file. A downloaded attachment, a compressed copy, and an updated link can create three different experiences.
3. Separate reaction from change
“This feels slow” is a valid reaction. To turn it into work, identify where, which objective it affects, and the desired result. The editor can still propose the best solution.
4. Consolidate comments
If the client, agency, and leadership comment independently, one person should resolve contradictions before feedback returns to editing. Ten comments are not ten equally authoritative orders.
5. Close the round
Mark which observations are accepted, rejected, or outside scope. Then create a new version and retain the previous one for comparison—not for continued editing.
When a screenshot is enough
A screenshot helps discuss composition, color, text, or a visual element. It cannot adequately communicate rhythm, transition, synchronization, or movement. Sent through chat, it can also lose its relationship with the source video.
If you save it as a separate asset, record at least its video, version, and source timecode so another person can return to the context.
Searching and reviewing are different jobs
A team may first need to find “the shot where the person enters the door” among hours of material and then review the edit containing it. Polimake's DAM is designed to archive and search content—including within video frames—through its interface, API, or MCP.
Search helps retrieve the scene. The version and timecode remain necessary for communicating a specific correction in an edit.
Checklist before submitting feedback
- I am viewing the active version.
- My comment has a timecode or interval.
- I identify the affected element.
- I explain the problem, not only my reaction.
- I clarify the expected result.
- I flag any conflict with another decision.
- I know who approves the round.
Good review is not about writing more. It makes everyone talk about the same frame in the same version, with a decision production can execute.
— Oli Ser, founder of Polimake