> ## Documentation Index > Fetch the complete documentation index at: https://docs.bizzyco.ai/llms.txt > Use this file to discover all available pages before exploring further. # Tasks > How tasks work in Bizzy and the priority matrix that powers your home page A **task** is a unit of work tracked inside Bizzy — something that needs doing, by someone, at some point. Tasks can be created by you, by an agent, or by an automation, and they all surface in the same place: the priority matrix on your home page. ## Anatomy of a Task | Property | Description | | --------------- | -------------------------------------------------------------------------------------------------- | | **Title** | Short summary of what needs doing | | **Description** | Optional longer detail | | **Status** | Where the task is in its lifecycle | | **Importance** | How significant the task is — `low`, `medium`, `high` | | **Urgency** | How time-sensitive the task is — `low`, `medium`, `high` | | **Category** | Type of work — bug fix, feature request, meeting, planning, research, review, documentation, other | | **Due date** | Optional deadline | | **Assignees** | Members of the organization responsible for the task | ### Status Lifecycle Tasks move through a small set of states: ``` backlog → todo → in_progress → in_review → done ↘ cancelled ``` You can jump between states freely — the order is suggestive, not enforced. ## The Eisenhower Priority Matrix Bizzy uses the **Eisenhower matrix** as the model for prioritising work. The idea, popularised by Dwight Eisenhower's "what is important is seldom urgent and what is urgent is seldom important," is to plot tasks on two axes — urgency and importance — and act differently in each quadrant. | | Important | Not important | | -------------- | ----------------- | ----------------- | | **Urgent** | **Q1 — Do First** | **Q3 — Delegate** | | **Not urgent** | **Q2 — Schedule** | **Q4 — Don't Do** | Bizzy maps each task to a quadrant using a deliberately strict rule. Only `high` counts as **urgent** or **important** — `low` and `medium` are treated equally as "not". And tasks with `null` urgency or `null` importance are routed straight to Q1, regardless of the other axis, so unclassified work can't slip past you without being triaged. * **Q1 — Do First.** Urgent and important. The fire-fighting quadrant. * **Q2 — Schedule.** Important but not urgent. Where deep work belongs — block time for it. * **Q3 — Delegate.** Urgent but not important. Hand off if you can; otherwise batch. * **Q4 — Don't Do.** Neither urgent nor important. Cut, archive, or politely ignore. ## The Home Page Widget Your organization home page leads with the priority matrix widget. It pulls together up to **50 tasks** plus up to **25 unread messages** and groups them into the four quadrants, sorted by due date and then creation time. You can flip between a 2×2 grid and a flat list, and act on items inline without leaving the page. Messages appear in the matrix because in a communications-driven business, an unread email is often a task in disguise. Treating both as items on the same grid means the AI's triage of incoming mail flows directly into your work queue. ## Where Tasks Come From Tasks are first-class entities — anything that produces work can produce a task: * **People.** You create tasks manually for things you need to track. * **Automations.** A rule like "when a customer asks for a refund, create a task for the billing team" emits a task. * **Agents.** When an agent is given the `createTask` tool and decides a follow-up is required, it can create one. Tasks created this way are flagged so you can audit them. Assignees are members of your organization. A task can have multiple assignees — useful for things one person owns but several people need to follow. ## Related Topics How to create, edit, and triage tasks in the web app Tour of the home-page priority matrix How automations create tasks for you How agents work with tasks