Skip to content
ELFBRIX

Open task and blocker sweep

Stuck work found the same day, not when a customer complains. One short list each morning of what's stuck and who needs to act.

ELFBRIX elf handling open task and blocker sweep for operations

Hours back

3

hours a week back, typically

How it runs

What we build, step by step.

This is the usual shape. Yours gets built around how your team actually does the job.

  1. 01

    Every channel read on a schedule

    The shared inbox, team chat and open jobs in your job software, checked each morning for anything new or unanswered.

  2. 02

    One task list kept current

    New requests are added with their source attached. When the work shows up as done somewhere else, the task is marked for closing with the evidence shown.

  3. 03

    Waiting versus blocked sorted out

    A tag for information isn't a request. A direct question left unanswered past a day (or past your own limit) counts as a blocker and is grouped by who's waiting.

  4. 04

    Sorted by how loudly to tell you

    Routine updates are logged quietly and most things wait for the morning list. Only a few kinds of problem, like a customer job at risk today, trigger a message straight away.

  5. 05

    A morning list to the right people

    Each manager gets what's stuck in their area, with the person to chase and the original message linked.

Runs inGmailOutlookMicrosoft TeamsWhatsAppGoogle SheetsJobber

Shown with software we see a lot. If your team uses something else, we build it into that instead.

Built for your business

Same job, different business. We build yours.

Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.

  • Your steps

    Built around the order your team already works in, odd exceptions included.

  • Your software

    Runs inside the tools you already pay for, set up the way you use them.

  • Your rules

    Your wording, your limits, your sign-offs. Nothing generic goes out in your name.

You sign off

Your team keeps the final say.

Tasks are only closed after a person confirms them, at least until you trust its track record. You decide which problems are urgent enough to interrupt someone, and only a person can change that rule.

What it's worth

What those hours add up to.

3 hours a week, over 46 working weeks, is 138 hours a year. At $50 an hour, that’s

$6,900

back in the business, every year.

Typical, not promised.

Before and after

The job, before and after.

How it runs today

A request comes in by text, gets forwarded to an email, gets mentioned in the group chat, and then nobody owns it. The job board says one thing and the inbox says another. Stuck work only surfaces when a customer rings to complain.

What we build

  • Every channel read on a schedule
  • One task list kept current
  • Waiting versus blocked sorted out
  • Sorted by how loudly to tell you
  • A morning list to the right people

A month in

Requests stop falling between the inbox, the chat and the job board. Whoever's stuck gets found the same day, not the following week.

Decide what's worth an interruption

A system that tells you about everything gets ignored within two weeks. Before it goes live we sort every kind of finding into four levels: logged quietly, held for the morning list, a message to answer when you can, or an immediate interruption. Almost everything belongs in the first two.

The rule is written down and agreed with you, then tuned after the first couple of weeks. Every time someone says 'I didn't need to know that' or 'why wasn't I told', we change the rule, not the person.

One list beats five

The moment there's a second task list, things fall between them. You get one list where open work lives, and the inbox, the chat and the job board all feed into it.

FAQ

Does it read people's private messages?

No. The open task sweep only reads the shared channels and inboxes you choose to connect. Most businesses connect the office inbox, the team chat and the job software, and leave personal accounts out.

Will it close jobs that aren't really finished?

No. The sweep suggests closing a job with the evidence attached, and a person confirms it. Reopening anything it got wrong is one click.

Next step

Bring this one to a free live build.

Thirty minutes on open task and blocker sweep. We build its elf with you, live, and you keep it.