← Journal

Journal

Get usable driver content across a championship without chasing everyone

Create a clear driver submission brief with one requested contribution, a shared handoff and a selection record across the field.

Nick LambertFounder, Turn One

2 min read

A championship has stories across the grid, but asking everyone to “send content” produces uneven results. Some teams send polished films, others send context-free clips, and several do not know what would be useful.

Request a specific contribution for a specific editorial job. Give contributors a clear recording brief, a submission location and a deadline, then acknowledge what arrived. Consistency comes from making the request understandable, not from demanding identical personalities.

Ask a question the contributor can answer

Illustrative request: “Explain one decision you changed between practice and qualifying, and what you learned. Record somewhere quiet, identify the session, and send one permitted detail shot if it makes the explanation clearer.”

The championship can give a format and context without scripting an emotion or outcome. Allow a driver to say that the change did not work. A truthful answer is more useful than manufacturing a positive ending for every submission.

Include the practical details in the same brief

  • Who the intended viewer is and what the piece should explain.
  • Preferred orientation and any essential framing instruction.
  • Where original files and context should be submitted.
  • Deadline, named contact and publication timing if known.
  • What permissions and factual checks the contributor must confirm.

For younger competitors or footage involving other people, resolve the applicable consent and approval process with the organiser before soliciting material. Do not assume that an uploaded clip is cleared for every use.

Track receipt and selection separately

Acknowledge receipt so the contributor knows the files arrived. Then record whether the material is usable, needs a clarification, is held for a later story or has been selected. Submission should not imply a promise to publish.

Keep a record of who has appeared recently and why a contribution was chosen. It makes repeated reliance on the same responsive teams visible. Where gaps emerge, commission a relevant contribution from elsewhere in the field rather than making unsupported claims of equal coverage.

Return a focused request when something is missing

“Please confirm which session this describes” is easier to answer than “We need more context.” If the audio cannot be understood, request the explanation again while keeping any usable visual material. Avoid requiring a full reshoot when one missing element would make the story work.

After publication, share the link with the contributor and retain the permissions and factual context with the project. Feed recurring problems into a clearer next brief.

The between-rounds editorial guide explains how those contributions can form a connected sequence. For planning, editing and distribution around your series, explore Turn One for championships.

Related questions

A few useful answers.

Should every driver answer the same question?

A shared question can create a useful series when different perspectives matter. Use individual prompts when a specific story requires different context.

Does submitting a video guarantee publication?

No. State the selection process in the brief and acknowledge receipt separately from an editorial decision.

Put it into practice

Build a connected championship story.

Plan contributions, editorial review and publication around your series.

Explore championship content
Turn One

Driver testimonial

Video from the existing Turn One testimonial library. Open the original player