The Plaud worked. That's the problem.
It was so easy to record that you recorded everything: client calls, site visits, one-to-ones, that conversation in the car you didn't want to lose. Six months on, there they all are: dozens of recordings, faithfully captured, sitting in the app. Some transcribed. Some summarised. Almost none of them acted on.
Somewhere in that pile are commitments you made, decisions you were part of, and details you're currently trying to remember from scratch. The backlog isn't a failure of discipline. It's what happens when capture is effortless and everything after capture isn't.
Why the backlog built up
Processing a recording is a chore even when the tools are good. You have to open it, read or skim the summary, decide what matters, move the actions somewhere, and file the rest. Multiply that by every meeting in a busy month and "I'll do it at the weekend" becomes six months of weekends.
And then there's the quieter frustration: the sense that your own recordings are on a meter. Minutes and quotas, monthly allowances, features that gate what you can do with conversations you already had. When re-processing your own backlog feels like it's going to cost you, in money or in monthly allowance, the rational move is to keep putting it off. So you do.
The result is a strange kind of debt: a complete, accurate record of half a year of your working life, generating no value at all.
The backlog is an asset, not a guilt pile
Here's the reframe worth making before you touch a single file: those recordings aren't a to-do list you failed. Most of the actions in a six-month-old meeting are dead: done long ago, overtaken, or irrelevant. You don't owe the backlog a full processing pass, and you shouldn't give it one.
What the backlog actually holds is context. What was agreed with that client before the scope changed. What the supplier promised in March. Why a decision went the way it did. That's not a pile of overdue tasks. It's the searchable history of your work, waiting to be somewhere it can actually be used.
What to do with it
Move it, don't process it. Upload the transcripts into ka-do and let each one attach to what it belongs to: the client, the project, the thread of conversations it's part of. You're not extracting actions from a January call; you're putting January where it can answer questions.
Then handle the recent stuff differently. The last few weeks are the only part of the backlog where the actions are probably still alive. Those are worth running through properly, transcript in, tasks out, onto a schedule that can tell you if they fit. That's the same transcript-to-task-list process — just applied to today's recording instead of a backlog.
Upload once. It's yours. No throttling, no limits on your own data, no re-processing fees, no meter running on conversations you already had. That's not a feature. It's just what ought to be true about your own record of your own meetings.
Going forward, the habit changes shape: paste the transcript in while the meeting is still warm, and there is no backlog. The pile you're looking at now is the last one.
The recordings were always meant to go somewhere
The Plaud did its job: six months of your working life, captured cleanly. What it couldn't do is make any of it useful, and that's not a capture problem. It never was.
The backlog is raw material. Moved somewhere it can be searched, linked, and asked questions of, it stops being a guilt pile and starts being the thing it always should have been: your record, working for you.
Ka-do is where it goes.
Ka-do connects your meetings to your tasks, your schedule, and the threads running through your work. Try it free →