Music Practice Log Template: What Students Should Track After Every Session

Most music practice logs fail because they try to do too much. A long form with twelve fields, a free-text journal that asks for paragraphs of reflection, or a printable template with empty boxes labelled "thoughts" — these get filled in for the first two weeks and then quietly abandoned. The log that survives is the one short enough to complete in ninety seconds and useful enough to actually help the next session. This article gives that template — six fields, one card, easy to write and easy to read — along with a walkthrough of why each field matters and how to choose between paper, spreadsheet, and digital formats.

The audience is any music student, adult learner, or serious hobbyist who wants the practice log they keep to actually do something for them. The Pract.is article on how to use a practice log without turning it into homework covers the broader philosophy; this article is the practical template — what to write down, why those six fields, and how to make the log survive past the second week.

The six fields a useful log entry contains

The template below works for any instrument, any level, and any practice context. It is intentionally short. Each field answers one question the next session needs answered. Anything longer than a sentence per field is almost always too much.

The example above shows what a finished log looks like in practice. Six lines. None of them long. Every line answers a question the next session would otherwise have to figure out from memory. The rust-coloured sixth field is the most important — and the one most students skip when their log gets tired by week three.

Field 1 — Piece

The first field is the piece or exercise you worked on. Two notes: be specific (Bach Invention No. 8, not "Bach"), and if a single session covered multiple pieces, log them as separate entries rather than one entry with three pieces inside. The point is to have a per-piece trail you can scan later. A session note that says "worked on three pieces" produces no useful comparison across weeks; three separate entries do.

For students who work on a sub-section rather than a whole piece, narrow this field further: "Bach Invention No. 8, bars 9-12" is clearer than "Bach Invention No. 8" when most of the session went to those four bars. The Pract.is article on how to practise when you are learning more than one piece covers the multi-piece case in detail.

Field 2 — Goal

The second field is the specific goal you set for the session — what you wanted to be different by the end. "Practise Bach" is not a goal. "Bars 9-12 hands together at quarter = 76" is a goal. "Memorise the exposition" is a goal. "Run the whole piece three times to find the worst section" is a goal.

The reason this field matters is that a written goal at the start of the session focuses the practice. Without it, sessions drift toward whatever feels easy. With it, the session has a target to test itself against — and the rest of the log fields make more sense because they describe what happened in pursuit of that target. The Pract.is article on how to set practice goals that actually work for adult hobbyists covers the goal-setting side.

Field 3 — Time

The third field is the total time spent. This is the simplest field and the one most likely to get over-weighted. Time is not progress; it is just context. A useful log records time the way a runner records distance — to anchor the rest of the data, not to celebrate the number. The Pract.is article on why am I not improving at piano covers why minutes alone are an unreliable signal of improvement.

If you find yourself paying more attention to this field than to the goal or the next-step field, the log has tipped into productivity tracking instead of practice tracking. The fix is simply to read the time as one line of context and move on.

Field 4 — Difficult section

The fourth field names the part of the session that did not go well. The hardest bar. The passage that broke down at tempo. The transition that kept catching you out. Be specific: "bar 11, left-hand crossing" is more useful than "the hard bit." This field is the early-warning signal of stalled progress — if the same difficult section appears week after week with no movement, the practice on it is not working and the method needs to change.

Some students find this field uncomfortable to fill in because it feels like admitting failure. It is not. It is admitting honesty. A log full of "everything went great" is a log that produces no useful planning for next time. The Pract.is article on why you keep making the same mistakes in music practice covers what to do about recurring difficult sections.

Field 5 — What improved

The fifth field names one specific thing that got better. Even on a hard day, something usually improves — three clean repetitions where there used to be two, a fingering that started feeling natural, a tempo target reached for the first time. The discipline of finding one improvement per session matters more than the size of the improvement; the field becomes a record of forward motion, however small, that compounds across weeks.

If you cannot identify anything that improved, write that. "Nothing measurable improved today — the passage stayed at the same level it was last session." That is honest data. It usually means the next session needs a different approach to the same problem, not more of the same work.

Field 6 — What to do next

The sixth field — the rust-coloured one — is the most important and the most often skipped. It is the instruction the next session needs to know. Where to start. What tempo to try. What to add. What to test. A short sentence: "Same loop at quarter = 84, then add the lead-in from bar 8."

