Guide
There is no universal number. The honest answer is your own, measured over one ordinary week. A paper log and a kitchen timer that prompts a check-in every 30 minutes will get you there for free, and your calendar shows what meetings take. If you work on a Mac and keep forgetting to log, Dayflow records your screen and writes the timeline for you.
You sit down a little before nine. Coffee, inbox, a quick look at chat. A call at ten runs over. You open the document you meant to finish yesterday, read the first paragraph twice, and answer a message that turns into a small fire. Lunch happens at your desk. In the afternoon you finally write the thing, and it takes forty minutes once you start. You close the laptop after six and feel like you worked all day.
Then someone asks, “How many hours do you actually work?” and you realize you have no idea. Nine, if you count from the first email to the last? Four, if you count the parts that felt like real work? Maybe two, on the bad days? The number shifts depending on your mood when you guess it.
This article is about finding your own answer, not an average for everyone. We’ll cover why the number is so hard to pin down, six things you can try this week (most need nothing more than paper, a timer and your calendar), and how to tell after a week whether each one is working.
One note before we start: Dayflow, which comes up near the end, is our product. Everything before that section works without it.
Memory is not built to keep a ledger. It keeps the vivid moments, like the tense call or the hour when the work finally flowed, and drops the rest. Ten small interruptions blur into “the morning.” When you look back, you’re reconstructing the day from a handful of highlights, and the gaps get filled with a guess.
Being at your desk and working are also different things, and many people feel the difference without ever measuring it. You can be at your desk for nine hours and spend much of that time switching between tabs, waiting for replies, rereading the same paragraph or recovering from a meeting. None of that is laziness. It’s what a modern working day looks like for a lot of people, and it mostly doesn’t feel like anything while it’s happening.
Feeling busy throws the guess off too. A day full of messages can feel longer and harder than a day with three quiet hours of focus, even if the quiet day produced more. Tiredness is a poor clock.
And the word “work” stretches. Is reading industry news work? Is the walk where you solved the problem work? Is the thirty-minute catch-up that wandered off topic work? If you haven’t decided, every answer you give is a different answer to a slightly different question.
If your days often end with that blank “where did it all go” feeling, our guide on where your day went covers that side of things in more detail.
What to do: Before you measure anything, write three to five categories on a card or sticky note. Keep them broad and personal. A common set looks like this: focused work (the thing only you can do), meetings and calls, messages and email, admin, and breaks. If your job has a category that matters more, like client calls, writing or code review, give it its own line.
Then decide on one rule for gray areas. For example: “If I’d mention it in a status update, it’s work.”
Illustration: A designer might choose: Design, Feedback and reviews, Meetings, Messages, Admin. Reading design blogs goes under Admin on the days it’s for a project and under Breaks on the days it isn’t. She writes that rule on the card so she doesn’t have to decide again each time.
After a week: It’s working if you can sort almost every part of a day into a category without stopping to think. If you keep inventing new categories or arguing with yourself about where something goes, cut the list down or merge two categories.
What to do: At the top of a page or in a note, write the time you start working and the time you stop. Add a rough figure for long breaks like lunch or school pickup. Start minus stop minus breaks gives you your desk time. You don’t need to be exact to the minute. The nearest quarter hour is fine.
This is the easy half of the question, and it’s worth having on its own. Many people find their desk time is quite different from what they would have guessed, sometimes longer and sometimes shorter.
Illustration: Monday: started 8:50, stopped 6:20, lunch 40 minutes. That’s about 8 hours 50 minutes of desk time. Tuesday: started 9:30, stopped 5:00, lunch 30 minutes. That’s 7 hours. Two days in, the person already sees that their days vary by nearly two hours, which they hadn’t noticed.
After a week: It’s working if you have seven pairs of times, or five for a weekday-only job, with no more than one you had to reconstruct the next morning. If you keep forgetting the stop time, write it on a sticky note on the laptop lid as you close it.
What to do: Use a kitchen timer, a cheap egg timer or any clock that rings. Set it for 30 minutes. When it rings, write one short line about what you were doing at that moment, and put the category from your card beside it. Reset and carry on. Don’t try to summarize the whole half hour. Just note what was in front of you when it rang.
This is a form of sampling. You won’t capture every minute, but over a week, the pattern shows up clearly. A printed sheet helps, and our daily work log template gives you a ready layout.
Illustration:
| Time | What I was doing | Category |
|---|---|---|
| 9:30 | Replying to a scheduling thread | Messages |
| 10:00 | Weekly team call | Meetings |
| 10:30 | Weekly team call (still) | Meetings |
| 11:00 | Reading the brief again | Focused work |
| 11:30 | Looking for a file | Admin |
| 12:00 | Drafting section two | Focused work |
At the end of the day, count lines per category and multiply by 30 minutes. In this illustration, two lines of focused work suggest roughly an hour, out of a three-hour morning.
After a week: It’s working if you’ve filled at least most of the check-ins, and the totals feel recognizable when you read them back. If you keep missing the timer because you’re in a meeting, mark those slots with an “M” and move on. Missing data is fine. Trying to fill it in from memory is what makes the numbers drift.
What to do: On Monday morning, before you’ve tracked anything, write down three guesses: how many hours of desk time you’ll have this week, how many of those will be focused work, and how many will go to meetings. Fold the paper and don’t look at it. On Friday, compare it with what your log says.
The point isn’t to score yourself. It’s to learn which way your guesses tend to lean. Some people consistently overestimate how much focused time they have. Others underestimate how much time messages take. Knowing your own lean is useful every time you plan a week. If you want a quick, low-stakes version of this, the time estimation test has you compare your sense of a short interval with a clock. It’s an exercise, not a diagnostic.
Illustration: A developer guesses 20 hours of focused work in a week. His log shows closer to 11, with messages taking much more than he expected. Next week, instead of planning around 20, he plans around 12 and protects two mornings.
After a week: It’s working if you can name which way your guess was off and roughly by how much. Try it again the following week. If the gap shrinks, your sense of your own time is getting sharper.
What to do: On Friday afternoon, open your calendar and walk back through the week. For each meeting, note how long it was, and also how much usable time sat on either side. A 30-minute meeting at 10:30 often turns the hour before it into a stretch of small tasks, because nobody starts deep work with a meeting looming. Mark those gaps.
If you’d like to see what recurring meetings cost in total, the meeting cost calculator does the arithmetic. If you’d rather sketch the whole week at once, the where does my week go calculator lays out your hours by category.
Illustration: A manager has six hours of meetings on her calendar. Looking backward, she notices that three of them sat in the middle of the morning, which left her with no stretch longer than 45 minutes on those days. The meetings took six hours, but they shaped closer to twelve.
After a week: It’s working if you can point to one or two meetings that could move, merge or become a written update, and you’ve asked about at least one. If every meeting really must happen where it is, the useful finding is that your focused hours need to live elsewhere, maybe early mornings or one blocked afternoon.
What to do: Pick a friend, partner or colleague who’s curious about the same question. At the end of each day, send each other one short message with your desk time and your focused time. No commentary, no comparing, just the two numbers. At the end of the week, have a ten-minute chat about what surprised you.
Saying a number to another person tends to make you write it down. It also takes the shame out of a low day, because the other person’s numbers move around too.
Illustration: Two friends who both work from home text each other at 6 p.m.: “8h desk, 2.5h focus.” “7h desk, 4h focus, no meetings today.” By Thursday, they’ve both noticed that their best days are the ones without morning meetings.
After a week: It’s working if you sent the numbers most days without much effort, and the Friday chat produced one thing you want to try. If it started to feel like a competition, drop the focused-time number and just share desk time.
Every method above has the same weak spot: you have to remember. The timer rings during a call, the stop time gets lost, Wednesday is reconstructed on Thursday. For some people that’s fine. For others, remembering to log is exactly what falls apart.
On a Mac, an automatic record removes that step. Dayflow records your screen at one frame every 10 seconds and has AI write the day into a readable timeline, so there’s no timer to start and nothing to reconstruct. You can read it back at the end of the day or week and sort it into your own categories.
A few specifics, based on Dayflow 2.2.0 documentation reviewed on 2026-09-06:
For more on turning a record into something you can recall later, see how to remember what you worked on.
Dayflow publishes this article, so weigh this section with that in mind.
Be clear about the limits before you install anything.
Sometimes the question “how many hours do I work” is really a different question: why do I feel exhausted no matter how much or how little I do? If long hours have become the norm, if rest doesn’t restore you, or if you suspect burnout, anxiety, sleep problems or ADHD are part of the picture, a log can show you the pattern, but it can’t tell you what’s behind it.
This article isn’t medical advice. A doctor or licensed clinician is the right person for diagnosis and treatment. Bringing a week of notes to that appointment can make the conversation more concrete. If time slipping away is a familiar struggle, our guide on what helps with time blindness offers practical ideas alongside, not instead of, professional care.
No outside figure will tell you how many hours you actually work. Your own week will. Pick your categories, write down your start and stop times, let a timer prompt you to notice what you’re doing, and compare the result with your Monday guess. Do it for one ordinary week without judging the numbers as they come in.
Most of that needs only paper and a timer. If remembering to log is the part that keeps failing, and you work on a Mac, an automatic record can fill that gap. For a fuller version of this exercise, see how to do a time audit on a Mac. Either way, the goal is the same: a number that’s yours, so the next decision about your time rests on what happened rather than on how the day felt.
There is no honest single figure, because people define work differently. Some count only focused work, and others count everything from email to commuting between meetings. The useful number is your own. Write down your start and stop times for a week, check in every 30 minutes, and sort what you did into a few categories you choose. That gives you a figure you can act on, which a general average cannot.
Many people find that focused work is a much smaller slice of the day than the time they spend at the desk. Messages, meetings, switching between tasks and small admin jobs fill the rest. That does not mean you are lazy or doing something wrong. Measure your own week first, then decide whether you want to protect more focused time or whether your current mix suits your job.
Use paper and a kitchen timer. Set the timer for 30 minutes, and when it rings, write one line about what you were doing. Reset it and carry on. At the end of the day, add up the lines by category and write your start and stop times at the top of the page. Keep it up for a week, then total each category. It costs nothing and works on any device.
Hours at your desk is the span from when you sit down to when you stop, minus breaks. Hours worked depends on what you decide counts, such as focused work, meetings, messages or admin. The gap between the two numbers is usually where the surprises are. Writing both down for a week shows you how much of your desk time goes to the work you care about most.
One ordinary week is enough to see a pattern, and two weeks is better if your schedule changes a lot. Pick a week without travel or a deadline crunch so the result reflects a normal day. Do not judge the numbers while you collect them. Wait until the week is over, total each category, and then decide what, if anything, you want to change.
Dayflow records your Mac screen at one frame every 10 seconds and has AI write the day into a readable timeline, so you do not need to start or stop a timer. You still decide what counts as work. The AI summaries can miss or misinterpret what you did, so read the timeline before relying on it. Dayflow is free and MIT licensed, and it runs on macOS 14 or later.
No. Dayflow does not create invoices, handle payroll approvals or produce team reports. If you bill clients, a dedicated invoicing or timesheet tool is the better choice, because it ties hours to clients and rates and turns them into bills. Dayflow can help you remember what you worked on, and it can export a date range as Markdown, but it is a record of your day rather than a billing system.
No. Dayflow is Mac only and needs macOS 14 or later. It sees only what is on your Mac's screen, so work on a phone, a Windows machine or paper does not appear. If you split your work across several devices, a paper log or a simple notebook will give you a more complete picture, because it goes wherever you go and records whatever you write in it.
Full screen recordings and the local timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis also stays on your Mac. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync. Your own provider's terms apply if you use one.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required