A creator has answered your pitch. Before recording begins, give them a short brief that makes the collaboration easy to understand and the game easy to play. The brief should capture the decisions you have agreed on, leave room for their creative judgment, and identify anything still unresolved. Here is a practical structure for a first Roblox collaboration, with a fictional example you can adapt.
1. Define the job in a few lines
Open with the game name, a working experience link, the person responsible for the collaboration, and the purpose of the video. Choose one main purpose: introducing a new experience, showing a particular mechanic, or explaining an update. A brief that asks for every feature to appear gives the creator too little direction about what matters most.
Describe the player experience in plain language. For example, a fictional co-op escape game could be summarized as: Two players see different clues and must talk to solve the same room. That explanation gives the creator a starting point for a scene. A long list of systems and currencies usually does not.
- Game name and experience or preview link.
- One sentence about what players do.
- One main communication goal.
- A named contact and a way to reach them.
2. Explain exactly how to get a playable session
Test the link using an account with the same access a creator will have. Record any genuine setup steps, the supported devices you have checked, and the number of players needed to demonstrate the idea. If another teammate must join, agree on a time rather than assuming someone will be available during recording.
Give the creator a short route to the interesting moment. Explain where to start, what action reveals the mechanic, and any current bugs that could affect the session. If a feature is unfinished, label it as unfinished. Avoid asking the creator to describe a future feature as something players can already use.
Keep login credentials out of the brief. Arrange access through the appropriate account permissions and share only what the recipient needs to play. Have a backup plan for a broken build, such as rescheduling the recording after a confirmed fix.
3. Separate required facts from suggested ideas
Use two small sections: facts that must be accurate, and ideas the creator can adapt. Required facts might include the correct game name, the launch date if confirmed, and the destination link. Suggested ideas might include a timed challenge, a first-play reaction, or a team competition.
Let the creator tell you if the suggested format does not fit their channel. A useful brief explains the mechanic and the opportunity for a video; it does not script every reaction. Do not require praise, invented experiences, or claims about the game that neither side can support.
Agree on factual review boundaries before production. For example, you might check that a game link and update date are correct while leaving the creator responsible for their opinions and presentation. Specify who provides feedback, when feedback is due, and how many revision rounds are included.
4. Write down the deliverables and payment decisions
Replace vague phrases such as a few videos this month with a count, platform, format, and agreed publishing window. If the creator is delivering a draft rather than publishing it, say so. Treat a short video, a livestream, and a reusable edited clip as separate deliverables.
Summarize the compensation both sides agreed to, including any upfront payment, commission arrangement, expenses, payment timing, and cancellation discussion. If a point is still being negotiated, mark it as unresolved rather than making the brief appear final. A content brief is a working summary; use an appropriate agreement for the terms that need one.
Discuss reuse explicitly. Paying for a video does not tell the creator whether you want to repost it on your studio account, edit it into another video, or use it in an advertisement. Agree on the intended uses, duration, credit, and any additional fee before treating footage as a studio asset.
5. Plan the disclosure and viewer destination
Identify the commercial relationship and discuss how the creator will disclose it on the platform where the content will appear. YouTube requires creators to notify the platform about paid promotions using its paid-promotion setting; its official guidance is linked in the resources below. Check the rules for each publishing platform rather than copying a setting from another one.
Provide one clear destination for interested viewers. Confirm whether that is the playable experience, a preview page, or another genuinely available next step. Open the exact link before handing it over, and agree where it should appear in the content or description.
Decide what reporting you will request and when. A published URL and a screenshot of agreed performance metrics may be enough for an initial collaboration. Keep video views, link clicks, and game visits separate. If you cannot attribute game activity to the video, do not label all growth during the publishing window as a result of that creator.
6. A fictional brief you can adapt
The following is a planning example, not a real campaign or a claim about expected results. Replace the bracketed fields, then confirm the deliverables and terms with the creator.
- Game: [Name], a two-player Roblox escape game. Playable link: [tested link]. Studio contact: [name and contact route].
- Goal: Show how players exchange clues to escape the first room.
- Access: Two players required. [Contact] will confirm a recording slot and explain any access steps before the session.
- Creative idea: Try the first room without seeing each other’s clues. The creator can propose another format that suits their audience.
- Accurate facts: [confirmed game name], [available mechanic], [viewer link]. Avoid describing unfinished content as released.
- Deliverable: [agreed number] [format] on [platform], with [agreed publishing window].
- Review: [person] checks factual details by [deadline]; [agreed revision scope].
- Compensation and reuse: [confirmed terms or a clear reference to the agreed document].
- Disclosure and reporting: [platform-specific plan], published URL, and [agreed metrics] after [agreed interval].
7. Confirm the brief before anyone records
Send one version of the brief and ask the creator to confirm the access, deliverables, timing, and open questions. Keep a dated copy of the agreed version. When something changes, identify the change directly so neither side is working from an outdated message.
The best final check is practical: can the creator join the game, understand the interesting moment, tell what they are expected to deliver, and reach someone if the session fails? Resolve those basics before expanding the brief with extra talking points.
- The playable link works outside the development team.
- The recording setup and any teammate availability are confirmed.
- Required facts and optional ideas are clearly separated.
- Deliverables, feedback, compensation, and reuse have been discussed.
- Disclosure, viewer destination, and reporting are agreed.
- Unresolved decisions have an owner and a deadline.
Resources
Find creators for your next game.
Build a relevant shortlist and keep your outreach organized with Rscout.
Get started →