The reason this field matters more than the others is that tomorrow's session begins by reading it. Without it, tomorrow's session begins with "what was I working on?" — and the first ten minutes go to reconstructing yesterday's state instead of building on it. With it, the practice is continuous across days rather than restarting daily. The Pract.is article on how to review a practice session so tomorrow goes better covers the underlying habit; this single field is the operational expression of it.

"The \"what to do next\" line is the only field tomorrow\u2019s practice cannot do without. Skip it and the next session begins with reconstruction instead of building."

Paper, spreadsheet, or digital — choosing the format

The template works in any format. The choice between paper, spreadsheet, and a dedicated digital tool is a question of which format makes the log easiest to keep up and easiest to read across time.

Paper. A small notebook with one entry per page, dated. Strengths: zero friction at the moment of writing, physical record you can flip through, no batteries. Weaknesses: hard to search across weeks ("when did I last work on the Bach?"), the notebook gets lost, the trail across months requires manually paging through dozens of entries to spot patterns. Paper is best for students who already keep a notebook habit and who do most of their planning visually rather than by search.

Spreadsheet. A Google Sheet or Excel file with one row per session and six columns. Strengths: searchable across all entries, columns sortable by piece or date, easy to share with a teacher. Weaknesses: a spreadsheet is a clumsy place to write at the end of a session, the rows blur together visually, recordings or any attachments cannot live in the same place. Spreadsheets work for students who are spreadsheet-fluent and who value the search and filter capability more than the writing experience.

Digital practice tracker. A dedicated tool like Practis that is built around the per-session log idea. Strengths: writing the entry takes seconds because the structure is already there, the trail across weeks is visible without manual scrolling, recordings and notes can live alongside the log entry, and a teacher can read what you wrote if you choose to share. Weaknesses: requires opening an app at the end of the session, which is one more step than picking up a pen. Digital tools are best for students who want the log to remain useful past month two and who value the cumulative view of their own progress more than the act of physically writing.

The decision between the three is less important than picking one and using it consistently. A paper log that gets filled in every session is more useful than a digital log abandoned by week three. The Pract.is article on digital practice logs vs paper journals for music students covers this comparison in more detail.

A week of log entries, in shape

One way to see what the template actually does is to look at a week of entries side by side. The shape is consistent: same six fields, different content per session, and the trail across the seven days reveals patterns that any single entry could not show.

The pattern across the seven entries shows the week's work clearly. The same difficult section appeared on Monday and Tuesday — and the Wednesday entry shows it had eased. Thursday's tempo push exposed a new variant of the problem; Friday dropped back and rebuilt. By Sunday, the passage was stable enough to mark as done. None of this would be visible from the time totals alone. It is the per-session log that produces the pattern.

Common mistakes when logging

A few specific patterns recur and are worth flagging.

The first is writing the log before the session. The fields cannot be filled in until the session is done; pre-filling them turns the log into a wish list rather than a record. The discipline is to write the log at the end, no exceptions.

The second is writing everything in field 5. Some students treat "what improved" as a journal and write paragraphs. The field works better as a single observation: one specific thing that got better. Paragraph reflections belong in a separate weekly review, not in the per-session log.

The third is skipping the next-step field. This is the field that connects today's session to tomorrow's. Skipping it is the single most common reason practice logs stop being useful — they become history without producing planning.

The fourth is not reading the log before the next session. A log is only as useful as the rate at which it is read. The discipline is thirty seconds at the start of each session looking at yesterday's entry. Without that, the log is producing data that nobody is using.

The fifth is over-engineering the template. Six fields. The temptation to add a seventh ("mood"), an eighth ("energy"), or a ninth ("tempo target reached?") almost always leads to a heavier template that students abandon faster. Six fields, ninety seconds, every session.

What changes when the log is consistent

Students who maintain a six-field log across a month report several specific things. The first ten minutes of each session become productive instead of reconstructive — the next-step field tells them where to start. Recurring difficult sections become visible across weeks, which prompts changing the method rather than continuing to grind. Progress that is happening but feels invisible becomes legible because the trail of small improvements is now in writing. Weekly reviews with a teacher become evidence-tied — both sides can look at the log together rather than relying on memory.

The deeper change is that practice stops feeling like a series of disconnected sessions and starts feeling like a continuous project. The log is the thread that connects yesterday's session to today's and today's to tomorrow's. Practis is built around exactly this kind of per-session log connected into a longer trail, which makes the cumulative pattern easier to see than any paper or spreadsheet version typically manages. But the underlying template — six fields, ninety seconds, written at the end — works regardless of the medium.

Pick a format. Write six lines. Read them tomorrow before you start. That is the whole system. It is enough.