Facilities Contract Hardware: Proof of Attendance and Tasks
Cleaning and facilities contracts are paid on work performed at locations the client controls and the contractor rarely visits in person. That makes the record of what happened the commercial product, and the hardware exists to produce it.
The record is what gets paid
A different starting point from most operations.
In a warehouse, the record supports the work. In a facilities contract, the record is frequently the only evidence the work occurred — nobody from the contractor watched it, and the client sees a clean building rather than a completed task list.
Three consequences.
Attendance must be verifiable, not asserted. A scan at the location proves someone was there. A tick on a form proves someone ticked a form.
Task completion needs to be specific. "Cleaned" is not auditable; a list of defined tasks, each confirmed, is.
Exceptions matter as much as completions. Room locked, area in use, consumables not available — these need recording as structured reasons rather than left as gaps, because an unexplained gap looks like work not done.
Scan points around the building
The practical mechanism, and the labels are where it fails.
Fixed identifiers at defined points — entrances, washrooms, plant rooms, individual areas — scanned as staff work through a round.
Those labels live in demanding places.
Washrooms and wet areas mean constant moisture and cleaning chemicals. Paper facestock disintegrates and wax printing dissolves. Synthetic facestock with a resin ribbon is the minimum, and adhesive matched to tiled, painted or laminate surfaces. Our media guide covers the pairings.
They are cleaned directly, repeatedly, by the same staff scanning them. A label that degrades stops the process it was there to record.
Retention is years. Direct thermal fades within months and is the wrong choice entirely — the same reasoning our asset tagging guide sets out.
Include human-readable text, so a supervisor can identify a point when the code is obscured.
Where signal does not reach
Facilities work happens in the parts of buildings with no coverage — basements, plant rooms, stairwells, service corridors, car parks.
Offline capture is a requirement, not a resilience feature. Scans, task completions, photographs and exception reasons recorded while disconnected and uploaded on reconnection, preserving the true time of the event rather than the upload time.
That last point matters commercially: if the record shows the upload time rather than when the work happened, an out-of-hours clean can appear to have occurred the next morning.
Round data should also load before the shift rather than during. Our field service guide covers the same pattern.
Devices for this workforce
Four practical constraints.
Carried all shift alongside equipment, so compact and light matters more than a large screen. Our mobile computers guide covers the trade-off.
Cleanable and chemical-tolerant. Devices meet cleaning products constantly. Note that an IP rating describes dust and water rather than chemical resistance — separate questions, as our washdown guide covers.
Gloves worn, with touchscreen response varying considerably between devices.
Shared across shifts, which means devices are handed over rather than owned. Keep spares configured and charged rather than boxed — a spare needing setup is not usable at six in the morning.
Simplicity matters here more than in most sectors. High staff turnover and part-time working mean the device must be usable by someone on their second shift, which argues for few, obvious actions rather than a rich interface.
Reporting to the client
What the hardware ultimately feeds.
Photographs for completed deep cleans, damage found, and anything the client should see. Camera quality matters in the poor lighting typical of service areas.
Structured exception reasons so patterns are visible — an area repeatedly inaccessible is a contract conversation, and it only surfaces if the reason was recorded consistently rather than as free text.
Consumable and stock reporting, since restocking is frequently part of the contract and running out is a visible failure.
The evidence principle is the same one our chain of custody guide covers: what is not captured at the time is unrecoverable afterwards, and a record that cannot be substantiated is weak exactly when it is challenged.
Multi-site realities
Contracts cover many buildings with dispersed, part-time staff.
Standardise the build — one device model, one label specification, one configuration profile. One spare of each then covers the contract, and a supervisor arriving anywhere finds the same arrangement. Our standardisation guide covers why variety costs more than it saves.
Plan for label replacement. Scan points degrade and get painted over, removed during refurbishment or damaged. Someone needs to notice and replace them, or coverage quietly declines and the record with it.
Train for the exceptions, since that is where records break — what to do when a label is unreadable, when the device is offline, when an area cannot be accessed. Our deployment guide covers why the workaround becomes the process if nobody hears about it.
Common questions
Why does attendance need scanning rather than a form?
Because a scan at the location proves someone was there, while a tick on a form proves someone ticked a form. In a facilities contract the record is frequently the only evidence the work occurred.
Why do scan point labels fail?
They sit in wet areas, meet cleaning chemicals constantly, and are cleaned directly by the same staff scanning them. Paper disintegrates and direct thermal fades within months — synthetic facestock with a resin ribbon is the minimum.
Why does the true event time matter?
Because if the record shows the upload time rather than when the work happened, an out-of-hours clean can appear to have occurred the next morning — which is a commercial problem, not just a data one.
How should exceptions be recorded?
As structured reasons rather than free text, so patterns are visible — an area repeatedly inaccessible is a contract conversation, and it only surfaces if the reason was recorded consistently. An unexplained gap looks like work not done.
What matters most for the device itself?
Simplicity, alongside being compact, cleanable and glove-friendly. High turnover and part-time working mean it must be usable by someone on their second shift, which argues for few obvious actions rather than a rich interface.
Tell us how many scan points and what surfaces they go on, and we will specify labels that survive the cleaning.
