Peak Hours Don't Announce Themselves: A One-Week Energy Audit for Small UK Firms

A hundred and sixty-eight hours land in your lap every Monday, and most calendars treat them as interchangeable. Nine o'clock, two o'clock, half four on a Friday — all just boxes to be filled. The trouble is that the brain doesn't work like that. It hands out sharp, fluent, problem-solving thinking in short bursts, and then it spends the rest of the week doing admin, replying to things, and staring at a spreadsheet with quiet resentment.

Most small firms schedule as though this weren't true. Meetings get slotted into whatever gap the calendar offers, deep work gets pushed to the end of the day, and the actual thinking — the stuff that grows a business — happens in the leftover minutes between calls. A one-week energy audit is a cheap way to find out what's really going on, and to do something about it without redesigning the whole company.

The myth of the interchangeable hour

You'll hear people say they're "not a morning person" as if it's a personality quirk. In practice it's closer to a scheduling problem. Almost everyone has a window where their concentration is noticeably better, a stretch where it dips, and a couple of hours where anything requiring genuine thought is a losing battle.

If your team's best hours are being spent on things a half-awake person could handle, you're effectively paying peak rates for trough work. That's the thing an energy audit exposes — not laziness, not bad attitudes, just a mismatch between the shape of the day and the shape of the work.

Three zones, not two

It helps to think in three bands rather than the usual "busy or free" distinction.

Peak is when a person can hold a complex problem in their head without losing the thread. Writing, planning, pricing, designing, diagnosing a client issue, reading something properly.

Trough is the post-lunch dip or the late-afternoon slide. Fine for replying to emails, filing, tidying the shared drive, chasing invoices, sorting the rota.

Red zone is the sneaky one. These are the hours that get filled by default — the 11am Tuesday slot that became a meeting simply because it was empty, the Thursday 4pm catch-up nobody can quite remember agreeing to. Red zone hours aren't necessarily low energy. Often they're decent hours that got colonised before anyone thought about it.

Running the audit

Keep it small. Anything elaborate will collapse by Wednesday.

Ask each person, for one working week, to score each chunk of the day from one to five on a single question: could I do my hardest thinking here today? Split the day into four blocks — early morning, late morning, early afternoon, late afternoon — and add a column for what they actually did.

Three minutes at the end of each day is enough. A shared spreadsheet works; so does a paper grid stuck to the wall of the office kitchen. Anonymity is optional, but honesty is not, and people are more honest when the exercise is framed as a design problem rather than a performance review.

Add one extra column at the end of the week: which meetings did you sit in that could have been an email, a note, or nothing at all? That column is where the useful arguments usually come from.

What small UK firms tend to find

A six-person architectural practice in Bristol ran something like this last year and discovered that its two most productive hours — mid-morning, Tuesday to Thursday — were almost entirely consumed by client calls that could have been batched into one afternoon. The design work was being done at 5pm by people who'd been on the phone since nine.

A fourteen-person accountancy in Manchester found the opposite problem: everyone's peak was different. Two partners did their best work before eight, three of the juniors didn't get going until half ten, and the post-lunch slot was a write-off across the board. The fix wasn't a company-wide rule; it was staggered starts and a shared understanding that 1pm to 2pm was for anything that didn't need a brain.

A Leeds e-commerce team of nine discovered their red zone was Friday afternoon. Nothing important happened there, but three recurring meetings had drifted into it over eighteen months, and nobody had ever asked whether they needed to exist.

The red zone is usually nobody's fault

It's worth saying plainly that the red zone isn't created by villains. Calendar tools sort by gap, not by capacity. When someone needs to book a meeting and sees an empty hour, that hour looks like availability. It doesn't announce that it's the only clear stretch the operations manager has for planning the quarter.

That means the solution is rarely "be more disciplined". It's usually structural: make the peak hours visible, and make the default harder.

Protecting peak without pretending

A few things that tend to work in firms of five to fifty people:

• Identify the one or two hours most of the team shares as peak, and move standing meetings out of them.
• Declare a shared deep-work window — Tuesday to Thursday, say, 9:30 to 11:30 — and hold it for a trial month.
• Batch client calls into afternoons rather than scattering them across the week.
• Put a short note in the calendar entry for protected blocks explaining what they're for, so colleagues know it's work and not a day off.
• Keep recurring meetings on a six-month leash. If nobody can say what it's for, it goes.

And be realistic. You are not going to reclaim twenty hours. If a team of ten recovers four to six genuinely useful hours a week between them, that's a meaningful gain and it won't collapse under its own ambition.

The honest limit

The point of an energy audit isn't to pretend that every hour should be sacred thinking time. Plenty of necessary work belongs in the trough: invoicing, compliance paperwork, tidying the CRM, sorting out the stationery order. Those hours aren't wasted; they're just misused when they're spent on things that need a clear head.

What the audit really does is put a number on something people already sense. Once you can see that Thursday at 4pm is nobody's friend, moving a meeting out of it stops feeling like a strange request and starts feeling like basic housekeeping.

Run it once. Look at the grid. Move two things. Then get back to work — ideally in an hour when your brain is actually on.