Freelance capacity planning: how much client work can you take on?

Freelance capacity planning means checking whether the work you have promised, plus a proposed project, fits into the time you can actually deliver. Compare hours in each week before accepting another deadline. A quiet week next month cannot rescue a deadline that is already overloaded next Friday.

This guide gives you a small weekly calculation and an example you can adapt. The numbers are illustrative, not a recommended working week or a benchmark for every freelancer.

What should a freelance capacity plan include?

Start with three things: usable working hours, existing commitments, and the timing of the new work. Capacity is more than the number of clients on your list. One project requiring daily revisions can use more of your week than three projects waiting for feedback.

The Association for Project Management’s resource capacity framework considers time commitments, competing project demands, skills, and dependencies. Atlassian’s capacity-planning guide likewise compares workload with available time and skills. The worksheet below adapts those ideas to one person making a booking decision.

Calculate the hours you can commit

Use this calculation for each week the proposed project would touch:

Capacity for client delivery = usable working hours − business operations − contingency.
Room for a new project = delivery capacity − existing client commitments.

• Usable working hours: time you intend and are able to work, after leave, appointments, and other fixed limits. Start from your actual calendar.
• Business operations: bookkeeping, sales, proposals, and general administration. Count project-specific meetings and messages with that project instead, so you do not subtract them twice.
• Contingency: time held back for uncertainty. Choose it from recent experience and the risks in the work; there is no universal percentage that makes every schedule safe.
• Existing commitments: this week’s production, client calls, expected revisions, and delivery tasks for work you have already accepted.

If you regularly use all your contingency on predictable admin, move that time into business operations. A project buffer is more useful when you can distinguish uncertainty from work you already know is coming.

A worked example: can you accept a six-hour assignment?

Imagine an independent designer has 30 working hours available next week. They reserve seven for running the business and three for unexpected work. That leaves 20 hours for client delivery.

Illustrative one-week capacity calculation

Item	Hours
Usable working time	30
Business operations	−7
Contingency	−3
Capacity for client delivery	20
Existing client commitments	−12
Room before the new assignment	8
New assignment, including its call and revision allowance	−6
Unallocated delivery time after accepting	2

The assignment fits the hourly budget: 20 − 12 − 6 = 2 hours left. That is a reason to consider accepting, not a guarantee. Check that the six hours exist in usable blocks before the deadline and that the client can supply the inputs you need.

If the estimate is six to ten hours, run the calculation at ten as well. The result becomes 20 − 12 − 10 = −2. You could reduce the agreed deliverable, arrange a later deadline, or gather enough detail to narrow the estimate before promising the date.

Check the busiest week, not just the project total

Longer projects need a week-by-week view. In this second illustrative example, a freelancer appears to have enough time across three weeks, but the middle week is overloaded:

Illustrative demand across three weeks, in hours

Week	Delivery capacity	Already committed	New project	Remaining
Week 1	20	12	6	2
Week 2	18	10	10	−2
Week 3	20	14	4	2

The three-week total has two spare hours, yet Week 2 needs two more than are available. Moving two hours into Week 1 would resolve the arithmetic only if the work can happen earlier. If those tasks depend on an approval due in Week 2, the spare time is not interchangeable. Check project dependencies before moving work between weeks.

Turn the calculation into a booking decision

1. Define the deliverable. Record what the estimate includes: preparation, production, meetings, revisions, and handoff. An unclear request needs clarification before it needs a confident number.
2. Place the work in the relevant weeks. Reserve likely feedback and revision time, even when you cannot yet name the exact day.
3. Compare demand with capacity. Test a plausible higher estimate when the work is unfamiliar. Do not treat all tentative inquiries as confirmed work; track them separately until you make a commitment.
4. Resolve any overloaded week. Agree a different scope or date, move genuinely flexible work, or decline. Do not silently change another client’s commitment to make the numbers fit.
5. Confirm the assumptions. Tell the client when inputs are needed and what happens to scheduling if those inputs arrive later.

A practical reply might be: “I can deliver the agreed first draft on Thursday if I receive the final copy on Monday. If the copy arrives later, I’ll confirm the next available delivery date before starting.” Adapt the wording to the agreement and the actual work.

Keep the plan close to your tasks

In ProjectBook, keep delivery tasks with their projects and put scheduled work in the daily planner. Use task durations to represent your current estimates. Add the client-specific review and handoff tasks as well as the production work.

Keep the weekly capacity calculation in a simple note or worksheet and compare it with your schedule. This is a manual planning method: the article does not assume that ProjectBook calculates portfolio capacity or forecasts how many projects you should accept.

During your weekly review, update remaining estimates, move work only where its dependencies allow, and check the next booking before you promise a date. For more on organizing the work behind that decision, browse the project management guides.

Common capacity-planning questions

How many clients should a freelancer take on?

There is no useful universal client count. Compare the hours, timing, and coordination each client needs with the hours available in the same period. Set a client limit only after you understand the load those clients create.

Should I count work that is waiting for feedback?

Count the time you expect to spend following up, reviewing feedback, and making revisions when it is likely to occur. You do not need to count every waiting hour as work, but you do need room for the task that resumes when the feedback arrives.

What if I do not have reliable time estimates yet?

Use a range, write down the assumption, and compare it with completed work during your next review. Keep early commitments small enough that an estimate change can be discussed before it becomes a missed promise.

Once the available hours are clear, use the maintenance and project-work planning guide to allocate ongoing service requests alongside finite deliverables.