Sound Effects/Audio Assets for Local Music Festival
Designing custom audio assets for a local music festival.
Photo: Egor Komarov / PexelsSound Design · 2–3 MonthsThe Brief
What you'd be taking on
A set of sound effects/audio assets for a local music festival, delivered as a real RogueBoard project. A local music festival needs this because their current audio (if any) is generic stock sound.
The Programme
Six phases, brief to handover
Every RogueBoard project runs the same six phases. Each one below carries the part of the brief it owns.
The task-by-task breakdown is written with the team when the project starts and opens in the workspace on day one. What's below is the brief as it stands today.
Discovery
Get inside the problem before touching the work: scope, constraints, and who you're building for.
What you need coming in
- Beginner-friendly for most roles
- Own laptop
- Willingness to commit 3–5 hours per week
Discovery task list · opens in the workspace when you join
Research
Gather the evidence the decisions will rest on.
The objectives to work against
- Agree the required sound assets
- Source or create raw audio
- Edit and polish each asset
- Deliver a final organised audio pack
Research task list · opens in the workspace when you join
Planning
Split the work, pick the tools, agree the dates.
Who does what · 4 roles
Project Lead
Coordinates the team, keeps the brief on schedule, and liaises with the project owner.
UI/UX Designer
Designs visual assets and mockups aligned to the brief.
Content Writer
Drafts copy, captions, and supporting written material.
Marketing Lead
Plans how the finished work gets shared and positioned.
Tools the team runs on
Planning task list · opens in the workspace when you join
Execution
The build. Most of the hours on this project live here.
Skills you'll practise here
Execution task list · opens in the workspace when you join
Quality Assurance
Check the work against the standard before the client ever sees it.
How the founder judges done
- A set of sound effects/audio assets completed to brief
- Approved by the project owner
- Delivered within the agreed timeframe
QA task list · opens in the workspace when you join
Delivery & Reflection
Hand it over properly, then write down what the team learned.
What the client walks away with
A set of sound effects/audio assets that a local music festival can put to immediate use.
Handed over
- Short handover notes for the project owner
Delivery task list · opens in the workspace when you join
FAQs
Common questions
Is this project paid?
No — RogueBoard projects are unpaid. What you earn is real experience, portfolio evidence, and a verified reference.
Can beginners join?
Depends on the role — check the Difficulty rating and each role's required skills above. Several roles on this project are beginner-friendly.
What if I miss a meeting?
Let your Project Lead know in advance where possible. One missed check-in won't remove you from the team, but consistent attendance is expected.
Can I leave early?
You can step back from a project, but try to hand off your work cleanly so the team and the credential process aren't disrupted.
Will I receive a reference?
Yes — completing your role to the agreed standard earns a verified RogueBoard credential and a reference you can point employers or clients to.