August 2026
"Workflow" is a horrible word. It sounds like something a consultant says on a slide. But it means something very simple, and you already have one.
A workflow is the things that have to happen, in order, every time. You have one for every concert you play. Nobody has ever written it down, which is why it lives in your head and occasionally wakes you at four in the morning.
One thing before I go any further, because it matters. None of what follows is about being disorganised. Most of the musicians I work with are unusually organised, and that's exactly why they're tired. They do the joining-up by hand, every time, and they do it well. The problem was never them. It's that nothing they use knows about anything else.
Let me take one booking and follow it the whole way through.
A festival programmer emails in April. They'd like you the following June. Are you free?
You check the calendar, then the email, then the spreadsheet. You're trying to work out what else is happening that month, whether you're already going to be in that part of the world, and what's sitting either side of it that hasn't been confirmed yet.
Twenty minutes. And you do it again the next time someone asks about a different date.
What a system does: the shape of that month is one screen. Not three places to check, each holding a different part of the answer.
The fee gets agreed in one sentence, halfway down the fourth email. The contract arrives as an attachment and is read once. Six weeks later, what am I owed across this season? is a question you can't answer without opening nine emails.
What a system does: the fee is a number in its own place, not a sentence buried in a thread. Whether the contract is signed is a box that's either ticked or it isn't. There's no remembering involved, and no scrolling.
This is where things fall off, and it's worth being honest about why.
Preparing a concert isn't one job. It's about eighteen. Finalise the programme. Send the biography and the photograph. Book flights and a hotel. Agree what may be recorded and who owns it. Confirm rehearsal time in the hall. And so on.
Not one of those is difficult. Not one of them is urgent — until all of them are, in the same week.
What a system does: it holds the list so you don't have to. The same list appears on every concert, because it genuinely is the same list every time. You tick things off as you go, and you can see that you're nine of eighteen through the October one and three of eighteen through the one after. Which tells you what to do with your Tuesday.
Suddenly you need things quickly. What's the postcode. Is there parking. What time can you get in. Who do you ring if the door's locked.
You're on a train, scrolling backwards through the thread from last spring, and the confirmation, and a text message from March.
What a system does: it's all sitting on the concert already. Not because someone typed it there, but because the concert is joined to the venue, and the venue knows its own address. You wrote that down once, years ago, the first time you played there.
An invoice, if there's one. A thank-you, always.
And then the thing that almost nobody does: write down what it was actually like. Full hall. Difficult acoustic, needed more air between movements. The programmer stayed for the second half and mentioned a series next year.
What a system does: keeps that with the venue, so it's in front of you in eighteen months when they email again — instead of you trying to remember whether that was the good one or the other one.
That sounds abstract, so here it is plainly. The concert knows which venue it's at, so it already has the address, the phone number, and the note about the piano. It knows which pieces you're playing, and each piece knows how long it lasts, so it can tell you the programme runs fifty-two minutes without you adding anything up. It knows what's still outstanding.
You follow one thing to the next. Look at a venue and you see every concert you've played there. Look at a person and you see everything you've done together.
The practical effect is that you write something down once, ever. A venue changes its production team; it's updated in one place, and every engagement you will ever play there is correct.
Four things, and I'd hold to all of them.
You write it once. If you're ever typing the same thing in twice, something is built wrong.
The system remembers, not you. The point isn't saving time. Ten minutes on a contract is fine. Carrying "I must chase that contract" around for three weeks is the part that actually costs you.
It tells you things. A folder of emails will answer any question you think to ask it. A system should tell you the things you didn't think to ask — what's coming up, what's still unsigned, what you're owed, and how empty next spring is looking while there's still time to do something about it.
It survives you being ill. If you're in bed for a week and nothing can move without you, you don't have a system. You are the system.
None of this is really about software. Whichever tool you use, the job is the same — get to the outcome without carrying it.
It's about this. Right now, some part of your brain is holding a list of things that must not be forgotten. It has been holding that list for years. It's the reason admin feels heavy even in the weeks when there isn't much of it.
That part can stop. That's all a workflow is for.