Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Inspection Checklist

  • Widget
  • 9 installs
  • v1.0.0
  • Nov 18, 2026
  • MIT license
  • v4.2+

Inspection and maintenance checklist for devices and assets. Technicians mark each item Pass, Fail or N/A, add notes and submit. Each inspection is saved as a time-stamped record in a time series key. Shows the last result, who did it, failed items and when the next one is due or overdue, plus the full inspection history with every answer and note. Critical items fail the whole inspection. Answers are kept as a draft if the page reloads.

Widget Type
  • Latest
Category
  • Input Forms
Use Cases
  • Predictive Maintenance
  • Industrial Automation
  • Smart Building
  • Fleet Tracking

Who it’s for

Field technicians, maintenance crews and safety inspectors who check equipment on a schedule: compressors, pumps, chillers, vehicles, fire doors, production lines. The technician wants to know whether everything on the unit has been checked and recorded properly. The supervisor wants to know when this unit was last inspected, who did it, what failed and whether the next inspection is overdue.

What it does

A technician opens the dashboard for Compressor C-12, marks eight items Pass, Fail or N/A, writes “belt glazed, replacement ordered” on the one that failed and presses Submit. The widget saves one record and shows “Passed with remarks, 6 of 8 passed, Ivan Petrenko, 13 Nov 09:42”.

  • Your own checklist. Items, sections, critical items and optional items are set in the widget settings.
  • Pass, Fail or N/A per item, with a note on any item. A note is required on failed items unless you turn that off.
  • Overall result:
    • Failed if any critical item failed.
    • Passed with remarks if only non-critical items failed.
    • Passed otherwise.
  • Last inspection summary: result, counts, date and age, inspector, failed items with their notes, and the overall comment.
  • Due date: with an inspection interval set, it shows when the next inspection is due or how long it is overdue.
  • Full history. Each inspection is saved as one time-stamped record in a time series key, so earlier inspections are never overwritten.
  • Drafts survive reloads. Unsaved answers are kept in the browser for 7 days, per widget, user and device, and the widget offers to restore or discard them.
  • Safe retries. If the connection drops while saving, pressing Submit again within 15 minutes rewrites the same record instead of creating a duplicate.
  • Several devices. If the alias resolves to several devices, a Device selector appears, and each device keeps its own draft.
  • Plain error messages, for example when your user may not write data for the device, or when there is no connection.
  • Works anywhere on a dashboard: from a 200 px phone column to a wide strip, light and dark themes, and custom background and text colors.

Limitations:

  • One checklist per widget. Devices that need different checklists need separate widgets, for example one per dashboard state.
  • Only the last inspection is shown. Use a Timeseries table on the same key to browse the history.
  • Drafts stay in one browser. They don’t follow the technician to another device or browser.
  • Saving needs a time series key. It is not possible on demo data, on attribute or entity-field keys, or for public dashboard viewers; the form still works and the widget says why Submit is off.

How to set up

Data keys

Key Role Type Description
inspection (any name) Inspection records Time series Read: the latest value is shown as the last inspection. Write: each submit adds one JSON record at the submit time. The key does not need to exist yet.

Datasource

  1. Add the widget and choose an entity alias for a single device or asset, or an alias that resolves to several, for example all compressors.
  2. Add one time series key, for example inspection. Only one key is allowed per datasource.
  3. Open the widget settings, enter your checklist name and items, and set the inspection interval if you want due dates.
  4. Make sure the users who will inspect can write telemetry for these entities. Customer users need their customer to own the devices, and on PE a role that allows writing telemetry.

Edge cases

  • Nothing inspected yet: the summary says “No inspection recorded for this device yet”. With an interval set, it says one is due now.
  • The key holds something else: if the latest value isn’t a record from this widget, the summary says so. Submitting writes a new record on top, which then becomes the latest value.
  • Attribute or entity-field key: the last value is read but Submit is off. Records belong in time series so history is kept.
  • Demo data, the function key in the default config: everything works except Submit.
  • Public dashboards: viewers can fill in the form but can’t save.
  • Alias finds no entity: the widget shows “No device found”.
  • Checklist changed after a draft was started: the draft is discarded with a notice, so answers never land on the wrong item.
  • Required item left unanswered, or a failed item without a note: Submit lists how many items need attention and jumps to the first one.
  • Save fails: the answers stay on screen and in the draft, and the message says why, for example “your user is not allowed to save data for Compressor C-12”.

How to customize

  • To name the checklist — set Checklist name. It appears under the device name and is stored with each inspection.
  • To add, remove or reorder items — edit Checklist items. Items appear in the order listed.
  • To group items under headings — give items the same Section. Each section appears once, at the position of its first item.
  • To make an item fail the whole inspection — turn on Critical for that item.
  • To let technicians skip an item — turn on Optional for that item.
  • To allow failing an item without a note — turn off Note required on fail.
  • To hide the overall comment field — turn off Overall comment.
  • To show due and overdue dates — set Inspection interval to a number with Hours, Days or Weeks. 0 turns it off.
  • To change status colors — set Passed color, Remarks color and Failed color. They color the summary result and the left stripe of each card.
  • To change the size or weight of the result — set Result font.
  • To change how item names look — set Item font.
  • To go somewhere after saving — add an action under Actions, On inspection saved, for example back to a list state. Custom actions receive the saved record as additionalParams.inspection.
  • To change the title, background or text color — use the widget’s standard Appearance settings. The widget follows them.

The settings dialog can’t be saved while the checklist has no items, or while two items in the same section have the same name.

Tips

  • Record format, for rule chains and reports. Each record is JSON with:
    • result: passed, remarks or failed
    • counts: pass, fail, na and unanswered
    • items: each with label, section, critical, result and note
    • comment
    • inspector: id and name
    • startedTs and submittedTs
    • checklistName
    • checklistId: changes when items change
  • To raise an alarm on failed inspections, check result in a rule chain. Check in your version whether telemetry saved from the UI reaches your rule chain.
  • Renaming an item creates a new item as far as history is concerned. Old records keep the old name, because each record stores its own labels.
  • Long checklists: give the widget more height on wide dashboards. From about 640 px wide, items show in two or more columns.

Share Your Widget with the Community

Built a custom widget? Export it as a JSON from ThingsBoard and publish it to the IoT Hub through a simple 4-step wizard (Upload, Listing, Readme, Review & Submit). Share it with thousands of ThingsBoard developers worldwide and get featured in the catalog.