Online release
A Release-Day Run Sheet for a Limited-Time Online Release
A limited-time online release is a small, friendly way to reach listeners in Japan. A one-page run sheet keeps both sides calm on the day.
The easiest release day is one where everybody has read the same one-page sheet. Write down the go-live time in both time zones, name one person on each side who presses the button and one who watches, list the exact links and files, and agree what you will record as the day goes by. A limited-time online release is one of the small pilot formats the Japan partnership window describes, and a clear run sheet is what turns it from a nice idea into a smooth day.
Why a limited-time release suits a first pilot
The partnership window suggests starting small: a short, clearly bounded project with a single goal, agreed before it begins. A song, a video or a short set released online for a fixed period fits that advice well. It has a visible start and a visible end, it does not require anyone to travel, and it produces something you can measure honestly afterwards.
Because the release is time-limited, listeners understand it as a special moment, and your team can concentrate its energy. When the period ends, you sit down with your partner, compare what happened with what you hoped for, and decide whether to continue, adjust or close. That review is easier when the day itself was well documented, which is exactly what a run sheet does.
Before release day: lock the facts
Two or three days ahead, confirm the following with your partner in writing. Each item below takes a few minutes, and each one prevents a mix-up.
| Item | Decide | Example wording |
|---|---|---|
| Go-live moment | Date and time in both time zones | Friday 10:00 in Tokyo, which is Thursday evening for the sender |
| Window length | When the release goes offline | Available for a fixed number of days, then taken down together |
| Where it lives | The exact page or channel on each side | One main link, plus one link per partner channel |
| Title and credits | Final spelling in English and Japanese | Names, roles and song title written out once and reused everywhere |
| Who holds what | Which rights each side holds for each work | Recorded in the agreement before the release |
| Goal and measures | Up to three success measures | Listener reactions, ease of working together, time and cost |
The window records the question of who holds which rights for each work and puts the answer in the agreement, so settle that line first. Everything else on the sheet depends on it, because it tells you which channels may carry the release and which version of the credits is correct.
Use a shared document that both sides can edit, and put the date of the last change at the top. When two people read two slightly different versions of a plan, small mistakes grow quickly.
The hour-by-hour sheet
Here is a template for a single release day. Adjust the clock times, but keep the order. The labels "Side A" and "Side B" stand for you and your partner.
- Two hours before go-live: final check. Side A opens the final files and listens to the full track once through headphones. Side B opens the Japanese page and checks the title, credits and artwork. Both reply "ready" in the shared chat.
- One hour before: links and previews. Each side tests every link from a phone and from a laptop. Look at how the link preview appears when pasted into a message, since that is the first thing most listeners see.
- Thirty minutes before: scheduled posts. Confirm that any scheduled posts carry the right time zone. A post set to the wrong zone is an easy slip, and it takes seconds to check.
- Go-live: one press, one confirmation. The person responsible on the lead side publishes. The partner confirms in the chat with a screenshot or the live link. Both write down the exact time.
- First thirty minutes: watch and welcome. One person on each side watches the page, replies to early comments and thanks the first listeners. Answer in the listener's language when you can, and keep replies short and warm.
- Mid-day: a quick pulse check. Share two or three simple observations in the chat: where the first comments came from and which line or moment people mention. Keep it light.
- End of day: a wrap-up note. Each side writes three lines in the shared document: what went well, what was confusing, what to do differently next time.
Print the sheet or keep it open on a second screen. Having it visible lets the team stop asking each other what happens next.
Roles: keep it to four jobs
A small release does not need a committee. Four roles cover almost everything, and one person can hold more than one if the team is small.
- Publisher. Presses the button at go-live. Has the logins ready and tested the day before.
- Watcher. Monitors the page, comments and messages during the first hours.
- Translator or language lead. Handles replies in the second language, and checks that titles and credits read naturally. Where possible, one person on each side covers their own language.
- Note taker. Records the time, the problems and the good surprises. This person feeds the review meeting later.
Write the names next to the roles in the run sheet. If someone is unavailable on the day, agree a stand-in the day before. The partnership window recommends naming roles and deadlines before a pilot starts, and the run sheet is the place where that advice becomes concrete.
Time zones and timing the day well
Japan does not use daylight saving time, so the offset to Japan changes with your own clock changes. Check the difference on the actual day rather than relying on last month's figure, and write both times side by side in the sheet. A tool that shows two clocks is useful for the whole team.
Choose a go-live time that sits in a comfortable part of the day for the side that has to do the most watching. Often the partner who will answer comments in the first hour is the one whose morning or early evening should be protected. Share the plan with your listeners too: a short line such as "available for a limited time from Friday" in both languages gives everyone a clear expectation and adds a pleasant touch of occasion.
Look at the Japanese calendar before you fix the date. Public holidays and long breaks change when people are online, and the partnership window has an article on choosing pilot dates around Japanese holidays and seasons that is worth reading first.
What to record on the day
The window's own guidance on evaluating a pilot recommends recording a few simple things throughout: how many exchanges took place, how much time and money went in, and what problems and successes appeared. Release day is the richest moment for that record, so give it a page of its own.
- Timeline. Planned and actual go-live time, plus any delay and the reason for it.
- Exchanges. The number of messages and calls between you and your partner on the day.
- Time and cost. Hours spent by each person and any small costs, such as a promotion or a translation.
- Listener reactions. A short list of comments, in the original language with a one-line translation. Quote only what you are free to share.
- Problems. What broke or confused people, with the fix you applied.
- Good surprises. Anything better than expected, written down while it is fresh.
Keep numbers simple and honest. A few clear facts are more valuable than a large spreadsheet that nobody reads.
After the window closes
When the agreed period ends, take the release down on both sides at the planned time and post a short thank-you. Then schedule the review meeting while memories are fresh, ideally within a few days.
At the meeting, compare your three success measures with what actually happened. The window describes a sensible order: compare goals with results, talk it through with your partner, agree the next adjustments, then decide whether to continue, change the form or stop. Stopping is treated as a valuable result in its own right, because it tells both sides something true. If you decide to continue, the next step is an agreement that confirms the terms before you scale up.
A tidy run sheet, a short record and a friendly review make a limited-time release a solid foundation for whatever comes next, whether that is a second song, a joint class or a shared stage. When you are ready to plan yours, start a conversation with Global Music Partnership and bring your goal, your time zone and the work you would like to share.
FAQ
How long should a limited-time online release stay up?
Choose a short, fixed period that both sides write into the plan before release day, and take it down together at the agreed time. A short period keeps the pilot focused and easy to review.
Who should press the publish button?
Name one publisher on the lead side and one person on the partner side who confirms. Agree this in the run sheet so nobody has to guess on the day.
What is an easy release-day slip to avoid?
A scheduled post set to the wrong time zone. Write the go-live time in both zones and have each side check it thirty minutes before.
What should we record during the release?
Record the timeline, the number of exchanges, the time and cost, listener reactions, problems and good surprises. These feed straight into the review meeting.