Video Edit Request Document

Sending vague messages like "the intro feels slow" or "change the music" forces editors to guess. The next cut inevitably changes the wrong parts while leaving the actual problems untouched. Extra revision rounds happen mostly because of ambiguous feedback, not editor incompetence.

The Task section converts subjective impressions into concrete editing actions. "Drags on" is just an impression; "Shorten intro logo duration" is an actionable instruction. Keeping the original phrasing in parentheses lets the editor ask clarifying questions if the translation misses the nuance.

The chronological table in Format is the core of this document. Editors work sequentially along the timeline, so ordering by time rather than by raw note order lets them work in a single pass. The priority column helps them triage under tight deadlines.

The Constraints prevent two common errors: guessing missing timestamps (a wrong timestamp is worse than none) and inventing extra revisions. Wrapping notes in """ establishes them as ground truth data, and masking names into roles ensures the document is ready for broader sharing.

A prompt like this just turns notes into clean bulleted sentences. Without timestamps, the editor must rewatch the entire video to locate each issue, and they won't know if "audio quiet" refers to dialogue or music. The AI might also hallucinate unsolicited suggestions like "add transition effects."

Remove personal names, contact info, or confidential project details before pasting your notes. Edit request sheets often get circulated across teams and vendors, so keeping references strictly to roles and on-screen content is safer. You don't need to upload the video file itself—timestamps and notes are sufficient.