Project folders
Shared Folder for a Music Project | GLOBAL MUSIC PARTNERSHIP
Create one shared folder for the whole pilot, divide it into six numbered subfolders and name every file with date, project, item and version. A short weekly routine keeps it tidy from week one to the review.
Create one shared folder for the whole pilot, divide it into six numbered subfolders (agreements, planning, audio, lyrics and scores, images and video, and the log), and name every file with the same pattern: date, project, item, version. That setup is all a small pilot needs. This article gives you a folder tree you can copy, a naming pattern that English and Japanese speakers can both read, and a short routine that keeps the folder tidy from the first week to the pilot review.
About the writer: Taanaa-sensei (Naoto Tanaka, known as TARNAR) has been a vocal trainer for 30 years and has taught more than 50,000 people. As the writer and producer on the Japan side of the co-writing projects on this site, he works with partner teams who share demos, lyrics and plans across borders, which is why a clear shared folder matters.
Why is one shared place worth the setup?
A small pilot with a partner in Japan has a short life, often a few weeks, and a single clear goal such as a co-written song, an online class or a joint showcase. In a short project, time is precious, and the question "which file is the latest?" can use it up quickly. When files travel by email, by chat and by different cloud services, the answer is often unclear.
The partnership approach on the Global Music Partnership site asks teams to settle goals, roles, deadlines and the way to review before the pilot begins. A shared folder is where those decisions live. It supports the later review too, because the pilot log, the version history of the work and the written agreements sit in one location.
Decide at the first online meeting which service you will use. Choose one that both teams can open without special software and that works in both countries. Then name one person on each side who looks after the folder.
What does the folder tree look like?
Numbers at the start of each folder name keep the order the same on every computer, whatever the language settings. Short English names are readable by nearly everyone and by translation tools.
| Folder | What goes inside | Who updates it |
|---|---|---|
| 01_agreements | Signed documents, written proposals, rights notes, credit lists | Both leads, after confirmation |
| 02_planning | Goal sheet, role sheet, schedule, meeting notes, decision log | Both leads |
| 03_audio | Demos, stems, rough mixes, guide vocals, final files | Whoever records |
| 04_lyrics_scores | Lyrics in each language, chord charts, lead sheets, translations | Writers |
| 05_images_video | Photos, video clips, artwork, logos | Whoever captures |
| 06_log | Hours and costs, weekly updates, review notes | Both leads |
Inside 03_audio, add one subfolder per song, and inside each song folder add three more: demos, stems and finals. Inside 04_lyrics_scores, keep one document per song with the languages side by side, or one file per language. Keep the six top-level folders fixed during the pilot. If something does not fit, place it in the closest folder and mention it in the weekly update.
In a camp setting such as the two-night co-writing retreat described on the partnership site, the same layout works with one addition: a folder for each day inside 03_audio, for recordings made at the inn. The first day's reference songs, the second day's piano sketches and the third morning's demo vocal then have clear homes.
How do you name files so both teams can read them?
Good file names sort in time order and make sense without opening them. A reliable pattern has four parts separated by underscores.
- Date in year-month-day form, for example 2027-03-05. This sorts correctly and avoids confusion between day-first and month-first habits.
- Project short name, such as the working title of the song.
- Item, such as demo, lyrics, plan or notes.
- Version, written v1, v2, v3, with the initials of the person who saved it.
An example is 2027-03-05_seaside-song_demo_v2_AB. Anyone who sees that name knows the date, the song, the type of file, the version and who made it. Add the word "final" to the file that both leads have confirmed, and keep it away from any file that might still be edited.
| Instead of | Use | Reason |
|---|---|---|
| final_final2.wav | 2027-03-05_seaside-song_demo_v3_AB.wav | Clear order and author |
| Song (copy).docx | 2027-03-05_seaside-song_lyrics_v2_CD.docx | Replaces the automatic copy suffix |
| Names with spaces and symbols | Plain letters, numbers, hyphens | Arrive intact across systems |
| New folder 7 | 03_audio | Predictable position |
Keep file names to plain letters, numbers and hyphens where you can. Different operating systems and transfer tools treat accents and special characters differently, and a plain name arrives the same everywhere. Japanese characters work well inside documents; only the file names benefit from plain letters.
Who can see and change what?
A shared folder is useful when the right people can open it and safe when only those people can. Decide permissions at the start and keep them simple.
- Two leads have full access to every folder, including the agreements folder.
- Working team members can add and edit files in audio, lyrics and images, with view-only access to the agreements folder.
- Guests, such as a studio engineer or a translator, get access to the subfolder they need, for the length of their work.
Write the access list in the planning folder and review it at the end of each week. When the pilot finishes, remove access that is no longer needed. The partnership site confirms rights work by work and records them in the agreement, so treat the agreements folder and any unreleased audio with particular care and share them with the people named in your arrangements.
How do versions and the golden copy work?
Every song needs one place where the current version lives. Call it the golden copy and make it obvious. A simple method is a file in the song folder named 00_current followed by the name of the latest approved version, or a short text note that says which file is current. Update the note whenever the current version changes.
When someone wants to try a new idea, they save it as a new version and mention it in the weekly update. The idea becomes the golden copy when both leads say so. This habit keeps everyone working on the same latest file.
For large audio files, agree on formats in advance. A lighter file for listening and a full-quality file for mixing are both useful, so label them clearly. The article on sharing demos and files with a partner in Japan covers formats and transfer methods.
A weekly ten-minute clean-up
Tidy as you go. Put a recurring ten-minute slot in both calendars, ideally right before the weekly update, and run through this list.
- Move loose files into the right folder.
- Rename files that differ from the pattern.
- Archive older versions in an "old" subfolder, so that history stays available.
- Check that the golden-copy note for each song is current.
- Update the log with hours spent and costs.
- List open questions in the weekly update.
The weekly update itself can be short. The related article on weekly update notes describes a simple template, and linking to the new files in that note tells your partner what to open first.
How do you adapt the layout to other kinds of pilot?
The six folders suit a song project, and the other pilot types described on the partnership site need only small changes.
| Pilot type | Change to the layout |
|---|---|
| Online class between schools | Replace 04_lyrics_scores with 04_lesson_materials; add a subfolder for class recordings, with a note on who may watch them |
| Joint showcase or shared stage | Add 07_stage with the rider, stage plot, running order and run sheet |
| Limited-time online release | Add 07_release with artwork, text, links and the release-day run sheet |
| Study visit or group trip | Add 07_travel with the roster, travel dates and booking confirmations |
Keep the numbers in the same order, so that anyone who has seen one project folder can find their way around another.
Where do messages and decisions live?
Files are half of a project; the rest is conversation. Decide where messages live. Many teams use a chat tool for quick questions and email for anything that needs a record. Whichever you choose, copy decisions out of chat and into the decision log in 02_planning, with the date and the names of the people who agreed. This keeps decisions easy to find three weeks later, particularly across time zones where each side sees a different part of the day.
A good decision-log entry has four short fields: date, decision, reason and who confirmed it. The related article on decision logs explains the format. Link each entry to the file it affects so that a reader can move from the decision to the result in one click.
How do you plan for backups and lost access?
Shared services occasionally fail, accounts get locked and people change jobs. Two simple measures protect the project. First, each lead keeps a local copy of the folder, refreshed weekly. Second, the access list in 02_planning includes a backup contact for each side, so that someone can restore access if the lead is away. These steps take minutes and make the whole project calmer.
How do you close the folder at the end of the pilot?
The pilot review compares goals with results, includes a talk with your partner and ends with a decision to continue, adjust or stop. Prepare the folder for that meeting. Make sure the log is complete, the agreements are filed, the final audio is labelled and a short summary sits at the top level.
If the pilot continues, keep the same structure and add a new date range to the file names. If it stops, archive the whole folder, note who has access and agree how long each side keeps the files. A tidy close is a courtesy to your partner and a gift to your future self, and it makes any later project with the same partner easy to restart.
Related articles
- How to Share Demos and Files With a Partner in Japan
- A Decision Log for Your Music Project With Japan
- A Weekly Update Note for a Music Pilot With Japan
- What to Save When a Pilot Ends: A Simple Project Archive
- How to Evaluate a Small Pilot With a Partner in Japan
To begin a pilot with a partner in Japan, send your goals and a few lines about your team through Global Music Partnership.
FAQ
How many folders does a pilot need?
Six numbered subfolders cover a song project: agreements, planning, audio, lyrics and scores, images and video, and the log. Other pilot types add a seventh folder for the stage, the release or travel.
What file-naming pattern works for English and Japanese teams?
Use date, project, item and version separated by underscores, for example 2027-03-05_seaside-song_demo_v2_AB. Plain letters, numbers and hyphens arrive intact on every system.
What is a golden copy?
It is the one approved current version of a song. Mark it with a 00_current file or a short note, and change it when both leads confirm a new version.
Who should have access to the agreements folder?
The two leads have full access, and working team members have view-only access. Guests receive access to the subfolder they need for the length of their work.