Guide
Use an automatic tracker that reads window and tab titles, because design apps usually show the open file name there. Timing wins if you bill clients and need reports. ActivityWatch wins if you want free, local, open-source logs and can work with raw data. Toggl wins for team billing with timers. Dayflow, our product, wins if you want a written timeline of what you designed each day.
You want a real number at the end of the week. How many hours did the onboarding redesign take? How much of the retainer did the brand refresh use up? Do you spend more time in Figma than in meetings about Figma?
It usually goes wrong in one of two ways. You start a timer when you open a file, then drift into Slack to answer feedback and forget to stop it. Or you track nothing and rebuild Friday’s timesheet from version history and memory. Design work also moves between apps: research in a browser, moodboards, Figma, an export in Photoshop, a prototype review on a call. A timer tied to one app misses most of it.
This guide shows a method that works with any tool, including pen and paper. Dayflow is our product, and it is one way to handle one of the steps. The tool details below are a comparison of each vendor’s own documentation as published on October 4, 2026.
Tracking for an invoice is different from tracking to see where your week goes. Billing needs per-client totals that hold up if someone asks about them. Self-review needs patterns: how much time is deep design work and how much is switching, reviews and admin. Team capacity planning needs everyone tracking the same categories.
Write the question down in one sentence before choosing anything.
Illustration: A freelance product designer has three retainer clients and one fixed-fee project. Her question is: “How many hours did each client get this month, and is the fixed-fee job going over?” That rules out a tool that only reports “Figma: 31 hours.” She needs time split by client.
Mistake to avoid: Tracking everything at maximum detail “just in case.” Detail you never read costs review time every week. Start with the question and add detail only when it fails to answer it.
Automatic trackers mostly work from the active app plus its window or tab title. Design apps usually put the open file name in that title, so the file name ends up as the main clue a tracker has. “Untitled” or “v3 final FINAL” tells it nothing.
Use a fixed pattern such as Client - Project - Area. Open a file, look at the window title or browser tab, and confirm the name shows up there before you rely on it.
Illustration: A designer renames her Figma files to “Acme - Checkout - Mobile,” “Acme - Checkout - Desktop” and “Northwind - Brand - Logo explorations.” Her exports in Photoshop follow the same prefix. When she later sets up a rule saying “anything with ‘Acme’ in the title goes to the Acme project,” it catches Figma, Photoshop and the Acme folder in Finder in one go.
Mistake to avoid: Putting the client name only in the Figma project or team name, not the file name. Project and team names often do not appear in the window title, so the tracker never sees them.
There are three ways to capture design time, and the right one depends on your answer to step 1. If you want the wider set of options first, our guide to Mac time trackers covers them, and there is a narrower list of time tracking apps for designers.
Toggl (formerly Toggl Track) is the main timer-based option here (how it compares on Mac). You start a timer with a project and description and stop it when you switch. The vendor also lists automated background tracking and a timeline in the desktop app, plus calendar integrations. It runs on web, Mac, Windows, iOS, Android and browser extensions, and the free plan covers up to 3 users. Billable rates need a paid plan: Starter is $9 per user per month billed annually or $12 per user per month billed monthly.
Timers are precise when you remember to use them. Designers tend to forget them during the work that matters most, the long focused stretches.
Timing records apps, websites and documents on the Mac, down to specific URLs (Timing compared with Dayflow). The vendor states tracked times stay local unless you opt into sync. It lists billing status tracking, reports with rounding and AI activity summaries. There is no free tier: Professional is $9 per month billed annually or $11 per month billed monthly, with a 30-day trial and no credit card required.
Rize tracks apps and websites and uses AI to categorize and tag them (Rize compared with Dayflow). It runs on Mac and Windows, stores data in the cloud on Amazon Web Services, and starts at $9.99 a month billed annually or $12.99 billed monthly for Basic, with a 7-day trial.
ActivityWatch records the active app, window title and whether you are away from the keyboard (ActivityWatch compared with Dayflow). Its browser extensions add tab titles and URLs. It is free, open source under MPL-2.0, and keeps all data on your device. No AI summaries are listed.
Dayflow records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Instead of “Figma, 2h 14m,” you get a description of what was on screen. Recordings and the timeline are stored on your Mac. It is free and MIT licensed, with an optional Pro plan at $20 a month.
Illustration: The freelancer from step 1 needs per-client totals and invoices, so she trials Timing. A design lead who mainly wants to see how much of the week is real design work starts with ActivityWatch, because it is free and the window titles answer his question.
Mistake to avoid: Choosing on features you will never open. If you do not invoice from your tracker, invoicing integrations are not a reason to pay for one.
A lot of design work happens away from the canvas. Research in the browser, reading feedback in Slack or email, a critique call, writing a handoff note, exporting assets in another app. If only Figma counts, a project can look like it took half the time it did.
Make a short list for each project of the apps, sites and channels that belong to it. Keep shared tools like email under a general bucket unless the content is clearly one client’s.
Illustration: For the Acme checkout project, the list is: Figma files starting with “Acme,” the Acme Slack channel, browser tabs on Acme’s staging site, and calendar events with “Acme” in the title. Rize can connect Google Calendar to capture meeting time. With other tools, the designer adds calls by hand at the end of the day.
Mistake to avoid: Assigning all browser time to whichever project is open in Figma. Browsing for inspiration during a client project might be fair to bill. Watching a conference talk is usually not. Decide the rule once instead of arguing with yourself every week.
Raw logs are a list of app names and titles. Rules turn them into “Acme: 6.5 hours.” Most automatic trackers let you assign activity to projects based on app, title keywords or URL. Your naming scheme from step 2 makes these rules short.
Write the rules, then check them against one real day. Look for unassigned time and for time assigned to the wrong client.
Illustration: In Timing, a rule says titles containing “Acme” go to Acme, and “Northwind” goes to Northwind. After the first day, 40 minutes is unassigned: a Figma file someone else shared, called “Checkout explorations.” She renames her copy and adds the rule. In ActivityWatch, the same idea works through its categorization settings, matched against window titles.
With Dayflow, there is less rule work because the timeline is already written in sentences, such as “Worked on Acme checkout mobile states in Figma, then reviewed Slack feedback.” You still need to check it. AI summaries can miss or misread work, especially when two client files look alike.
Mistake to avoid: Writing a rule per file. You end up with dozens of rules that break each time a file gets a new name. One keyword per client is usually enough.
Once a week, open the tracker, fix the misassigned blocks, and copy the totals into wherever they need to live. Weekly is often enough to remember what an odd block was, and not so often that it becomes a chore.
For billing, use the billable hours log or your tracker’s own reports. For self-review, a simple time audit helps you compare categories week to week. If you want to know what an hour of your design time actually earns after unbilled work, the real hourly rate calculator does that math.
Illustration: On Friday, the freelancer spends 20 minutes in Timing. She moves a Northwind block that was filed under Acme, rounds to the nearest quarter hour, and exports per-client totals. The fixed-fee project shows 18 hours against a 15-hour estimate, so she raises it with the client before the next phase rather than after.
With Dayflow, the equivalent is reading the week’s timeline and exporting a date range as Markdown from Settings, then Export. The totals still go into your timesheet by hand, because Dayflow has no invoicing or billable reports.
Mistake to avoid: Leaving review for month end. By then, a block called “Figma, 1h 40m, untitled” is a guess.
| Approach | Effort | What you get | Cost |
|---|---|---|---|
| Manual log in a spreadsheet | High. You write every block yourself | Whatever you remember to write down | $0 |
| Timer app (Toggl) | Medium. Start and stop timers, fix forgotten ones | Precise project entries when used; billable rates and team reports on paid plans | Free for up to 3 users; Starter $9 per user per month billed annually or $12 per user per month billed monthly |
| Automatic tracker (Timing) | Low to medium. Set rules once, review weekly | App, document and URL records assigned to projects; billing status and reports | Professional $9 per month billed annually or $11 per month billed monthly; 30-day trial, no free tier |
| Automatic tracker (ActivityWatch) | Medium. Set up categories, read raw data | Local log of apps, window titles and away time | Free, open source |
| Dayflow | Low. Review and correct the written timeline | A readable daily timeline of what was on screen, exportable as Markdown | $0, optional Pro at $20 a month |
To restate: Dayflow is our product. Keep that in mind when reading the row above, and check each vendor’s own page before you decide.
Tracking the app, not the work. “Figma: 28 hours” does not tell a client what they paid for. Fix it at step 2 with file names.
Forgetting about NDAs. Screen recording client work is a different decision from logging window titles. Dayflow stores recordings on your Mac, and its Local AI mode keeps screenshot analysis on-device through Ollama or LM Studio. If you connect your own cloud provider or use Dayflow Pro, selected screenshots leave your Mac. Under the privacy policy, Pro deletes screenshots after processing but may keep activity data for sync. The details are on the local and cloud processing page. If no screen capture is acceptable, use a title-based tracker like ActivityWatch or Timing.
Treating every minute in Figma as billable. Updating your portfolio, tidying your component library for your own use and checking a friend’s file all happen in the same app. Give non-client work its own bucket.
Skipping the first-week check. Rules always miss something in the first week. Check one full day against your own memory before trusting totals.
Mixing team and personal tools. If your agency bills through Toggl, a private tracker can help you fill it in, but it does not replace the shared system.
Dayflow writes a timeline. It does not provide invoices, payroll approvals, team reports or website blocking.
Good design time tracking comes from file names and a weekly review more than from the tool. Name files Client - Project - Area, decide what non-Figma work counts, map it with a few keyword rules, and fix the week every Friday.
For the capture step: pick Timing if the numbers go on an invoice, Toggl if a team shares them, ActivityWatch if you want free, local logs with no screen capture, and Rize if you want AI categorization on Mac or Windows. Pick Dayflow if what you mostly want is a readable record of what you designed each day, and you are fine moving totals into a timesheet yourself.
Most automatic trackers read the active app and its window or tab title. Design apps usually put the open file name in that title, so a file called "Acme - Checkout - Mobile" shows up in the log under that name. If you work in Figma in a browser, you need a tracker that reads tab titles or URLs, such as Timing, Rize or ActivityWatch with its browser extension.
Yes, as long as the tracker can see browser tabs. Timing records websites down to specific URLs. Rize tracks apps and websites. ActivityWatch needs its browser extension to add the tab title and URL. A plain timer like Toggl's works in either case because you start and stop it yourself, but it only knows what you tell it.
For billing, Timing is the strongest fit among the tools covered here. Its documentation lists billing status tracking, customizable reports with rounding and GrandTotal invoicing integration depending on plan. Professional costs $9 per month billed annually or $11 billed monthly, with a 30-day trial and no free tier. Dayflow has no invoicing or billable reports, so Timing beats it for this job.
ActivityWatch is free and open source under MPL-2.0, stores data on your own device and records the active app and window title. Toggl has a free plan for up to 3 users built around timers. Dayflow is free and MIT licensed, with an optional Pro plan at $20 a month. Timing and Rize have no free tier, only trials.
It depends on where the screenshots go. Dayflow stores recordings on your Mac, and its Local AI mode keeps screenshot analysis on-device through Ollama or LM Studio. Using your own cloud provider or Dayflow Pro sends selected screenshots off-device. If any screen capture is a problem, ActivityWatch records app and window titles rather than the screen and keeps data local.
Decide up front which apps and sites belong to a project, then map them with rules or tags. Browser tabs with the client's name, Slack channels, and calls on the calendar all count. Rize can connect Google Calendar for meeting time. If your tracker only sees app names, add a short manual note at the end of each day for the context it missed.
Rize names designers among its target users. It tracks apps and websites automatically, uses AI to categorize and tag time, and runs on Mac and Windows. Data is hosted in the cloud on Amazon Web Services. There is no free tier; Basic is $9.99 a month billed annually or $12.99 billed monthly, and the trial is 7 days with no credit card required.
Toggl runs on web, Mac, Windows, iOS, Android and browser extensions. Rize runs on Mac and Windows. ActivityWatch runs on Windows, Mac, Linux and Android. Timing and Dayflow are Mac only, and Dayflow needs macOS 14 or later. If your design team is split across platforms, Toggl is the simplest shared choice of these.
Detailed enough that a client or manager can see what the hours bought, and no more. Project, task type and a short description per block usually do it, for example "Checkout flow, mobile states, 2.5 hours." Per-frame or per-minute logs are rarely useful. Round consistently, and keep the raw tracker data in case anyone asks how a total was reached.
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