Time Management
How to Track Time When You Switch Clients Five Times Before Lunch
Context switching time tracking is usually treated as a focus sermon. Close Slack. Protect the block. Become a monk until 11:30. That advice is fine for a writing day. It is useless on a Tuesday morning where you take a five-minute access question from Client A, jump to Client B’s standup, unblock a designer on Client C, and then actually start the work you billed as “implementation.”
The timesheet problem is not that you switched. The timesheet problem is that the log becomes a composite: one blob called “morning,” or the last client you remember, or nothing until 4 p.m. when you reconstruct the day from email. Composite tasks are how you underbill the noisy clients and over-explain the quiet ones. They are also how you teach yourself that time tracking is a novel you write at night.
The rule: a switch is a new task, even if it lasted twelve minutes. Do not invent a mega-entry called “misc clients.” Name the client, the project, and the kind of work. Reconstructing a chopped-up morning from memory is how Friday becomes fiction.
Why a chopped-up morning still has a shape
Freelancers do not fail at time tracking because they lack discipline. They fail because the day does not look like the tool. A flat timer with one running label assumes you inhabit one job. A calendar assumes meetings are the work. Chat assumes the ping is the unit. None of those is a billable unit a client will recognize.
A useful shape is still boring: client → project → task. Time belongs on the task. When you switch clients, you are not “multitasking.” You are ending one task’s clock and starting another’s. If you keep a single “consulting” timer running across three logos, you have not tracked time. You have tracked presence.
This is different from “how many clients is too many.” Roster size is a capacity question. Context switching is a logging question. You can have four healthy clients and still wreck the morning by refusing to name the hops. You can have eight clients and log cleanly if each hop lands on a real task. The test is whether Thursday’s history is readable without a decoder ring.
Stop creating a composite task for the in-between
The composite task has aliases: “admin,” “slack,” “various,” “catch-up.” Sometimes those names are honest — true internal overhead should not be stuffed into Client A so the week looks billable. Sometimes they are a dumpster for work that had a client all along. A twelve-minute access debug for Northwind is Northwind. A standup for Contoso is Contoso Meetings, not “morning.”
If you already know unbillable CI and code review rot when they live on Implementation, you already know the pattern. Context switches rot the same way when they live on whoever you were with at 9:01. Split by client first, then by kind of work: Meetings, Support, Implementation, Discovery. The names should survive an invoice. Ticket IDs should not be the line.
- Under five minutes? Still name it if it had a client. Rounding can wait; identity cannot. A pile of unnamed five-minute favors is how you donate a day.
- Same client, different mode? Meetings vs implementation still deserve different tasks. A hop inside one logo is still a hop.
- No client? Put it on an internal project you actually review, or stop tracking it. A junk drawer labeled “switch tax” that you never look at is theatre.
People who bounce between sites have a physical version of the same rule. The clock that matters is the one you can start in a lobby, not the one waiting on your desk. Waiting until you are “back” is how the first two hops vanish. Phone in pocket, name the task, start, stop, start. Ugly. True.
A morning protocol that does not require a personality transplant
You do not need a 90-minute deep-work shrine to log switches. You need a default that is faster than lying.
The five-hop morning, logged
- Before the first ping. Decide the task you intend to inhabit. Start that clock. Intention is not a vow; it is a default so the first interruption has something to stop.
- On interrupt. Stop. Start the other client’s task — Support, Meetings, whatever is true. Do not pause in a nameless void “for a second.” Seconds accumulate into a client you cannot invoice.
- If you forgot. Do not rewrite the whole morning. Log the slice you actually remember on the right task for the right day. A clean 20-minute correction beats a fake 3.0h novel.
- At lunch. Open today — not last month. If two hops are missing, add them while the conversations still have nouns. History is for course-correcting the day, not for literature.
One running timer is a feature of honesty, not a missing multi-clock mode. Three open clocks is how you pretend you were in three places. One clock, stopped and started, is how a chopped-up morning stays a sequence instead of a puree.
What to review so the switches teach you something
Context switching is expensive even when every hop is billable. If you logged it, you can see whether Client C’s “quick questions” are a second job. If you did not log it, you will feel busy and still be surprised on the invoice. A weekly review can wait until Friday. A daily glance cannot: the hops are still named in your head at 12:15 and gone at 6:40.
Look at today grouped by client, then by task. You want two questions, not a dashboard hobby: (1) Did any client get a composite dump? (2) Did any hop land on the wrong kind of work? Fix those two. Do not optimize your life into a timesheet. The point of tracking a noisy morning is so you can say no with last week’s data later — or raise a rate — without relying on the vibe that “Tuesdays are a lot.”
If you work across many logos, you already know the roster can get too wide. This article is the other half: even a sane roster will shred a morning. Tracking across multiple clients is the map. One running timer is the honesty rule. Naming the hop is the habit.
Where a daily tool helps — without becoming a surveillance story
You want a timer you started on purpose, a catalog that already has the clients, and a today-view you will actually open. You do not want screenshots, idle popups that start the clock for you, or a bot that silently edits the morning. Those products are built for managers. Consultants need the opposite: stop, start, name, confirm.
MinuteShark is built around that sequence. Time is tracked on a task under a project under a client. Start from dashboard search — “Search anything or start a task” — instead of hunting a tree while someone waits on speakerphone. Starred tasks sit on the dashboard as a widget so the three logos you are actually inhabiting this week are one play icon away; starring is not a second project list. History defaults to today, with a BILLABLE badge if you turned rounding on. One running timer across web and mobile. iOS Live Activities if you are between buildings. Smart reminders can nudge. They do not start the clock.
If the hop already happened and you are walking out of the cafe, MinuteShark AI can log forgotten time in plain English — on mobile you can speak, review the transcript, send. Nothing is written until you confirm a proposal card. You can edit the card. You can often revert from chat. It will not invent a composite “morning” task to save you from naming Northwind. That is the point. The dashboard widgets guide is the map of starred tasks, to-dos, notes, Pomodoro, and History. Pomodoro is a focus clock. The sidebar timer is the billable one. Do not conflate them when the morning is already chopped.
MinuteShark Starter is free (1 user, 3 clients, 5 projects, 30 AI messages/month). Standard is $5/user/month or $50/user/year if you need more clients than a demo roster (300 AI messages). You do not need an integration marketplace to log a hop. You need the hop to have a name — and a confirmation card before anything is written.