When the App Updates
Phone operating systems and vendor releases both change what the app can do. The check that catches it before the refusal rate does.
Running it · Procedure
This deployment sits on two moving foundations: the vendor's app and the phone's operating system. Both change without asking you.
What the operating system changes
Location permission behaviour, which has tightened repeatedly and will again.
Background execution limits, which can stop a queued punch syncing.
Battery optimisation defaults, which reduce location accuracy silently.
Permission prompts that reappear, asking users to confirm — and some will decline without realising the consequence.
The symptom is always the same: refusal rate rises across one phone platform, a week after an update.
What the vendor changes
New features, frequently enabled by default: continuous tracking, automatic clock-out, punch photographs.
Permission requests, which can expand.
Retention defaults.
Export formats, breaking whatever payroll consumes.
What a supervisor account can see, which can widen without announcement.
The post-release check
Twenty minutes, after every release.
Read the notes for anything about location, permissions, defaults or visibility.
List the capture settings and compare against what was recorded at go-live.
Check what permission the app now requests.
Test one punch and one refusal.
Record the result, because "we never enabled continuous tracking" is a claim that may need supporting with dates.
Watching the platforms
Track refusal rate split by phone platform, which is the early warning.
A rise on one platform only is almost always an operating system change, not a workforce change.
Tell people what happened and what they need to do, which is usually re-granting a permission.
A month of unexplained refusals is how a working deployment loses its credibility.
If something arrived enabled
Turn it off and note the dates it was on.
Assess what was collected in the interim and whether it should be deleted.
Tell the workforce if anything was collected that the notice said would not be. Uncomfortable, and it is what keeps every future statement believable.
The contract term
Notification before changes that alter what is collected or what accounts can see.
Ask for it at procurement, when it is a negotiating point rather than a favour.
Split the refusal rate by platform
The early warning that costs nothing to produce.
Android and iOS change location behaviour on their own schedules.
A rise on one platform only is almost always an update, not a workforce change.
Tell people what happened and what to do, which is usually re-granting a permission.
A month of unexplained refusals is how a working system loses its credibility.
Check the difficult case
Use the integration overview to frame one representative test. The useful evidence is the record created when an employee corrects an entry and an administrator exports it.