How to Manage Agency Employees and Client Projects, with Client Status Cards
Managing agency employees and client projects is one job with two halves, and most agencies run only one half well. Either the projects look tidy and the team is worn out, or the team is happy and client work slips. Both halves break at the same point: the gap between what you promised a client and the hours your people actually have.
This guide gives you a working system for closing that gap. You’ll get a client command sheet, a task ownership table, capacity math you can run today, a weekly rhythm, a scope change process, and a health scorecard. If you want to see how the tooling side works, the TechXaro One product tour walks through the screens.
The short answer
To manage agency employees and client projects, plan capacity before you promise dates, give every task one owner, write scope down and route changes through a request, run a fixed weekly rhythm, and review client health and team workload together every Friday. Keep all of it in one system so nobody has to ask for status.
Why managing agency employees and client projects separately fails
An agency sells time it can’t store. An hour nobody billed on Tuesday is gone by Wednesday. So a scheduling mistake costs you twice: once as idle capacity, and again as the overtime that follows when deadlines stack up.
The numbers show how thin the margin is. SPI Research’s 2026 benchmark, as reported by GigRadar, put professional services billable utilization at 66.4 percent for 2025, the lowest on record. Most agency guides set a healthy range between 60 and 85 percent depending on the role, as Everhour lays out. A firm sitting at 66 percent isn’t lazy. It is usually scheduling by gut feel.
Gut feel is common. The Global Agency Landscape report, cited by Productive, found that only about 21 percent of agencies track forecast against actual utilization. The rest find out about overload when somebody quits or a deadline slips.
Client-side problems start earlier. Nulab traces much scope creep back to poor client onboarding, where the team follows a brief that never matched the client’s expectations. So the fix has to cover the first week of a project, not only the delivery weeks.
Step 1: Build one command sheet per client
Before the first task exists, write a one-page command sheet for the client. It is the document you open when someone asks, “What did we agree?” and nobody remembers. Keep it inside the project, not in a drive folder nobody checks.
| Field | What goes in it | Why it matters |
|---|---|---|
| Client goal | One sentence on the result the client wants, with a number if possible | Stops the team from delivering work that looks good and misses the point |
| Scope and exclusions | What is included and, just as important, what is not | Gives you something to point to when a “small extra” arrives |
| Hours or budget per month | The hours the client pays for, split by role | Lets you compare time used against time sold every week |
| Delivery lead | The one person who owns delivery for this client | Gives the team one name to ask |
| Client approver | The one person on the client side who signs off | Prevents five reviewers sending five versions of feedback |
| Turnaround promise | How fast you reply and how fast the client replies | Turns “the client is slow” into a measurable delay |
| Escalation contact | Who gets called when the project is red | Removes the panic search for a phone number |
| Next review date | The date of the next client health review | Keeps the sheet alive instead of filed |
If you can’t fill a field, that is your first finding. A missing approver or an unwritten exclusion is a problem you want to meet in week one, not week six.
Step 2: Give every task one owner
Two names on a task means no names. When a deliverable slips, the first question is who had it, and an agency can’t afford a long conversation about that. Assign one owner per task, and decide the role split once for the whole team.
| Role | Owns | Signs off | Does not do |
|---|---|---|---|
| Account manager | The client relationship, scope, and change requests | Scope changes and invoices | Assign day-to-day tasks to specialists |
| Project manager or delivery lead | The plan, task owners and weekly status | Delivery dates | Approve work in the specialist’s craft |
| Specialist | Their tasks, from first draft to submission | Nothing alone; work goes to review | Change scope or dates with the client |
| Reviewer | Quality check before the client sees anything | Approval, or a reopen with a written reason | Rewrite the work silently |
| Client approver | One round of consolidated feedback | Final approval | Send feedback through three channels |
In TechXaro One task management, each task has one assignee, a due date, subtasks, and a priority. The step that matters most is the review: a reviewer approves the submission or reopens it with a reason. After a month, you can see which kinds of tasks keep coming back, and that tells you whether the problem is the brief, the skill, or the timeline.
Step 3: Plan capacity before you promise dates
Utilization is billable hours divided by available hours. A designer with 40 hours in the week and 6 hours of meetings and admin has 34 hours for client work. If you book all 34, one revision round breaks the week. I’d plan to use about 80 percent of available hours and leave the rest for review rounds and surprises.
The math scales up fast. HiveDesk gives the example of an agency selling 6,000 billable hours a quarter at 70 percent utilization, which needs 16 or 17 delivery staff. Using 520 available hours per person per quarter (13 weeks of 40 hours), the chart below shows how each five-point change in your target moves the headcount by roughly one person.
Use the number as a signal, then act on it. The table is a rule of thumb, not a standard, so adjust it to your own retainers.
| Team utilization | What it usually means | First move |
|---|---|---|
| Below 60% | Idle capacity or untracked work | Check that all billable work is logged, then look at sales pipeline |
| 60% to 75% | Room to take work, or too much non-billable time | Audit non billable categories weekly |
| 75% to 85% | The working zone for delivery staff | Protect it, and review each person’s load every Monday |
| Above 85% for two weeks | Burnout and quality risk | Move work or push dates before anyone asks |
Two cautions. One blanket target for everyone hides the real picture, because a senior strategist can be on target at 62 percent when the role includes proposals and team direction, a point Everhour makes well. And track the hours you don’t bill. Time you log against internal work is the only way to see why the billable number is low.
Step 4: Run a fixed weekly rhythm
Most agency teams don’t have too many meetings. They have meetings at random times, so no day is safe for focused work. Pick a rhythm and keep it for a quarter.
| When | What | Length | Output |
|---|---|---|---|
| Monday | Capacity check with delivery leads | 30 minutes | A list of who is over and who has room |
| Tuesday and Wednesday | Focus days with no internal meetings | None | Work submitted for review in the task |
| Thursday | Send work to clients for approval | Async | Client’s feedback window starts |
| Friday | Client health review and team retro | 30 minutes | Updated client status and one thing to change |
| Monthly | Client review call | 45 minutes | Decisions on scope, budget, and next month |
The Thursday rule is the one agencies skip. If work goes to the client on Thursday, their feedback window starts before the weekend, and the revision lands early next week. Work sent on a Friday afternoon sits until Tuesday, and the delay becomes your fault in the client’s mind.
Step 5: Control scope with change requests
It starts as one line in a chat: “While you’re at it, can you also…” Nobody says no, because it’s small and the client is friendly. Four weeks later, three small asks have eaten a day of someone’s time, and nobody can show where it went.
A change request fixes this in four moves:
- Acknowledge the request and say you’ll confirm the effort.
- Estimate hours for each role and state the cost or the date impact.
- Get the client’s written approval from their named approver.
- Add it as a new task, so the time lands against it.
The pattern matters more than the form. PMI’s 2023 Pulse of the Profession found that organizations prioritizing power skills such as communication and collaborative leadership had only 28 percent of projects hit by scope creep, as the PMI release reports. Saying “yes, with a change request” is a communication skill before it is a process.
Step 6: Keep approvals and client updates in one place
Feedback that arrives by email, chat, a call, and a shared doc can’t be reconciled. Pick one place and tell the client at kickoff. Agree a feedback window up front, three working days is a common choice, and name who inside the client’s team gives final approval.
Clients also stop asking for status when they can see it. In TechXaro One, a client with a Guest seat can review and approve the work you assign to them, and nothing else, so one client never sees another client’s projects. See how roles work on the features page. For the weekly update, use the same four lines every time:
Done this week. What was delivered and approved.
Next week. What is planned and who owns it.
Needed from you. Decisions, files, or approvals, with dates.
Risks. Anything that could move a date or cost hours.
It takes five minutes to write, and it replaces a status call. Clients start to read it because it is always in the same shape.
Step 7: Manage the people, not only the tasks
A task system can show you that someone is late. It can’t tell you why. The people half of agency management is mostly about catching the cause early, and a few habits do most of the work.
Set workload caps
As starting points, try no more than three active client accounts per person, no more than eight tasks due in the same week, and a conversation whenever someone passes 85 percent utilization two weeks running. Adjust after a month of data.
Make accountability visible
People meet deadlines they can see. When every task carries an owner and a due date, nobody has to chase. Our guide on how to make employees accountable for deadlines goes deeper on this, including how to handle repeat misses without turning into a micromanager.
Hold short 1-on-1s
Fifteen minutes every two weeks is enough. Ask what’s blocking them, what’s boring them, and what they’d drop if they could. The third question gives you the best information about next quarter’s resignations.
Adapt for remote teams
If part of your team works from home, written handoffs and fixed overlap hours matter more. Our piece on how to manage remote employees covers the routines that hold up across time zones.
Watch for burnout signals
| Signal | What it usually means | First move |
|---|---|---|
| Tasks reopened more often than before | Rushed work or unclear briefs | Review two reopened tasks with the specialist and the reviewer |
| Submissions arriving late at night | Daytime hours are consumed by meetings or overload | Check Tuesday and Wednesday for meeting creep |
| Slow replies on tasks | Context switching across too many clients | Reduce active accounts for that person |
| Rising overdue count for one person | Overload, not laziness | Move one task before the next deadline |
| Quiet in team check-ins | Disengagement or a private problem | Book a 1-on-1 this week |
PMI’s data hints at where the skill gap sits. Project professionals spend 46 percent of their development hours on technical skills and 29 percent on power skills, according to the same 2023 release. If your team leads are great at the craft and weak at conversations, training them to give feedback and reset expectations will pay back faster than another tool.
Step 8: Track a short list of numbers
More dashboards do not help an agency. Seven numbers, reviewed on Friday, are enough to tell you which client and which person needs attention.
| Metric | Formula | Direction you want |
|---|---|---|
| Billable utilization | Billable hours / available hours | Inside your range for each role, not a single firm wide number |
| Realization rate | Hours invoiced / billable hours worked | Close to 100%, falling means unlogged extras or discounts |
| On time delivery rate | Tasks delivered by due date/tasks due | Rising, tracked by client |
| Reopen rate | Tasks reopened / tasks submitted | Falling, tracked by task type |
| Approval turnaround | Days from submission to client approval | Stable or shorter |
| Overdue tasks per person | Open tasks past due date, by owner | Near zero; a spike signals overload |
| Effective hourly rate | Project fee / actual hours logged | Above your cost plus margin target |
You can pull most of these from the reports in TechXaro One, which cover completion rate, workload, and time to close for any project or date range. If you use a spreadsheet for the rest, the formulas above are all you need.
A client health scorecard you can copy
Score each client on Friday using the table. Any client with two reds gets a conversation on Monday. The thresholds are starting points, so tune them to your contracts.
| Signal | Green | Amber | Red |
|---|---|---|---|
| Hours against budget | At or below the share of the month elapsed | Up to 15% over pace | More than 15% over pace |
| Approvals | Inside the agreed window | 1 to 2 days late | More than 2 days late |
| Scope changes | All logged and approved | One unlogged request | Several unlogged requests |
| Client responsiveness | Replies within the promised time | Replies slip once | Silence while work is blocked |
| Team load on this account | Owner below 75% utilization | 75% to 85% | Above 85% |
Setting this up in TechXaro One
Full disclosure: TechXaro One is our product, so weigh this section accordingly. TechXaro runs SEO, content, and web development work for several clients at once, and One grew out of the way that team tracks it. The structure above maps onto it like this.
- Create one project per client, then add the command sheet fields to the project description.
- Assign each task to one person, and set the due date, priority, and subtasks.
- Use submissions for review. Each submission is versioned, and a reopen carries a stated reason.
- Give the client approver a Guest seat so they can review and approve what you assign to them.
Time is tracked per task, with elapsed time, pauses, and resumes, which feeds the utilization math in Step 3. You can see every screen on the product tour, compare plans on the pricing page, or start from the TechXaro One homepage and try it on one real client project. Whatever tool you pick, run that one project end to end before you move the rest.
Four mistakes that keep showing up
- Booking to 100 percent. One revision round and the week is broken.
- Letting small extras slide. They are the main reason realization falls.
- Giving the client five reviewers. Name one approver at kickoff.
- Reviewing numbers monthly. By then the overloaded person has already burned out. Look every Friday.
Frequently asked questions
Q. What is agency project management?
Ans: Agency project management is the practice of planning, assigning, and delivering work for several clients with a shared team. It covers scope, capacity, approvals, and budgets, because an agency’s main resource is employee time. The goal is on-time delivery, protected margins, and a team that isn’t stretched past its limits.
Q. How do you manage multiple client projects at once?
Ans: Give each client one project with a written scope, one delivery lead, and a named approver. Plan capacity per person before you accept dates, hold a weekly capacity check, and keep every task, file, and comment in one system. Clients see status without asking, and your team stops switching context to answer questions.
Q. How do you manage agency employees effectively?
Ans: Set one owner for every task, cap workload, and compare hours against capacity every week. Hold short 1-on-1s, give feedback inside the task, and watch overdue work, reopened tasks and late hours as early signals. People perform well when expectations are visible, and workload is realistic.
Q. What is a good utilization rate for an agency?
Ans: Most sources put agency billable utilization between 60 and 85 percent depending on role, with 75 percent a common target for delivery staff. Leads and account managers sit lower because they spend time on proposals and direction. Treat 100 percent as a warning sign, not a goal.
Q. How do you handle scope creep with clients?
Ans: Write scope and exclusions before work starts, then route every extra request through a change request with hours and cost. The client approves it in writing, and it becomes a new task. Absorbing small extras without logging them is how realization rates drop without anyone noticing.
Q. What is the best project management software for agencies?
Ans: It depends on your size and billing model. Look for time tracking on tasks, a workload view, client access that limits what each client sees, approval history, and reports. Test two or three tools on a real client project before you commit. TechXaro One covers these and offers a free trial based on your plan.
Q. How do you keep clients updated without constant meetings?
Ans: Send one written update a week with four parts: done, next, needed from you, and risks. Give the client guest access so they can check status themselves, and keep approvals in the task where the history is stored. Save calls for decisions.
Q. How do you prevent burnout on an agency team?
Ans: Cap active accounts and weekly tasks per person, protect non-billable time, and move work when anyone stays above 85 percent utilization for two weeks. Watch for late hours, reopened tasks, and slow replies. Fixing scheduling early costs less than replacing someone who left.
Where to start this week
You don’t need to adopt everything at once. Pick the client who currently causes the most stress, write their command sheet, and run the Friday health scorecard on them for four weeks. Add the weekly rhythm next. By the time you roll the system out to the rest of the agency, you’ll already know which parts your team will keep.
