Demo hand-off
How to Share Demos and Files With a Partner in Japan
Use one shared folder, one file-name pattern and a three-line note with every upload. This guide shows how to set up each habit for a pilot with a Japanese partner.
The best way to share demos and files with a partner in Japan is to use one shared folder with a fixed structure, name every file with the same pattern, and attach a three-line note to each upload. Those three habits remove almost every confusion that appears when two teams in different countries pass demos back and forth. A co-production with GLOBAL MUSIC PARTNERSHIP is built around a small pilot with one clear goal, and a tidy hand-off system is the practical way to keep the pilot's agreements alive during the work.
Written by Tarnar-sensei (Naoto Tanaka), voice trainer for 30 years who has coached more than 50,000 people. He has 119 or more music productions to his name, including theme songs, jingles and program openings, and leads the Japanese side of the songwriting camp as composer, lyricist and producer.
Why do music hand-offs need a plan?
When two teams work in different time zones, a file often arrives while the other side is asleep. The first thing a collaborator sees in the morning is the file name and the note. If the name is unclear, they may open an old version, comment on the wrong take, or wait for a reply that costs a day. A hand-off system turns each upload into a complete message: what it is, which version it is, and what you would like back.
It also protects the creative record. At the end of a pilot, the team agrees on credits, splits and next steps, and a clean file history makes that conversation easier because everyone can see who contributed which part and when. If you are still deciding how to begin, the GLOBAL MUSIC PARTNERSHIP home page explains the five-step process, and the goal, roles, deadline and review method are agreed before the pilot starts. A shared folder is simply where those agreements live from day to day.
- Each upload answers three questions: what is this, which version is it, and what do you want back.
- Each file has one home, so nobody searches through messages for the latest take.
- Each decision is written down, so credits and next steps are easy to settle at the end.
How should you set up the shared folder?
Create one shared location that both teams can open, and agree on its structure at the kick-off meeting. A simple layout works for most pilots, from one co-written song to one online class.
| Folder | What goes inside | Who adds files |
|---|---|---|
| 00_Brief | Goal, roles, schedule, reference card | Both sides |
| 01_Lyrics | Lyric drafts in each language, with plain translations | Lyricists |
| 02_Demos | Rough recordings: piano, guide vocal, sketches | Composers and singers |
| 03_Stems | Separate tracks for mixing or arrangement | Producers |
| 04_Mixes | Mix versions for listening and review | Producers |
| 05_Final | Approved files only | Project leads |
| 06_Credits | The written record of credits, splits and next steps | Project leads |
The numbers at the start of each folder name keep the order the same on every computer. The Final folder is only for files that both sides have approved, so nobody wonders which file is the finished one. If you want a deeper look at roles, A Pilot Role Sheet: Who Does What, and By When shows how to name an owner for each folder.
What file-name pattern works best?
A good file name tells the reader what the file is without opening it. A pattern that works well has five parts, separated by underscores: the project, the song, the type of file, the version and the date. Write the date in year-month-day order so that files sort correctly in any language.
- Pattern: Project_Song_Type_Version_Date
- Example: Pilot_SeaLight_GuideVocal_v03_2026-11-12
- Example: Pilot_SeaLight_Lyrics-EN_v02_2026-11-10
- Example: Pilot_SeaLight_Mix_v01_2026-11-15
Keep file names in plain letters and numbers. Avoid spaces and special symbols, because different systems treat them differently. Never rename a file after you have shared it, because your partner's notes will point to the old name. If something changes, make a new version number instead.
A version number that only goes up gives the whole team a shared language. When someone says "v03 chorus", everyone knows exactly which recording they mean, and a comment on v02 can be answered by v03 without any guessing.
What goes in the three-line note?
A short note travels with the file. It should take less than a minute to write and answer three questions.
- What changed? One line, for example: "Second verse melody simplified; bridge lyric shortened."
- What do you want back? One line, for example: "Feedback on the chorus melody only, by Friday 18:00 JST."
- What is next? One line, for example: "Next upload will be the full guide vocal."
Writing the deadline in JST plus the local time avoids a missed hand-off, and naming exactly what feedback you want keeps comments on the parts that are ready. Japan Standard Time is UTC+9 all year, so a deadline written once in both clocks can be read correctly by everyone. For a longer look at scheduling, see Scheduling a Music Project With Japan Across Time Zones.
Which file type fits each purpose?
Not every moment needs a full-quality file. Matching the file type to the purpose keeps uploads quick and reviews focused.
| Purpose | Suggested file | Tip |
|---|---|---|
| Quick listen on a phone | A compressed audio file | Good for early ideas and daily check-ins |
| Careful listening | An uncompressed audio file | Use for the demo vocal and for mix reviews |
| Arrangement or mixing | Stems, all starting at the same point | Export every track from bar one so they line up |
| Lyric review | A plain text or document file | Show each language in its own column |
| Melody sharing | A short recording at the piano | Say the key and the tempo in the note |
At the songwriting camp, the melody and chorus are shaped at the grand piano and the team records a demo vocal on the last morning. Those two moments produce the most important files of a pilot, so label them carefully and put them in the right folders straight away. The camp format is described in Songwriting Camp in Japan: A Two-Night Co-Writing Retreat by the Sea in Atami.
Add a spoken slate to each demo
A small habit with a big effect is to record a ten-second spoken slate at the start of each demo: your name, the song title, the version and the key. When a file is played months later, or by someone who was not on the project, the slate tells them exactly what they are hearing. For lyric sheets, put the title, the version and the language in the first line of the document for the same reason.
How do feedback rounds reach a finish?
Open-ended feedback can go on indefinitely. A fixed number of rounds gives a pilot a clear shape. A pattern that suits a short project is three rounds for each major piece.
- Round one, direction: Is the idea right? Comment on feeling, structure and story only.
- Round two, detail: Comment on words, notes and arrangement.
- Round three, approval: Confirm or request one last change, then lock the version.
At the end of each round, the sender writes a one-line summary of what was decided, and both sides reply with a short confirmation. The confirmed version moves to the Final folder only when both teams agree. Because the pilot has a deadline and a review method, the rounds keep everyone on schedule. A gentle tone helps as well, and Giving Feedback on a Demo Across Cultures: A Simple Method offers phrases that work in both English and Japanese.
A checklist for every upload
- The file is in the right folder.
- The name follows the five-part pattern.
- The version number is higher than the previous one.
- The three-line note is attached.
- The deadline is written in JST and in the local time.
- The recipient knows which language to reply in.
Keep the checklist near the shared folder, and review it together in the first week. If something is unclear, adjust the system once, early, and then keep it steady.
What common hand-off problems come up, and how do you fix them?
| Problem | Fix |
|---|---|
| Two people edit the same file at once | Name one owner per file type, and let others comment in a separate note |
| Feedback arrives on an old version | Put the version number at the top of every comment |
| A file is too large to send quickly | Send a compressed listening copy first and the full file when it is approved |
| Nobody knows which lyric is current | Keep only one current lyric file per language, and move older ones to an Archive sub-folder |
| The mix sounds different on each side | Share the listening setup in the note, such as headphones or speakers, and compare on the same device when possible |
Keep a record from day one
Keep a simple log in the Brief folder with one line per upload: date, file name, who sent it and what was decided. This log becomes the backbone of the credits conversation at the end of the pilot, when the team agrees on credits, splits and next steps and records them in writing. It is also helpful if a new person joins the project midway, because they can read the log in ten minutes and understand how the song has grown. For the wider picture of ownership, Sharing rights across borders explains what to agree before a co-production starts.
When the pilot ends, copy the Final and Credits folders to a safe location that both sides can access, and agree who keeps the original session files. Decide this before the last day, not after, so the end of the project feels settled and clear.
How do you begin with one shared folder?
You do not need special software to begin. A single folder with these seven sub-folders and a clear naming pattern is enough for a pilot of one song, one class or one showcase. When you are ready to plan a co-production, share your company, country, time zone, goals and preferred language. After the first online meeting, in English or Japanese, you receive a written proposal with the cost and payment schedule, and we can set up the working method together.
Visit GLOBAL MUSIC PARTNERSHIP to start a conversation
FAQ
What is the simplest way to share demos with a partner in Japan?
Use one shared folder with numbered sub-folders, a five-part file name and a three-line note with every upload. This keeps both sides on the same version even when they work in different time zones.
How should I name demo and stem files?
Use the pattern Project_Song_Type_Version_Date, with the date in year-month-day order and plain letters and numbers only. Never rename a file after sharing it; make a new version number instead.
How many feedback rounds should a pilot have?
Three rounds for each major piece suit a short project: direction, detail and approval. Each round ends with a one-line summary and a short confirmation from both sides.
Which audio file should I send for a quick review?
Send a compressed audio file for quick listens on a phone, and an uncompressed file for careful listening to the demo vocal and mix reviews. Stems should all start at the same point so they line up.
Do we need special software for a pilot?
No. A single shared folder with seven sub-folders and a clear naming pattern is enough for a pilot of one song, one class or one showcase.