The pipeline shows how work moves through LenGrowth from queued to active, waiting, monitoring, and completed states.

Use the pipeline when you want to see the execution flow instead of a simple task list.

The pipeline is useful when:

If the task list tells you what exists, the pipeline tells you what is happening to it.

The page title is Execution Pipeline.

The description explains that the pipeline helps customers track specialist work as it moves through delivery stages, customer blockers, and completion.

At the top of the page, customers see:

The pipeline summary card shows counts for:

These are the main workflow buckets in the app. The page also uses Done to represent completed work.

The summary is useful because it gives a quick sense of whether work is stuck, moving, or already finished.

The pipeline itself is arranged as a horizontal board. The helper text says:

Drag horizontally to inspect the full pipeline.

Each bucket appears as its own column with a title, a description, a count, and a set of task cards.

When a bucket is empty, the page shows Nothing in this stage right now.

Each task card inside the pipeline shows a mix of:

The pipeline cards are more compact than the full task detail view, so they are best for scanning and triage.

The pipeline buckets are not just a flat list. They represent the flow of work through the system.

The visible bucket names in the company pipeline can include:

When specialist work is involved, the stage labels can become more detailed and reflect request stages such as:

This is the part of the product where it becomes clear that a task is not only a checklist. It is a workflow that can move between people, states, and review points.

If the page says you need to choose a workspace, use the company selector in the header first.

The pipeline is company-specific. If no company is selected, the page will not show the execution flow.

Read the Queued, Active, Waiting, and Monitoring badges before opening any cards.

This helps you spot bottlenecks immediately. A large waiting count usually means the next action is not more production work. It is customer input.

Use Search pipeline cards when you know part of a task title, summary, objective, or channel.

Search is helpful when the company has many tasks or when you are looking for a specific specialist handoff.

The filter controls are there to narrow the board without changing the underlying tasks.

The visible filters are:

Use them like this:

Click a task card to open the task detail dialog.

That is where you can inspect the task, review the discussion, see the specialist request, and update the state.

Use Create task when the pipeline has the right company selected but the work does not exist yet.

That button opens the same task creation flow used in the company task page.

When the pipeline is filtered, the page updates only the view, not the underlying data.

When you open a task card, you move from the pipeline into the task detail dialog.

When you create a task, the new work should appear in the pipeline once it is part of the company’s execution flow.

When work moves into waiting or monitoring, it usually means the next action belongs either to the customer or to a post-delivery review.

If the page says No pipeline items yet, that means the company does not yet have work moving through the execution flow.

The pipeline needs a selected company. Use the company selector in the header or create a company first.

Use the Stage filter instead of searching manually. That is the fastest way to focus on one part of the pipeline.

Waiting usually means the task needs input before it can move forward. Open the task detail dialog to see the missing context.

Some views emphasize different workflow states. A task may be easier to find in the task list or the task detail dialog depending on its current status.

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