Break one step into tickable subtasks

Some steps are really several small actions. Add subtasks and your team gets a short, tickable list right inside the step — so nothing in the “obvious” part of the work quietly gets skipped.

Start your free trial. No credit card required.

Prep the conference room Step
Test the projector and screen share
Completed by Dana Ruiz · 8:42am
Lay out handouts and name cards
Completed by Dana Ruiz · 8:47am
Set out water and coffee
Dial in the video bridge 10 minutes early

Detail without a wall of steps

You could split every little action into its own step — but then a five-minute task reads like a twenty-step procedure. Subtasks keep the step list clean while still spelling out the small moves inside a step, so newer teammates know exactly what “done” means.

One big vague step
  • “Prep the room” — and hope everyone remembers what that means
  • The little things get skipped under time pressure
  • No way to see which parts actually got done
One step, a few subtasks
  • Each small action is spelled out and tickable
  • Optionally, none of them can be skipped
  • Every tick shows who did it and when

From workflow template to ticked-off run

1

Add subtasks to a step

Open any step in your Workflow, add a subtask, type its title, and add more. Drag to reorder the list until it reads the way the work actually happens.

2

Start a Run

Every time you run the Workflow, that step arrives with its own fresh copy of the subtasks — ready for this run, unchecked and waiting.

3

Tick them off

Whoever is working the step checks each subtask as they go. If you want, the step can't be marked complete until the whole list is done.

Make the whole list a requirement

Flip on Require list completion before completing step and the step becomes a real gate: it won't complete until every subtask is checked. Try to finish early and Manifestly stops you with a clear reason instead of letting a half-done step slip through.

  • Set it per step — require the list on the steps that matter, leave it optional elsewhere.
  • The same rule guards approval steps: an approver can't sign off with subtasks still open.
  • Leave it off for a gentle guide the team can tick at their own pace.
Verify shipment Require list
Match packing slip to the order
Photograph any visible damage
Log serial numbers into the record
Complete step Complete all required subtasks first

Every tick is on the record

A subtask isn't just a checkbox that flips — when someone checks it, Manifestly stamps who completed it and when. Completed items show struck through with a completion note, and each check, un-check, and edit is captured in the run's activity. Un-check a subtask and it drops back onto the list, no drama.

  • Completion is attributed to the exact person who ticked it.
  • Timestamps and edits land in the run activity feed for a clean audit trail.
  • Titles auto-link URLs and support the same tokens as your step content.
Run activity
Confirm customer contact details
Completed by Priya Shah · Mon, Aug 10, 9:14am
Send the welcome packet
Completed by Priya Shah · Mon, Aug 10, 9:15am
Schedule the 30-day check-in
Un-checked by Alex Kim · 9:20am

Subtask or step? A simple rule of thumb

Reach for a subtask when…

  • The actions all belong to one person, in one sitting.
  • You just need a reminder of the small moves, not separate tracking.
  • You want the step list to stay short and readable.

Reach for a full step when…

  • It needs its own assignee, due date, or approval.
  • It should capture data in a form field.
  • It gates later steps or drives conditional logic.

Check them off from anywhere

Subtasks aren't stuck in the browser. Tick them from Slack while you work, or complete them programmatically through the v2 API — the same endpoints AI agents use over MCP to work a run to plan.

Slacktick as you go v2 API & MCPcomplete · uncomplete Subtaskwho & when recorded
  • Complete or un-complete a subtask and the required-list gate updates with it.
  • Agents see the same list, titles, positions, and completion state you do.
# Mark a subtask complete on a run step
POST /api/v2/runs/812/run_steps/6/subtasks/42
{ "action": "complete" }

# → response records who and when
{
  "id":              42,
  "title":           "Log serial numbers",
  "completed_at":    "2026-08-10T09:15:04Z",
  "completed_by_id": 137
}

Where a subtask list earns its keep

Setup & prep steps

A single “get the space ready” step with the small checks folded in.

Test the A/V, lay out materials, set out refreshments — all ticked before the step closes.

Inspections & QA

A verification step that must not be finished with anything skipped.

Require the list so a shipment can't be signed off until every check is done.

Onboarding touches

The little welcome tasks that ride along with one bigger step.

Confirm details, send the packet, schedule the check-in — each attributed to who did it.

Subtasks, answered

A step is the main unit of a Workflow — it can have its own assignee, due date, form fields, approvals, and conditional logic. A subtask is a lightweight, tickable item inside a step: just a title and a checkbox. Use subtasks to spell out the small actions within a step without lengthening your step list.

Yes. Turn on Require list completion before completing step for that step. While any subtask is still open, the step can't be completed — Manifestly shows “Complete all required subtasks first.” The same guard applies to approval steps. Leave the option off and the list is an optional guide.

Yes. Each completed subtask records the user who checked it and the time they did, shown right on the item. Checking, un-checking, and edits are also captured in the run's activity feed.

You define subtasks once on a step in your Workflow. Each time you start a Run, that step gets its own fresh copy of the list to tick off, so completions in one run never affect another. Update the Workflow and future runs pick up the change.

Yes. Drag subtasks into the order that matches how the work happens; that order carries into every run.

Yes. You can tick subtasks from the Manifestly Slack integration, and complete or un-complete them through the v2 API — the same endpoints AI agents use over MCP. The required-list gate updates as subtasks change, wherever the change comes from.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Subtasks for Workflow Steps

With Manifestly, your team will Never Miss a Thing.