Communication

After the First Call: A Recap Email to Your Japan Partner

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

The first online meeting is a good moment, and a short recap email makes it last. Here is a template and a routine for turning a good conversation into clear next steps.

After your first online meeting with a music partner in Japan, send a short written recap within a day or two. Keep it to four parts: what you talked about, what you both agreed, who will do what next, and when you will speak again. A recap of this kind takes ten minutes to write and removes the small misunderstandings that grow when two teams work in different languages and time zones.

In the partnership process, the first online meeting is the second of five steps. It follows your first contact and it leads into the conversation about rights and goals. The recap is the bridge between those steps. This guide explains why it matters, what to put in it, and how to write it so that it is easy to read in English or Japanese.

Why a recap helps more than you expect

A good first meeting feels clear while it is happening. People nod, they say they understand, and the ideas seem to line up. A day later, each person remembers a slightly different version. One colleague recalls a deadline, another recalls a different one. A goal that sounded settled turns out to have been two goals described in similar words.

When you work across languages, this effect is stronger. People speak at different speeds, use different expressions for the same idea, and sometimes agree politely when they have not fully followed. A written recap gives everyone a calm second look at the same words. It lets your partner confirm what is right, correct what is not, and add the details they thought of afterward.

It also prepares the ground for the written proposal. After the first online meeting, the partnership team sends a written proposal with costs and a payment schedule. If your recap already states the goal, the roles and the possible dates, the proposal can be built on a shared understanding rather than on guesses.

The four parts of a good recap

Keep the structure the same every time. A predictable layout lets a busy reader find the part they need in seconds.

PartWhat it containsExample of a clear line
DiscussedThe topics that came up, in a few bulletsWe talked about a co-written song as a first project and about the preferred language for lyrics
AgreedOnly the points both sides said yes toWe will hold the next meeting in English, with a Japanese summary afterward
ActionsOne owner and one date for each taskOur side will send three reference songs before the next meeting
Next meetingDate, time with both time zones, and a topicA meeting to review rights and goals, with the time written in both zones

The line between discussed and agreed is the most useful one to keep clean. Discussed items are ideas that may still change. Agreed items are the ones you can rely on. When you keep them separate, your partner can see at once what is firm and what is still open.

A template you can copy

Here is a version you can paste into an email and fill in. Adjust the wording to your own voice, but keep the order.

  1. Greeting and thanks: thank the team for their time and mention one thing you valued in the conversation.
  2. Discussed: three to five bullet points, each in a single short sentence.
  3. Agreed: the decisions made, with plain verbs such as will send, will review and will confirm.
  4. Actions: a list with the owner and the date next to each task.
  5. Open questions: items still to decide, each phrased as a question.
  6. Next meeting: the proposed date and time in both time zones, plus the topic.
  7. Closing: invite corrections, for example by asking your partner to tell you if anything looks different from what they remember.

That closing invitation is worth keeping. It tells your partner that the recap is a shared document, not a verdict, and it makes it comfortable for them to add or fix details.

To see the pattern in action, imagine a recap for a label that met the partnership team to explore a first project. The Discussed section would hold a line about a co-written song as a pilot and a line about which language the lyrics should use. The Agreed section would say that the next meeting will be in English and that both sides will list the rights for the songs involved. The Actions section would name one person on your side who sends three reference songs by a stated date, and one person on the partner side who sends a draft schedule. The Next meeting section would give the date with both time zones. Four short blocks, and the whole conversation is captured.

When something was left open, say so cheerfully and give it a home. A line such as one question remains, which is the date for the pilot review, and we will settle it at the next meeting, shows progress rather than doubt. Open questions are a normal and healthy part of a young partnership, and naming them keeps them from being forgotten.

Writing for a bilingual reader

Your recap may be read by someone whose first language is Japanese, or forwarded to colleagues who use a translation tool. A few habits make it easy to read in either case.

  • Use short sentences with one idea each. Long chains of clauses are hard to translate cleanly.
  • Prefer common words to idioms. A phrase such as moving forward is clear; a sports metaphor may not be.
  • Write dates with the month as a word, so that a day-month order cannot be confused with month-day.
  • State the time zone each time you mention a time.
  • Offer to continue in the partner's preferred language. The partnership team works in English and Japanese, so you can ask which they would like for the written record.

If you are comfortable in both languages, you can add a short Japanese summary at the end. If you are not, do not worry. Clear English with a simple layout is already a good basis for a shared record.

Connecting the recap to the five steps

The recap works best when it points toward the next step in the process. After the first online meeting, the next conversation is about rights and goals: who holds which rights, and what each organization will do. Your recap can prepare for it by listing what you plan to bring.

  • A short description of the material involved, such as the songs, the recordings or the course content.
  • A plain note on who holds the rights to each item.
  • The goal you would like the first project to reach.
  • The people on your team who will take part.

From there, the path continues to a small pilot. The pilot is short, with a fixed end and a single goal, such as one co-written song, one online lesson or one joint showcase. Before it begins, both sides decide the goal, the roles, the deadline and the method of review. A recap that already holds early versions of these four items saves time later.

Common mistakes and quick fixes

Most recap problems are small, and each has an easy fix.

  1. The email is too long. Cut it back to one screen. If a topic needs more space, move it to an attachment and link to it in one line.
  2. Decisions and ideas are mixed together. Split them into discussed and agreed, as in the table above.
  3. Tasks have no owner. Give every action one name, even if the whole team will help.
  4. Dates are vague. Replace next week with a calendar date and a time in both zones.
  5. The email is sent too late. Aim to send it while the meeting is still fresh, ideally the same day or the next.
  6. The tone is too formal or too stiff. Friendly and direct works well, and a warm thank-you opens the door to a good working relationship.

Keep a running record

After the first recap, keep the habit. A recap after each meeting builds a record that you can use later in many ways. It supports the one-page report you may need to write for your management, it feeds into the decision log of the project, and it gives you a clear base when it is time to review the pilot together.

Store the recaps in one folder with a simple naming rule, such as the date followed by the meeting topic. If your team uses a shared drive, put the folder there and tell your partner where to find the latest version. A tidy record shows care for the partnership, and it reflects the same attention to detail that makes music projects run smoothly.

When you are ready to take the first step toward a partnership with Japan, you can begin with your first message on global-music-partnership.jp, and after your first online meeting, a recap like the one in this guide will keep everyone moving in the same direction.

FAQ

How soon should I send a recap?

Send it the same day or the next day, while both sides remember the conversation clearly. A short, well-organized email is better than a long one sent late.

Should the recap be in English or Japanese?

The partnership team works in English and Japanese. Ask which language your partner prefers for written records, and keep the sentences short either way.

What if my partner remembers the meeting differently?

That is exactly what a recap is for. Invite corrections in your closing line, then update the record and send the corrected version.