> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/operations/tasks.md).

# Tasks

Running an event means juggling dozens of to-dos across multiple vendors and timelines. Vendor Space's task system keeps everything organized in one place so nothing slips through the cracks.

***

## Creating a Task

1. Navigate to **Tasks** in the sidebar.
2. Click **New Task**.
3. Fill in the task details (see below).
4. Click **Save**.

### Task Fields

| Field           | Required | Description                                         |
| --------------- | -------- | --------------------------------------------------- |
| **Title**       | Yes      | A short, clear description of what needs to be done |
| **Description** | No       | Additional details, notes, or context               |
| **Due Date**    | No       | When the task should be completed by                |
| **Priority**    | Yes      | Low, Medium, High, or Urgent                        |
| **Event**       | No       | Link the task to a specific event                   |
| **Vendor**      | No       | Link the task to a specific vendor                  |

> **Tip:** Always link tasks to the relevant event and vendor when possible. This makes filtering and searching much easier as your task list grows.

***

## Task Statuses

Every task moves through three stages:

| Status          | Meaning                                            |
| --------------- | -------------------------------------------------- |
| **Pending**     | The task has been created but work has not started |
| **In Progress** | Someone on your team is actively working on it     |
| **Completed**   | The task is done                                   |

To update a task's status, click on the task and select the new status from the dropdown, or use the quick-action checkbox to mark it as completed.

***

## Priority Levels

Priorities help you and your team focus on what matters most:

| Priority   | When to Use                                            |
| ---------- | ------------------------------------------------------ |
| **Low**    | Nice-to-have items with no hard deadline               |
| **Medium** | Standard tasks that should be done on schedule         |
| **High**   | Important tasks that could impact the event if delayed |
| **Urgent** | Time-sensitive items that need immediate attention     |

***

## Filtering and Finding Tasks

The task list includes a filter bar at the top to help you zero in on exactly what you need:

* **By Event** -- See only tasks related to a specific event.
* **By Status** -- Show only pending, in-progress, or completed tasks.
* **By Vendor** -- Find all tasks associated with a particular vendor.
* **By Priority** -- Focus on high-priority or urgent items.

You can combine filters. For example, show all **High priority**, **Pending** tasks for your **Summer Market** event.

***

## Working With Tasks Day to Day

Here are a few ways to get the most out of the task system:

### Before the Event

* Create tasks for each major milestone: finalize vendor list, confirm booth assignments, send onboarding forms, order signage.
* Set due dates that give you buffer time before the actual event date.
* Use the **High** or **Urgent** priority for anything that blocks other work.

### During the Event

* Mark setup-related tasks as completed in real time.
* Use the vendor filter to quickly check if all tasks for a specific vendor are done.

### After the Event

* Review any incomplete tasks and decide if they need to carry over.
* Create follow-up tasks for post-event items like sending thank-you messages or processing refunds.

> **Tip:** Start each week by filtering tasks to the current event and sorting by due date. This gives you a clear picture of what needs attention right away.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/operations/tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.