Client work that changes hands without changing story
Agency work passes through several people before it ships — strategy, design, copy, build, review. Each transfer is where context is lost and where a client’s question becomes unanswerable. TaskIt records the transfer itself.
Free for 30 days, with every feature unlocked.
What usually goes wrong
Written from how this kind of business actually runs, not from a generic template.
How it goes today
The brief lives in five places
A call, an email, a chat message and two rounds of feedback. The person doing the work reconstructs the brief before starting it, and reconstructs it slightly wrong.
Work bounces between specialists
Design to copy to build to review and back again. Every bounce is a reassignment that keeps the name and loses the reasoning.
Approval is informal until it is a problem
Somebody says it looks good in a thread. Nobody can later show who approved what, or on which version.
Client questions arrive weeks later
"Why was this changed?" and "when did we sign that off?" both need a record. Reconstructing them from chat costs a morning and produces a hedge.
Utilisation is a feeling
Who is overloaded and who is not is judged by who complains, which systematically rewards the quiet ones with more work.
With TaskIt
A brief captured as fields, not prose
Build an intake form per work type — campaign, design request, build ticket — from eighteen field types, so the deliverable, the client, the deadline and the constraints arrive with the task rather than after it.
Handovers between specialisms
When design passes to build, the handover records what was completed, what is pending, the notes that explain a decision, and the progress figure at that moment — all on the same task ID.
Route to a discipline, not a person
Raise work for the design or development department and let whoever is free claim it. In Collaborative mode several people can work one deliverable, each logging their own progress.
Review before it ships
Work is submitted for review and approved or rejected by the person who raised it, or anyone with the review permission. Nobody approves their own output, and a rejection returns the task with the reason recorded.
A record you can quote back
The activity timeline, the handover history and the audit log answer a client’s question about the past in minutes rather than in a morning.
One deliverable through a studio
A brand refresh, four specialists, one task ID.
- 1
Brief
The account lead raises it against the campaign form: client, deliverable, deadline, formats, brand constraints, approval limit.
- 2
Design
Raised to the design department. First designer free accepts. Progress and comments build the timeline.
- 3
Handover to copy
Completed: three routes at concept stage. Pending: headline copy for routes two and three. Notes: route one was rejected by the client in the previous cycle — do not resurrect it.
- 4
Handover to build
Copy approved, assets exported, one font licence still outstanding. Progress recorded at 70%.
- 5
Review
The account lead who raised it approves. The task reaches Completed with every transfer and every note in order.
- 6
Six weeks later
The client asks why route one was dropped. The answer is in the handover note, with a date on it.
The result
Nobody had to remember the constraint, and the answer to the client took two minutes.
The result
No percentages, because nothing here has measured yours — these are the changes the mechanism produces.
Less rework from lost context
The most expensive rework in an agency is the kind that repeats a decision already taken. A recorded handover is the cheapest possible prevention.
Approvals that can be evidenced
Who approved what and when is a recorded review rather than a message somebody will have to search for.
Workload you can rebalance fairly
The Workload report shows what each person is holding, so allocation stops depending on who is most vocal.
Handover reports that reveal process problems
Work that consistently changes hands three times usually points at a missing step or an unclear owner rather than at the people involved.
Frequently asked questions
No. There is no timer, timesheet, rate card or invoicing for client work. It measures elapsed time between recorded events — accepted, started, completed — which is useful for turnaround but is not a billable-hours record.
No. A workspace is for your team; there is no client portal or external guest access. What you can do is export a report to PDF or CSV and share that, which is usually what a client actually wants.
Not in the Gantt-and-milestones sense — there is no dependency planning, no critical path and no sprint board. It is built for the flow of individual pieces of work through people, which is what most agency days actually consist of.
A rejected review returns the task as Reopened on the same ID with the reviewer’s reason attached, so the second round sits in the same history as the first rather than becoming a separate task nobody can connect to it.
Where to go next
The capabilities behind this page, and the neighbouring situations they also cover.
Put one live job through it
Take a deliverable that will pass through three people this month and record every transfer.