# Assign and Track Tasks (/docs/guides/run-your-team/tasks) The **Tasks** page is your team's follow-up ledger: everything that needs a human, assigned, dated, and tracked to done. View it as a table or a kanban board. Tasks and Requirements [#tasks-and-requirements] Two item types live here: * **Tasks**: general follow-ups with a title, description, assignee, and due date. Statuses: To Do, In Progress, Done, Cancelled. * **Requirements**: paperwork items tied to a specific policy, tracked as Captured or Not Captured, with reopen and cancel actions. Use them for outstanding documents and carrier requirements so nothing stalls a policy silently. Tasks arrive three ways: created here, created inline from an [Inbox conversation](/docs/guides/agents/your-inbox), or created by **task automations** (the **Automations** button on this page). Task Automations [#task-automations] Task automations use the same triggers and filters as campaign automations, but their action is different: they create one or more configured tasks instead of enrolling or removing a customer from a campaign. Each task template can set a title, description, tags, priority, and due offset. Available triggers are Lead Created, Customer Created, Policy Created, Policy Status Changed, Campaign Completed, Campaign Failed, Date-Based, Birthday, Day of Year, Time In Campaign, and Task Completed. Task Completed matches a chosen task tag and either the Done or Cancelled status. It can also require the linked policy to have one of selected statuses. Date-Based, Birthday, Day of Year, and Time In Campaign run on the shared nightly schedule at `0 8 * * *` UTC. Date-Based, Birthday, and Day of Year only match their exact UTC fire date; missed dates are not caught up. Time In Campaign uses an at-or-before threshold, so an active membership can still match after the configured number of days has passed. Creating, updating, or enabling an active time-based automation also evaluates today's matches. Tasks are assigned to the member currently assigned to the customer. If the customer has no assigned member, the automation skips task creation. Each template is deduplicated independently, so retries do not create the same task again. Due offsets work as follows: * `0` means the task has no due date. It does not mean due today. * A positive calendar-day offset adds that many 24-hour periods to the time the automation runs. * A positive business-day offset starts at UTC midnight and counts weekdays, skipping Saturday and Sunday. It does not skip holidays. Optional filters are shared with campaign automations and use a single **Match ALL** / **Match ANY** group. Policy filters use only the policy that caused a Policy Created, Policy Status Changed, or Date-Based trigger. A Task Completed trigger also uses only its linked policy when it has one. Other triggers can match any non-deleted policy held by the customer. See [Automation Triggers and Filters](/docs/guides/reference/automation-triggers-and-filters) for the full field and operator reference. Who Sees What [#who-sees-what] Visibility follows [roles](/docs/guides/run-your-team/roles-and-permissions): agents see their own tasks, managers can view and assign across their managed NPNs (the assignee picker shows per-person open counts), and admins see everything. **Manage Tags** keeps a shared tag vocabulary for slicing the list. How agents experience the tasks you assign. Tasks and requirements in the flow of a conversation.