How to brief an OnlyFans video editor

Define the job before sending the footage

“Make this look professional” leaves almost every decision open. Instead, name the piece, who it is for, and what a viewer should understand by the end. A recorded studio update, a Q&A, and a public preview need different edits even when they come from the same session.

Describe the expected length, framing, pace, text treatment, and audio work. Separate essential instructions from preferences. If a sentence must remain intact, identify it. If you would like a shorter opening but are flexible about the cut, say that too.

Confirm that the editor is an adult, understands the nature of the material, and accepts the assignment before you transfer it. Choose tools and services whose current rules permit the intended material and use. This guide describes a production handover, not OnlyFans account-management features or a substitute for applicable consent and verification requirements.

Choose the smallest useful handover

Prepare an assignment folder with only the selected footage, approved graphics, and instructions needed for this edit. Leave subscriber messages, payment information, identity documents, and unrelated projects out. Review the actual source clips, including their beginnings, endings, reflections, and background audio, before sharing them.

When handing over an existing Premiere project, Adobe documents a Project Manager option that collects media used by selected sequences into another location. Its Exclude Unused Clips option leaves unused media out of that collection. Treat collection as an organizational step: inspect the resulting package yourself before sharing it. A used clip can still contain private material outside the portion visible in the timeline.

Keep your originals separately. Open the handover copy and check that the files and any required fonts, graphics, or other dependencies are available as intended. If sending an editable project would expose too much, discuss a smaller, reviewed source selection instead.

For a file-editing job, the editor can return files for you to review and upload. Do not include your platform password, sign-in codes, or recovery details in the brief. An editing assignment does not need to become an account-access assignment.

Agree on tools and access before the transfer

Name the transfer service, editing application, and review route you both intend to use. Discuss whether the editor plans to upload footage to transcription, AI, or other external services. State which processing and subcontracting you authorize; silence should not become a vague permission to send the files elsewhere.

Google Drive’s documentation distinguishes restricted sharing from access for anyone with a link. It also explains that folder permissions flow down to the files inside. If you use Drive, review the parent folder as well as the individual item. Its documentation is an example of access behavior, not an endorsement of Drive for every kind of creator material.

Our suggested arrangement is a separate assignment location shared with the named editor, with permissions matched to the task. Check that they can retrieve the inputs and return the work without seeing the rest of your archive. Do not solve an access error by making the whole archive publicly reachable.

Access controls limit access through the service; they do not recall copies someone has already downloaded. Agree in advance on what may be retained, where it may be stored, and when the editor should remove working copies. Keep the agreement separate from your public promotional material.

Specify the files you expect back

Write a delivery list rather than asking for “the final video.” It might include the reviewed video export, an editable project if agreed, a thumbnail, and a caption file or a version with captions in the picture. Specify the container, resolution, orientation, and other export settings you have checked against the intended destination’s current requirements. Do not copy settings from an old brief without reviewing them.

If you need both a subscriber version and a public preview, list them as separate deliverables with separate approved source selections. Identify material that must never appear in the public version. A shorter export is not automatically a suitable preview.

Assign caption work explicitly. W3C describes captions as synchronized text for speech and meaningful non-speech audio, and says automatic captions need accuracy review. Decide who corrects the text, who checks timing, and how the captions will be delivered. Use our separate captioning guide for the detailed review.

Agree on the first-cut deadline, your feedback deadline, the final delivery date, and the number of revision rounds included in the price. Define what counts as correcting a missed instruction and what would be a new request. An additional version can involve more work even when its running time is shorter.

Adapt this brief for a small first assignment

The following is a fictional example for a non-explicit studio update. Replace the details with your own decisions; it is a production note, not a contract template.

Project: studio-update-01. Purpose: explain next month’s recording schedule to existing subscribers. Output: one landscape video, approximately two minutes. Keep the three schedule points in order. Remove false starts and long setup pauses; preserve the meaning of the answers. Use only the clips and title graphic in the assignment folder.

Privacy limits: exclude the doorway shot and the spoken private name marked in the source note. Do not add other people’s material, music, or stock assets without approval. Do not upload the source files to additional processing services or pass them to another editor without written agreement. No portfolio or promotional use is authorized by this brief.

Delivery: one review export named studio-update-01_v01, then an approved export and the agreed editable project. Confirm export settings before starting. Include a corrected caption version using the delivery method we agree. First cut due 23 October 2026; feedback due 24 October; final due 26 October. One consolidated revision round is included in the agreed fee; extra deliverables require a new scope and price.

Approval and closure: I review and publish the approved version. After acceptance, confirm removal of downloaded source and working copies by the agreed date, and identify anything retained under our agreement. Keep my original archive separate throughout the job.

Give feedback that points to a decision

Watch the complete first cut before writing comments. Consolidate feedback into one list with the version name, timestamp, requested change, and reason. Distinguish a blocking problem from a preference so the editor can prioritize the work.

For example: “v01, 00:42–00:48: remove the sentence containing the private name; resume at the next complete answer.” That is easier to act on than “privacy needs work.” For pacing: “v01, opening: shorten the setup pause while keeping the whole introduction” gives a direction without requiring the editor to guess which words matter.

Review the next export again from beginning to end. A correction can change caption timing, audio transitions, or what appears in a new crop. Check the exact delivery file, not just the preview link or the project timeline.

Keep approval explicit and tied to a filename or version. If something has not been checked, record it as outstanding. Payment, a friendly message, and a folder called final are poor substitutes for a clear publication decision.

Close the assignment while the details are fresh

Save the approved export, agreed project files, brief, and final feedback in your own archive. Open the returned project if it is part of the delivery and confirm that the required media links work. Record which version you publish in your content log.

Review shared access when the assignment ends and remove permissions that are no longer needed. Ask for the agreed confirmation about working copies and any remaining retention. This is a follow-through step, not proof that every copy has disappeared.

Finally, note one useful improvement for the next brief. Perhaps you needed a public preview but forgot to specify its framing, or the caption wording needed an approved spelling list. Turn that lesson into a clearer instruction. A good handover reduces repeated guessing without requiring a different system for every video.