Retainer hour tracking for technical writers.
Freelance technical writers on monthly retainer face a fundamental client perception gap: clients think in pages and documents, but billable hours include everything that happens before a word is written. SME interviews, product feature research, documentation audits, and information architecture planning can consume half a month’s retainer before the first draft exists. When clients don’t see a running balance, they compare their monthly fee to the document count and feel the ratio is off — even when every hour was genuinely necessary. HourTab gives each client a live balance URL with a full work log so invisible pre-writing investment becomes visible contribution.
Free forever for your first retainer · no credit card.
Why technical writing retainer tracking goes wrong
-
Research and SME interview time is invisible before the first word is written.
Accurate technical documentation requires understanding the product before it can be explained clearly. That understanding comes from SME interviews (typically 90 minutes per SME, with 2–3 SMEs per complex feature), product feature exploration, code review, and information architecture planning. For a new API authentication guide, that might be 10–14 hours before the first draft begins. A client who sees their writer submit the first draft on day 10 of the month may feel like the first two weeks were unproductive — unless the work log shows exactly what those hours built. Research invisibility is the most common reason technical writing retainers don’t renew.
-
Revision cycles compound scope invisibly across stakeholder reviewers.
Technical documentation typically passes through engineering SMEs (accuracy), product management (customer clarity), and sometimes legal or compliance (terminology and liability). Each stakeholder has different requirements, and addressing one reviewer’s changes sometimes creates new issues for another reviewer. What the client describes as “a few tweaks” can become 3 rounds of revisions across 8 hours. Without a work log showing each revision round as a distinct entry, the revision labor appears as a mysterious hour total on the invoice that doesn’t match the client’s mental model of “small edits.”
-
Legacy documentation maintenance is systematically underestimated.
When a client asks a technical writer to “update this one doc,” updating it properly often means discovering 5 related docs that reference the same outdated information, re-testing the described procedures, and updating code samples and screenshots. The single document update becomes a 3-day maintenance sweep. Without a live balance showing that sweep as it happens, the client sees their monthly allocation disappearing on what they thought was a 2-hour task — and the explanation happens on an invoice, not in a productive conversation about documentation scope.
How it works for technical writers
-
1
Create the retainer. Enter the client name, monthly hour cap, and retainer start date. For clients with separate documentation programs (API reference vs. user guides vs. internal runbooks), you can either run a single pooled retainer with document-type tags in descriptions, or create separate retainers per program if the client has distinct documentation budgets.
-
2
Import time entries by CSV. Export from Toggl, Harvest, Clockify, or your tracking tool. Each entry appears in the client-facing log with description (e.g., “Authentication API guide — SME interview ×2, 4h” or “Payment flow guide — revision round 2 (legal), 3h”), date, and running balance. Update weekly to keep client visibility current.
-
3
Share the URL at engagement start. Drop the link into the engagement letter or the documentation kickoff email. The client checks the balance before requesting the next guide or maintenance sweep. You skip the “how many hours do I have left?” question. The live work log also becomes your documentation record — a month-by-month account of every doc created, updated, and reviewed under the retainer.
Clients see documentation hours consumed before the next request. Pre-writing investment is visible, not invisible.
“Technical writing clients consistently underestimate how many hours go into understanding the product before the document can be accurate. The work log is how you teach them.”
— freelance technical writing practice notes
A live work log turns invisible research and SME time into visible investment before the invoice arrives.
Frequently asked questions
How do freelance technical writers structure monthly retainer agreements?
Technical writing retainers typically cover 20–60 hours per month of documentation creation, maintenance, and review support. The monthly fee gives the client ongoing documentation capacity without scoping each piece individually. The core challenge is that clients think in terms of documents produced, not hours invested. A single API reference document might require 3 SME interviews (6h), research and outline (4h), first draft (8h), two revision cycles (6h), and a final review (2h) — 26 hours for one document. Without a live balance showing that breakdown, clients compare their monthly fee to the document count and wonder why the ratio feels off.
How should technical writers track SME interview and research time before writing?
SME interviews, product research, and documentation planning are the most commonly underestimated hours in a technical writing retainer. A client who sees their technical writer spend 12 hours before delivering the first draft may not understand that those 12 hours were necessary to produce accurate documentation — unless the work log shows “API authentication SME interview ×2, 4h” and “Authentication flow research and outline, 3h” as explicit entries before “Authentication guide first draft, 8h.” The prep work log turns invisible research into visible investment.
How do revision cycles expand scope invisibly in a documentation retainer?
One revision request from a client often triggers a cascade: the technical writer revises the content, the engineering SME requests additional changes for accuracy, the product manager requests restructuring for customer clarity, and the legal team flags a compliance issue. What started as “a few tweaks” becomes 3 rounds and 8 hours. A work log that shows “Payment API guide — revision round 1 (engineering), 2h” and “revision round 2 (product), 3h” and “revision round 3 (legal compliance), 3h” makes the revision cascade legible to the client.
Does HourTab work with documentation platforms like Confluence, Notion, or Readme?
HourTab works via CSV import, not direct integration with documentation platforms. If you track your writing hours in Toggl, Harvest, Clockify, or a spreadsheet, you export those time entries as CSV and import them into HourTab. The documentation platform your client uses to publish and maintain their docs (Confluence, Notion, Readme.com, GitBook, Docusaurus) manages the content — HourTab manages the documentation retainer balance your client checks before requesting the next guide or reference section.