Inspections & Toolbox Talks
A toolbox talk in QuickInspect is not a separate module — it is a dedicated inspection type. You build it in the inspection template builder, run it like any other inspection, and it produces the same kind of record. That is why they are documented together.
Note
Inspections are project-scoped. Who may create templates, run inspections and close actions is controlled per role in your company's feature access matrix.
One builder, four template types
When you create an inspection template you pick its type, and the type decides how it behaves on site:
- Standard — a general HSE inspection or walkthrough
- Compliance — a checklist tied to a regulatory framework, so answers can be scored against it
- Installation — an acceptance inspection, which can additionally run the customer-confirmation flow
- Toolbox talk — a pre-task safety briefing, which collects a signature from every attendee
Questions can be yes/no, multiple choice, numeric or free text, each with optional help text, a compliance reference, and a photo requirement. The AI question generator is aware of the type, so a toolbox-talk template gets briefing points rather than audit questions.
Running an inspection
On site, an inspection is a paged checklist with a live compliance score at the top. For each question you record the answer, add a note, and attach photo evidence.
It is offline-first: if there is no signal in the plant, in the tank or down the shaft, capture continues normally and syncs itself the moment you reconnect. Nothing waits for someone to get back to a desk.
Inspections carry a status of Open → In Progress → Completed, and can be assigned to a person and scheduled to repeat.
Non-conformities that go somewhere
Anything that needs fixing becomes a corrective action. Tap + during the inspection to raise one, already linked to the inspection. In a compliance inspection, every Non-compliant answer is a non-conformity: it needs a comment, and once the inspection is completed it is listed on the Actions tab, where Create Action from Finding turns it into an action. Actions are not a dead end in a report — they link into the rest of the platform:
- tracked in the Actions module with an owner, a priority and a due date
- linkable to the risk assessment that covers the activity
- rolled into your incident and action KPIs
An inspection can only be completed once all its actions are closed.
What the toolbox-talk type changes
Everything above applies to a toolbox talk too — same builder, same offline capture, same PDF. Picking the toolbox talk type changes one thing: the sign-off.
Instead of signatures added when the PDF is generated, a toolbox talk collects a signature from every attendee on one device. You pass the phone around the crew and each person signs in turn. Attendees who are QuickInspect users are recorded as app users and linked to their profile; everyone else signs as a named participant.
The result is an attendance record with the topic, the date, the project, and a signature per person — the compliance evidence the briefing exists to produce. The PDF export reflects the type, so a toolbox talk prints as an attendance record rather than an inspection report.
Reports
Every inspection exports as a PDF with your company logo, its questions, answers, photo evidence, actions and signatures. Standard, compliance and installation inspections can be signed by as many people as you need when you generate the PDF. For raw data, the Actions and Incidents lists export to Excel.
Related
- Risk Assessment — the assessments actions can link back to
- Working Offline — how offline capture and sync behave
- Photo Documentation — attaching and annotating evidence