Skip to content
← Engineering notes

Micro-apps and AI agents

Quality checks with photos on a tablet: designing the checklist so it gets filled in

14 November 2026 · Shalaka engineering team

Moving an inspection from paper to a tablet does not make it better by itself. A badly designed form on a tablet gets filled in at the end of the shift from memory, just as paper did, and now it looks more official. The design of the checklist decides whether the data is true.

Keep the check short and ordered

Put the checks in the order the inspector physically does them, walking round the part, not in the order a quality manual lists them. Each item should be answerable with one tap: pass, fail, or not applicable. Free text is the last resort.

Limit one screen to what fits without scrolling on the tablet in use. If an inspection has 40 items, split it into sections by stage, and show progress.

Rules for photos

Photos help most on failures. Ask for one when the inspector marks an item as failed, and make that automatic, not optional. For passes, a photo is useful only for items where a later dispute is likely, such as a labelled carton or a final assembly.

Some limits:

  • Compress photos on the device. A full-resolution photo from a recent tablet is several megabytes, and 200 of them a shift will clog a weak Wi-Fi link.
  • Store the photo with the part serial or lot number, the inspector, the station and the time, in the file record, not in the filename alone.
  • Allow marking up a photo with a circle or arrow, so the defect is obvious to someone who was not there.

Reject reasons

Use a fixed list of reject reasons, grouped by type: dimensional, cosmetic, functional, labelling. A list of 8 to 15 options per product is usually enough. Add “other” with a note, and review the “other” entries each month, because they show which reasons are missing from the list.

With coded reasons, a trend of defects by line, product and shift comes with no extra work. A spike in one reason on one line points at a cause.

Work offline

Shop floors have dead spots. The app should keep working on the local network or with no network, hold records on the tablet and sync when the link returns. An inspector who has to wait for a spinner will go back to paper.

Test the form with the inspectors

Before rolling out, have two or three inspectors use the form on production parts for a shift. Watch where they hesitate, where they tap the wrong item and which fields they skip. Remove or reword what they skip.

What it does not fix

A good form records what the inspector sees. It does not make an inspector look harder, and it cannot stop someone ticking “pass” on every line. Pair it with periodic audits of a sample, and with a culture where recording a defect is not punished.


If your inspections are still on paper or in a spreadsheet, we can build a tablet checklist with photos around your process, see micro-apps for electronics and manufacturing or book a discovery call.

Tell us what you are building.

A 30-minute discovery call with an engineer. We reply within 48 hours.

Book a discovery call