What to Do When You Have More Work Than You Can Take

Published July 29, 2026

Disclosure: Some links below are affiliate links. If you sign up through them we may earn a commission at no extra cost to you. We only recommend tools we'd genuinely suggest to a friend. See our full disclosure.

Almost everything written for freelancers and solo business owners assumes the same thing: that you need more work than you have. How to find clients, how to write the cold email, how to get the proposal accepted, how to fill the pipeline. It is reasonable — that is where most of the anxiety lives.

Then one week the calendar tips the other way. Two projects overlap, a referral lands, an old client resurfaces with something urgent, and you are looking at a month you cannot actually deliver. And there is almost nothing written about that, beyond the unhelpful observation that it is a nice problem to have.

It is not a nice problem. It is a decision with a deadline attached, and it comes with a default answer that is almost always wrong: say yes to everything and absorb the difference out of your own evenings. This is what to do instead.

The quick version

• Get the real number before you decide anything. Overload is often a scheduling illusion — three deadlines in one week and a quiet month behind it. Look at the calendar, not the inbox.
• Name the shape: spike or ceiling. A spike is temporary and clears itself. A ceiling is structural and does not. They have nearly opposite correct answers.
• There are only five real responses: schedule it out, cut the scope, raise the price, hand it off, or say no. Everything else is absorbing it, which is not a response.
• Absorbing it is paid for by the client you already have, not by the new one. That is the cost nobody sees on the way in.
• Scheduling out a ceiling is the classic mistake. You end up booked four months ahead, which reads to good clients as unavailable.
• Say no fast, specifically, and honestly. A clear no this afternoon is worth more than a maybe that dies in two weeks.
• Do not stop marketing while you are full. That is how the famine after the feast gets built.

First, find out whether you are actually over capacity

Being swamped and being over capacity are different things, and they feel identical from the inside.

Swamped is a feeling generated by your inbox: several things due soon, several people waiting, and no clear picture of what is where. Over capacity is a fact about a calendar: the hours you have committed exceed the hours you have. It is very common to feel the first while the second is not true, and to make a permanent decision — turning down a good client, raising prices, hiring — on the strength of a bad Tuesday.

So before anything else, do the boring arithmetic once.

Write down the projects that are genuinely live, with their real deadlines. Estimate what each has left in hours — not the total, the remainder. Then write down the working hours you actually have between now and those deadlines, which is not the number of days times eight: take out admin, calls, the hours you lose to context switching, and the ones you will not get because life happens. Most people find their real delivery capacity is somewhere around half to two thirds of their working week, and the gap between that and the number they had in their head is usually where the panic was coming from.

Then compare the two numbers. Now you know which conversation you are having.

Two things fall out of this that are worth noticing. The first is that a good chunk of apparent overload is sequencing, not volume — the same work spread over six weeks instead of three would be perfectly comfortable, which means your problem is a scheduling problem and has a scheduling solution. The second is that if you cannot do this exercise in ten minutes, that is its own finding: a simple record of your projects and clients turns a recurring evening of dread into a two-minute look at a list.

Then name the shape: spike or ceiling

This is the fork the whole decision hangs on, and it is the one most people skip.

A spike is temporary. Two projects overlapped, a client moved their launch, one referral arrived at an awkward moment. It has a cause you can point at, and if you did nothing at all it would clear in a few weeks.

A ceiling is structural. Demand for what you sell, at the price you sell it, is reliably larger than the hours you have. Nothing is colliding; this is just what your business looks like now.

They feel the same in the week you are living through. The test is not how full you are — it is which direction your availability has been moving.

Look at your earliest realistic start date over the last three months. If a new enquiry could have started in two weeks, then four, then seven, the trend is the answer: that is a ceiling, and it will keep getting worse, because nothing in that pattern is self-correcting. If the date was fine, jumped this month, and has an obvious cause, that is a spike.

Why it matters is that the responses diverge almost completely:

• A spike is a timing problem, so timing solutions work: push work later, trim scope, borrow hands for a few weeks.
• A ceiling is a pricing and structure problem, and timing solutions actively make it worse. Every enquiry you push into the queue makes the queue longer. Eventually your standard answer is “I could start in four months,” which good clients read as unavailable — so they stop asking, the pipeline thins from the top without you noticing, and the ceiling finally breaks in the worst possible way: as a sudden quiet spell.

