Background
Field users have highlighted that when entering "actuals" against "planned" time and dates, the system currently defaults to the shift start date and time. This leads to unnecessary manual input, especially when actuals often match the planned time, slowing down data entry in the field.
https://jam.dev/c/d3ae2ea5-989e-4248-a8e9-38268d0d4c8d
User feedback insight
It would be more efficient if the "actual" field defaulted to the planned time when selected. In most cases, actuals align with the planned schedule, so this small change would significantly reduce the number of steps for field users, especially when operating under time constraints.
Proposed solution
When a field user taps into the "actual" time field, it should automatically populate with the corresponding planned time and date.
Users can still adjust the "actual" time if it differs from the planned, ensuring flexibility.
This change streamlines the data entry process, saving time and reducing manual effort, particularly in fast-paced site environments.
Expected benefits
Increased efficiency – speeds up data entry by reducing repetitive inputs.
Improved user experience – matches real-world workflows where actuals often align with planned times.
User stories: focused on field users
User story 1: speed up data entry
As a field user,
I want the "actual" time to default to the planned time when I select it,
So that I can enter data faster with fewer manual inputs.
User story 2: maintain flexibility for edits
As a field user,
I want to easily adjust the "actual" time if it differs from the planned,
So that I can accurately log any changes on site.
1
1
