How Freelance Designer Time Tracking Should Split Design QA and Handoff From Visual - MinuteShark

Time Management

How Freelance Designer Time Tracking Should Split Design QA and Handoff From Visual

Freelance designer time tracking usually collapses the last fifth of a website or product job into “UI.” You finished the visual. Then you spent Thursday checking states, exporting icons, naming files, writing the handoff note, and walking an engineer through what is not in the file. Friday’s invoice still says Visual. That is how a revision-heavy week becomes a donation you cannot see.

Design QA and asset handoff are real work. They are not a moral leftover of making pixels. Track them as named sibling tasks — or as locked phases — so R1 stays R1, Visual stays Visual, and the hours that actually closed the job have somewhere to live. The client-facing PDF can stay coarse. Your private catalog should not.

The rule: when visual design is done enough to QA, stop putting minutes on Visual. Open Design QA. When the file is ready to leave your desk, open Asset export / Handoff. Lock the phase you left so it cannot quietly absorb the next two days.

Why Visual ate Friday

Designers already know revision rounds need their own names. Mixing R1 into R3 is how you lose the argument about extra rounds. This piece is the week after that argument: visual is “done,” and the job is not. QA is looking. Handoff is packaging. Neither is drawing.

Three things get dumped onto Visual because it was the last task with a play button:

  • Checking work that is already drawn. Spacing, type, empty states, the mobile breakpoint you swore was fine. That is QA. It has a start and an end. It is not a new mockup.
  • Exporting and naming. SVG vs PNG, 1x/2x, the zip the developer actually opens. Asset export is a delivery task. Visual was the making.
  • Explaining the file. A written note, a walkthrough, the Slack thread that is really a meeting. Handoff is communication. If you always hide it in UI, you will never price it.

We already argued that code and meetings should never share a task. Design has the same split with prettier filenames. A calendar block called “Acme website” is still not a timesheet. The hour you spent in QA is not the hour you spent pushing pixels, even if both happened in the same tool.

A catalog that matches how a design job actually ends

You do not need a kanban to name the work. You need Client → Project → Task, and enough leaves that Friday is not a blob. A freelance designer catalog that survives invoice week usually looks like this — steal the names, not a process religion:

  • Discovery / audit
  • UX / wireframes
  • UI / visual
  • Prototyping
  • Revisions R1–R3
  • Design QA
  • Asset export / handoff
  • Meetings

Revision rounds as locked phases are a different article. Here the load-bearing pair is Design QA and Asset export / handoff. If you only add one task this month, add those two under the current project. Put the brief, screenshots, and file links in the project or task description so the leaf has context. That is a note you own. It is not a marketplace that “connects to Figma.”

Lock the phase you left

The failure mode is muscle memory. Visual still has a play icon. You sit down to export and hit play on the thing that was already running yesterday. Two days of handoff land on UI. The report then tells you visual design is “slow,” which is a lie you will use to underquote the next site.

When you leave a phase, lock or close that task so it cannot take more time. Closing a task should stop the clock without erasing History. You are not deleting the work. You are refusing to dump QA onto a finished drawing task. If a real visual change appears during QA — a button that is actually wrong — open Visual again on purpose, or log a named revision round. Do not keep Visual unlocked “in case.”

Subtasks are optional. If Design QA has three passes, they can be leaves under a parent, or sibling tasks named QA pass 1 / 2. Time lives on the leaf. Do not put an assignee on a parent that has subtasks; the person doing the export is on the export. The invoice does not have to print every leaf. Presenting time to non-technical clients is a translation job. Your catalog is allowed to be finer than their PDF.

What the report should prove by Thursday

Once a week, generate one report for that project — What = the project, When = this week — and glance at QA vs Visual vs Handoff vs Meetings. You are looking for a shape, not a confession:

  • If Handoff is bigger than Visual, you did not “over-design.” You under-named delivery. Price the next package with an export line, or a cap on walkthroughs.
  • If QA keeps matching another full visual round, the brief is still moving. That is a revision conversation, not a personal failing.
  • If everything is still Visual, the catalog is not in use. Fix names before you argue with a client.

Fixed-price jobs should see this before overrun. A tracker on the project that emails you at a percent of the estimate is for the whole container. Named tasks tell you which part is burning. Fifty percent of the estimate is a conversation; a blob called Visual is an autopsy. The reports guide is the mechanical map of What × Who × When. This piece is only the designer split that report is allowed to show.

Where MinuteShark fits (after the habit)

If you already work in MinuteShark, time is tracked on a task inside Client → Project → Task (subtasks on Standard). Onboarding is still Add Client → Add Project → Add Task. Put Design QA and Asset export / handoff next to UI / visual. Lock Visual when you leave it. Start the next leaf from dashboard search or the task list — one running timer, not three clocks. Rich text on the project or task is for the brief, screenshots, and links you need while you work. The Notes widget is private; it is not the client handoff document.

Generate a report for the project this week. Pivot by task. If rounding is on, original duration stays stored and BILLABLE is the rounded-up view. Generate Invoice from the same report if the client bought a coarse line called Website Redesign; you can still know QA was nine hours. MinuteShark AI can log forgotten QA time in plain English after you confirm a card — “I forgot to log 30 minutes on yesterday’s Design QA task.” It will not silently move those minutes onto Visual because Visual was last played.

Sarah L., an independent consultant, said MinuteShark “feels like it was built exactly for how I work.” For designers, that sentence is a catalog that matches the job: clients, projects, tasks, and the unglamorous closeout. Starter is free if you are testing the habit on a few clients. Standard is $5/user/month or $50/user/year when you need unlimited projects and subtasks, with a 30-day trial and no credit card. You do not need Asana to become an invoice. You need two extra task names and the discipline to lock Visual.

Previous Post Back to Blog Next Post