Is This Task Delegable?
Four questions about one recurring task you already have. The rules are published below the form — every combination of answers resolves to exactly one outcome, so you can reach the same result by reading rather than clicking.
Most delegation advice starts after the decision. This is the check before it: one recurring task you already carry, four questions, one stated outcome.
The four questions are not arbitrary. They are the conditions the underlying position already names — the task shape that suits a standing job, the kinds of work that never do, whether the criteria can be stated in advance, and whether the value compounds through repetition.
What this does not claim
- A result here is an orientation, not an approval to proceed.
- This does not assess any specific vendor, model, or product.
- This does not claim all work is suitable for delegation, nor that responsibility can be transferred to a system.
- This is not legal or compliance guidance.
Answer every question to see the result.
The rules this applies
Deterministic and complete: every combination of answers resolves to exactly one outcome below. Read them and you can reach the same result without the form.
- If
needs_human_judgmentis True → Keep this one. It is human work. escalate to a person - If
recurring_shapeis False → Not an agent slot as written — reshape it into something watched, remembered, or noticed. - If
criteria_explicitis False → Delegable only once you can state the criteria in advance. - If
payoff_repetitionis False → Delegable, but the payoff is thin — this is one answer, not a standing job. - If any remaining case → This is an agent slot. Set it up with a stated boundary and a named owner.
What this tool will not decide
- Work needing continual clarification, creative leaps, taste judgments or emotional intelligence sits outside this shape regardless of how capable the system is — so a person decides this case, not a checklist.
Machine-readable rules: /tools/is-this-task-delegable.json