Skip to content

Reviewing NFC skips

Work through the queue of NFC skips technicians have raised in the field, and accept or decline each one.

Required role

Supervisor or Admin.

Overview

When a technician can't scan an NFC tag — it's damaged, missing, unreachable, or the device has no NFC — the mobile app lets them skip the scan and record a reason so they can still do the work. Each skip lands in the NFC skips review queue on the web portal for a supervisor to look at.

This page is the review queue: a working list of skips you act on one at a time. It's different from the read-only NFC skip report (on the NFC tags page), which is an analytics view of skip patterns over time. The queue is where you acknowledge individual skips; the report is where you spot trends.

Prerequisites

  • You're signed in as a Supervisor or Admin.
  • At least one technician has skipped an NFC scan from the mobile app.

Open the queue

NFC skips in the sidebar.

The list shows one row per skip:

Column Meaning
Task / Task point Which task point the technician was working on.
Section The section of the plant the task point sits in.
Technician Who raised the skip.
Reason Why they couldn't scan (e.g. tag damaged, tag missing, no NFC on device).
Raised When the skip was recorded.
Status Pending, Accepted, or Declined.

The queue is scoped to your part of the organisation — you see skips from the technicians and sites you're responsible for, not the whole company (when hierarchy scoping is on).

Filter the queue

Use the filter bar to narrow the list:

  • Status — Pending (the default working view), Accepted, or Declined.
  • Section — focus on one area of the plant.

Large queues paginate. Clear the Status filter to see everything, or keep it on Pending to work through what's still outstanding.

Accept or decline a skip

Open a row to see the full detail — the task point, the technician's reason, and any note they added. Then choose one action:

Click Accept to acknowledge that the skip was justified — the tag really was unscannable and the technician was right to proceed without it. The skip moves to Accepted status.

Click Decline if the skip wasn't justified — for example, the tag is fine and the technician should have scanned it. The skip moves to Declined status, and you can follow up with the technician.

Both actions are acknowledgements only. Accepting or declining a skip records your decision and updates its status — it doesn't reopen, reassign, or change the underlying task. The work the technician did stands either way; you're confirming whether the missed scan was reasonable.

How this differs from the NFC skip report

NFC skips queue (this page) NFC skip report (NFC tags)
Purpose Act on individual skips Spot patterns over time
You can Accept / decline each skip Read and export only
Granularity One row per skip Aggregated by tag and technician
When to use Daily / per-shift Monthly trend review

A skip that keeps appearing for the same tag in the queue is a signal to open the report and check whether that tag needs replacing — see NFC tags › Skip report.

Things to watch for

Clear the queue every shift

Pending skips pile up quickly on a busy site. A quick pass at shift end keeps the queue meaningful and catches a failing tag before half the team has skipped it.

A pattern of skips points at a physical problem

If the same tag or section produces repeated skips, the fix usually isn't coaching — it's a tag to rewrite or relocate. Check the skip report before assuming it's a behavioural issue.

Declining doesn't undo the work

Declining a skip flags your disagreement with the missed scan; it doesn't reopen the task or remove the technician's submission. Follow up directly if the work itself needs redoing.

Troubleshooting

Problem Fix
A skip you expect isn't in the queue Check the Status filter isn't hiding it, and that the skip falls within your part of the hierarchy
The queue is empty on a busy day Either no scans were skipped, or your Section filter is too narrow — clear it
The same tag keeps generating skips Open the skip report; the physical tag likely needs rewriting or moving
You declined by mistake Re-open the row and accept it; status reflects your latest decision