Back to blog
Guide

One More Hour A Week

Owners say they have no time, then spend six hours a week on work that could belong to somebody else or to nobody. A short audit that reliably finds the hours.

Where they actually are

Work that should belong to somebody else. Held onto because delegating it once costs more than doing it once. ⚠️ True for the first instance and false from the second onward — and the calculation never gets revisited.

Work that should not exist. The report nobody reads, the check that duplicates another check, the approval for something that has never been refused.

Interruptions that a decision would prevent. ⚠️ The same question, from different people, every week. Each answer takes two minutes; the pattern takes hours and is invisible because no single instance is large.

Work being done twice. Entered somewhere, then re-entered somewhere else. Nearly universal and nearly always unnoticed.

The audit

One week, no changes, a rough log. Not detailed — just what and roughly how long.

Then sort every line into four:

Only I can do this — genuinely, not by habit. Somebody else could, with training. ⚠️ The largest category, always. Nobody needs to do this. The second largest, and the fastest to act on. This would not happen if a decision existed. The recurring question.

Most operators find four to eight hours in the bottom three categories.

Acting on it

Start with "nobody needs to do this". No training, no handover, no risk. ⚠️ Stop it and see if anyone notices — that is the whole implementation.

Then the recurring questions. Each one is a decision that has not been made and written down. Make it once, write it once, stop answering it weekly.

Then delegation, one thing at a time. With the first instance done together, which is the cost that has been deferred all along.

Why it does not happen

The audit week feels like overhead. It is one week and it finds hours every month afterwards.

⚠️ And the honest reason: some of the work is comfortable. Familiar tasks are a refuge from harder ones. Worth naming, because that hour is the most expensive one on the list — it is doing the work of avoiding a decision.

What to do with the hour

Decide before you have it, or it fills itself with the same work.

⚠️ The hour that returns most is usually the one spent on the thing that has been deferred longest — a conversation, a price change, a supplier, a person. It has been deferred because there was no time, and now there is.

Three hours you already have

Work that migrated to you and never went back
Work that exists because a decision was never made
Work that is checking work you already trust

⚠️ The second is the largest and the least visible. Every undecided question becomes a recurring task for whoever is nearest.

Finding the second kind

"Am I doing this because it needs doing, or because nobody decided?"

⇒ Ask it of the three things you did most often last week.


The audit that takes one week

Every task over ten minutes: what, how long, could anyone else do it

⚠️ The third column is the whole point. The first two are just the cost of collecting it.

⇒ ⚠️ Do it for one week only. Longer and the recording becomes the work.


Handing something over properly

Show once, watch once, then leave

⚠️ Most handovers stop after the first step, which is why they come back. Watching once is where the actual transfer happens.

The part people skip

Tell them what "done" looks like, and who to ask. Without both, they will check with you every time — and you have not gained the hour.


Why the hour disappears again

1. It was never protected, only freed
2. The old task came back because nobody was told it moved
3. Something new expanded to fill it

⚠️ Three is inevitable unless the hour has a name in advance.   ⇒ Decide what it is for before you free it, not after.


What it should be for

Not admin      you will have more of that regardless
Not more shifts   you already work them
The thing that only you can do

⚠️ In most venues that is: talking to people. Guests, staff, suppliers. It is the work that has no deadline and therefore never happens.


Check after a month

Is the hour still there, and is it still doing what you named it for?

⚠️ If it is gone, do not re-run the audit — find which of the three reasons above took it. The audit will just give you the same answer twice.


Ask any operator what they would do with an extra hour a week and the answer comes immediately. Ask where the hour would come from and it does not.

The hours exist. They are in categories nobody examines because each individual instance is small.


Three to hold

Hours logged in the audit week, by category. ⚠️ Do it once a year; the answer changes.

Recurring questions answered more than twice. Each is a decision waiting to be written down.

Whether the freed hour went where you decided. Usually not, the first time.

Where the record has to sit

Double entry is the largest single hour-sink, and it exists wherever the same fact has to be written in two places. Whether that is your problem is answerable in one afternoon: follow one booking from enquiry to settlement and count how many times it gets written down.

tasteck keeps a booking, its dispatch, its payment, and its guest record on one thread, so the same fact is entered once.

The hours are not missing. They are in a category you have never counted, and each one is too small to notice alone.


Related reading

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days