Pilot preparation
A Dry Run Before Your Japan Pilot: Test Tools and Timing
A short rehearsal of the process, with a practice file instead of a real song, finds the small snags before they cost you a working session. Here is a one-hour dry run you can run with your partner.
A dry run is a short practice session, held after you agree on a pilot and before the real work begins, in which both teams test the call, the sound, the file exchange and the reply rhythm using a practice file instead of a real song. One hour is enough. It turns hidden snags, such as a meeting link that fails on one side or a folder that one team cannot open, into small, cheap fixes rather than lost minutes in a working session.
The Global Music Partnership approach asks you to decide goals, roles, deadlines and a review method before a pilot starts. A dry run is the natural last step of that preparation. It confirms that the plan you wrote down also works in practice.
Why a rehearsal pays off in a cross-border pilot
Working across time zones raises the cost of every delay. If a call fails to connect, the next free slot for both teams may be days away. If a file arrives in a format one side cannot open, the reply cycle can take a full day. A dry run lets you meet those problems while nothing important depends on them.
It also builds quiet confidence. Both teams have already spoken once, solved something small together and tried the habits that will carry the pilot. That makes the real kickoff feel like a second meeting, not a first one.
What to settle before the dry run
Agree these five points by message, so the hour itself is spent testing rather than deciding.
- Date and time in both time zones, with the date spelled out.
- The meeting tool and who will send the link.
- The shared place for files, and who creates it.
- The practice file: a short recording of a few seconds, such as a hummed phrase, a clap pattern or a spoken sentence. It should be nothing you mind sharing.
- One lead on each side, so there is a single person to ask if something goes wrong.
The one-hour running order
| Minutes | Block | What you test |
|---|---|---|
| 0 to 10 | Connect | Meeting link, camera, microphone, screen share |
| 10 to 25 | Sound | Speaking levels, playing a recording, headphones, background noise |
| 25 to 40 | Files | Send and open the practice file; test the folder structure |
| 40 to 50 | Notes | Write a short recap together and send it |
| 50 to 60 | Rhythm | Agree reply times, the update day and the contact route for urgent matters |
Connect
Join the call on the device you will use in the pilot, and from the place you will normally work. Check that each person can see and hear the others, that the screen share works in both directions, and that the call stays stable for ten minutes. If anyone must join from a network with restrictions, find that out now.
Sound
Sound is the heart of a music project, so give it the longest of the technical blocks. Ask each person to speak at normal volume, then play a recording through the call and ask the other side how it sounds. Online calls compress audio and add a small delay, so a recording heard over the call is a guide to the idea, not to the final quality. Agree that anything judged for quality, such as a vocal take, will be sent as a file and listened to on good headphones.
Test the room, too. A quiet space with a door that closes makes a large difference to how clearly a voice or an instrument comes through.
Files
Send the practice file through your chosen shared place and ask the partner to confirm that it opened, played and could be saved. Then ask them to send one back. Try three small things that often trip teams up:
- A file name with a date and a short title, for example "2026-12-01_practice-clap_v1".
- Two versions of the same file, to check that version labels are understood.
- A short text note with the file, to check that notes and files stay together.
If your project will produce lyrics or notes in two languages, include one short line in each language in the text file, to see whether both scripts display correctly on both sides.
Notes
Write the dry-run recap together, live, in a shared document. Doing this once, in a calm setting, shows both teams what a recap should contain: date, attendees, decisions, tasks and next meeting. After the call, one person sends the recap, and the other adds corrections. The habit will serve you every week of the pilot.
Rhythm
End by talking about pace. Agree on the answers to these questions and write them in the recap.
| Question | Example answer |
|---|---|
| How fast do we reply to routine messages? | Within one working day |
| When do we send the weekly update? | Every Friday morning in Tokyo time |
| What is the route for an urgent matter? | LINE message to the named lead, then email |
| Which holidays or busy days should we avoid? | List the dates now |
| Who has the final word on a creative question? | Name one person on each side and how they decide together |
The partnership desk is reachable through its contact form and LINE, so you can decide which route each kind of message will use. Agreeing this at the start means no one wonders where to write when something comes up.
Who does what during the hour
Even a short test runs better with clear roles. Give each person one job so that nothing is forgotten and nobody is doing three things at once.
| Role | Job during the dry run |
|---|---|
| Host | Sends the meeting link, starts the call on time and keeps the running order |
| Sound checker | Leads the audio block, listens on headphones and reports what they hear |
| File keeper | Creates the shared place, sends and receives the practice files, checks names and versions |
| Note taker | Writes the recap and the log of problems and fixes |
On a small team, one person may hold two roles. What matters is that every role has a name beside it, and that the partner's team knows whom to ask about each one.
If the dry run goes badly
A dry run that surfaces many problems has done its job. Write each one in the log, fix the easiest first and book a short second test. Because the pilot has not started yet, there is no pressure on the creative work, and the second test is usually quick. Problems found now are problems your real kickoff will not have to face.
Collect what you learn
Keep a short log during the dry run. The pilot guidance on the partnership site encourages recording interactions, time spent, problems and successes, and the dry run is a good moment to begin.
| What happened | Cause | Fix | Owner |
|---|---|---|---|
| Video froze after eight minutes | Weak wireless signal | Move to a wired connection | Our lead |
| Practice file would not open | Unusual file format | Use a common audio format both sides can open | Partner lead |
| Recap arrived late | Unclear who sends it | Name the sender for each meeting | Both leads |
The entries above are illustrations of the kind of items you might record; your own log will show what your teams actually meet. Fix each item and mark it done before the pilot starts.
Common questions the dry run answers
- Can everyone join the call without extra steps?
- Can both sides hear a recording well enough to judge an idea?
- Do files open on both sides and keep their names and versions?
- Do both scripts display correctly in notes and lyric sheets?
- Do both teams agree on reply times and the weekly update?
- Does each side know exactly who to contact first?
If the answer to any of these is no, plan a second, shorter test. Fifteen minutes is often enough to close the gap.
A printable checklist
- Meeting link works on every device we will use.
- Camera, microphone and screen share tested in both directions.
- Recording played over the call and judged "good enough for ideas".
- Practice file sent, opened, saved and returned.
- File names, versions and notes arrive together.
- Both scripts display correctly in notes.
- Reply times, update day and urgent route written down.
- Holidays and busy days listed for the pilot period.
- One lead named on each side.
- Recap sent and corrected by the partner.
After the dry run: kick off with confidence
Once the log is clear, send a short message confirming the pilot start date and attaching the final recap. In the first seven days, begin with the lightest task, such as sharing reference songs or the class plan, so momentum builds before the complex work. At the end of the pilot, add one line to your review about the dry run: did it save time? The answer will shape how you prepare for the next project.
When you are ready to plan your own pilot, start with a first online meeting through the Global Music Partnership desk.
Plan your pilot with the Global Music Partnership desk
FAQ
How long should a dry run take?
One hour is enough for most pilots. If you find a problem you cannot fix on the spot, schedule a short follow-up test.
What should we use as a practice file?
A few seconds of something you are happy to share, such as a hummed phrase, a clap pattern or a spoken sentence.
Who should attend?
The lead on each side and anyone who will handle files or run the sessions.
Is a dry run needed for a very small pilot?
A shorter version still helps. Even fifteen minutes to test the call, the audio and one file exchange can save a working session later.