+1Hi, I think the app automatically closes a lone worker activity after 12 hours, but the user doesn’t receive any notification to check-in or notification that the activity has stopped.
We had a situation earlier where a user checked in at 1pm and the activity automatically ended after 12 hours at 16.37, meaning a time period of over 3 hours where the lone worker could have been in trouble.
Could this be looked into?
Thanks,
Harry
Hey Harry,
We’re looking at exploring ‘maximum’ time frames for lone worker jobs, but perhaps 12 hours is wrong - we’ll look to ensure adequate coverage. We want to minimise the frequency of accidental duress alerts occurring from team members failing to finish a job - but recognise we need better controls here if a team member extends an activity, etc.
If you have any further details about the situation the user was in, and the context around that, it would help us with scoping the required changes. Was this individual undertaking a 15 hour shift?
+1That’s great - thank you Nick! In most cases 12 hours should be OK for my companies operations, but I think a notification similar to check in would be ideal just for peace of mind.
Appreciate the quick response!
Harry
Already have an account? Log in with your username and password, or with your SafetyCulture account.
Don't have an account? Sign up or log in with SafetyCulture.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
