Guide
Start by totaling your calendar's meeting hours. Then record what actually happens for two weeks and add prep and follow-up time. Toggl's free plan works if you will start a timer for every call. Timing or Rize track meeting time automatically, and Rize can pull in Google Calendar. Dayflow is a free option on macOS 14+. For whole teams, Toggl or Timely is the better pick.
You want one honest number: how many hours a week go to meetings, and which meetings they are. With that number you can drop a recurring sync, push back on a new one, or at least stop wondering why Thursday produced nothing.
The usual attempt goes wrong in a predictable way. You open your calendar, add up the colored blocks, and get a figure that looks reasonable. But a calendar records what was planned. It misses several things:
The calendar number is a starting point, not the answer.
This guide gets you the real figure in about two weeks. You use the calendar as a baseline, keep a record of what actually happened, and then compare the two. The tool details below come from a comparison of each vendor’s own documentation as checked on October 4, 2026.
Disclosure: Dayflow is our product. It shows up below as one way to do step 3, and the method works without it.
If you go the tool route, these are the options covered here:
For the wider field, see our roundup of Mac time trackers.
Go back two full work weeks and total every event that involved another person. Mark any you skipped, and any you declined but joined, as far as you remember. Record the hours per day, not only the weekly total, so you can see which days are heavy.
You can do this in a few ways:
Illustration: suppose the calendar shows 6 hours on Monday, 2 on Tuesday, 5 on Wednesday, 7 on Thursday and 1 on Friday. That totals 21 hours. The per-day view tells you more than the total: Monday and Thursday are nearly gone before they start.
Mistake to avoid: counting focus blocks, reminders and “hold” events. Count only events with other people. Otherwise the baseline is inflated and the comparison in step 5 will mislead you.
Decide your definition before you start recording, or you’ll argue with yourself every evening. A practical definition: any synchronous work conversation with at least one other person, whether or not it had an invite. That includes:
Write the definition at the top of your log. Also set a minimum length. Ignoring anything under five minutes keeps the log from filling up with noise.
Illustration: a designer might count design reviews, client calls and huddles, but not async comment threads on a design file. A manager might count 1:1s, standups and interviews, plus the hallway catch-ups that happen in between.
Mistake to avoid: changing the definition halfway through. If week one excludes huddles and week two includes them, the trend you see comes from the changed definition, not your schedule.
This step is what makes the exercise worth doing. You have three options.
By hand. At the end of each day, list every meeting with its real start and end time. Use the daily work log template or a spreadsheet. This costs nothing and works anywhere. The weakness is that end-of-day memory rounds things off, and overruns are exactly what memory forgets.
With a timer. Start Toggl when a call begins and stop it when the call ends. This is accurate when you remember, and the free plan covers it. The weak point is ad hoc calls, the ones you don’t think of as meetings until they’re over.
With an automatic tracker. These record activity in the background, so you don’t have to press anything:
AI summaries can miss or misread work, so check the timeline before you trust a total. For more detail, see how automatic time tracking works on a Mac.
Illustration: you have a 30-minute client call on the calendar at 10:00. The record shows the call app open from 9:58 to 10:47, then a 12-minute huddle at 11:05 with no invite. The calendar said 30 minutes. The record says about an hour.
Mistake to avoid: tracking only meeting time. Record the whole day so you can see what the meetings displaced.
A note on privacy: anything that records your screen during calls captures other people’s faces, names and shared screens.
Check your employer’s policy. If this is a concern, read time tracking without surveillance.
The meeting itself is only part of the cost. Add three things to each meeting in your record:
An automatic record helps here. Prep and follow-up happen in other apps, and they’re easy to spot right next to the call. If you’re logging by hand, add a “prep and follow-up” column and estimate.
Estimates are the weakest part of a manual log. If you suspect your guesses run short, the time estimation test is a short exercise comparing your sense of time with a clock.
Illustration: a weekly status meeting is 30 minutes on the calendar. Collecting updates beforehand takes 25 minutes, and writing up notes takes 15. The 20 minutes before your next call at the top of the hour usually go to Slack. The real cost is closer to 90 minutes.
Mistake to avoid: counting every gap as meeting cost. A 90-minute gap between two calls is usable time. Count only gaps you couldn’t realistically use. Pick a threshold, such as 30 minutes, and stick to it.
Put three numbers side by side for each week:
Then sort the recorded meetings by type: recurring status meetings, 1:1s, decision meetings, client calls, interviews and ad hoc calls.
Each comparison tells you something different:
Two calculators help at this point. The meeting cost calculator puts a price on a recurring meeting. The where does my week go calculator shows what’s left of the week after meetings.
Illustration: the calendar says 21 hours, the record says 26, and with prep and fragments the total is 32. Recurring status meetings account for 9 of those 32 hours, which makes them the obvious place to start.
Mistake to avoid: judging from one week. A launch week or a hiring push can double the count. Use at least two weeks and look at the average. For a broader version of this exercise, see how to do a time audit on a Mac.
Pick one change, not five. Common candidates:
Then measure for another two weeks with the same definition and the same method. Without a second measurement, you’ll remember the change as working whether it did or not.
Illustration: you replace a Monday status call with a written update. The next two weeks show the call gone, plus 20 minutes of writing on Monday afternoon. Overall, you got back most of the time, and Monday morning is now free for focused work.
Mistake to avoid: cutting meetings that were doing real work. If a canceled 1:1 turns into three ad hoc calls, the record will show it, so check before you call the change a success.
| Approach | Effort | What you get | Cost |
|---|---|---|---|
| Calendar plus spreadsheet | A daily log of about ten minutes, from memory | Planned time plus your recollection of overruns | $0 |
| Toggl (timer) | Start and stop a timer for each call | Accurate times for calls you remember to time, with calendar integrations | Free plan for up to 3 users; Starter $9 per user per month billed annually, or $12 per user per month billed monthly |
| Timing (automatic, Mac only) | Set up once, then review each week | Record of apps, websites and documents, with call tracking listed | Professional $9 per month billed annually, or $11 per month billed monthly; 30-day trial |
| Rize (automatic) | Set up once and connect Google Calendar | App and website tracking with AI categorization, plus calendar meeting time | Basic $9.99/mo billed annually, or $12.99/month billed monthly; 7-day trial, no free tier |
| Timely (automatic) | Approve AI-drafted entries | Background timeline turned into draft timesheet entries | Starter $9 per user per month billed yearly, or $11 per user per month billed monthly; 14-day trial |
| Dayflow (automatic, macOS 14+) | Install once, then read the timeline | AI-written timeline from screen captures, exportable as Markdown | $0, MIT licensed; optional Pro plan at $20 a month |
To repeat the disclosure: Dayflow is our product. It is free and open source. It has no invoicing, payroll, team reports or website blocking. You can export a date range as Markdown from Settings → Export, which is handy for pasting your two-week record into a spreadsheet or a weekly note.
Your calendar gives you a baseline, and two weeks of real records give you the answer. Define what counts as a meeting, record what happens, add prep and follow-up, compare, then change one thing and measure again.
A spreadsheet is enough if you’re disciplined about logging daily. Toggl’s free plan works if you’ll start a timer for every call. If you’d rather not depend on remembering, an automatic tracker catches the unscheduled calls and overruns your calendar never saw. Timing, Rize and Timely are paid options. Dayflow is free on macOS 14 or later, with the limits listed above.
Treat your calendar as a baseline and then check it against a record of what actually happened. Track every synchronous work conversation for two normal weeks, including calls that had no invite. Then add prep, follow-up and short gaps you couldn't use. The difference between the calendar total and the recorded total shows how much meetings overrun and how many happen off the calendar.
Usually not on its own. A calendar shows what was planned. It misses overruns, unscheduled huddles, phone calls, and meetings you declined but joined anyway. It also counts meetings you accepted and then skipped. Use it as a baseline and as a list of what to look for. Then compare it with a manual log or an automatic tracker for at least two weeks.
Yes. Timing is a Mac-only automatic tracker that records apps, websites and documents, and it lists call tracking. Rize tracks apps and websites automatically and can connect Google Calendar to capture meeting time. Dayflow records the screen at one frame every 10 seconds and has AI write a timeline on macOS 14 or later. Check any AI-written record before trusting a total.
For a team, Toggl (formerly Toggl Track) or Timely is a better fit than Dayflow. Dayflow is a personal Mac app with no team reports. Toggl has a free plan for up to 3 users, with team reports and paid plans for larger groups. Timely is priced per user and adds team and budget management on its Premium plan, which costs $16 per user per month billed yearly.
Yes, several. A spreadsheet or a daily log costs nothing and works anywhere. Toggl's free plan includes timers and calendar integrations for up to 3 users. Dayflow is free and MIT licensed on macOS 14 or later, and its optional Pro plan is $20 a month. Rize, Timing and Timely have no free tier, only trials.
Count them, but keep them in a separate column so you can see both numbers. A 30-minute status meeting can cost much more once you add collecting updates beforehand and writing notes afterward. Gaps between meetings that are too short to use also belong in the total. Pick a cutoff, such as 30 minutes, so that every gap isn't counted.
Two normal work weeks is a sensible minimum. One week can be skewed by a launch, a hiring push or a holiday. Skip weeks with conferences or offsites. After you make a change, such as dropping a recurring sync, measure for another two weeks using the same definition of a meeting and the same method. Otherwise you can't tell whether the change worked.
Dayflow records the screen at one frame every 10 seconds, so a video call appears in the timeline along with what was on screen. Recordings and the local timeline are stored on your Mac. With Local AI, screenshot analysis stays on-device. With your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Check your employer's policy before recording calls.
Multiply the meeting's real length, including overruns, by the number of attendees and by a rough hourly cost for each person. Then multiply by how often it happens. Add prep and follow-up if you measured them. Dayflow's free meeting cost calculator does this arithmetic for you. The input that matters most is the measured length, not the calendar length.
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