Running a checklist against a location, and closing out what it finds. Inspections is the tool behind pre-pour checks, safety walks and ITPs, and it is built on the project's location map.
Locations first
Before an inspection can be planned, Teralo needs to know what the site looks like. Locations live in the project's Tools area and are shared by every tool, not just this one. The structure is free form, buildings and levels and units and rooms, or zones, or chainages, and you name each tier yourself so the labels match how your project talks. Large sites can be imported from a spreadsheet rather than typed.
Templates and plans
A template is the checklist: sections, items, and an answer type per item, with items optionally assigned to a responsible organisation. A plan binds a template to the site, either across a set of locations or on a recurring cadence such as a weekly safety walk. Plan due dates can be linked to a task in the programme with an offset, so moving the pour moves the inspection with it.
Running one
My Inspections shows what is due for you, computed live from the plans, and nothing is created until you press Start. You work down the checklist marking items, adding notes and photos as you go.
Raising an observation
This is the habit that makes the tool pay for itself. When an item fails, raise an observation straight from it: type, priority, assignee, due date and photos, with the location inherited automatically. The inspection then cannot finalise while that observation is open, so a defect cannot quietly disappear behind a completed checklist.