Treating a ceiling like a spike is the single most expensive mistake in this whole situation, and it is expensive precisely because it feels responsible. You are not turning anyone away. You are just booking further out. It looks like success right up until it looks like a drought.

The five real responses

When more work arrives than you can take, there are exactly five things you can do with it. Everything else is a variation on absorbing it.

1. Schedule it out

Give the work a real start date rather than a vague one, and put it in the diary.

This is the most under-used option, and it is the right one for most spikes. Clients are far more flexible about when than freelancers assume — what they cannot tolerate is not knowing. “I could start this on the 14th of next month and have it with you by the end of that month” is a completely acceptable answer to most enquiries. “Things are quite busy at the moment, let me see how the next few weeks go” is not, because it is not an answer.

Doing it well is mostly about being concrete:

• Give a date, not a duration. “About three or four weeks” starts an argument later about when the clock began.
• Do not hold a slot on goodwill. A booked slot without a deposit is not booked; it is a hope with a date on it. Take a deposit and it becomes real for both of you — the same logic that makes deposits standard in freelance contracts.
• Re-confirm before the slot arrives. A week out, check the brief still stands. Projects agreed two months ago change quietly, and the worst time to discover that is the morning you clear your desk for it.
• Keep the queue short. A queue is a scheduling tool, not a growth strategy. If it runs beyond a couple of months you have stopped managing a spike and started ignoring a ceiling.

If you are queueing more or less permanently, formalise it — a proper waitlist with a real date and a way to be notified is a much better experience than an inbox full of people wondering whether you have forgotten them.

2. Cut the scope

The enquiry that does not fit at full size often fits at a third of it.

Instead of asking “can I take this project?”, ask “what is the smallest version of this that would genuinely be useful to them?” A full site becomes the two pages that actually convert. A brand identity becomes the logo and the colour system, with the guidelines later. An audit becomes the first pass and a written list of recommendations they can act on without you.

This is not a discount. The price comes down because the work comes down, and the rate does not move — which is the distinction to hold on to, because clients will sometimes try to keep the scope and take the smaller number. Scope reductions are also the honest alternative when you want to make a yes easier: change what you deliver, never what you charge per hour of it.

The bonus is that small first projects are the natural start of a longer relationship. A client who has already worked with you once, on something small that went well, is the cheapest source of future work you will ever have — which is most of the argument for repeat clients as a strategy rather than an accident.

3. Raise the price

This is the only response that fixes a ceiling permanently.

If demand consistently exceeds your capacity, your price is below what the market will pay. Raising it reduces the number of enquiries that convert while raising the value of the ones that do — which is exactly the trade you want when hours, not leads, are the scarce thing. It is also the only lever here that improves your income rather than just rearranging your week.

Two honest caveats. First, it is a response to a ceiling, not a spike: repricing your business because of one collision month is how you end up quietly less competitive for a reason that evaporated. Confirm the pattern over several months. Second, a price rise is its own project with its own mechanics — when to do it, how to handle existing clients versus new ones, and what to say — and doing it badly costs more than doing it late. That is worth its own read: how to raise your prices, and if you have never set them deliberately in the first place, how to price freelance services comes before it.

A useful in-between if you are unsure: hold your price for existing clients and quote new enquiries higher. You learn what the market pays without touching a single relationship, and if the higher number keeps getting accepted you have your answer.

4. Hand it off

There are two versions of this and they are not remotely the same.

Referring means the client works with someone else directly. You are out of it — no margin, no liability, no management. It costs you nothing but the introduction, and it is chronically under-used because it feels like giving away money. It is not: the fee was never available to you, because you could not do the work. What you get instead is a client who remembers that you solved their problem when you could not take their money, and someone else in your field who now owes you one. Refer to a named person you would actually vouch for, ask that person first, and tell the client plainly what you are doing and why.

Subcontracting means you keep the client and pay someone to do part of the work. This is a real option and a much heavier one than it looks, because you have not removed a job — you have swapped a delivery job for a management job, in a week that was already full. It works when the piece is well-specified and repeatable enough that you could brief it in writing, when the margin is big enough that paying someone properly still leaves you a sensible return, and when a wobble would not damage a relationship you care about. It works badly on the strategic core of the work, on vague briefs, and on anything you have never documented.

