How much can I actually take on this month?

Why an empty calendar overstates what’s available

A month with open slots on the calendar reads as available capacity, because an open slot is, visually, the absence of a booking. That reading skips a step: available for what actually gets billed, once the time that always disappears into overflow, admin and the unexpected is accounted for.

Nothing about an empty grid tracks that overflow, because overflow doesn’t show up as a booking — it shows up later, as work that ran long or a task that wasn’t on the calendar at all. The grid was never built to subtract for it.

What your formula actually accounts for

Say you’re a freelancer who plans month by month and use a specific formula: available capacity is the ceiling, minus whatever’s already committed, minus a fixed buffer. “The buffer is what keeps the month from breaking,” you say — without it, one delay anywhere cascades into everything after it.

This month’s calendar looks roughly half-booked, suggesting plenty of open capacity. Run through your formula rather than read off the empty slots, the real figure is smaller: “About 14 hours — the ceiling minus what’s committed minus your buffer, not the 40 the empty-looking calendar suggests.”

Why the buffer never shows up on its own

A general-purpose model asked how much room is left this month will count the open slots on the calendar and report that figure, because open slots are the visible, countable thing. It has no access to your buffer, since a buffer isn’t a booking — it’s a decision you made about how much margin the month needs.

That’s exactly the gap between 40 and 14: not a miscount, but a genuinely different question answered. “How many slots are open” and “how much can I actually take on” only produce the same number if there’s no buffer at all — and for you, there always is.

What the formula returns instead of the grid

Hold your formula where it can be run against the current month’s commitments, and “how much can I take on” stops being read off the calendar’s open slots and starts being calculated the way you actually decided it should be — ceiling, minus committed, minus buffer.

That’s the difference between an optimistic number and a usable one: not a smarter look at the grid, but the figure you would arrive at yourself if you ran the sums by hand every time a new offer landed.

An empty-looking calendar overstates real capacity because it never subtracts the buffer a freelancer decided the month needs; measured context runs the freelancer’s own ceiling-minus-committed-minus-buffer formula, so ‘how much can I take on’ returns the usable figure, not the optimistic one.

Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Read further

• Can I take this project? Against my capacity
• The capacity-planning review, through Unl
• The workload check, through Unl
• Am I overcommitted? Against my weekly capacity rule