Recording Away From a Desk

Most timesheet products are designed for someone at a keyboard. A substantial part of the workforce recording time is not, and the gap shows up after purchase.

What breaks

No signal. A yard, a basement, a rural site. A product requiring connectivity to record simply does not work there.

Gloves, which defeat capacitive touchscreens.

Bright sunlight, where a low-contrast interface is unreadable.

Shared devices, where several people use one terminal and the product assumes one account per device.

Battery, on a twelve-hour shift.

One hand, because the other is holding something.

None of these appears in a feature comparison and all of them decide whether the deployment works.

Offline behaviour, specifically

Can an entry be created offline?

How long can it hold before syncing?

What happens to a conflict when the same person also recorded elsewhere?

Is the queue visible to the person, so they know their entry has not yet arrived?

Does the app say clearly when it is offline, or fail silently?

Ask for a demonstration with the device in flight mode, which is the test vendors least expect and which separates real offline support from a cached page.

Location

A check at the moment of clocking is proportionate for site-based work: it confirms presence at a site, once.

Continuous tracking through the shift is a different thing and needs its own justification, which for most roles does not exist.

Ask which the product does by default, and whether the continuous version can be disabled permanently rather than per user.

State the answer in the notice to the workforce, in terms they can check.

Shared and fixed terminals

Fast identification, because a queue of thirty people at shift change needs seconds per person.

A documented fallback for when the terminal fails, recorded as a fallback rather than as a normal entry.

Tolerance for the environment: dust, temperature, wet hands.

Consider whether a badge is enough. Biometric readers are frequently proposed for the sharing problem and carry obligations that a badge does not.

Testing it properly

In the actual environment, not in an office.

By the people who will use it, wearing what they wear.

At shift change, when the queue exists.

With the connection deliberately broken.

A half-day of this before purchase is worth more than any amount of specification, and it regularly eliminates a product that looked best on paper.

Test in the actual place

Half a day that regularly eliminates the product that looked best on paper.

In the yard, the basement, the site — not in an office.

By the people who will use it, wearing what they wear.

At shift change, when the queue exists.

With the connection deliberately broken, and then restored, to see what happens to the queued entries.

Nothing in a feature comparison predicts any of this, and all of it decides whether the deployment works.

Test outside the office

Mobile and remote claims should be exercised on the real connection, device and permission model. This platform overview provides one starting point for building those test cases.