If subcontracting keeps coming up, the thing that makes it survivable is written process — the same standard operating procedures that make outsourcing work at all. Briefing from a document is a different activity from briefing from memory, and only one of them saves you time.

Whichever version you choose: tell the client. Discovering after the fact that their work went to someone they never met is the kind of surprise that ends relationships.

5. Say no

Sometimes the work does not fit at any date, any size, or any price, and the correct answer is a clean no.

A no that keeps the door open has three parts, and skipping any of them is what makes people dread sending it:

1. A clear no. Not “I might be able to,” not “let me see.” The word itself, early in the message, so they can start solving their problem.
2. An honest reason that is about your capacity, not about them. “My schedule is full through October” is true, impersonal and impossible to argue with. Invented reasons are a bad idea for the ordinary reason that you will have to remember them. (If the real reason is fit rather than capacity, “this isn’t the right fit for me” is just as complete an answer and needs no evidence attached — declining on fit is a separate decision with its own signals.)
3. One specific alternative. A date you could start, a name you would trust, or the smaller version of the job that would fit. This is the part that turns a rejection into a useful reply.

And send it fast. The kindest thing about a no is its timing: a client who hears no today can go and find someone else this week. The same no after ten days of silence has cost them ten days and cost you the relationship anyway — you have simply become the person who went quiet, which is exactly as frustrating from their side as it is from yours.

Vague softening is the trap here. “Maybe later in the year?”, sent because a flat no feels rude, leaves the client holding an answer you have already made and checking in politely for a month.

What absorbing it actually costs

The default response — take it, say nothing, find the hours somewhere — deserves a name, because it is a decision and not a neutral state.

The cost does not land where you expect. You are not, in practice, paying for the new project with spare capacity, because there was none. You are paying with the work you already promised. The existing client’s deadline slips — and if it does, say so early rather than hoping to catch up quietly, because a slip you announce is a scheduling change and a slip they discover is a broken promise. Or their draft gets one pass instead of three, or the small thoughtful improvements you would normally make quietly stop happening. They rarely complain, because they cannot see the version of the work they were supposed to get. They just do not come back with the next thing.

The second cost is the one that compounds. Weeks of over-commitment do not resolve into a triumphant catch-up; they resolve into the flat, resentful exhaustion that ends most solo businesses — not through a dramatic failure but through a slow decision to stop. That is not a motivational point, it is a scheduling one: capacity you borrow from yourself gets repaid with interest, and burnout is what the interest is called.

Absorbing it is occasionally the right call — a genuinely exceptional client, a genuinely short overlap, eyes open. The rule is simply that it should be a decision you made rather than the one that happened because you did not answer the question.

There is also a cost with a delay on it that almost nobody anticipates: a heavy month is a month of hours and expenses spent before any of it turns into money, so the tightest week in your bank account frequently arrives one or two months after the busiest stretch you have had. That timing is exactly wrong for spotting it, because by then everything feels like it is going well — see freelance cash flow for why the good months are the ones that open the gap.

If you have to cut, cut the right things

When the arithmetic says something has to go, the instinct is to drop the smallest invoice. That is usually the wrong filter.

Rank by margin per hour actually spent, not by invoice size. The five-figure project with endless revision rounds, three stakeholders and a weekly call can easily earn less per hour than the small fixed-scope job that runs itself.

Then adjust for drag — the unbilled work a client generates around the work. Long email threads, briefs that arrive in pieces, decisions that get remade, approvals that need chasing. Some clients cost several hours of overhead for every billable hour, and none of it shows up in the quote. If you are consistently at capacity, the overloaded calendar is often the point at which you notice you have been subsidising one relationship with all the others — which is the practical reason difficult clients matter commercially and not just emotionally.

Before you cut anything real, check how much of the load is work that is already finished. Projects that were delivered months ago but never formally closed keep generating small unpaid requests indefinitely, and they occupy attention out of all proportion to their weight. Closing them out properly — a stated end date, a support boundary, an offer of paid ongoing work — often frees more capacity than dropping a live client, and costs nothing.

Two more considerations, then decide:

