Customers can create tasks from the company task list, from the company pipeline, or from the dedicated create-task route.

Use the task creation flow when:

If you are only trying to review existing work, open the company task list instead of creating a new task.

In the Create task modal, the first option is Use suggested tasks.

This path is for customers who want to review work LenGrowth already prepared for the company. The panel explains that the suggested tasks are already live and that the user should review them in the task list or pipeline before starting a duplicate.

Use this path when the task probably already exists in some form and you want to avoid creating a second copy.

The second option is Write a task.

This opens the guided setup used for custom tasks. The modal describes it as a way to create a manual task with measurable targets and structured guidance. If the current plan does not allow more custom tasks, the modal tells the user that directly before they continue.

Use this path when you need to create something specific that LenGrowth did not already prepare.

Open the company task list at /companies/[id]/tasks.

If you want the direct create route, use /companies/[id]/tasks/create.

On the tasks page, the main actions are:

The New task button only appears when the user has permission to create tasks for that company.

When the Create task modal opens, choose between:

If you choose suggested tasks, the modal sends you back to the task list or pipeline so you can review existing work.

If you choose Write a task, the modal opens the guided custom wizard.

The custom task wizard is organized into four steps:

The step indicator is visible at the top of the modal, and the current step can only move forward when the required fields are filled in.

The first step asks for:

The title should name the work clearly.

The task type should match the kind of work you are asking for. The dropdown shows the allowed task types for the account.

The description should explain what needs to be done and why it matters. This field needs to be specific enough to stand on its own when someone opens the task later.

The second step is optional, but useful.

It includes:

Use this step when the task depends on a larger business story or when the target audience affects how the task should be done.

The third step covers delivery details:

Priority lets you choose High, Medium, or Low.

Due Date opens a calendar and shows Pick a date until a date is selected.

If you check Request Specialist immediately, the task is flagged for review and assigned to a human specialist after creation.

If you check Recurring task, the wizard reveals frequency controls. The visible options are:

The Dependencies section lets you search existing tasks and select any tasks that must finish before this one can begin.

The fourth step asks for the success criteria.

In the simple mode, the field is Definition of Done * and the placeholder explains that each line becomes a separate checklist item.

There is also an advanced mode. When that mode is enabled, the wizard lets you build checklist items one by one and add details such as:

The wizard also includes an Expected Outcome field so the task can describe what measurable impact the work should have.

When the task is created, LenGrowth saves it to the selected company and then refreshes the task data.

If you requested a specialist immediately, the task also gets a specialist request after creation.

After that, the new task should appear in:

That means the task is not only stored, it becomes part of the visible workflow right away.

The title, type, and description matter most. If those are vague, the task will be hard to understand later, even if the form technically saves.

Always confirm the company context before creating the task. The task belongs to the company route you opened, so creating it in the wrong company will make the rest of the workflow confusing.

Use suggested tasks is for reviewing and opening existing work. It is not the same as creating a custom task.

If the button is not visible, the current user may not have permission to create tasks for that company.

The wizard will not let you continue unless the definition of done is clear enough. That is intentional, because the task needs a visible finish line.

If the task depends on other work, add the dependency in the wizard. That keeps the execution order clear.