Pilot planning

How Long Should a Pilot Last? Length and Checkpoints

 By the GLOBAL MUSIC PARTNERSHIP editorial team / Supervised by Naoto Tanaka (Tarnar sensei)

A pilot is meant to be short, but short can mean two weeks or three months. This guide helps you match the length to your goal and place checkpoints so that the review has real material to work with.

The right length for a pilot is the shortest period in which your single goal can be reached and judged. A one-song co-write or a single online class needs a few weeks of calendar time, a joint online showcase needs a little longer for preparation, and a limited-time online release needs room for listeners to respond. Choose the length from the goal, set two or three checkpoints along the way, and fix the review date before you start.

Start from the way the partner describes a pilot

The partnership desk in Japan describes a pilot as short, with a fixed period and one goal. Before it begins, the two sides agree on the goal, each side's role, the deadline and how they will look back afterwards. Typical examples are one co-written song, one online class and one joint showcase.

Two ideas in that description matter for length. The first is that the period is fixed, so a pilot never drifts on without an end. The second is that the review is planned from the beginning, so the pilot's last day is also the day you learn something. Together they mean that "how long?" is really two questions: how long does the work take, and how long before the review do you want results to settle?

Match the goal to a time window

These windows are planning guides drawn from common project rhythms, not fixed rules of the partnership. Adjust them to your calendars and agree the final dates with your partner.

Pilot goalWork phasesSuggested window
One online class or workshopChoose topic, prepare materials, hold the class, collect feedbackThree to five weeks
One co-written songAgree theme, exchange ideas, write, record a demo, agree creditsFour to eight weeks
One joint showcaseChoose programme, rehearse separately, test the connection, perform, reviewSix to ten weeks
Limited-time online releasePrepare release, announce, run the release period, read reactionsSix to ten weeks
A visit to Atami for a campPlan the team, send reference songs, stay two nights, follow up on creditsEight to twelve weeks including preparation and follow-up

If your goal is not on this list, break it into phases yourself. Write each phase on a line, estimate the working days it needs on each side, and add a margin for replies across time zones. A reply from the other side of the world often takes a day, so every back-and-forth costs two days of calendar time, not two hours.

Build in the waiting time that people forget

Teams usually estimate the active work correctly and forget the waiting. Look for the places where one side must wait for the other, and count those days honestly.

  • Replies. With a time-zone gap, a question sent at the end of your day is read at the start of theirs, and the answer reaches you by your next morning. Plan on one exchange per day at best.
  • Holidays and busy periods. Both countries have them. Compare the two calendars before fixing dates, and keep important sessions away from them.
  • Approvals. If anything needs sign-off from a manager, a school board or a rights holder, add the days it takes to get an answer.
  • Practice and recording. A rehearsal or a demo take almost always needs a second attempt. Leave space for it.

When you have listed them, add a buffer of roughly one fifth of the total window. A pilot that finishes a few days early is a pleasant surprise. A pilot that overruns undermines trust in the schedule.

Set two or three checkpoints

A checkpoint is a short, scheduled moment to ask, "Are we still heading toward the goal?" It prevents the situation in which a problem grows unnoticed for a month. Two or three are enough for a pilot of this size.

  1. The start check, in the first week. Confirm that roles are clear and the first task is under way. This is also the time to ask whether anything in the plan feels too heavy.
  2. The midpoint check. Look at the work so far, however rough. Compare it with the goal and decide whether to continue as planned or adjust the scope. Cutting a small element at this point is easier than rescuing the whole thing later.
  3. The final check, a few days before the end. Make sure the finishing tasks are complete, the records are collected and the review meeting is booked.

Each checkpoint can be a ten-minute call or even a short written note. What matters is that both sides do it on the same days.

Decide what you will record

The partner's own guidance on evaluating a pilot suggests recording three things as you go: how many exchanges you had, how much time and money each side spent, and what problems and successes occurred. Keep these notes light, in a shared table, updated at each checkpoint. They turn the review from a vague impression into a conversation about facts.

The same guidance suggests keeping the success measures to about three, for example quality of the work, how easy it was to work together, the response of listeners, or time and cost. Pick your three before the start, and place each in the checkpoint that will first show evidence for it. Quality can be judged at the midpoint, ease of working together at every checkpoint, and listener response only after the work has been shared.

Plan the review before the pilot begins

The review follows a simple order: compare the goal with the result, talk it through with the partner, decide the next adjustment, then choose whether to continue, change the form or finish. Finishing is described as a valuable outcome in its own right, so do not treat it as a failure.

Put the review meeting in both calendars on day one. Give it a fixed duration, such as an hour, and a date close enough to the end of the work that memories are fresh but far enough that listener responses or student feedback have time to arrive. A gap of one to two weeks after the final delivery works well.

MomentWhat happensWho attends
Day oneAgree goal, roles, deadline and review dateLeads on both sides
Week oneStart checkLeads and note-taker
MidpointMidpoint check and scope decisionLeads
Final daysFinal check, collect recordsLeads and note-taker
Review dateCompare, discuss, decide next stepEveryone involved

A sample plan: one online class in five weeks

This is an illustration of how the pieces fit, written as a template and not as a record of any real project. Imagine a music school that wants to try one online vocal class led from Japan, with its own students joining from home.

WeekWorkCheckpoint
1Agree the goal, class topic, roles, class date and review date; share the school's one-page profileStart check at the end of the week
2Choose the students; confirm the time zone conversion for the class; send a short guide to familiesNone; replies only
3Dry run call; finalize the lesson outline; prepare a feedback formMidpoint check after the dry run
4Hold the class; collect feedback the same dayFinal check the day after
5Gather feedback, fill in the time and cost table, prepare the review notesReview meeting booked for the following week

The plan has one goal, five weeks, three checkpoints and a review date. Everything else is detail. You can replace "online class" with "co-written song" or "joint showcase" and keep the shape: a start, a middle, an end and a review, each with a date.

A good habit is to write the plan on a single page and send it to the partner for comments before work begins. Differences between the two sides' expectations surface quickly when both are looking at the same dates.

Questions to ask your partner about dates

  • Which weeks are busiest on your side, and which are quiet?
  • Who must approve the plan, and how long does approval usually take?
  • What is the latest date by which you need the final material?
  • Is there a date that, if missed, would make the pilot pointless, such as a school term or an event?

Signs that your pilot is the wrong length

Look at the way the work feels. If you reach the midpoint and have nothing to show, the window is probably too short or the goal too large; reduce the goal before extending the dates. If you finish in half the time and spend the rest waiting, the window was too long, and the next pilot can be shorter or a little more ambitious.

Either way, the information is useful. Write down the actual length of each phase, and use it for your next plan. After one pilot, your estimates will be far better than any rule of thumb in an article.

If you are not sure which length fits your idea, bring your goal and your calendar to the first online meeting with the partnership desk. They can help you shape a pilot that is small enough to finish and clear enough to judge.

Discuss your pilot timeline with the Global Music Partnership desk

FAQ

Can a pilot be extended?

If both sides agree at a checkpoint, a small extension is possible. Record the reason and the new date, and keep the goal the same.

Is a shorter pilot always better?

No. Choose the shortest period that lets you reach and judge your goal. A window that is too short leaves no evidence to review.

When should the review meeting happen?

Fix the date at the start, typically one to two weeks after the final delivery, so feedback has time to arrive.