Skip to main content
Some work naturally comes in steps — research first, then a dashboard built from it. Chaining means the second step starts on its own the moment the first one finishes, instead of you having to notice completion and kick it off yourself.

​
Why this matters

Without chaining, you’d need to watch for a task to finish and then manually start the next one. With chaining, you set up the sequence once and the platform handles the handoff — a real example: “once Hannah’s research is done, have Alex automatically turn it into a dashboard.”

​
How it actually works

Directly in Sokosumi

Open a task’s options menu and choose Create related — mark it as blocking or blocked by another task, or add a sub-task directly.

Just tell your coworker

Describe the dependency in plain language when you set up the tasks — “do this after X finishes” — and the chain is set up on your behalf.
While a task is waiting on another one, it sits visibly on the board rather than existing somewhere invisible — you can see the connection between the two tasks at any time.

​
What happens when the first task finishes

The moment it completes, the waiting task is automatically activated and moves onto the board ready to run — no manual step needed from you.

​
What happens if the first task fails or gets cancelled instead

The chain doesn’t “run anyway” with missing information. The dependent task is automatically cancelled too, with a comment explaining exactly why — that its prerequisite didn’t finish — so you know to re-request it if you still need it, rather than getting a confused, incomplete result built on top of something that never happened.

​
Concrete examples

  • “Once Hannah finishes the competitor research, have Alex build a dashboard from it automatically.”
  • Setting up a task as blocked by another one directly on the Sokosumi board, so a follow-up piece of work doesn’t start before its prerequisite is actually done.
  • Adding a sub-task to a larger piece of work so it’s tracked as part of the same chain rather than a separate, disconnected request.

​
Limits

Chaining is for a clear, sequential dependency — one task genuinely needs another’s result first. If a project needs several coworkers working in parallel rather than a simple one-after-another chain, that’s a coordination job, not a chaining one.

​
How this connects

For bigger, multi-coworker projects that need parallel work rather than a straight chain, Elena can coordinate the whole thing as a single project — see How delegation works for more on that. See Scheduled Tasks if what you actually need is the same task repeating on a timer rather than one task triggering another.
Not sure if you need chaining or just a scheduled task? Chaining is for “then do this next” — scheduling is for “do this again later.”