Coming soon: site inspections and incident tracking
Twind is launching a dedicated module so prevention teams can record the inspections they carry out at their sites, raise incidents against the contractors working there and follow them through to resolution.
Available in Twind web; the mobile app is coming soon.
⭐ Inspections and incidents is a feature that must be purchased separately. If you want to activate it in your account, contact your Customer Success here: ttps://twind.io/es/contacto/
Set up the module before the first inspection
From Settings › Inspections and incidents, the client prepares three elements before getting started:
Form templates: the questionnaire inspectors will use, organized by sections. Sections can be reordered and deleted as the procedure changes.
Inspection types: optional labels to classify the inspection (scheduled periodic, before work starts, after an emergency...).
Incident types: a catalog the client can configure (Unsafe act, PPE non-compliance, Housekeeping, Hazardous substances...).
Plan, carry out and raise incidents in the same flow
The inspector plans the inspection (contractor, contract, site, inspector, date), carries it out using the configured template and records the result — compliant or non-compliant. The result is always the inspector's judgment; it is never calculated automatically.
From the same inspection, the inspector can open as many incidents as needed, specifying priority, resolution deadline, type, description, corrective measures, resources involved and photographic evidence. The contractor, contract and site of an incident are inherited from the inspection and locked — an incident can never be unlinked from the record that originated it.
You can also open an incident without an originating inspection, directly from the Incidents menu.
Resolution cycle with the contractor
When an incident is raised, the contractor receives a notification. In their portal, they see what was found, what they need to fix, the deadline and the inspector's evidence. To report the fix, they must include a comment — evidence is optional but recommended.
The client reviews it and either closes or rejects it, stating what is missing. A rejected incident goes back to the contractor marked as Rejected. There is no limit on the number of rounds. Each status change notifies whoever has the next step and is logged with author, company, timestamp and attached evidence. Only the client can close or cancel — both statuses are final.
Overdue incidents are highlighted in red in both portals.
