NFC-Bound Checklists & Proof of Work

Tap the thing.
Do the right checklist.

CHKKT Checklist binds a digital inspection, maintenance or compliance form to the actual room, machine, vehicle, cabinet or property being checked. The worker taps the NFC point, CHKKT identifies the physical asset, loads the correct checklist and records the completion against that exact location.

Asset-specific NFC
Conditional questions
Timestamped completion
Audit history
CHKKT CHECKLISTPHYSICAL TAP VERIFIED
NFC asset identified

Boiler Room · Plant 02

Tag CHK-94A7 · Smithdown Estate · Maintenance Inspection

Question 03 / 09
Is there any visible water leakage around the pump assembly?
NO
YES
Question 04 / 09
Record current system pressure
1.6 bar
Started 13:42:18NFC BOUNDE. JONES
A form that knows what it is attached to

The checklist begins with physical proximity.

Generic QR links and bookmarked forms can be opened anywhere. CHKKT binds each checklist entry point to a specific NFC identity. The tag identifies the actual place or asset and can select the right form, revision, customer and workflow automatically.

What did they tap?

Every NFC point maps to a named room, asset, machine, cabinet or property in CHKKT.

Which checklist applies?

The NFC identity can select the correct inspection template and current revision automatically.

Who completed it?

Associate the submission with the authenticated worker, time, asset and physical tap event.

Was it completed?

Track incomplete, overdue, failed, escalated and completed inspections across the entire estate.

How it works

Tap → identify → inspect → prove.

The physical tag becomes the bridge between the real asset and the digital workflow. There is no need for the worker to search through a list of sites or guess which form to use.

01

Tap NFC

The worker approaches the actual tagged object and taps it with an NFC-capable phone or reader.

02
#

Resolve code

The NFC's site/asset code resolves to the correct customer, location, object and permitted checklist.

03

Run checklist

Questions can branch according to answers, demand numeric values, photos, comments or supervisor action.

04

Preserve evidence

CHKKT stores who, what, where, when, answers, exceptions, checklist version and completion status.

Physical workflow engine

Put the procedure on the object itself.

A tag on a fire door can open the fire-door inspection. A tag beside a boiler opens the plant checklist. A tag on a cleaning cupboard opens the room-specific cleaning record. The worker does not navigate CHKKT. The physical environment navigates CHKKT for them.

One NFC identity. One physical context.

Program the tag with a CHKKT URL/token or use a secure dynamic NFC tag for stronger anti-cloning and replay resistance.

Yes / no checksSimple pass/fail inspection items with mandatory exception handling.
Multiple choiceStructured answers for condition, fault class, service action or outcome.
Numeric readingsCapture pressure, temperature, meter values, dimensions or test results.
Free-text notesRecord observations, remedial work and comments where structured answers are insufficient.
Conditional branchingA failed answer can expose additional questions, evidence requirements or escalation paths.
Photo evidenceRequire an image of the completed work, fault or inspected component.
Completion trackingSee which checks are complete, missing, overdue or abandoned.
Supervisory controlEscalate exceptions for review, override or sign-off by authorised staff.
Where CHKKT Checklist fits

Any procedure that must happen at a particular physical thing.

Maintenance & plant

Bind service checklists to boilers, pumps, lifts, generators, plant rooms and other equipment. Failed answers can create immediate remedial actions.

Property inspections

Place NFC points in HMOs, rental properties, communal areas and facilities so the correct local inspection appears at the point of work.

Cleaning & facilities

Give every room, washroom or service area its own check-in/checklist identity and build a completion record across a large estate.

Evidence model

From “form submitted” to “task performed here.”

Each submission can be tied to several independent pieces of evidence rather than a single web form timestamp.

Physical identityNFC tag assigned to a specific site, room, asset or machine
Worker identityAuthenticated operator, contractor or employee account
Workflow identityChecklist template and exact revision used at submission time
Question logicYes/no, multiple choice, multi-select, numeric, text, tabular and conditional branching
EvidenceAnswers, photos, comments, exception states, timestamps and optional Attendance correlation
ManagementCompletion status, overdue work, supervisory review, exports and audit history
NFC optionsStatic NDEF URL/token for low-cost deployment; secure dynamic NFC for higher-assurance anti-cloning deployments
The checklist should not ask the worker where they are. The thing being inspected should tell CHKKT what it is.

Turn every asset into its own inspection terminal.

Program an NFC tag, attach it to the physical object, define its checklist and start building a timestamped record of what was checked, by whom and when.

Talk to CHKKT →