Smart Tasks
A prioritised, per-profile task list so the team always knows what to do next.
A task list works when it is finite and can be completed, which is why an audit that produces sixty items generates no action while a shortlist of five, refreshed as they close, generates all of it.
What it does
There is a predictable failure that follows every thorough audit. Sixty findings arrive, ranked and colour-coded, and nothing happens. Not because the findings were wrong — they are usually correct — but because a list that cannot be finished offers nowhere obvious to start and no sense that starting would help.
The problem is one of completion rather than motivation. A person facing five tasks can see the end of them, and finishing produces the momentum that gets the next five started. A person facing sixty cannot see an end, so the list becomes something to feel guilty about rather than something to work through, and it is quietly abandoned around week three.
The fix is unglamorous: cap the visible work. Show a small number of items, chosen by what they are costing rather than by what is easiest, and only reveal the next ones as the current ones close. The full inventory still exists — it is simply not what anybody is asked to look at.
This also imposes a useful discipline on prioritisation. When only five things can be shown, the question of which five stops being rhetorical, and the answer has to be defended by something. That is a considerably better position than a ranked list of sixty where everything is technically prioritised and nothing is actually chosen.
Everything Smart Tasks gives you
Capped visible list
A small number of open items, with the rest held back.
Cost-based selection
Items chosen by what the gap costs rather than by how quickly it closes.
Refill on completion
The next item appears as one closes, keeping the list finite and moving.
Per-location queues
Each location with its own short list rather than one estate backlog.
Completion history
What was done and when, which is what makes progress demonstrable.
Effort estimate per item
So a short list is not silently full of long jobs.
Blocked-item handling
Work that cannot proceed set aside explicitly rather than clogging the list.
Recurrence for standing work
Tasks that return on a cycle rather than being closed permanently.
Throughput reporting
Items closed per period, which is the measure of whether any of this works.
From setup to first result
- 1
Generate the full inventory
Everything the audit found, kept in the background.
- 2
Rank by cost
What the gap is costing, rather than what can be finished before lunch.
- 3
Show five
A number small enough to finish, which is the property that matters.
- 4
Refill as they close
So the list stays finite and continuously moving.
- 5
Estimate effort per item
Five long jobs is not a short list, whatever the count says.
- 6
Set standing work to recur
Some tasks are cycles and closing them permanently is a fiction.
- 7
Track throughput
Items closed per period is the only honest measure of whether the system is working.
What changes with Smart Tasks
- Presenting the whole audit as the task list
- Ordering by ease of completion
- Leaving blocked items in place
- Counting items rather than effort
- Closing recurring work permanently
- Finishable lists get worked
- Sixty findings is an inventory, not a plan
- Capping forces real prioritisation
- Effort estimates prevent false brevity
- Blocked work poisons a short list
Finishable lists get worked
A visible end produces momentum. A list of sixty offers none and gets abandoned.
Sixty findings is an inventory, not a plan
It is a correct description of the problem and no help at all in acting on it.
Capping forces real prioritisation
When only five can be shown, choosing which five becomes a decision that has to be justified.
Effort estimates prevent false brevity
A five-item list of week-long jobs fails the same way a sixty-item list does.
Blocked work poisons a short list
An item that cannot proceed sits at the top and stalls everything behind it.
Throughput is the real measure
Items closed per period tells you whether the process works. List length tells you nothing.
What it measures
- Items open at once
- Items closed per period
- Median age of an open item
- Blocked items outstanding
- Inventory remaining
- Recurring tasks completed on cycle
What you get out of it
Work that gets done
Finite and finishable.
Genuine prioritisation
Forced by the cap.
Momentum maintained
Refill on completion.
Honest short lists
Effort estimated.
Nothing stalled
Blocked items set aside.
Demonstrable progress
Throughput recorded.
What Smart Tasks produces
Every output is exportable and white-label, with your branding and none of ours.
Active list
A small number of open items.
Full inventory
Everything found, held behind.
Effort estimates
Per item, so the list is honestly short.
Completion history
What closed and when.
Blocked register
Work that cannot proceed, and why.
Throughput figures
Items closed per period.
Who uses Smart Tasks
Manage every client profile from one place instead of juggling account access.
Push a change to every location and confirm it landed on all of them.
Hold a brand standard while letting franchisees maintain genuinely local detail.
Keep one profile complete and accurate without a weekly admin task.
Get more out of it
- Cap the visible list at a number that can genuinely be finished, and hold everything else back.
- Rank by what a gap costs, not by how quickly it can be closed, or the trivial permanently outranks the important.
- Refill as items close so the list stays finite and keeps moving.
- Estimate effort per item. Five week-long jobs is not a short list in any useful sense.
- Move blocked work off the list explicitly rather than letting it sit at the top and stall everything.
- Measure throughput rather than list length. Closed items per period is the only figure that means anything.
Presenting the whole audit as the task list
Sixty items is an accurate inventory and a guaranteed way to produce no action at all.
Ordering by ease of completion
The quick items permanently outrank the expensive ones, and the expensive ones are the point.
Leaving blocked items in place
They sit at the top, nothing moves behind them, and the list stops being trusted.
Counting items rather than effort
A short list of long jobs fails in the same way and for the same reasons as a long list.
Closing recurring work permanently
Some tasks are cycles, and marking them done once creates a gap that reopens quietly.
Manually vs with Smart Tasks
| Doing it manually | With Smart Tasks |
|---|---|
| Sixty findings presented at once | A capped, finishable list |
| Ordered by ease | Ordered by cost |
| Static list | Refilled as items close |
| Item count only | Effort estimated per item |
| Blocked work in the queue | Blocked work set aside |
| Progress by list length | Progress by throughput |
- Generate the full inventory in the background
- Rank by cost rather than ease
- Cap the visible list at about five items
- Estimate effort for each one
- Refill automatically as items close
- Move blocked work off the list
- Report throughput per period
Smart Tasks is 1 of 42 tools you get
Every tool below is on the same plan at the same price. Nothing here is an add-on, an upgrade, or a separate subscription.
Rank & Visibility
Manage Profiles
Posts & Automation
Reviews & Reputation
Reports & White-Label
Others vs Local Rank Checker
How the usual pricing and packaging in this category compares with ours.
“Other tools” describes the common pattern across the category, not any one named product.
Smart Tasks is included on every plan
One flat price per location covers all 42 tools. There is no higher tier, no add-on, and no per-seat charge.
- All 42 tools on every plan
- No per-seat charges
- No setup fee and no contract
- Cancel or change locations any time
Smart Tasks questions
Why not show every finding?
Because a list that cannot be finished offers no obvious start and no sense of progress, and it is abandoned within a few weeks.
How many items should be visible?
Around five. Small enough to finish, which is the property that makes any of it work.
Should items be ordered by how quick they are?
No. Ease-ordering means the trivial permanently outranks the expensive, and the expensive items are the ones that matter.
What happens to the rest of the audit?
It stays in the inventory and appears as items close. Nothing is discarded, it is simply not what anybody is asked to look at.
Why estimate effort?
Because a five-item list of week-long jobs is not short. Counting items without weighting them produces the same failure in a smaller package.
What about work that cannot proceed?
Move it off the list explicitly. A blocked item at the top stalls everything behind it and the list stops being trusted.
How is throughput measured?
Items closed per period. It is the only figure that says whether the process works; list length says nothing.
Should each location have its own list?
Yes. A single estate backlog is exactly the unfinishable list this is designed to avoid.
What about recurring work?
Set it to recur. Closing a cyclical task permanently creates a gap that reopens without anyone noticing.
Who decides the order?
The cost ranking proposes it and a person confirms it. The cap is what makes that confirmation a real decision.
How often should the list be reviewed?
Weekly. Long enough for items to close, short enough that a blocked item does not sit for a month.
Does this replace an audit?
No. The audit produces the inventory. This is the mechanism that turns an inventory into work that actually happens.
What if nothing gets closed?
Then the items are too large, blocked, or unowned. Throughput near zero is a finding about the process, not about the list.
Can tasks be assigned to people?
They should be. An unowned item on a short list is the most common reason a short list stops moving.
What is a reasonable throughput?
It varies entirely. What matters is your own figure and whether it is stable, since a falling rate is the early signal.
Should clients see the task list?
Usually the completion history rather than the open list. Finished work is evidence; open work is a plan.
How does this relate to profile optimisation?
Optimisation finds what is missing. This decides what gets done about it and in what order.
What if everything genuinely is urgent?
Then rank by cost and accept the order. A list where everything is urgent is a list where nothing is prioritised.
Does capping mean slower progress?
The opposite, in practice. Finishable lists get worked and unfinishable ones get abandoned, so the cap raises throughput.
What is the single most useful rule?
Never show more than can be finished. Almost every abandoned improvement programme violated exactly that one.
Every tool. One price. No add-ons.
$5.33 per location per month gets you Smart Tasks and the other 41 tools.