Am I about to overbook myself? A verdict

Why billable hours alone understate the week

Checking a new booking against the billable hours already committed feels like the right maths, and it’s incomplete maths. A week also holds travel to a client site, invoicing, admin, the overhead that comes with running a freelance business — none of it billable, all of it real time.

A calendar that only tracks billable hours will happily confirm a new booking fits, because by its own accounting there’s room. The room disappears the moment the hidden hours are added back in, and by then the booking is already confirmed.

What your full ceiling actually counts

Say you’re a freelancer juggling several clients and have fixed your ceiling to include everything, not just billable time: no week may exceed the line once travel and admin are counted too. “The hidden hours are what tip it,” you say — the billable total was never the number that mattered on its own.

A new booking this week looks fine against billable hours alone. Measured against your full ceiling rather than the billable total, the verdict changes: “About to — the new booking tips next week to 34 hours once admin is counted, over your ceiling.”

Why the hidden hours stay invisible without a rule

A general-purpose model asked whether the new booking fits will check it against whatever billable schedule it’s shown, because that’s the visible, structured part of the week. It has no access to your admin and travel estimate, or the rule that counts those hours toward the same ceiling.

That gap is exactly where an overbooked week gets confirmed by accident — not through carelessness, but because the check that would have caught it was never actually being run, only a narrower one that flattered the total.

What a full-count ceiling returns

Hold your ceiling counted your way — billable plus the hours around it — and every new booking gets checked against the real total, not the one that only looks at client-facing time.

That’s the difference between a ceiling that sounds sensible and one that actually holds: counting every hour that fills the week, the way you decided it should be counted, not just the part of the week a client would see on an invoice.

A ceiling that only counts billable hours misses the admin and travel time that actually fills a week; measured context applies the freelancer’s own full-count rule, so a new booking is checked against the real total, not a flattering one that ignores the hidden hours.

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

• Am I overcommitted? Against my weekly capacity rule
• Should I say yes to this client? Against my capacity rule
• The workload check, through Unl
• Why you realise you’re overcommitted weeks too late