You were in the studio nearly every night this month. You know it, your back knows it, the stack of bounces on the desktop knows it. Then somebody asks what that actually adds up to, a client, a tax form, or just your own curiosity at the end of the year, and the answer is a shrug. Working out how to track your studio hours as a producer sounds like admin. It turns out to be closer to self-defence.
The month that disappeared
Try to reconstruct last month from memory. There was the weekend you rebuilt the drop, the Tuesday that vanished into one synth patch, at least three evenings on a mix for a friend that was supposed to take one. Now put a number on it. Most producers land somewhere between a guess and a lie, and not because they are dishonest. The studio simply does not leave a paper trail.
The DAW is no help. Project timestamps tell you when you saved, not how long you sat there. Your calendar shows a dentist appointment and someone’s birthday. If you go digging through autosave folders and file-modified dates you can prove you touched a project, but not that you lived inside it until 4am. The gap between the month you experienced and the month you can prove is enormous, and it always shrinks in the wrong direction.
Run the numbers the other way and it stings more. If you charge by the hour, or ever intend to, every hour you cannot prove is an hour you cannot bill. If you produce for yourself, the missing hours are the difference between “I never have time for music” and the truth, which is usually kinder than you think.
You worked all month. On paper, it was nine hours.
Why track your studio hours at all
Two reasons, and they matter to different people at different moments.
The first is money. The moment someone pays you for studio work, mixing, production for another artist, session time, the hours become billable, and “I think it was about two days” is not a line you can put under an invoice. Even if you charge flat rates, your real hours tell you whether that flat rate is a fee or a donation. Plenty of producers discover, the first time they see an accurate number, that their day rate was funding somebody else’s record.
The second reason is quieter and, for most bedroom producers, bigger. The number tells you who you actually are in the studio, the way a notes habit tells you what you meant to do next. Which projects eat your life. Whether the track you keep saying you are finishing has received forty minutes in six weeks. Whether you are a night producer or just someone who remembers the night sessions. You cannot manage what you cannot see, and that applies to your own time before it ever applies to organising the projects themselves.
So the question is not whether the number is worth having. It is how to get it without turning every session into paperwork. There are three methods, and the first two deserve a fair hearing before anything replaces them.
Method one: the session log
The oldest method, and still underrated: a notebook, a text file, or a spreadsheet with four columns. Date, project, hours, what happened.
Its real advantage is not the hours. It is the fourth column. Writing “rebuilt the chorus, still hate the snare” takes ten seconds and is worth more, six months later, than any duration ever will be. A session log is the only method on this page that captures what the time was for, in your own words, at the moment you still knew. If you keep one honestly, keep it. Nothing below is an argument against it.
The word doing the work up there is honestly. A session log gets filled in either before the session, when you do not yet know what will happen, or after it, when you are tired and hungry, or three days later, when you are writing fiction. In practice the log survives exactly as long as the sessions go badly. The first time a session really works, you surface hours later with a finished drop and no memory of ever agreeing to do paperwork. The best sessions of your month are precisely the ones the log misses.
That is not a discipline problem. It is a design problem.
Method two: the general purpose timer
The obvious upgrade is a timer app. The general purpose time trackers, the ones built for freelancers and agencies, do the mechanical part well: press start, work, press stop, get a report. While the timer is running, the data is genuinely accurate, which is more than the session log can claim.
The advantages are real and worth naming. Weekly totals, tags, exports, numbers that add themselves up. If your studio runs on appointments, if sessions start when the client walks in and end when they leave, a timer app can absolutely carry you, and plenty of working studios bill from one without ever feeling the pain described below.
The failure is the button. A timer asks you to remember it at the exact moment you are least capable of remembering anything, which is when the session is finally working. Nobody has ever hit start on a stopwatch while falling into an idea. The stop button is worse: the timer you started at 9pm is still running at noon the next day, quietly billing your sleep to a client. So you end up editing entries after the fact, which is the session log’s fiction problem wearing a nicer interface. And the timer has no idea what a project is. Mapping “that thing from Thursday” to the right track is manual work, forever, across every session you ever run.
Both manual methods fail the same way. They hand the measuring equipment to the one person in the room with no spare attention: you, mid-session.
Method three: automatic, per project
The only stopwatch that survives a studio is one nobody has to press.
This is where Vantom comes in, and for once it is allowed to simply be the answer. Vantom is a desktop app for Windows and macOS that watches the folders your projects live in and builds one library across nine DAWs. Studio Time is the part of it that handles the clock. While you work on a project, the hours are booked to that project automatically. No start button, no stop button, no reconstructing yesterday from memory. You open the session, you work, you close it, and the time lands on the track it belongs to instead of on a vague sense of August.
Two limits, because a page that has spent four sections arguing for a tool owes you them. Vantom sits beside your DAW, not inside it. It does not read your DAW’s transport, and it has no idea whether you spent the hour writing a melody or staring at the arrangement in quiet despair. It knows which project you were in, for how long, and which plugins were loaded in it. That is all, and for a timesheet, that is exactly enough. Second: everything Studio Time records stays on your machine. Your hours are not a dashboard on someone’s server. They are yours, locally, full stop.
The number you did not expect
Time per project is what you came for. Time per plugin is what you did not know you wanted.
Because Studio Time also books hours against the plugins in your sessions, the month gets uncomfortably specific. Forty hours in the studio is a satisfying number. Eleven of those hours inside one synth is a different kind of information altogether. Maybe that synth is the sound of the record and those eleven hours are the best money you never spent. Maybe you have been redesigning the same patch for two weeks because it is easier than writing the second verse. Vantom will not tell you which it is. It reports the number; the conclusion is yours. There are no scores, no recommendations, and no streaks either, which is a deliberate decision rather than a missing feature. A studio is not a habit app.
The per plugin view also settles arguments you have been having with your wallet. When the number says you spent twenty hours last month inside one EQ, the upgrade you keep hesitating over stops being a question. When it says the expensive reverb got eleven minutes, so does that one.
From hours to an invoice
When the hours are billable, Studio Time exports a timesheet as CSV or PDF: sessions, projects, durations, ready to hand to whoever is paying. To be precise about what that is, because precision is the point of this article: it is a timesheet, not an invoice. Vantom does not do billing, rates, clients or payment. You write the invoice in whatever you already use and attach the timesheet as the receipt behind it.
That split is worth more than it sounds. A number on an invoice is a claim. A session history behind it is evidence. “Mixing, 14 hours” invites an argument; a per-session breakdown across three weeks ends one before it starts. The client can see the Tuesday you spent on revisions they asked for, dated, in order. Nobody has to take anybody’s word for anything.
There is a quieter use for the same export. Records outlive arguments: a year of timesheets is what you hand your accountant when the studio stops being a hobby on paper, and what you sit with yourself before deciding whether a rate goes up. Both conversations go better with a PDF than with a feeling.
Reading your own heat map
Then there is the view that has nothing to do with clients. Studio Time draws a daily heat map of your hours: a calendar where the days you worked are dark and the days you did not are not.
Producers are reliably wrong about their own patterns. You would swear you are a 1am producer, and the map shows your real output happens on Sunday afternoons. You would swear last month was dead, and the map shows eleven scattered sessions that never made it into memory because none of them ended with a finished track. The heat map does not congratulate you and it does not scold you. Same principle as the rest of the app: it reports, you conclude.
It also answers the question every part-time producer asks in a bad week: am I actually still doing this? Eleven dark squares in a month say yes, even when the release schedule says nothing at all. That is not motivation software. That is just the record, and sometimes the record is the encouraging thing.
Over a few months it becomes the time-shaped twin of keeping the whole library in one place. The catalogue shows what exists. The heat map shows what it cost. Put the two side by side and you know more about your own practice than most producers ever find out.
Start before you need it
Every method on this page, manual or automatic, shares one hard limit: none of them can measure backwards. The month you already lost is lost. A timesheet only exists from the day the tracking starts, and the day you actually need one, a client, a rate negotiation, a hard look at where the year went, is always later than the day you should have started.
So start while the number is still boring. Keep a session log if you love the fourth column; it earns its place next to any tool. But let something automatic carry the hours, because the hours are the part you will never carry yourself, and you now know exactly why. If that something is Vantom, the clock is already running the next time you open a project. Nobody has to remember anything.
You will still work all month. The difference is that this time, the timesheet will admit it.