Guide
Show outcomes next to hours. Write a line at each stopping point, tie each line to something the client can open, and send a short weekly update before the invoice. For the hours themselves, Harvest wins if you need invoices built from tracked time. Timing wins for automatic billable records on a Mac. Dayflow helps you recall what you actually did each day.
The invoice is finished, and it looks reasonable to you: 31 hours on the site redesign. Then the client replies with one polite line: “Could you break that down a bit?” You open your notes. You find “homepage stuff,” a couple of calendar blocks, and a gap on Thursday you cannot explain. You know you worked. You just cannot show it.
Sometimes the question never comes, and that is its own problem. The client pays, but you sense they are not sure what the hours bought. The next project gets a tighter budget. Nobody said anything was wrong, but the trust you thought you had turns out to be thinner than it looked.
This guide covers three things. It explains why freelance hours are so hard to explain. It gives six habits that make them easy to show, and most of these need nothing more than a notebook and a calendar. Then it covers where an automatic record of your screen fits in. Dayflow, the Mac app mentioned later, is our product. Everything said here about Harvest and Timing comes from their own websites, as checked on October 4, 2026.
Most of the trouble is not dishonesty or sloppiness. It is the gap between how work feels from the inside and how it looks from the outside.
Memory compresses. By Friday, Tuesday is a blur. You spent two hours finding out why a layout broke in one browser, and that shrinks to “fixed a bug.” The hour of back-and-forth email disappears entirely. Many people find that a day they remember as unproductive looks very different once it is written down, and the reverse happens too. If that blur sounds familiar, where did my day go walks through it.
Clients buy outcomes, but you sell inputs. The client sees a finished logo. You see the rejected sketches, the font licensing question, and the call where the brief changed. Hours measure effort, and effort is mostly invisible to the person paying for it.
A lot of real work does not look like work. Reading the client’s old documentation counts. So does thinking through the structure on a walk, or waiting for a login and then setting everything up. None of it produces a file, so none of it gets remembered.
The report arrives at the worst moment. Often the first detailed account of your hours shows up attached to a bill. Then every line reads as a cost. The same information sent a week earlier reads as progress.
Reconstructed breakdowns read as guesses. A breakdown written from memory a month later tends to use round numbers and vague verbs. It may be completely accurate, but the client cannot tell.
Each habit below targets one of these problems.
Do not try to track time continuously or rebuild it later. Instead, write one short line whenever you stop: before lunch, before a call, when you switch clients, at the end of the day. Include the time range, the client, what you did and what comes next. Paper works. So do a plain text file and the billable hours log template.
The stopping point matters more than the tool. You already pause there, and the details are still fresh. You are not trying to remember Tuesday on Friday. You are writing down the last ninety minutes.
Illustration: “10:05-11:40, Acme. Rebuilt the pricing table for mobile, two breakpoints left. Next: check with Sam on the annual pricing copy.”
How to tell after a week: Check how many of your working blocks have a line. If most do, the habit is holding. If the gaps cluster at one time of day, put a reminder at that exact spot. The usual culprits are right after meetings and late in the afternoon.
Once a day, read back over your lines and rewrite the verbs. “Worked on homepage” becomes “Homepage hero now uses the new brand fonts.” “Emails” becomes “Settled image rights with their legal team, cleared to publish.” The time stays the same. What changes is that the client can now picture what they paid for.
Here is a useful test: could the client point at this line and say “yes, I can see that”? If not, add the result. If there is no result yet, add what you learned that narrowed the next step.
Illustration: Before: “Research, 2.5h.” After: “Compared three payment providers against their refund requirement. Only one fits, recommendation is in the shared doc. 2.5h.”
How to tell after a week: Read your log aloud as if you were the client. If many lines still describe only activity, keep rewriting them. The best sign is a client reply that mentions a specific line, such as “Great, glad the image rights are sorted.”
Create a small set of honest categories for the work that never produces a file, and use them every time. For example:
Five categories is plenty.
Labeling these does two things. It stops this work from being silently dropped from the record. It also tells the client something useful. If revisions are eating a big piece of the week, you both want to see that while there is still time to change the process.
Illustration: A week’s summary reads “Core design 9h, client revisions 4h, calls 2h, coordination 1.5h.” The client notices the revisions figure and suggests collecting all feedback into one round.
How to tell after a week: Look for any category that is empty or unusually large. An empty one usually means you are forgetting to log that kind of work. A large coordination line is a conversation worth having with the client, not something to hide.
Once a week, send a short note. It should cover what got done, what is next, hours used so far against any estimate, and anything you need from the client. Keep it short enough to read in a minute. The weekly status report template gives you a skeleton, and how to write a weekly status report covers tone and length.
The point is timing. By the time the invoice arrives, the client has already seen each week’s hours with context. The invoice becomes the sum of things they have already seen, not a new number to question.
Illustration: “This week: checkout flow is done and on staging, 11h. Next: account settings. Running total is 23 of the 40 estimated hours. Need: final copy for the refund page by Wednesday.”
How to tell after a week: The first sign is fewer questions about the invoice. After a few weeks, a second sign appears: the client starts replying to the update with decisions, so you no longer have to chase them.
A lot of friction about hours is really disagreement about rules nobody stated. Before the project starts, write them down in the proposal or a short email:
Then report the way you said you would. If you round, round the same way every time, and say so on each report.
Illustration: “Billing is in 15-minute increments, rounded up per working block. Calls and email are included. I will flag it before we go past the estimate.”
How to tell after a week: Look for any line you hesitated over while logging. Each hesitation points to a rule you have not agreed on yet. Send a short note about it now, or add it to the next project’s terms.
You may be unsure what to charge, or how much unbillable time your rate has to cover. The real hourly rate calculator makes that visible.
Every meaningful chunk of hours should point to something concrete: a draft link, a staging URL, a commit, a recorded walkthrough, or a doc with its comments resolved. This is not proof that you were busy. It lets the client see the work directly instead of trusting a number.
Some work, like research, has nothing to link. For that, write the conclusion down somewhere the client can read it. A three-line note on what you ruled out counts.
Illustration: “Navigation rework, 6h. Staging link included, plus a note on the two patterns we tried and why we kept the second.”
How to tell after a week: Pick three random lines from your log. Check whether you could hand the client a link for each one. If you could not, the fix is usually one sentence written at the stopping point.
Every habit above depends on remembering what you did. The weak spot is the gaps: the afternoon you forgot to log, or the week that blurred together. An automatic record closes those gaps, because there is no timer to start and nothing to reconstruct.
Dayflow records your Mac’s screen at one frame every 10 seconds, and AI writes the day into a readable timeline. The recordings and the timeline are stored on your Mac. Analysis can run in three ways:
The local and cloud processing page explains what leaves the Mac in each mode. You can also export a date range as Markdown from Settings → Export, then turn it into log lines or a weekly update.
Treat Dayflow as a memory aid, not a client report. AI summaries can miss or misread work, so check the timeline before anything goes to a client. Do not send raw screen captures, because they can show other clients’ work. Dayflow is free and MIT licensed, with an optional Pro plan at $20 a month, and it runs on macOS 14 or later.
Dayflow is our product, and Dayflow publishes this article.
Dayflow is the wrong choice in several common freelance situations.
To weigh more options, see our roundup of Mac time trackers. If billing is your main concern, how to track billable hours on a Mac goes deeper.
Clients rarely doubt your hours because they think you lied. They doubt them because they never saw the work happen. Close that gap in four ways:
None of this needs software. A tool only helps with the part memory handles badly: knowing what you actually did on the Thursday you cannot account for.
Pair each block of hours with the outcome it produced and something the client can open, like a draft or a staging link. Put invisible work such as calls, revisions and coordination on labeled lines instead of folding it into vague totals. If you send a short weekly update before the invoice, the client has already seen the hours with context when the bill arrives.
At minimum, include the date, the time range or duration, the project, a short description written as an outcome, and the type of work, such as core work, revisions, calls or coordination. Add a link to the related work where one exists. State your billing increment and rounding rule on the sheet itself so the client never has to guess how the totals were calculated.
Usually not. Raw screen captures can show other clients' work, private messages and things unrelated to the project. Share the work itself instead: drafts, links, commits or a short written summary. If you use a tool that records your screen, such as Dayflow, treat it as a private memory aid. Check it, then write the client-facing summary yourself.
Weekly works for most projects. A short note keeps the invoice free of surprises if it covers what got done, what is next, hours used against any estimate, and anything you need from the client. A very short engagement may need only a summary at the end. A long retainer can use a quick mid-week note when hours run faster than expected.
Respond with detail rather than defense. Share the line-by-line log for the period, with outcomes and links to the work, and point to the billing terms you agreed at the start. If the question reveals a real mismatch, such as revisions taking far longer than either of you expected, treat it as a process conversation for the rest of the project rather than an argument about one invoice.
No. Dayflow does not provide invoices, payment handling or billing status. If you need invoices built from tracked time, Harvest is the better choice. Its Free plan is $0 forever for 1 seat and 2 projects and includes time tracking, invoicing and expense tracking. Its Teams plan is $9 per seat per month billed annually, or $11 per seat per month billed monthly.
Yes. Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month. It builds an automatic timeline of your screen on macOS 14 or later, but it does not create invoices. Harvest has a Free plan for 1 seat and 2 projects that includes invoicing. Timing has no free tier, but it offers a 30-day trial with no credit card required.
Log it like any other work, under a clear label such as research. Then turn it into something the client can read: a short note on what you looked at, what you ruled out and what you recommend. Agree at the start that research counts as billable. Many clients are comfortable paying for thinking time once they can see the conclusion it produced.
Rounding is common, but agree on the rule before work starts and apply it the same way every time. Each report should say which increment you use and whether you round per task or per day. Some tools support this directly. Timing, for example, lists report rounding among its features. Being consistent matters more than which increment you pick.
Both run on the Mac and capture work automatically. Timing records time across apps, websites and documents. It lists billing status tracking and report rounding, starts at $9 a month billed annually, and has no free tier. Dayflow records one screen frame every 10 seconds and has AI write a readable timeline. It is $0, with Pro at $20 a month, and has no invoicing.
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