Time Tracking for Freelance Writers: A Practical Workflow

If you bill per word, time tracking feels redundant. If you bill per hour, the timer never matches what you actually did. If you switch between the two depending on the client, you have two different problems running in parallel.

This post is for freelance writers who want to track time without making the work harder than it already is. It covers the specific shape of writing work, what to capture and what to ignore, and how to invoice both per-word and per-hour clients from the same underlying log.

Why writing time is hard to track linearly

A 2,000-word article involves work in shapes that resist clean timing:

• Research that includes reading three Wikipedia pages and one industry report
• An outline scribbled in a notebook
• A first draft written in one 90-minute session
• A revision pass after sleeping on it
• A second revision after the client's feedback
• An hour of editing one paragraph that resisted you for half the week
• A final read for typos at the printer

The total billable time might be 9 hours. The contiguous active-writing time is 4. The rest is real work that happens fragmented across days and platforms — Notion, Google Docs, Chrome (for research), a notes app, and possibly a notebook.

A traditional timer captures one slice of this. The other 5 hours leak out.

The four phases of a writing project

If you have to categorize writing time, the cleanest split is:

| Phase | Where it happens | Typical share of total | |---|---|---| | Research | Browser tabs, PDFs, books | 20-30% | | Outline / structure | Notes app, notebook, head | 5-15% | | Drafting | Word processor, Google Docs, Markdown editor | 30-40% | | Revision | Same editor + new browser tabs (fact-checking) | 20-30% | | Communication | Email, Slack — feedback rounds | 5-15% |

The first three are usually undercounted by timer-based tracking. Revision is overcounted because you tend to leave a timer on while distracted. Communication is almost never tracked, which is why you respond to four emails for free.

What to capture, what to ignore

Pure-volume capture (every website, every app, every minute) is too much data to make decisions from. Aim for:

• Capture every app and browser tab with timestamps — passive, no effort
• Aggregate at the project level rather than the file level
• Treat your text editor + research browser as one session when working on the same piece
• Ignore casual browsing under 2 minutes that happens between sessions
• Always log communication separately — Slack and email about a piece is billable; auto-categorize messages tagged with the project

What this means in practice: you do not need to remember to start a timer when you switch from drafting to fact-checking. The capture catches both. At end of day, you confirm "yes, that 90-minute block was for the Acme article — all of it billable."

Per-piece versus per-hour: same log, two reports

Most working writers have a mix of clients. Some pay per-word ($0.30/word, $0.50/word, $1+/word for premium). Some pay per-hour ($50-150/hour for content strategy, editing, consulting). Some pay per-piece (flat $400 for a 1,500-word blog post regardless of effort).

The good news: one underlying activity log supports all three billing models.

Per-hour billing: export the time per client/project for the invoice period. Done.

Per-piece billing: ignore the time when invoicing the client, but use the log internally to track your effective hourly rate. If a $400 article took 12 hours, you earned $33/hour. If another took 6 hours, you earned $66/hour. After three months of data, you know which clients to keep, which to raise rates on, and which to drop.

Per-word billing: same as per-piece — billing is independent of the log, but the log shows you whether the project was efficient. Per-word rates of $0.30 only work at a sustainable hourly when you can write at a certain pace. If you cannot, raise the rate or change clients.

The single most undervalued thing a writer can do with passive time tracking is stop billing per-piece blind. Without time data, you cannot tell which clients are quietly paying you $20/hour. With it, you can.

A 5-minute end-of-day routine

Once passive capture is running, the daily review takes 5 minutes:

1. Open the day's timeline.
2. Walk through the session blocks. Confirm each one is tagged to the correct project.
3. For sessions that span multiple projects ("I drafted for Acme then revised for Beta"), split the session at the right minute.
4. Tag anything pulled in from communication channels with the matching project.
5. Save. Move on.

Friday is then a 10-minute export, not a forensic reconstruction.

What about the work that happens away from the computer?

Writers do real work on walks, in the shower, while making coffee. None of it is captured by a tracker.

Two options:

1. Add it as a manual entry at end of day. "Tuesday afternoon walk — Acme article outline — 45 minutes." Honest, defensible, simple.
2. Don't bill it explicitly — instead bake it into your per-piece or per-word rate. Most experienced writers do this implicitly: the rate already includes thinking time.

Either is reasonable. Pick one and be consistent.

A note on focus apps and distraction blockers

Many writers run focus blockers (Freedom, Cold Turkey) that prevent browser distractions. These play well with passive time tracking because:

• The blocked sites do not show up in your timeline (so no false "I spent 20 minutes on Twitter" guilt entries)
• The sessions that DO show up — your editor, your research tabs — are higher signal-to-noise
• The two systems complement each other; one prevents the distraction, the other proves you were doing the work

If you do not use a focus blocker yet, consider it. Your tracker will be more accurate by accident.

What "fixed" looks like for a writer

A working time-tracking system means:

• You can answer "how long did the Acme article actually take?" without guessing
• You know your effective hourly rate per client, even when billing per-piece
• Friday afternoon is for writing, not reconstructing the week
• Communication time (email, Slack, calls) is captured automatically, not forgotten
• Your invoices match the work you did, not the work you remembered to log

If your current system does not produce all five, it is not working. The problem is not your discipline. The problem is the tool.

DayReplay's specific fit for writers

For full disclosure: I built DayReplay because most time-tracking tools assume you work in one app at a time on linear tasks. Writing is not that. DayReplay runs in the background, captures app + window-title + browser-tab activity locally on Mac or Windows, and produces a session timeline you can categorize per project.

A few things that matter specifically for writers:

• Browser-tab capture means research time is recorded with the article you were researching, not as undifferentiated "Chrome usage"
• Custom categories let you label per-project (Acme article, Beta blog post, ongoing newsletter) rather than per-app
• Idle detection pauses tracking when you step away — so the 45 minutes you spent thinking on a walk is not logged as 45 minutes of "Google Docs idle"
• CSV export per category gets you a per-client total in 30 seconds at end of week

The macOS guide and Windows guide walk through setup. The Customize Categories page covers project-level tagging. For the broader case against timer-based systems, see How to Track Work Hours Without a Timer.

If DayReplay is not the right fit, that is fine — the workflow principle (passive capture, end-of-day review, weekly export) works with any tool. The point is to stop forgetting half the research time and the editing rounds. Both are billable. Both should be in the log.