> ## 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. # Inspection settings > Inspection types, templates, and the questions each published version asks. The inspection settings screen ## Inspection types What kind of round this is: safety, statutory, condition, pre-start, handover. Types are how rounds are grouped and reported, and how *critical* findings are distinguished from routine ones. ## Templates A template is the set of questions a round asks. Templates are **versioned and published**. A round records the version it was answered against, so improving a template does not rewrite what earlier rounds meant. A draft version can be edited freely; a published one cannot, because rounds have been answered against it. To change a published template, create a new version and publish that. Rounds in progress finish against the version they started on. ## Template items The questions. Each carries: | Setting | Meaning | | -------------------------- | ----------------------------------------------------- | | **Prompt** | What the technician is asked | | **Answer type** | A measurement, a yes/no, or one of a list | | **Expected range** | What a passing answer looks like | | **Mandatory** | Whether the round can be submitted without it | | **Evidence** | Whether a photograph or signature is required | | **Critical** | Whether failing this is a critical finding | | **Raises corrective work** | Whether failing it creates a work order automatically | ## Expected ranges are the point An item with no expected range is a question with no answer — it records what somebody saw and judges nothing. Give items ranges wherever there is one: a bearing temperature under 70°C, a pressure between 4 and 6 bar. The grading is then done by the server, identically every time, rather than by whoever is holding the handset. ## Raising corrective work automatically Where an item is set to raise corrective work, a failed check creates a work order without anybody remembering to. This is the setting that makes inspections worth running: a failed check nobody acts on is a failed check nobody needed. Choose the work order type and priority the raised job should carry. ## Critical findings Items marked critical produce findings that appear in **Needs attention** on the [Executive dashboard](/get-started/dashboards) and stay visible until closed or waived. ## Linking a template to a plan A [maintenance plan](/maintenance/plan-builder) can name a template, and each round of the plan then raises an inspection alongside the work order. That is how a plant gets its statutory rounds done on schedule rather than on memory. ## Related topics - [Inspections](/maintenance/inspections.md) - [Work settings](/config/work.md) - [Document settings](/config/documents.md) - [Setting up the plant](/setup/overview.md) - [Maintenance plans](/maintenance/plans.md)