Project tools
A Decision Log for Your Music Project With Japan
When two teams work in different time zones, a shared decision log is the calmest way to remember what was agreed. Here is a simple version you can start today.
A decision log is a single shared page where each agreed point gets one line: what was decided, who decided it, when, and what happens next. For a music project with a partner in Japan, it is the easiest way to keep both teams aligned across time zones, because anyone can open the page at their own hour and see the current state without waiting for a reply.
The partnership process already moves in clear steps: contact, an online meeting, a conversation about rights and goals, a small pilot, and then an agreement that is signed before the work expands. A decision log follows those steps from start to finish. It gives the pilot a memory, and it makes the final agreement much easier to write, since the terms have already been written down along the way.
What goes in a decision log
Keep the log short enough that people really use it. One row per decision is enough, and a few columns cover everything that matters.
| Column | What to write | Example |
|---|---|---|
| Date | The day the decision was made, in a clear format | 12 March |
| Topic | A few words naming the subject | Lyric language |
| Decision | One sentence, written in plain words | The chorus will be in Japanese and the verses in English |
| Decided by | The people or roles who agreed | Both writers and the label contact |
| Next action | The task that follows, with an owner | Writer A drafts the Japanese chorus |
| Due | A date in both time zones | Friday, end of day in Tokyo |
| Status | Open, done or revisited | Open |
Resist the urge to add columns. Every extra field is a reason to skip an entry. If a decision needs more explanation, put it in a short note linked from the row.
Decisions worth logging
Teams sometimes worry that a log will slow down creative work. In practice it protects it. When the scope, the roles and the dates are written down, writers and singers can spend their energy on the music, and managers can answer questions from colleagues in one sentence by pointing to the page.
Not every remark needs a row. Log the decisions that would cause trouble if two people remembered them differently. A useful test is to ask whether the point affects the schedule, the money, the credits or the language of the work. If yes, log it.
Scope and goal
The single goal of the pilot, what counts as delivered and what is deliberately left for later. This is the entry people most often return to when a project starts to expand.
Roles and contacts
Who owns each task on each side, and who answers messages. Update it whenever someone joins or leaves the project.
Dates and time zones
Meeting times, deadlines and the review date, written in both time zones so nobody has to convert them in their head.
Rights and credits
Who holds which rights in each piece of work, and how credits will be written. Rights are confirmed work by work and recorded in the contract, so the log is the place to note which items are settled and which still need a signature.
Costs and payments
The written proposal that follows the first meeting sets out costs and payment timing. Log the date you received it, the date you replied and any changes agreed afterwards, so the paper trail is complete.
Set up the log in ten minutes
Any shared spreadsheet or document works. Choose the tool both teams can open without special accounts, and give it a name that includes the project and the word log. Then follow these steps.
- Create the table with the seven columns above and freeze the header row.
- Add the first three entries from your first online meeting: the goal, the contacts and the date of the next call.
- Name one person on each side as the keeper, who adds entries and checks them with the other side.
- Share the link in your project chat, and pin it so it is always easy to find.
- Put the log on the agenda of every meeting, and review the open items first.
When the structure is this light, the log does not feel like paperwork. It feels like a shared notebook, and over a few weeks it becomes the best summary of the project's history.
A weekly rhythm that fits two time zones
A log is only helpful when it is current. A short weekly rhythm keeps it alive without taking much time, and it fits the way a pilot is organized: short, focused and reviewed regularly.
| When | Who | What |
|---|---|---|
| After each call | Keeper of the side that hosted | Add new decisions the same day |
| Next morning | Keeper of the other side | Read the new rows and reply with a short confirmation or question |
| Midweek | Both keepers | Update the status of open actions |
| End of week | Trip or project lead | Read the open items and decide what needs attention |
The confirmation step is the heart of the habit. When one side writes and the other side confirms, a decision becomes a shared decision. A reply as short as "confirmed" is enough, and it closes the loop in a friendly way.
Using the log at the review and at the agreement
When the pilot ends, the log is the best preparation for the review. Read through it together and ask three questions. Which decisions worked well? Which ones were revisited more than once? Which open items still need an answer before we expand? The answers shape the next step, whether that means repeating the pilot, extending it or moving to a written agreement.
The agreement itself is signed before the work grows, and conditions, costs, dates and rights are checked at that stage. A log makes this stage easier, because each point has already been written, dated and confirmed. Your advisers can read the log in minutes and turn the settled points into contract language, while the open points become the agenda for the final conversation.
Keeping the log friendly
Share it generously too. Colleagues who join late, such as a new manager or a guest vocalist, can read the log and be fully informed in a few minutes, which saves both teams from repeating the same briefing again and again.
Use neutral, positive wording. Write "we will" instead of "you must," and thank people for confirmations. A decision log is a tool for trust, and the tone of the entries sets the tone of the partnership.
A sample log for a short song pilot
Here is how a log might look in the first weeks of a one-song pilot. The entries are an illustration of the style, to be adapted to your own project.
| Week | Topic | Decision | Next action |
|---|---|---|---|
| 1 | Goal | One co-written song, demo only, reviewed in four weeks | Both keepers confirm in writing |
| 1 | Contacts | One contact per side, replies within one working day | Share phone or chat details |
| 1 | Language | Messages in English, lyric discussion in both languages | Bridge person named |
| 2 | Reference songs | Each side sends three songs before the first session | Upload to the shared folder |
| 2 | Rights | Rights holders listed for each contributor | Add to the credit sheet |
| 3 | Session | Two online sessions at an overlapping hour | Book both in the calendar |
| 4 | Delivery | Demo shared as a dated file | Schedule the review call |
| 4 | Review | Next step chosen from repeat, extend or agreement | Owner writes the proposal request |
Read the sample from top to bottom and you can see the whole project. That is exactly the power of a log: a stranger could pick it up and understand what the two teams have agreed in less than two minutes.
Mistakes to avoid
- Logging opinions instead of decisions. Keep ideas in the notes and put only agreed points in the log.
- Writing vague dates. "Next week" means different days in different countries, so write the day and the zone.
- Letting one side own it alone. The confirmation step makes it a shared record.
- Editing old rows silently. If a decision changes, add a new row that says it was revisited and link it to the earlier one.
- Waiting for the end to write it up. A log kept day by day takes minutes, while a log rebuilt from memory takes hours.
Begin your log with the first message
You can start the log before the first meeting. Write down your goal, your time zone, your preferred language and the state of your rights, then send the same details to the partnership team. These are exactly the items the first message should contain, and they will become the first rows in your shared page. Begin at global-music-partnership.jp.
FAQ
What tool should we use for the log?
Any shared document or spreadsheet that both teams can open easily. Simple is best.
How long should each entry be?
One sentence for the decision, plus an owner and a date. Longer notes can be linked.
Who should keep the log?
One person on each side, so entries are added and confirmed by both.
Does the log replace the agreement?
No. It is the record that makes the agreement easier to write, and the signed agreement remains the formal document.