Short answer

No — nothing is created behind your back. When you mark a checklist item as a fault (or fail an inspection), the app offers to raise a defect and pre-fills it for you — the title comes through as the asset plus the fault reason (e.g. "Fire extinguisher — Discharged") so you don't have to type it. But you still have to choose to create it, and you don't have to. If you'd rather not track a separate defect, you can just complete the inspection: the Passed / Failed record and your answers are saved on the asset either way, and that inspection history is itself a perfectly good report.

Detail

Two things are worth separating:

  • The inspection record. Completing an inspection saves its outcome (Passed or Failed) and every answer you gave, against the asset. This happens whatever you do next — it's your evidence that the check was done and what was found. You can review or export inspection history without ever raising a defect.
  • The defect. A defect is a separate, stand-alone record that says "this asset has a problem to deal with", and it's the thing you later attach fixing jobs to. Raising one from a fault is an option the app hands you (with the title pre-filled from the fault), not an automatic step.

So when should you actually create the defect? Create it when you want to track and action a repair — assign it, add photos, raise jobs against it, and follow it through to resolved. Skip it when the inspection record alone is enough for your purposes, or when the item just needs noting rather than fixing.

This is why a failed inspection often links to a defect, but not always — it's the operative's call in the moment.

Watch-outs

  • "Failed" does not silently create a defect. If you want the problem tracked as a defect, you must take the offer and create it — check the asset's defects afterwards if you're unsure it saved.
  • No defect ≠ no record. Declining the defect doesn't lose anything: the Failed inspection and its answers are still on the asset. Don't raise a defect you won't action just to "keep a record" — the inspection already is one.
  • One real-world problem = one defect. If you do raise defects, keep one per issue (see the defect-workflow Q&A) so each photo, note and fixing job stays clean.
  • The pre-filled title is a starting point. It arrives as the asset + fault; tidy it if it needs to read as a clear work order for whoever picks it up.