This article explains how task status works in LenGrowth and how specialist handoff moves through the task detail flow.

Use this article when:

Task status is the high-level state of the work. It tells you whether the task is queued, moving, complete, failed, or deprioritized.

The status labels that appear in the app include:

Some screens show the underlying values as filter options or menu items. For example, the company task page exposes:

These are the same workflow family of states, but the labels may change depending on whether the page is showing a summary, a filter, or a task detail menu.

Queued means the task exists and has been placed into the execution flow, but active work has not started yet.

You will see this label on task cards and in status menus. In the pipeline, queued items usually sit in the first stage.

Use this status when the task has been created but has not yet started execution.

In progress means someone or something is actively working on the task.

In the task detail view, this can correspond to the broader Active state with a more specific active status beneath it. The task detail menu also exposes Active directly.

This is the default state customers expect when the work is underway and no one is waiting for a blocker.

Waiting means the task is active, but it cannot move forward until the customer provides something.

In the task detail view, the active-status menu includes Needs Information. The label presented to customers is Waiting.

This is the most important status to watch when a task is stuck on the customer side. It usually means the task needs a reply, missing detail, approval, or another external input before execution can continue.

In review means the task is at the stage where someone is checking the output before it moves on.

In the task detail menu, the active-status submenu includes Needs Review. The customer-facing presentation can show In review.

Use this label when the work exists, but the next step is review rather than more production.

Done means the task has completed successfully.

The task detail view only allows a task to move to Done when the checklist or accepted result requirements are satisfied. In other words, the app does not treat completion as a simple click if the task still lacks proof.

This matters because the product expects completion to be visible and defensible, not just marked finished.

Failed means the task did not complete as planned.

The task card explains that failed tasks can be reopened and continued manually or routed into a fallback path. The failure state is not the end of the record. It is a signal that the work needs a different approach.

Not priority means the task is not the current focus.

The task detail menu also includes Not gonna do, which is presented as Dismissed in the status helper. That is the stronger version of deprioritization: the work is not just delayed, it is intentionally removed from the active flow.

Use these labels carefully. They are not the same as Queued or Waiting.

Pending appears in the general task status helper as a valid state.

It is a lower-information state than Queued or In progress. If you see it, the task still exists, but the workflow has not committed it to an active execution state yet.

Snoozed means the task has a future snooze time set.

The status helper checks whether snoozeUntil is later than the current time. If it is, the task is presented as snoozed and the task card explains the time it will return.

This is different from Waiting. A snoozed task is intentionally paused by time, not by missing customer input.

Handoff is what happens when the task moves from one kind of execution to another, especially when a specialist is involved.

In LenGrowth, specialist handoff can happen in a few different places:

The important part is that handoff is visible. It is not a hidden backend change. Customers should be able to see where the work is, who is responsible, and whether they need to contribute anything next.

When specialist support is involved, the task detail and pipeline can show a more detailed stage than the broad task status.

The specialist stages visible in the app include:

These stages help customers understand what is happening after the initial request.

For example:

These stages are especially useful in the task detail dialog and the pipeline view, where the product separates workflow progress from the broader task state.

Open the company task page at /companies/[id]/tasks and click the task card, or open the task directly from the pipeline.

The task card status chip gives you the current high-level state. That is the fastest way to see whether the task is queued, in progress, waiting, in review, done, failed, or snoozed.

In the detail dialog, look for the status control and the active-status submenu. This is where the more specific Needs Information and Needs Review states appear.

Some task cards show a Blocked badge. When that appears, the task is waiting on dependencies, not just general status.

If the task shows specialist request stages or specialist actions, the work is in the handoff portion of the flow.

The next step depends on the current state:

If specialist support is involved, the task should move through the request stages until it reaches Delivered or Completed.

Open the task detail view. The task usually contains the context, discussion, or specialist request that explains what is missing.

That usually means the work is done enough to inspect, but not yet closed. Review the result or accepted output before marking it complete.

If checklist items are still open or the task has not produced an accepted result, the task detail flow can block completion until the proof is ready.

Not priority means “not now.” Dismissed means “not part of the plan.” Use the stronger state only when the work is intentionally removed from the current flow.

Different views emphasize different layers of the workflow. The task list, pipeline, and detail dialog can all present the same work with slightly different labels.

If something does not look right, confirm you are using the correct account, page, and permission level.