Skip to content

Delegation

Managers split work into parts and hand each part to a worker below them, with acceptance criteria. Settings control how far and how wide delegation goes.

How it worksLink to How it works

  1. A manager splits its work into parts.
  2. Each part becomes a child work item for a worker, with its objective, requirements and acceptance criteria.
  3. Independent parts run at the same time. A part can wait for another part.
  4. The manager waits for all parts, checks each result against its criteria and reports up.

A question from a worker goes to its manager first. It reaches you only when the manager cannot settle it.

SettingsLink to Settings

An owner or admin changes these in the organization settings list on Settings. Each one can also be set for one department or one worker.

| Setting | Default | What it does |
|---|---|---|
| delegation.scope | Own subtree only | A manager delegates only to the workers below it. "Anyone in the org" removes this limit. |
| delegation.maxDepth | 5 | How deep a chain of delegations can go before a worker must ask a person. |
| delegation.maxChildren | 25 | Child items that one item may delegate. |
| delegation.fanOut | All independent parts at once | "One part at a time" hands out the next part only after the last one finishes. |
| coordination.overlap | Same worker, else wait | When two items will change the same files in one repository, the second goes to the same worker or waits. "Always wait" or "Off (run both)" are the other choices. |
| limits.inherit | Bounded by every manager above | A worker's budget and capabilities are limited by every manager above it. "Own limits only" removes this. |

See it liveLink to See it live

Observe shows each worker, its tools and its delegations as they run. See Observe.

Checked against the product on 2026-10-05.

Was this helpful?