Core concepts

The ideas behind your practice plan

Practice Coach uses a few key concepts to understand your playing and build better plans. Here's what they mean and why they matter.

AYour playing

How Practice Coach understands your playing

Confidence

Your honest answer to "could I play this reliably right now?", on a 1–5 scale at your current working tempo: Shaky, Rough, OK, Solid, Nailed. Shaky means you're still learning the notes; Nailed means you could play it on stage today at this speed.

Why this matters: Lower confidence comes up more often. Honest ratings make better plans.

Confidence at tempo

Confidence changes with speed. You might be Nailed at 80 BPM but only Rough at 100. That's not failure — it's the natural cycle of building speed. When you bump up 5 BPM, confidence drops. When you consolidate, it climbs back.

Sonatina — I. Allegretto (Torroba) — live demo

Why this matters: The app expects confidence to drop when tempo increases and plans for it. You won't be penalised for pushing your tempo — the planner accounts for the dip.

Passages

A passage tracked separately from the whole piece. Each passage has its own confidence rating, working tempo, target tempo, and practice history. You create passages for the spots that need individual attention — a fast run, an exposed solo, a technical figure.

Why this matters: One weak passage can hide behind four strong ones when you only track a whole piece. Passages give the planner granular data to work around your actual problem areas.

Tricky Passages

A mark you put on a passage that always bites you: material that fades fast after a break from practice. It isn't a different kind of passage, just something you know about it: this one needs extra attention to stay solid. Mark it from any passage card. Practise your tricky passages to run up to six of your tricky passages in rotation, most in need first, with the clean-in-a-row counter. You can also start them for one event's setlist, or for one piece. If a passage keeps dropping after breaks, its card suggests marking it tricky, and one that holds through long breaks gets a suggestion to unmark it. The mark only changes when you tap.

Why this matters: The planner brings tricky passages back more often the longer they go unpractised. A week before a gig, Tricky passages on the event runs every one on the setlist.

Flags

A flag follows one mistake from the moment you find it until the fix has held. Find it: tap the flag on the practice bar, then tap the spot on the music. Fix it: Practise this flag drills just that spot, and the flag stays open until you mark it fixed. Check it holds: a fixed flag shows faintly, and It's back reopens it if the mistake returns. Mark a flag Solid once it's settled. Each flag keeps its history.

Why this matters: A flag marks a mistake you can fix, and passages with open flags go first in the Fix block of your plan. A tricky passage is one that fades after a break. They are different things, so the app keeps them apart.

What counts as progress

Progress is shown as what got better, not how long you played. The Progress page and the session summary lead with what changed: ratings that went up, tempo gains and flags you fixed. The days and time you practised are shown too, as context.

Why this matters: Research on practice suggests that time spent is a weak guide to progress: among 17 advanced pianists learning the same passage, practice time and the number of repetitions did not relate to how well they played it the next day, and how they handled errors did. (Duke, Simmons & Cash (2009), “It’s Not How Much; It’s How”, Journal of Research in Music Education 56(4), 310–321.)

Condition

How would it go if you played it now? Repertoire shows each piece as Ready, Patchy, Needs a refresh or Not rated: an estimate from your last rating that fades with the time since you played it.

Why this matters: It helps you spot what needs a refresh before a gig. It's a guide for you; the plan works from your ratings and events.

Stages and statuses

While you're learning a piece, it's in one of four stages: New to me, Coming together, Settling in or Nearly ready (see Learning stages). After that it has a status: Performance ready (Ready to perform. The plan rehearses it and keeps weak passages sharp.) Maintenance (Learned and kept ready with short, regular check-ins.) Archived (Set aside, and left out of plans and reminders until you move it back.)

Why this matters: Stage and status shape what kind of work the plan gives a piece. How often it comes up is weighed, not fixed: see Why a piece comes up.

Learning stages

