3. Run your first inspection loop
Templates and inspections
Templates and inspections are the foundation of LambdaAssetCheck. A template is the reusable form; an inspection is one completed or in-progress run of that form.
Last updated: July 2026
The short version
| What it is | Who uses it | |
|---|---|---|
| Template | The reusable form with sections, questions, response types, and answer actions. | Built by administrators. |
| Inspection | One run of a published template against an asset or site. | Completed by field users, inspectors, or auditors. |
| Inspection PDF | A standardised printable output for one inspection record. | Reviewed by managers, clients, or auditors. |
One template can create many inspections. Each completed inspection can be reviewed and downloaded as its own standardised PDF.
Templates
A template defines:
- The template type, such as asset inspection, audit, incident form, or SOP.
- The asset type or site context where it can be used.
- Sections and questions.
- Response types and response options.
- Required answers, notes, photos, signatures, scoring, and conditional logic.
- Answer actions that can raise work or flags.
Template status controls availability:
| Status | Meaning |
|---|---|
DRAFT | Being built and not available for inspections. |
PUBLISHED | Live and available to use. |
ARCHIVED | Withdrawn from new use; past inspections remain available. |
OBSOLETE | Superseded by a newer version. |
ERROR | Configuration needs attention before publishing. |
Open Create templates when you are ready to build one.
Inspections
An inspection is created from a published template and includes:
- An inspection number.
- The template version used.
- The asset or site being inspected.
- The inspector.
- Start and completion times.
- Answers, notes, photos, signatures, and meter readings.
- Status such as in progress, completed, or cancelled.
Answers save as the inspection progresses. Once the inspection is completed, it becomes a record of what was observed.
Inspection PDFs
An inspection PDF is the standardised printable output for one inspection record. It can include the summary, answers, failed responses, evidence, photos, and the logo from Organisation settings.
For trends across many inspections, use Analytics.
How a failed answer becomes work
A response option can be configured so that selecting it raises follow-up work or a flag.
Depending on setup, a failed answer can create:
- A work request when something needs attention.
- A work order when planned work should be carried out.
- A flag for audit or compliance follow-up.
Incidents are reported directly from the incident flow. They are not the same as answer-triggered work.
Versioning
Templates are versioned. Each inspection keeps the template version it was run against, so changing a template does not rewrite completed inspection records.
New inspections use the latest published version.
Frequently asked questions
Can I edit a published template?
Publish a new version instead. This keeps completed inspections trustworthy.
Can I edit a completed inspection?
No. A completed inspection is a record of what was observed at a point in time.
What happens when I archive a template?
It stops being available for new inspections. Existing inspection records remain available.
Why can't I pick a template for this asset?
Asset templates are tied to asset types, and only published templates appear. If nothing appears, the template may not exist for that asset type or may still be in draft.
Related articles
Was this page helpful?
