Pilot wrap-up
What to Save When a Pilot Ends: A Simple Project Archive
When a pilot ends, the most valuable things are easy to lose: why you chose what you chose, and what you learned. Here is what to keep, and how to keep it tidy.
When a small music pilot with a partner in Japan ends, save five things in one folder: the original goal and roles, the decisions you made along the way, the finished work and its source files, the log of time, cost, problems and successes, and a one-page lesson note written together with your partner. Together they let you hold a calm review, start a second step quickly, or close the project cleanly and still keep everything you learned.
Why an archive is worth an afternoon
A pilot is short by design. It has one goal, such as one co-written song, one online class or one joint showcase, and a clear end. The pilot guide on the Global Music Partnership site suggests a review in a set order: compare the goal with the result, look back with your partner, decide the next adjustment, and then choose whether to continue, change the form or stop. Every step in that order depends on having the facts in front of you. An archive is simply the place where those facts wait.
It also protects your team from forgetting. People change roles, calendars fill, and a project that felt vivid in October is hazy by March. A tidy archive means that the person who picks up the second step, who may not have been in the first, can understand the whole story in a short reading.
The five things to save
1. The starting page: goal, roles and deadline
Before a pilot begins, the two sides settle the goal, the roles, the deadline and the way they will look back. Save that page exactly as agreed, with its date. It is the yardstick for the review, and it shows how the plan stood before any changes.
2. The decisions, in order
Keep a list of the decisions that changed anything: a date that moved, a deliverable that shrank, a role that switched hands. Give each a date and one sentence of reason. This is the most useful and most neglected item in any archive. Without it, the final result may look odd to someone who was not there, and the team may reopen questions that were already settled.
3. The work itself and its source files
Save the finished piece, whether that is a song, a recording of a class or a video of a showcase, together with the files needed to rebuild it: lyric sheets, chord charts, lead sheets, session notes and the versions that came before the last one. Label each file with a date and a version number so that the final one cannot be confused with a draft. Credits and any agreements on rights for each work belong beside the files, because those are confirmed per work and recorded in writing.
4. The four-line log
The pilot guide on the site describes the records worth keeping: how many exchanges took place, how much time and money were spent, what problems appeared, and what succeeded. Save this log whole. It turns the review from opinion into evidence, and it is the best planning aid for a second step because it shows what the first one truly cost.
5. The lesson note
Write one page together with your partner, ideally at the review meeting. List what worked, what you would change, and what you would try next. Add the decision you took: continue, adjust or end. The guide says that ending a pilot is a valuable result too, and a lesson note makes sure that result is recorded clearly rather than remembered vaguely.
A folder layout that stays readable
A simple structure works better than a clever one. Use numbered folders so that they sort in the order a newcomer would read them.
| Folder | What goes in it | Who keeps it |
|---|---|---|
| 01 Plan | Goal page, role sheet, dates, contact names | Both sides, same copy |
| 02 Decisions | Dated decision list, meeting recaps | The pilot lead on each side |
| 03 Work | Final files, earlier versions, lyric and chord sheets, credits | The side that produced them, with a shared copy |
| 04 Log | Time, cost, problems and successes | Whoever kept the log |
| 05 Review | Lesson note, review agenda, the decision on what comes next | Both sides |
Name files in a way that works in both languages. Plain letters, dates written as year, month, day, and short words keep file names readable on any system. If a file holds Japanese text, say so in the name or in a short note, so that nobody wonders why a document looks unfamiliar.
A short archive checklist
- Is the starting page saved with its original date?
- Does every change of plan appear in the decision list with a reason?
- Are final files labelled as final, and earlier versions kept apart?
- Are credits written beside the work they belong to?
- Does the log show time, cost, problems and successes in one place?
- Has the lesson note been read by both sides?
- Does the folder have a named owner and a place where both teams can reach it?
Run through this list on the day of the review. If any answer is no, fix it that week, while memories are fresh. A gap that is closed in a day costs a few minutes; the same gap found six months later may cost the answer itself.
Using the archive in the review meeting
Bring the archive to the meeting and use it as the agenda. Start with the starting page and ask whether the goal was met. Move to the decision list and ask whether any change should be remembered for next time. Open the log and compare the effort with the result. Finish with the lesson note and the choice of what comes next.
Because both sides have looked at the same pages, the meeting stays focused on the work. There is less room for each side to defend a private memory, and more room for the kind of open, appreciative talk that makes a partnership last. If the choice is to continue, the archive gives you a list of what to repeat. If the choice is to adjust, it shows exactly where. If the choice is to end, it lets you close with a clear conscience and a record that you can both be proud of.
Keeping the archive useful over time
Give the folder an owner, and set a date, perhaps three months after the pilot, to reopen it and add anything new: a reaction from a listener, a follow-up idea, a contact. Small additions keep the archive alive, and they remind both teams that the pilot was the first step in a relationship rather than a closed chapter.
If your organisation has a manager or committee who approved the pilot, the archive also makes their reading easy. A one-page summary on top, followed by the five parts, is enough for a decision-maker to see what was tried, what it cost and what you propose to do next. That helps a good pilot grow into a wider agreement at a pace that everyone is comfortable with.
Four common archive mistakes and their easy fixes
Saving only the final file. A finished song without its lyric sheet, chord chart and notes is hard to rebuild. Keep the supporting files in the same place, and the final version will remain usable for years.
Keeping separate archives on each side. If each company holds a different version of the story, the review begins with a comparison of folders. Agree on one shared copy of the plan, decisions and lesson note, and let each side keep its own working files as it likes.
Leaving out the small failures. A missed call, a file that would not open or a misunderstanding over a date can feel embarrassing to record. In fact these notes are the most valuable pages for the next project, because they show exactly where a process needs a little more care. Write them without blame and in plain words.
Writing the lesson note alone. A note from one side shows one view. When both teams contribute a line or two, the note becomes a shared statement that either side can quote with confidence to their own management.
A last tip: write a one-paragraph cover note at the top of the folder that says what the pilot was, when it ran, who led it on each side, and where the final work lives. Anyone who opens the folder, even years later, will know within a minute whether it holds what they need. Add the date you last updated it, and the folder will quietly stay trustworthy.
Start a pilot that is easy to wrap up
The partnership window works with labels, music companies, schools and festival organisers, in English and Japanese, and the process begins with a message about your company, country, time zone, goal and preferred language. If you are ready to plan a small, well-defined pilot, you can reach the window at global-music-partnership.jp.