While you're still learning a piece, it moves through four stages: New to me (getting the notes, rhythms and fingering off the page), Coming together (passage by passage, at a tempo where it's accurate, with no full run-throughs yet), Settling in (building tempo, with the odd run-through), and Nearly ready (rehearsing it as you'd perform it, with light touch-ups). Each stage gets a different kind of plan.

Why this matters: Stage decides what kind of work the plan gives a piece. The plan holds back full run-throughs until a piece is ready for them, and after a session it suggests moving a piece on a stage when it's ready.

Collections

A way to group pieces by gig, season, or repertoire focus — wedding gigs, fall recital, jazz standards. Collections are independent of piece status: one piece can live in multiple collections at once. Pause a whole collection to silence its pieces from your daily plan and the Repertoire map without archiving them. Pieces linked to upcoming events still surface even when their collection is paused.

Why this matters: Status answers 'how am I working on this piece?'. Collections answer 'what is this piece for?'. Together they let you focus a season's prep without losing track of everything else — and pausing a collection silences its pieces everywhere except for upcoming events.

The Repertoire map

Your whole repertoire on one map, coloured by the lens you choose. More about the Repertoire map

Why this matters: When you're juggling thirty pieces, a list hides the shape of things. The map shows at a glance what's drifting and what's ready, so you can act on the whole picture instead of one row at a time.

BYour plan

How your plans get built

Why a piece comes up

The plan weighs four things for each piece: how close its deadline is, how long since you practised it, how confident you are, and how far it is from its target tempo. Pieces for an upcoming event come first, in time set aside for the event.

Why this matters: Nothing is scheduled by a fixed rota, so a piece that needs work comes up sooner and one that's secure waits.

Events and deadlines

Link pieces to a gig, concert, rehearsal, or lesson and, from three months out, your daily plan opens with a block for that event — time reserved for its pieces every day. The reserved share starts at about a third of your session and grows to most of it in the final week. If you're already spending most of your practice on the setlist, the plan follows you. Switch on Concert only (or Rehearsal only, Lesson only) to give the event all your practice time after your warm-up and daily essentials; the choice is remembered until the event has passed.

Why this matters: A date is a commitment, not just a weight. Reserving time means the pieces you're performing can't be crowded out by everything else in your repertoire — and you can still see, and add, what's been left out.

Build, consolidate, perform, taper

The plan works backwards from the event date. Build (until three weeks out): drills on the passages behind this week's tempo milestone, and slow play-throughs. Consolidate (three weeks to eight days): run-throughs every other day, drills only where something is still behind. Perform (from a week out until the day before): the whole setlist in concert order every day, with no tempo raises. In the last ten days, the plan first refreshes the setlist's tricky passages and any passage rated Rough or below, five minutes each, until each has had two sessions or a rating of Solid or better. Then run-throughs take over. You can skip the refresh for a day from the event block. Taper (the day before): one light run-through. On the day, a warm-up only. A rehearsal or lesson gets a shorter run-up that ends with a play-through the day before.

Along the way, each piece gets a weekly tempo milestone toward its concert tempo, timed to arrive ten days before the event. Milestones are suggestions: your saved tempo only changes when you change it, and a passage is only asked to go faster once you've rated it Solid at its current speed. Every passage on the setlist gets attention at least every three days.

Why this matters: It's the same peaking shape musicians and athletes use: build, settle, rehearse the real thing, then ease off. The phase name sits on the plan, so you always know where you are in the run-up.

In rotation, Resting and Shelved

A piece is In rotation while you're working on it: you've practised it recently, it's linked to an upcoming event, it has a goal, you've just added it, or you've pinned it. A piece is Resting when none of those apply. Shelved means you've put it aside, and an event brings it back. Pinned pieces stay in rotation however long they wait. Only pieces you're working on can become overdue. Outside an event's block, other pieces are offered starting with the ones that are fading, untouched for one to three weeks, before the ones that are slipping further away.

Why this matters: A big repertoire shouldn't drown out the music you're actually working on. Pieces you've never played are never pushed on you before a gig; with no event coming, the plan suggests one at most, and only adds it if you do.

Bottlenecks

The passage with the least tempo progress on a piece. The piece page and Today's insights point it out so you know where the time is going.

Why this matters: Polishing what's already strong feels productive. Knowing the weak link tells you where the work is.

Daily Essentials

Pin any piece, passage, or exercise to appear in every practice day — like your daily scales, a tricky passage you're working on, or a maintenance piece you never want to neglect. Set a time or a rep count for each one.

Why this matters: Essentials go into the Warm up block, and the plan fits everything else around them, so your daily fixed work happens even on a short day.

CYour sessions

How practice sessions work

The five blocks

Every item in your plan sits in one of five blocks. Warm up: your routine and daily essentials. Learn: music that's New to me, with the score first, then the passages you've marked, slowly, then a slow play-through. Fix: passages whose notes you know, until they're reliable. Connect: joining the passages back into the piece, with slow play-throughs, tempo steps and whole-piece work. Perform: run-throughs.

Why this matters: Each block has its own colour, icon and name on the plan, so you can see at a glance what kind of work an item is.

Practice modes

Fix is for building: working on one passage, counting clean attempts in a row until you reach your target. Run-through is for testing: playing a piece start to finish like a performance. Perform mode is for playing from the score as you would on stage: full screen, with page turns by tap, swipe or pedal.

Why this matters: Fixing and running through serve different purposes. The plan tells you which to do for each item, so you're always doing the right kind of work.

Tempo tracking

Every piece and passage has a current working tempo (where you can play it comfortably now) and a target tempo (where you want to get it). The gap between the two feeds into planning decisions.

Why this matters: A bigger gap weighs more when the plan decides what to work on.

Goals

A goal is a tempo target, a confidence target, or both, by a date: for example, 96 BPM by the concert.

Why this matters: A goal keeps its piece in rotation, and when a tempo goal falls behind the pace it needs, the plan brings the piece up more often.

Session summary

After a session, the summary shows what changed and what happens next. Stage suggestions, goals and notes sit under Details. Save session keeps it; Discard throws the session away without logging the time.

Why this matters: You see what the session moved before you leave, and the next plan starts from it.

Start practising with a plan

Invitation only for now.

Request an invite