> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # The work order explorer > Work counted by site, team, priority or type, with its SLA, opened one level at a time down to the jobs behind any number — and exported at every level. The work order explorer answers a manager's question that arrives as a path rather than as a report: which site is slipping, which building there, which floor, which jobs. It counts work orders by site, team, priority or type, with how many are open, overdue and inside or outside their service level, and lets you open any row onto the level beneath it until you reach the jobs themselves. Without it, the same walk meant opening a report for each level and retyping the filter between them. ## Opening it The explorer is listed among the reports. Open **Analytics → Reports** — or the **Work** category under it in the sidebar — and press **Open** on **Work order explorer**. It is marked **built in**: it is part of the product rather than a report somebody saved, so it has no **Run**, **Schedule**, **Edit** or **Remove**, and nobody shares it or hides it. See [reports](https://docs.assetinfinity.ai/analytics/reports.md). You need **View saved reports**, your organisation needs the report builder module, and your roles must reach the reports filed under Work. The counts are of the work orders you could already open: two people with different [site access](https://docs.assetinfinity.ai/setup/roles.md) see different totals, and both are right. ## Choosing what to count Four tabs decide how the first level groups the work, and where opening a row leads: | Tab | First level | Opening a row leads to | | - | - | - | | **Site wise** | Sites | The locations inside the site, one level at a time, down to the jobs | | **Team wise** | Teams | Each team's lead assignees, then the jobs | | **Priority wise** | Priorities | The sites with work at that priority, then the jobs | | **Work order type wise** | Work order types | The types filed beneath it, then the jobs | Two choices above the table narrow every level: | Field | Choices | | - | - | | **Raised in** | **The last 30 days**, **The last 90 days** (where it opens), **The last 12 months** or **Any time** — when the work order was raised | | **Work** | **All work**, **Reactive only** or **Planned only** — whether the job's [type](https://docs.assetinfinity.ai/config/work-orders.md#the-type-form) is marked as planned work | Changing a tab or either choice starts the walk again from the top. The header counts what the current level holds: **work orders**, **open**, **overdue**, the share of **SLA met**, and **SLA breached**. The SLA share is green from 90%, amber from 75% and red below that. ## Each level Each row is one site, location, team, lead assignee, priority or type. A place or a type with work recorded against itself as well as beneath it has its own row, such as "At Floor 1 itself", beside the rows for what is inside it. Work with no value at this level is grouped as **No site**, **No location**, **No team**, **No lead assignee**, **No priority** or **No type**. | Column | What it counts | | - | - | | The level's name — **Site**, **Location**, **Team**, **Lead assignee**, **Priority** or **Work order type** | The group. Its name is a link: an arrow beside it means it opens onto the next level; without one, it lists the jobs | | **Total** | Every work order in the group | | **Open** | Those in a status that counts as open | | **Overdue** | Open ones past their due date | | **SLA** | A bar of met against breached on the resolution target, with the share met. A dash where nothing in the row has a resolution target | | **SLA met**, **SLA breached** | Work orders that met or missed their resolution target | | **Response met**, **Response breached** | The same, for the response target | | One column per priority | How many are at each priority, in the order of your organisation's ladder. Only priorities that appear at this level get a column | | **Unassigned** | Work orders held by neither a person nor a team | A **Total** row at the foot adds each column up. Every number above zero is a link that lists exactly the jobs it counts — a count of 41 opens 41 jobs. Clicking **SLA breached** on a row lists that row's breached jobs, and clicking a priority's figure lists the jobs at that priority. The line above the table shows where you are, for example **Site wise › Columbus › Building A › Ground Floor · SLA breached**. The figure you clicked is named in it, so a short list is not mistaken for the place's whole workload. Click any earlier step to go back to it. ## The jobs At the end of the walk the table lists the work orders themselves, newest first. | Column | What it shows | | - | - | | **Number** | The work order number, as a link that opens the job. Clicking anywhere on the row opens it too | | **Title**, **Status**, **Priority** | As on the [work order list](https://docs.assetinfinity.ai/work/work-orders.md) | | **Site**, **Location** | Where the job is, with the location's whole path | | **Team**, **Lead assignee** | Who holds it | | **Raised** | When it was raised | | **Resolution due** | The resolution target | | **Resolution SLA**, **Response SLA** | **Met**, **Breached** or **Running** — still inside the target. A dash where the job has no such target | **Search number or title** narrows the list as you type, and **Filter** narrows it on any column, including the two SLA columns by reading. **Columns** chooses which columns are shown. These start afresh each time you open another list, so the list always begins as exactly the jobs behind the number you clicked. Where they leave nothing, the table says "No work orders here match these filters." ## Export **Export** in the header downloads what is on screen: the level's rows with every column, or the list of jobs as filtered. It needs **Export reports**. > [card] [The work order list](https://docs.assetinfinity.ai/work/work-orders.md) > > Every job, with views, filters and bulk actions. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.