> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluorine.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Create, Assign, and Manage Tasks Effectively in Fluorine
> Create tasks, build subtasks and dependencies, switch views, and keep work organized and moving forward.
Every task in Fluorine has a consistent set of fields — assignee, due date, priority, tags, description, subtasks, and dependencies — and a lifecycle that moves from To-do through Completed. Using these fields well keeps work clear, trackable, and free of the ambiguity that causes things to fall through the cracks.
## Create a task
Go to a project in the left sidebar, select the task list where the task belongs, and click **+ Add Task** at the bottom of the list.
Start with a verb. "Design the onboarding flow", "Review client feedback", "Fix payment redirect bug." A clear name means anyone on the team understands the work without opening the task.
Click **Assignee** and select a team member. One person per task. If multiple people need to be involved, use subtasks — each one can have its own assignee.
Click **Due Date** and pick from the calendar. Set **Priority** to one of four levels:
* **Urgent** — blocking other work, needs immediate attention
* **High** — important and time-sensitive
* **Normal** — standard work moving at a steady pace
* **Low** — backlog items or nice-to-haves
Priority levels feed into the workload view and AI daily digests — use them consistently.
Use the **Description** field for context: what needs to be done, why it matters, relevant links or references. A good description means the assignee can start immediately without asking clarifying questions.
Tags let you filter and group tasks across multiple projects. Use a consistent set — `bug`, `design`, `copy`, `client-facing`, `blocked` — rather than creating new ones for every project.
## Subtasks and dependencies
Complex work rarely fits in a single task. Use subtasks to break work into smaller steps and dependencies to enforce the order things must happen.
### Subtasks
Open a task and click **+ Add Subtask**. Each subtask is a full task with its own assignee, due date, and status. When all subtasks are complete, Fluorine marks the parent task as ready to close.
Use subtasks for parallel workstreams within a single deliverable. A "Launch campaign" task might have subtasks for copywriting, design, scheduling, and approval — each assigned to a different person.
### Dependencies
A dependency tells Fluorine that one task must be completed before another can start.
1. Open the task that is blocked
2. Click **Dependencies → Add Dependency**
3. Search for the blocking task and select it
Fluorine highlights dependencies in Timeline view and flags overdue blockers creating problems downstream.
Circular dependencies — Task A depends on Task B, which depends on Task A — are flagged and prevented from being saved.
## Task states
| State | Meaning |
| --------------- | --------------------------------------------------------------- |
| **To-do** | Not started. |
| **In progress** | Actively being worked on. |
| **Completed** | Done. Fluorine records the completion timestamp. |
| **Overdue** | Past its due date and not yet completed. Flagged automatically. |
Change state by clicking the status indicator in the task list or inside the task detail view. Overdue tasks are highlighted in red across all views.
## Views
Use the view selector at the top of any project or task list to switch between them.
A flat, scannable list sorted by status, due date, or priority. Best for day-to-day task management and quick status checks.
Kanban columns for each task state. Drag tasks between columns to update status. Best for sprint planning and visual workflow management.
Tasks on a calendar grid by due date. Best for spotting scheduling conflicts and planning across a month.
Gantt-style view showing durations and dependencies. Best for project planning and communicating schedules to stakeholders. **Pro and Business plans.**
How many tasks each team member is assigned over a given period. Spot overloaded teammates and rebalance before deadlines slip. **Business plan.**
## Custom fields
On the **Business plan**, add custom fields to capture information specific to your workflow.
1. Open **Project Settings → Custom Fields**
2. Click **+ Add Field**
3. Choose a type — Text, Number, Date, Dropdown, Checkbox, or URL
4. Name the field and set default values if needed
Custom fields appear in task detail views and are fully searchable. Common uses: client name, contract value, review status, external ticket number.
Custom fields are defined at the project level and apply to all tasks within that project.
## Handling overdue tasks
Fluorine surfaces overdue tasks in the list view, the daily AI digest, and productivity insights. Don't let them accumulate. For each one, do one of three things:
* **Reschedule** — update the due date to a realistic timeline
* **Reassign** — if the assignee is blocked or overloaded, move it to someone who can act
* **Close** — if the work is no longer relevant, mark it complete or delete it
The most common causes are unclear ownership, missing dependencies, and unrealistic due dates. Fluorine's workload view helps you spot patterns so you can fix them in future sprints.
In List view, use **Filter → Status → Overdue** to see all overdue tasks across a project or workspace. Sort by due date to see the most delayed tasks first.
## Tips for well-defined tasks
* **One task, one outcome.** If the name uses "and", split it into two tasks.
* **Assign at creation.** A task without an assignee belongs to no one.
* **Shorter due dates over longer ones.** A task due in two weeks is easier to lose than one due Thursday. Break long tasks into shorter-horizon items.
* **Use the description field.** Context in the task prevents back-and-forth in comments and keeps work moving when the assignee picks it up days later.