MOOIEV BLOG
Write a clear crew role brief before contacting collaborators
An original sound-recordist brief with explicit scope, provisional dates, separate costs and a practical way to resolve a conditional crew response.
In this article 9 sections
A collaborator needs a decision, not a mystery
A message that says “looking for sound on a small film” leaves the recipient to discover the job. Is it a dialogue shoot or a music playback session? Is the date fixed? Does “bring your kit” mean a recorder, radio microphones, a boom, or an entire sound department? A friendly introduction can still hide a substantial amount of unpaid clarification.
Write the role brief before choosing whom to contact. Its first job is to help someone decide whether the conversation fits their availability, experience and working conditions. A useful response might be a clear no. That is better planning information than an enthusiastic maybe built on different assumptions.
Separate the job from the person you hope to find
Start with the production problem: two people speak while moving around a reflective workshop, and the film needs usable location dialogue. That describes a requirement. “Someone who can do sound and a bit of everything” describes a gap in the plan.
ScreenSkills describes the production sound mixer as leading the recording of sound during filming and discussing capture methods with the director and producer before the shoot. It also identifies location noise as a preparation issue. Use that role context to ask a sound professional what the planned scene actually requires; do not assume one person can cover every sound responsibility.
For this brief, the producer remains responsible for arranging the location and resolving access questions. The sound collaborator advises on capture and records the agreed material. Editing, dialogue repair, music licensing and the final mix are outside this proposed role. If those are needed, scope them separately.
ScreenSkills: production sound mixer role and preparation responsibilities
Worked example: turn a vague request into an evaluable brief
Fictional exercise: Lantern Room is an invented six-minute short, set in an invented workshop in Bristol. All project details, dates, fees and sample replies below are fictional. This is not a live vacancy, a real offer or a report about a Mooiev customer. The dollar amounts demonstrate how to separate scope and costs; they are not market rates or recommended compensation.
The weak draft reads: “Need a sound person next month. One easy day, small budget, great crew. Send your reel.” Replace those judgments with facts the recipient can assess. A quiet rehearsal is a better basis for deciding whether the location is easy than the producer’s adjective.
| Brief field | Illustrative revised wording |
|---|---|
| Project and output | Lantern Room: a fictional six-minute narrative short. One workshop dialogue scene involving two performers; intended festival and online release. |
| Role and boundaries | Location sound recordist. Advise on the capture plan, record agreed dialogue and room tone, and provide labeled audio files and sound notes. No sound edit or final mix in this scope. |
| Date and working window | Proposed shoot: 14 November 2026, 09:00–15:00, including setup, a planned break and audio handover. Date remains provisional until both sides confirm. |
| Preparation | One remote planning call of up to an hour during the preceding week. A location recording and floor plan will be shared before that call. |
| Place and conditions | Bristol workshop; exact address shared privately after interest is confirmed. Reflective surfaces and a nearby road; access, power and quiet periods still need checking. |
| Equipment and staffing | Please propose the recording kit and whether a second sound person is needed after reviewing the scene and location. Producer has not assumed radio microphones or extra crew are included. |
| Compensation | Illustrative draft only: $400 labor for the stated shoot window, $60 prep, and a proposed $80 kit allowance: $540 total before any applicable taxes. Kit, travel, extra time and payment schedule must be agreed explicitly. |
| Response requested | Confirm availability or constraints, link one relevant dialogue example with your contribution identified, and flag equipment or staffing questions. No custom unpaid test requested. |
| Decision status | This is an initial inquiry. No date is booked and no work should start until scope, schedule and terms are confirmed directly. |
Expose the unresolved choices instead of burying them
The example deliberately leaves the kit and staffing open. That is an invitation to assess the scene, not a promise that the proposed allowance will cover it. If the recordist needs an assistant or different equipment, the producer has three useful options: revise the budget, simplify the scene, or move the shoot. Pretending the same plan will work unchanged only postpones the decision.
Put each unresolved item beside an owner and a next action. For example: “Producer: obtain a two-minute room recording by Tuesday. Recordist: review it before confirming the capture approach.” Do not call a date confirmed when the venue or a necessary collaborator is still unavailable.
Keep the first public version focused on the role and broad location. Share a private script extract, precise address or contact sheet only with the people who need it and when you have permission. The invitation does not need a client’s full project folder attached.
Send an introduction that points to the brief
Fictional first message: “I liked how the workshop dialogue in your selected work stayed clear while the performers moved. I am preparing a short with a similar recording challenge in Bristol. Our proposed date is 14 November; the attached brief separates the shoot, prep and kit discussion. Would you be open to checking availability and telling us what the sound setup would need?”
Use that opening only if you actually reviewed the person’s work and can describe it truthfully. If you have not, say what you are seeking without inventing familiarity. Keep the role brief accessible in the conversation so the recipient does not have to reconstruct the offer from several messages.
Treat a conditional answer as a decision point
Fictional reply: “Available on the proposed day. The sample scene needs a separate boom operator if both performers move as written. My quote also needs the location check and kit list.” This is not a booking confirmation. It identifies a dependency in the production plan.
A useful producer response would be: “Understood. We will review the blocking and add the second role or change the staging before asking you to confirm. Please keep the date provisional.” Record who owns that decision and when it must be resolved. Avoid turning “available” into “accepted” in the crew plan.
Before confirming, read back the agreed role, preparation, working window, equipment, deliverables, payment arrangements and remaining conditions in one place. If the plan changes later, name the changed item and ask the collaborator to confirm the revised scope. A longer day is not the same brief with a new finish time hidden in a schedule.
Use the work to start the conversation on Mooiev
Mooiev’s public network demonstration shows roles, selected work and project contributions as context for a connection. Its crew application demonstration shows reading a response, reviewing a portfolio and accepting an application. Use those steps to review the person against the actual brief, rather than treating a profile as evidence of availability.
The fictional brief in this article is a writing method you can use in your own role description and conversation. The sample does not imply automatic matching, a guaranteed response, a confirmed hire or a contract generated by Mooiev.
Explore roles and selected work in the Mooiev network
A final check before you contact anyone
Give the draft to someone who was not in the planning conversation. Ask them to point to the role, date status, location, scope, compensation and requested reply. Any answer that requires your verbal explanation belongs in the brief.
The useful outcome is a conversation about the film and its needs. Make it possible for a collaborator to respond with “yes, on these terms,” “no, I am unavailable,” or “this part needs resolving.” Each answer gives the production a concrete next move.
- Replace “easy day” and “small budget” with a stated working window and clear terms.
- Keep labor, preparation, kit and other costs distinguishable.
- State what the role does not include when the boundary could be misunderstood.
- Label provisional dates and unresolved dependencies.
- Ask for relevant existing work and availability; keep the response request proportionate.
- Confirm the arrangement directly before treating an application or connection as a booked collaborator.
Editorial notes and sources
Written by Mooiev with AI assistance and reviewed for this publication. Lantern Room, its brief, fees, messages and replies are original fictional teaching examples. No real recruitment offer, private project or customer correspondence is reproduced. No third-party imagery or paid assets are used.
Source pages were checked on 26 October 2026. ScreenSkills supports the narrow role-description paragraph; the brief, response decisions and checklist are Mooiev’s original planning suggestions. The linked Mooiev pages support only the public product workflows described above.