• Strategic value. Some work is worth taking at a mediocre rate because of what it leads to — the portfolio piece, the sector you want to move into, the client whose recommendation carries. That is a real reason. It is only a bad reason when it is applied to every project.
• Payment behaviour. A client who pays reliably is worth more than one who pays eventually, and a full calendar is exactly the right moment to stop carrying the second kind. If chasing money is part of the drag, fix the invoicing process before you blame the workload.

Keep the pipeline warm while you are full

The most predictable mistake of a busy month is to stop marketing — no posts, no outreach, no follow-ups — because there is no time and no need.

The need is the part that misleads you. Marketing pays out on a delay: the enquiries arriving this week are the result of things you did weeks or months ago. So the month you stop is not the month it stops working. The gap appears later, precisely when you have finished the big project, cleared the decks, and are wondering why it has gone so quiet. That is the mechanism behind the feast-and-famine cycle, and it is not a demand problem — it is a self-inflicted supply gap.

The fix is not heroic. It is to define the smallest version of your marketing that you can keep doing on the worst week, and never drop below it. One genuinely useful post. One message to a past client. One update to the page that brings you enquiries. If you have documented and part-automated the routine parts, this survives a busy month easily; if it lives entirely in your head and your energy, it will not.

There is also a version of this worth checking while you are full, because a full calendar hides it: how much of the overload is one client. Being too busy because of three clients is a capacity problem, and everything above applies. Being too busy because of one is a concentration problem wearing a capacity problem’s clothes, and it calls for a different response — the issue is not the volume, it is that you have no room to say no to any of it. And if that one client also sets your hours, supplies your tools and expects you in their meetings, the question worth asking is not about capacity at all: it is whether the arrangement has stopped being freelance work in anything but name.

And use the busy period for the thing it is genuinely good for: evidence. A full calendar is the best possible moment to ask for a testimonial, take a screenshot of the finished work, and write down what the project involved while you still remember. That is next quarter’s client-finding material, gathered at the only time it is easy to collect.

Five mistakes worth avoiding

Deciding from your inbox instead of your calendar. The inbox measures how many people are waiting for you. The calendar measures whether you have the hours. Only one of those should drive a decision you cannot reverse.

Quoting a rushed price to make it fit. Under pressure, the temptation is to price the new job at whatever gets it out of the way. You will deliver that project during the worst month of your year at your worst rate, and remember it.

Treating a queue as a plan. Pushing everything two weeks further out works exactly once. Repeated for six months it produces a lead time that quietly disqualifies you from work you would have wanted.

Hiring or subcontracting at peak panic. The worst week of the quarter is the worst possible time to choose someone, brief them badly, and learn on a live project whether they are any good. If you want that option, build it before you need it.

Apologising instead of answering. Long, guilty, non-committal replies are the ones that damage relationships. Clients do not resent a no. They resent waiting for one.

The decision, in order

1. Do the arithmetic. Real remaining hours per live project against real available hours. Ten minutes, once.
2. Name the shape. Has your earliest start date been drifting away for months (ceiling) or did it jump this month for a reason you can point at (spike)?
3. If it is a spike, use timing tools. Schedule it out with a real date and a deposit, cut the scope to fit, or hand off a well-specified piece.
4. If it is a ceiling, change the structure. Raise your price, and be more selective about which work you take at the new one. Timing tools will not fix this and will hide it for months.
5. Answer everyone within a day, even if the answer is a scheduled slot or a no. Speed is most of the goodwill.
6. Cut by margin and drag, not by invoice size — and cut before quality slips, not after.
7. Protect the minimum marketing. Whatever you can sustain on the worst week, keep doing it on the worst week.

The bottom line

Having more work than you can take is not a reward, and it is not a crisis. It is a fork, and it stays open for about a week before it decides itself.

Find out whether you are genuinely over capacity or simply badly sequenced. Then work out whether this is a spike that will clear or a ceiling that will not, because scheduling out a ceiling is how a business that looks like it is winning ends up with a four-month lead time and a thin pipeline. Pick one of the five real responses and say it out loud to the client — a date, a smaller scope, a higher price, a name, or a no. Never pay for new work with the quality of work you have already promised.

And keep the small marketing habits running through the busy weeks. The whole point of handling a full calendar well is to stop the empty one that usually follows it — which is, in the end, the same skill as running the business rather than reacting to it.