> ## Documentation Index > Fetch the complete documentation index at: https://docs.helmkit.com/llms.txt > Use this file to discover all available pages before exploring further. # Action Items > Per-event task lists that keep your team aligned on what needs to happen before a tour departs export const StatusLabel = ({value, showLabel = true}) => { let label = ""; let color = ""; let svg = null; switch (value) { case "todo": label = "Todo"; color = "#71717a"; svg = ; break; case "in_progress": label = "In progress"; color = "#d97706"; svg = ; break; case "done": label = "Done"; color = "#16a34a"; svg = ; break; case "cancelled": label = "Cancelled"; color = "#a1a1aa"; svg = ; break; default: return null; } return {svg} {showLabel && {label}} ; }; export const PriorityLabel = ({level, showLabel = true}) => { let label = ""; let color = ""; let svg = null; switch (level) { case "none": label = "None"; color = "#71717a"; svg = ; break; case "low": label = "Low"; color = "#71717a"; svg = ; break; case "medium": label = "Medium"; color = "#3f3f46"; svg = ; break; case "high": label = "High"; color = "#d97706"; svg = ; break; case "urgent": label = "Urgent"; color = "#dc2626"; svg = ; break; default: return null; } return {svg} {showLabel && {label}} ; }; ## What is an action item? An action item is a single task tied to one of your events — "call the client," "confirm the minibus," "upload the tickets." Each item has a title, an owner, and a status you can move through as the work gets done. Action items live inside the event detail panel. Open any event (from the calendar, the agenda, or anywhere you can click into a booking) and you'll find them in the right-hand column. That's the single place they're created, edited, and marked done. If you find yourself repeating the same items on every event of a given experience, set them up as a [template](/features/preflight/action-items/templates) instead. Helm will create them for you every time a new booking comes in. ## Creating an action item From the event detail panel: It's one of the sections inside the event's right-hand panel. If nothing's there yet, you'll see an empty state with a button to add the first item. A new row appears, ready for a title. Hit enter to save a minimal item — everything else can be added later. Click the new row to open the editor, where you can set the description, pick a due date, assign it to one or more teammates, add labels, attach files, and more. ## The fields Every action item has the same set of fields. Most are optional. The short name of the task — what you'll see at a glance in the list. Keep it punchy; the description is where details go. A rich-text block below the title. Use it for instructions, links, or context that helps whoever picks up the task. The specific date and time this item is due. Items past their due date show up in [Triage](/features/preflight/triage) as **overdue**, and deadline reminders fire based on how far away the date is. One or more teammates who are on the hook for the item. Being assigned also subscribes you to the item by default, so you're notified about changes — though you can unsubscribe from notifications while staying assigned (see [Subscriptions](/features/preflight/action-items/subscriptions)). Items with no assignee show up in [Triage](/features/preflight/triage) as **unassigned** — a prompt to either assign them or resolve them. A visual tag from up to . Priority affects sort order in Triage for items assigned to you, and it's how you signal "this one matters more" to teammates scanning the list. Four states an item can be in: * — hasn't been started yet * — someone's working on it * — complete, no action needed * — no longer relevant, will not be done Items in **Todo** and **In progress** are still open; items in **Done** and **Cancelled** are closed and stop generating notifications or Triage entries. Short colored tags (like "urgent," "paperwork," "client-request") you define once for your organization and reuse across items. Admins set up the available labels; every team member can apply them. Upload any files directly onto an item — a booking confirmation, a scanned ticket, a client's photo. Drag and drop works inside the editor. Two ways to link items together: * **Blocks** — this item is holding something else up * **Blocked by** — this item is waiting on something else Use it for items that must be done in order — "pick up the permits" blocks "hand them to the guide," for example. ## Viewing action items In addition to the per-event panel, you'll see action items in several other places: * **In Triage**, via one of three signals: overdue, unassigned, or assigned to me (see [Signals](/features/preflight/triage/signals)). * **In the activity history of each event**, where every change to an item is recorded (status changes, assignments, edits). * **In email and in-app notifications** if you're a subscriber to the item (see [Notifications](/features/preflight/action-items/notifications)). ## Editing and acting on an item Click any row to open the full editor. From there you can edit every field in one place. For quicker changes, **right-click the row** to open the context menu. It exposes the most common actions without opening the editor: * Change the status * Change the priority * Change the due date * Add or remove assignees * Add or remove labels * Follow or unfollow the item * Delete the item Some items are created automatically by Helm — **system items** that can't be deleted, only marked done or cancelled. They show up alongside your manual items but behave a little differently: their title and description are fixed, and the delete option isn't available on them. ## Up next Set up a checklist once per experience, have it auto-create on every new booking. Who gets notified about which changes — assignees, followers, and event followers. Configure deadline reminders, change notifications, and new-booking summaries per situation.