Feature Ideas

Since Red Rover already includes the long‑term tracker option within an absence or vacancy, it would be incredibly helpful to have a customizable system rule. Something like: “Hey Red Rover, when this long‑term sub reaches 16 consecutive days in this assignment, flag it!” However the notification appears, I’d love to see an automated way for Red Rover to track this and alert us once a substitute reaches the long‑term threshold.

Per our state statue, anyone with a 1 year emergency substitute certification serving in a long term position can only work 20 consecutive days in a long term absence or vacancy. We would like Red Rover to create a flag system to notify us of when those substitutes are getting close to the 20 day mark, so we can notify principals and they can plan accordingly.

We pay our substitutes by the full and half day, but we place those subs at times into small fractions of a day for several different employees. This can cause the system to believe that the subs should get paid for more than a full day. We'd love for the system to somehow know to flag this to help us catch situations where a sub could be overpaid.

It would be helpful if we had a different way to enter schedules for vacancies. Right now, if there is a vacancy for a few months and one or more of the days has a different start or time, we have to manually adjust each day (for example, if the schedule is M/Tu/W/Th 8am-3pm, F 8am-2pm), we have to manually adjust each Friday. This can be time consuming for our team and schools. It would be nice if there was an option for us to enter a schedule based on each day. If we had somewhere to type in: M/Tu/W/Th 8am-3pm, F 8am-2pm, the system would automatically make those adjustments for us.

It would be helpful for substitutes to see the notes to substitute prior to accepting an assignment. This can help them determine if the job is a good fit for them. In the event that a sub accepts a job and then later declines due to the notes, this would prevent a last minute cancelation.

The rules under the default employee permission set allow the SuperUser to set how far in the future and how far in the past an employee can Create AND Edit an entry. That same permission set allows us to establish if the user group can cancel an assignment after a SUB has been assigned. At this time I would like to be able to restrict employees from canceling an entry the same day. I don't want to restrict all cancelations because that would put a significant number of new communication and transaction changes onto Administrators. IF the Create, Edit and Cancelation after a SUB has been assigned options all had settings (see screenshot below) then we could restrict the cancelation of the SUB same day without Administrator assistance.

I would like a way to mass delete a sub from upcoming jobs. Our subs pick up jobs for months in advance and when they pick up a longterm assignment or leave the district, I have to go in and delete individual assignments. Sometimes there are 20 or more and it's very time consuming.

When an absence is denied it does not show under the employee profile. Is there a way to keep that history without having to run a report. This person requested a day off for 1/19 it was denied and now it does not show.

We have an Art, PE and Libarian that are shared between buildings. It would be nice for the Principals in the other buildings to know when they are gone and if they have a sub for day so they don't waste their time walking over to the other building.

It would be helpful if Red Rover could make the activity logs more accurate and transparent so users can more easily understand what actions and updates have occurred. For example, when an assignment that was previously verified is reverified and saved, the activity log currently shows “Vacancy detail changed,” even though no vacancy details were modified and only the pay hours were updated on the verification side. Adjusting the activity log to better reflect what actually changed would help reduce confusion. Additionally, having the ability to view more detailed change histories, such as which fields were updated, previous values, when it was modified, and who made the change, could make it easier to identify discrepancies and resolve conflicting information more efficiently.