Background
We released overlaps & visit supervisor start/stop times on April 13th, 2026. A major goal of this work:
Visit supervisors will not be able to enter overlapping transport, wait, or visit time on a single visit report, saving time that would have been spent reviewing and correcting later.
Our team monitored the conflicts that are still appearing in the Report and Reimbursee Conflicts tabs, with the goal of identifying the remaining conflicts that can be prevented by the Sprout UI.
Is your feature request related to a problem? Please describe.
There are still some preventable conflicts being entered using the Sprout UI. These conflicts are currently caught with the Time Conflicts tab(s) but it would be better for the Sprout UI to catch them.
Imagine a future where the feature is done and live on Sprout. How would we know we'd been successful?
Preventable time conflicts are prevented in the Sprout UI at the the time of entering a visit report. With this change, visit supervisors will make the correction before submitting the visit report, where it will be easiest to fix.
Description
The following time conflicts are caught by the Sprout UI and the user gets a clear & helpful error message:
- "During" visit transports:
- Does not overlap with any times except visit time. (During visit transports will by definition happen during the visit time.)
- End time of the during visit transport is after the start time of that same transport. (This prevents a.m./p.m. typos.)
- Transport only visits:
- Wait time and visit time do not overlap. (Note that there are no visit supervisor start/stop times for transport only visits.)
Background
We released overlaps & visit supervisor start/stop times on April 13th, 2026. A major goal of this work:
Our team monitored the conflicts that are still appearing in the Report and Reimbursee Conflicts tabs, with the goal of identifying the remaining conflicts that can be prevented by the Sprout UI.
Is your feature request related to a problem? Please describe.
There are still some preventable conflicts being entered using the Sprout UI. These conflicts are currently caught with the Time Conflicts tab(s) but it would be better for the Sprout UI to catch them.
Imagine a future where the feature is done and live on Sprout. How would we know we'd been successful?
Preventable time conflicts are prevented in the Sprout UI at the the time of entering a visit report. With this change, visit supervisors will make the correction before submitting the visit report, where it will be easiest to fix.
Description
The following time conflicts are caught by the Sprout UI and the user gets a clear & helpful error message: