Co-writing practice

A Contribution Log for a Co-Write: Who Did What, Day by Day

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

Ideas move fast in a co-writing session, and memory fades faster. A one-page daily log keeps the story of the song clear for everyone.

A contribution log is a plain page, filled in during or right after each session, that notes what was brought to the song and by whom: a melody idea, a title, a chord change, a line of lyric, a translation choice. Keep it short and keep it kind. Its purpose is to make the last-day conversation about credits and next steps easy, because everyone can see how the song actually grew. It is a working memory aid, and the formal agreement on rights and credits is a separate written step that both companies settle in advance.

Why a log helps in a two-night camp

The co-writing camp described on the Global Music Partnership site runs over two nights and three days. On the first day the team chooses a theme, a lyric language and a target listener. On the second day the morning goes to melody and chorus at the grand piano, the afternoon to lyrics, and the evening to a run-through in the lounge. On the third day the team records a demo vocal and, before the 10:00 check-out, agrees on credits, distribution and the next step.

That is a lot of creative movement in a short time. A phrase hummed over breakfast may end up as the hook by evening, and by the third morning nobody is sure who first sang it. The log catches these moments while they are fresh. It also protects the mood of the camp: when everybody can read the same page, nobody needs to defend their memory against someone else's.

What the log is and is not

It helps to be clear about the log's job so that it stays light.

  • It is a shared diary of the song's growth, written in plain words, that supports a friendly discussion at the end.
  • It is a place to note the reason for a choice, such as "we moved the key up because the chorus sat too low for the demo singer".
  • It is not a contract. Rights and credits for each work are confirmed with the people who hold them and recorded in a written agreement, and the camp article on the site says that this written agreement should be settled before the camp begins.
  • It is not a scoreboard. Songs are made by trading small ideas, and a good log shows the trade rather than a count.

The page layout

One table per day is enough. Every row is a moment in the session, and the columns stay the same from day to day so the page is quick to fill.

TimeWhat happenedWho brought itLanguageStatus
MorningOpening melody for the chorus found at the pianoName or "both"WordlessKeep
Late morningTitle idea in English, with a Japanese alternative notedNameEnglish / JapaneseTry
AfternoonFirst verse lines drafted; one line rewritten after discussionName and nameBothKeep
EveningRun-through; bridge removed to keep the song shortGroup decisionWordlessDecided

The "Status" column is the quiet hero. Marking items as keep, try, drop or decided lets you reread the log in the evening and see in thirty seconds where the song stands. The "Language" column matters for a team working in English and Japanese, because the choice of lyric language is one of the three decisions the camp begins with.

Who writes it and when

Name one scribe per day, and rotate the role. A person who is not leading the melody on that day is often a good choice, since they can listen without interrupting their own work. Set a short pause, perhaps after each major step, for the scribe to read aloud the last two or three lines. Reading aloud turns the log into a quick check: "Is that how you remember it?" A small correction made on the spot costs a few seconds. The same correction made on the final morning can cost a mood.

If part of your team joins online, share the page on a screen or in a shared document so that everyone sees the same lines at the same time. Keep the writing style neutral and specific. "Chorus melody, descending, found at the piano" is better than "great idea from the left side of the room". Specific notes remain useful after the camp, when someone needs to rebuild the arrangement from the demo.

Using the log on the last morning

When the last morning arrives, the log turns from a diary into a tool. Here is a calm way to use it before the bags are packed.

  1. Read the three days from top to bottom. Take turns reading so that the whole team hears the story in order.
  2. Mark the surprises. Ask whether any entry looks different from what a person remembers. Fix it together.
  3. Turn the log into a credit draft. Write names against the parts of the song, such as melody, lyrics, arrangement and translation, as a proposal for discussion.
  4. Compare the draft with the written agreement. If the agreement made before the camp already covers the point, follow it. If a new question appears, note it as a topic for the people who confirm rights.
  5. Write the next step with a date. A song that leaves the camp with an owner for the next task and a date is far more likely to be finished.

Keeping the tone generous

A log can feel formal if it is introduced badly. Introduce it as a gift to the future song: "We want to remember how this came to be." Many co-writers enjoy rereading it later, because it preserves small moments of humour and discovery that would otherwise be lost.

The producer on the Japan side, TARNAR, writes and produces the music, and the camp is built around listening to each other's ideas. A log supports that spirit. When every contribution is noted with a short reason, the team learns what each person tends to bring: one may find melodies, another may find the turn of phrase that makes the lyric land. That knowledge guides how roles are shared in later projects.

It also helps to log decisions about what was left out. A note such as "second verse cut to keep the song short" prevents the same debate from returning in the next session. And if an idea was set aside rather than dropped, write where it is stored, so that it can be found when the right song arrives.

After the camp

Save the log with the demo and any reference files, in the shared folder that your team uses for the project. When the song moves to the next stage, such as polishing the arrangement or preparing a release, the log tells new people how the work arrived at its current form. If someone on your team was not at the camp, a five-minute read gives them the whole picture.

Finally, bring the log to the first check-in after the camp. It gives you a concrete starting point for agreeing the next step, and it shows your partner that you value a clear, shared record. That kind of care is how a first co-write becomes the beginning of a longer partnership.

Three habits that keep the log honest

First, write the entry as close to the moment as you can. A note made within a few minutes is usually accurate; a note made at night tends to flatter whoever is writing. Second, record shared moments as shared. When two people reached a line together, write both names, or write "both", rather than trying to divide something that cannot be divided. Third, let anyone add a comment. If a teammate feels an entry is incomplete, a comment beside it is a gentle way to say so, and it keeps the conversation on the page instead of in the corridor.

Photographs of a whiteboard or a lead sheet can be attached to the matching row. A picture of the chord chart on the piano stand on day two often answers a question that words cannot, and it costs only a few seconds to take.

A short sample of the final summary

At the end of day three, many teams find it helpful to condense the log into five lines that can travel with the demo: the working title, the lyric language, the parts of the song and who shaped each one, the open questions, and the next step with a date. The summary is imagined here as a format, not a real song record, but it shows how little is needed. Five lines read in one minute give any newcomer the full picture, and they give the people who handle rights a clear starting point for their own conversation.

Plan a co-writing camp with us

The partnership window welcomes labels, music companies, schools and festival organisers who want to start with a small, well-defined project. To talk about a co-writing camp in Atami, send your goals, your team and your preferred language through the form or LINE at global-music-partnership.jp.