The RPC has two guidelines that apply to approval of ad-hoc rides:

1.  The “non-competition guideline”.  This protects a scheduled ride from losing riders to a “competing” ad-hoc ride proposed for the same day.  This guideline requires that no ad-hoc ride may be too similar (considering pace, distance, and start point) to a scheduled ride on the same day.

2.  The “non-repetition guideline”.  This protects a scheduled ride from losing riders to an identical (pace, tour number) ad-hoc ride proposed for a few days before the scheduled ride , and prevents the ride schedule from becoming too repetitive. This guideline requires that no ad-hoc ride may duplicate a scheduled ride that is within one week after the date of the proposed ad hoc ride.

Implementation:

When an ad-hoc ride is proposed, the Ride Coordinator will compare it to all rides scheduled for that same day and to all rides scheduled during the week following the proposed ride.

An ad-hoc ride is too similar to a scheduled ride on the same day if the ad-hoc ride is the same pace, a similar distance (usually ±10 miles, more for longer (>50 mile) ad hoc rides), and a nearby start point (e.g. Pluckemin is near Far Hills).  There is some flexibility in this; the ride terrains will also be considered in determining similarity. 

If you propose an ad-hoc ride that is too similar to a scheduled ride,  or that duplicates a same-paced ride scheduled within the week after the proposed ride the Ride Coordinator will let you know that your ad hoc ride has not been approved, and why. If time permits, the Ride Coordinator will suggest other rides that you may wish to consider leading instead.

If a proposed ad-hoc ride is the same (pace, tour number) as a ride scheduled less than one week before the ad hoc ride and does not violate the non-competition guideline, the ad hoc ride will be approved, but will not be broadcast until after the completion or cancellation of the scheduled ride.