Pilot review
A Time and Cost Log for Your Pilot With a Japan Partner
The review after a pilot is only as good as the notes behind it. Here is a light log that two teams in different time zones can keep without extra work.
Keep one shared log for the whole pilot, and record five things in it: the number of exchanges, the time spent, the cost, the problems you met and the successes you had. These are the records the GLOBAL MUSIC PARTNERSHIP desk suggests for any small pilot, and they give you what you need for the review at the end: a comparison of goals with results, a joint meeting with your partner and a decision to continue, adjust or end. A log takes five minutes a week, and it turns a vague memory of the project into a clear picture.
Why a log is worth the five minutes
Pilots are short, and short projects move fast. Two weeks in, the details of the first meeting are already blurred. If you work across time zones, messages arrive while one side is asleep, and it is easy for each team to remember a different version of what was agreed. A shared log gives both sides the same facts.
It also protects the people who do the work. When the review arrives, the log shows who prepared what, how long it took and where the effort went. That makes the conversation about the project fair and specific, and it helps managers on both sides see the value of a small start.
| Without a log | With a log |
|---|---|
| Each side remembers a different timeline | One list of dates and decisions |
| Time spent is guessed at the end | Hours are noted as they happen |
| Problems are forgotten or argued about | Problems are named when they appear |
| Wins are overlooked | Wins are collected for the review |
The five records
The five records below match the desk's guidance. Each has one question to answer and one example of a note.
| Record | Question | Example note |
|---|---|---|
| Exchanges | What contact did we have this week? | One online meeting, three email threads, one shared folder update |
| Time | How many hours did each side spend? | Preparation for the meeting, writing the brief, listening to demos |
| Cost | What did we spend or commit? | Items named in the written proposal, plus anything extra agreed in writing |
| Problems | What got in the way? | A file format that did not open, a meeting time that was too early |
| Successes | What worked well? | A first draft that both sides liked, a clear decision in one call |
Write short notes. A line or two for each record is plenty. The aim is to make the review easy, not to create a second project.
A template you can copy
Create a shared sheet or document with one row per week. Both teams edit it, and one person on each side is responsible for their own columns. The desk works in English and Japanese, so you can write your notes in your own language if you add a one-line English summary.
| Week | Exchanges | Hours (our side) | Hours (partner side) | Cost items | Problems | Successes |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 |
Add a header section above the table with four lines: the goal in one sentence, the roles, the deadline and the way you will review the pilot. These are the four things the desk asks two teams to agree before a pilot starts, so copying them to the top of the log keeps everyone pointed at the same target.
Keeping the log across time zones
Time zones are the quiet challenge of a Japan partnership. A few habits help the log stay accurate:
- Record dates with the time zone. Write "12 March, 10:00 Japan time" so that nobody has to convert later.
- Update at a fixed moment. Choose the end of your working week, and write the update before you close your laptop.
- Use the shared sheet as the single place. Copy important decisions from email into it, with the date.
- Use short sentences. They are easy for a translation tool or a second language reader to follow.
- Do not edit your partner's columns. If you disagree with a note, add a comment and talk about it in the next meeting.
When a pilot involves online lessons for overseas students, the desk arranges times across time zones, so note the agreed hours in the log with both local times.
Counting time and cost fairly
Two teams may count differently. One side counts only meeting hours, and the other counts preparation, editing and travel. Settle the rules at the start, in one sentence, so that the numbers can be compared.
| Count this | Usually not this |
|---|---|
| Meetings and rehearsals | Time that would have been spent anyway on your regular work |
| Preparation made only for the pilot | General research about the market |
| Costs named in the written proposal | Costs outside the project that nobody agreed to |
| Travel to a meeting in Tokyo or Atami, if you go | Travel for other business on the same trip |
The desk sends a written proposal with the cost and payment schedule for the pilot after the first online meeting, and it confirms terms, fees, schedules and rights case by case before any agreement. Copy the proposal's cost lines into the log so that actual costs sit next to the planned ones. If something extra is agreed, write it down with the date and the name of the person who agreed.
An illustration of one filled row (an example, not a real case)
| Field | Sample entry |
|---|---|
| Week | 2 |
| Exchanges | One 45-minute online meeting; two emails with reference songs; one shared folder update |
| Hours (our side) | Meeting, plus time choosing songs and writing a one-page brief |
| Hours (partner side) | Meeting, plus time listening to our songs and drafting two melody ideas |
| Cost items | Nothing beyond the written proposal this week |
| Problems | The audio files were in a format that the partner's software did not open |
| Successes | Both sides picked the same two reference songs, which saved a round of discussion |
A row like this takes a few minutes to write and gives the reviewer a lot to work with. The problem about the file format also points to a simple fix for the next week: agree on one file type and one folder structure at the start.
A ten-minute weekly check-in
If the two leads can spare ten minutes at the end of each week, a short call keeps the log honest. Read the new row aloud, ask the partner whether it matches their view, and fix any difference on the spot. Then name the one thing you will do before the next check-in. This rhythm also surfaces small problems before they grow, which is cheaper than finding them at the review.
Sharing the log with your own management
Managers, head teachers and festival boards rarely read a whole log, but they like a one-paragraph summary. Take the totals at the end of the pilot, add the best success and the main lesson, and send them with a link to the log for anyone who wants the detail. A clear summary helps the people who approved your time and budget to see what was learned.
Using the log in the review
At the end of the pilot, the log becomes the main input for the review. The desk's decision steps run in order: compare the goals with the results, meet with the partner, settle adjustments and then choose to proceed, change the format or end the project. The log answers the first step in minutes.
- Add up the exchanges, the hours on each side and the costs.
- List the problems and group them into two or three themes.
- List the successes, and pick the one that mattered most.
- Write three sentences: what we did, what we learned, what we suggest next.
Bring those three sentences to the meeting. If you also keep success criteria limited to about three points, such as the quality of the work, ease of production, audience response, or cost and time, the log gives you the evidence for each one.
Getting started
Keep the first log small. A sheet with the header and the first week's row is enough on day one, and you can add columns later if the project asks for them. Both teams will find the habit easier if the template is simple, and the review will be easier still.
The best moment to create the log is the day the pilot is agreed. Make a copy of the template, fill in the goal, the roles and the deadline, and invite your partner to the same file. The desk suggests starting with a small format, such as co-producing one track, a single exchange performance, an online workshop or a limited online release, and a log fits any of them.
To talk about a pilot of your own, send a message with your organisation, country, time zone, goals and preferred language. Contact the GLOBAL MUSIC PARTNERSHIP desk, and ask for help setting up your log at the first online meeting.
FAQ
What should we record during a pilot?
The number of exchanges, the time and cost spent, and the problems and successes you met.
How often should we update the log?
Weekly works well. Choose a fixed moment, such as the end of your working week.
Who keeps the log?
Both teams share it. One person on each side takes responsibility for their own columns.