# Service tasks Once a service request is approved, a Service Task is automatically created and assigned to the relevant vendor. This gives facilities teams a centralised view of what needs to be fulfilled, by whom, and by when. ### Viewing service tasks 1. Go to **Service Tasks** from the sidebar (available to Admins, Building Admins and Approvers) 2. Tasks are sorted by delivery time, with the date range defaulting to today 3. Use filters to narrow by building, service category, status, date range, or user ### Task status workflow Each task moves through the following statuses: * **Pending** — task created, awaiting vendor action * **In Progress** — vendor has started working on the task * **Delivered** — items have been delivered * **Completed** — task is finished Tasks can be transitioned backward for corrections when needed. Overdue tasks (past delivery time while still Pending or In Progress) are flagged automatically with a red indicator. ### Task details Expand any task to see the full detail panel, including: * Service items with pricing * Booking details and event date * Status timestamps * Vendor notes * Cost centre and matter number ### Vendor assignment * Vendors are assigned at the service category level and automatically inherited by tasks * If a category's vendor assignment changes, active (Pending/In Progress) tasks update automatically * Tasks are cancelled if the associated service request is declined or relevant parts of the booking are edited ### Exporting service task data You can export Service Tasks as a CSV for financial reporting, cost reconciliation, and vendor performance reviews. * Click the **Export CSV** button on the Service Tasks page * The export includes delivery dates, item-level pricing, cost centres, matter numbers, and vendor details * The export respects your current filters, so you get exactly the data you need * Vendors only see their own tasks in the export * The filename reflects the selected date range --- # Agent Instructions: 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: ``` GET https://support.meetuma.ai/uma-knowledgebase/getting-started/services/service-tasks.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.