GoScript
Back to Blog
GoScript Journal

Hiring your first editor: the awkward parts

·8 min read·GoScript Team /Craft

Start with one paid test edit

Never hand a stranger your week of uploads and hope. Give a single short video and pay the full rate even if you do not use it. How they handle a tight brief tells you more than a portfolio. I learned to ask for the raw project file back so I could see how they structured tracks, labels, and cuts.

One editor I tested sent back a beautiful edit with every clip renamed after a burger. Funny, and impossible for anyone else to touch. The rename habit became a question I now ask up front: what are your file conventions?

Write a style guide, not a wish list

A style guide with timestamps and examples beats a paragraph of adjectives. Include your intro length, your cut rhythm, your caption font, and two reference videos with notes on what you like about each. Be specific about the pauses you keep and the ones you cut.

Keep it to one page. If you need three pages, your format is not consistent yet, and no editor can guess a moving target.

Give notes in one pass

Scattered DMs across three days confuse everyone. Watch once, write all notes with timecodes, and send them together. I sort my notes into two buckets: must change, and opinion. Labeling opinion as opinion keeps trust high and makes the next edit faster.

Pay on a schedule. Late payment kills good editors faster than a bad brief.

  • One paid test edit before any commitment
  • One-page style guide with reference videos
  • All notes in a single timecoded pass
  • Separate must-changes from opinions
  • Pay on the agreed date, every time

Your job as the client is to remove ambiguity, not to supervise.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel