Create a custom task
You can create a custom task from https://lengrowth.com/companies/[id]/tasks/create, or from the "New task" action on the company task list at https://lengrowth.com/companies/[id]/tasks.
When to use this
Use the custom task flow when:
A company needs a specific deliverable that was not generated automatically
You already know the goal and want to define it clearly
You want to attach a due date, recurrence, or dependencies
You want to request specialist help immediately after the task is created
You need a checklist or a more detailed definition of done
If you are still deciding what work should exist, open the company workspace first and use "Run Growth Diagnostics" or "Request an Initiative" before creating anything manually.
Step-by-step
The create flow is split into two entry paths:
"Use suggested tasks"
"Write a task"
If you choose "Use suggested tasks", LenGrowth does not ask you to build a brand-new task from scratch. It points you back toward the tasks that already exist for the company so you can review them in the task list or pipeline.
If you choose "Write a task", LenGrowth opens a guided setup flow. That flow is the one you use when you already know what needs to happen and want to turn that into a structured task.
Click "New task" if the button is available.
Or open https://lengrowth.com/companies/[id]/tasks/create directly.
Choose whether you want "Use suggested tasks" or "Write a task".
If your plan or permissions do not allow manual task creation, LenGrowth will show a notice in the dialog and may disable the guided setup button.
Pick "Use suggested tasks".
Read the note that says the suggested tasks are already live.
Open the tasks list or the pipeline to review what is already available.
This path is best when you want the next best move quickly and do not need to define a new task.
Pick "Write a task".
Click "Guided setup".
Continue through the four-step wizard.
The custom wizard is the detailed path. It is where you define the task cleanly so someone else can act on it without guessing what you meant.
The first step asks for:
Title
Task Type
Description
These three fields are required. The page keeps the "Next" button disabled until the title is at least three characters long, a task type is selected, and the description is at least 10 characters long.
Use the title to name the task plainly. Use the description to explain what needs to be done and why it matters.
The second step is for business context and audience.
Business Context is optional
Target Audience is optional
Use this step when the task depends on earlier work, a current campaign, a particular segment, or a specific business constraint.
The third step controls execution details:
Priority
Due Date
Request Specialist immediately
Recurring task
Frequency
Interval
End date for recurrence
Dependencies
If you select "Request Specialist immediately", LenGrowth automatically flags the task for specialist review after creation.
If you enable "Recurring task", additional controls appear for frequency and interval. That is useful for work that needs to repeat on a fixed schedule.
Dependencies let you tie the new task to existing tasks. Search the existing tasks list in the dialog and select the ones that must finish before this new task can begin.
The last step asks how success will be measured.
You can use either of two formats:
A simple one-line-per-item checklist
Advanced Mode with structured checklist steps
The simple format is the fastest way to create a checklist. Every line becomes a separate checklist item.
Advanced Mode gives you more structure. Each checklist step can include:
Step text
Quantifiable target
Tool suggestion
Tool URL
Instructions
Use Advanced Mode when the task needs a very explicit delivery standard or a particular tool reference. If a task has a complicated handoff, this format helps the next person avoid assumptions.
The wizard also asks for an Expected Outcome. Use that field to explain the measurable impact you want, not just the action itself.
The wizard is designed to keep bad task drafts out of the system. If something is missing, the form will stop you before you can proceed.
Typical checks include:
Title too short
No task type selected
Description too short
No definition of done
No checklist steps in Advanced Mode
That is intentional. A task that is too vague on creation usually turns into a slower handoff later.
Fill out Goal, Context, Assignment, and Definition of Done.
Review the recurrence and dependency settings.
Check whether "Request Specialist immediately" should be enabled.
Click "Create Task".
Wait for the success message.
Close the modal when LenGrowth confirms the task was created.
If the task was created successfully, LenGrowth closes the wizard and refreshes the task list for the company.
After creation:
The new task appears in the company task list
The task can appear in the execution pipeline
Any selected dependencies remain attached to the task
If specialist help was requested, the specialist workflow starts right away
If you created the task from the company create page, you can then go back to https://lengrowth.com/companies/[id]/tasks to review it in context.
If you asked for specialist help immediately, expect the task detail panel to show specialist-related delivery controls once the task is available.
Check the required Goal fields first. The most common causes are:
The title is too short
No task type is selected
The description is too short
That usually means manual task creation is not available on your current plan or in your current workspace state.
After creation, LenGrowth refreshes the company task list rather than leaving you on the form. That is normal. Open the task from the list or switch to the pipeline if you want to see how it is moving.
Double-check whether "Request Specialist immediately" was selected before you created the task. If it was not selected, you can request specialist help later from the task detail panel.
Common problems
The dependency search only shows existing tasks for the current company. Make sure you are on the correct company and that the task already exists in that workspace.
Related articles