What is Time Rules Behavior?
The Time Rules Behavior feature determines how ride scheduling interacts with the time rules set for a service. Time rules specify when bookings can be scheduled (e.g., between 8:00 AM and 6:00 PM). Depending on the selected behavior, the system interprets these time rules differently, particularly in how it schedules pickup and dropoff windows around a rider’s requested time.
Time Rules Behavior is crucial for maintaining a balance between operational efficiency and rider fairness. It governs whether the rider’s requested time and associated time windows (pickup and dropoff) need to fit partially or fully within the defined time rules.
A Recap of Key Concepts:
Time Rules: Define when bookings are allowed to be scheduled (e.g., 8:00 AM to 6:00 PM). Requests outside this time will not be accepted.
Window: A period (e.g., 10-minute pickup or dropoff window) that indicates the timeframe for the pickup or dropoff to occur.
Relevant Window: The most important window based on the request type. For "Leave At" or "Leave ASAP" requests, the pickup window is considered the relevant window. For "Arrive By" requests, the dropoff window is the relevant window.
What is the value?
Time Rules Behavior offers value to Spare customers by allowing them to define how strictly time rules are applied to trips. This has significant implications for service planning, operational management, and rider satisfaction:
Service Planners can customize how flexible their system is with time rules to match the goals of their service (e.g., maximizing service coverage vs. prioritizing fairness).
Operations Managers can strike a balance between system capacity and efficiency. For example, allowing more flexibility in scheduling can reduce peak-time bottlenecks, while stricter rules improve predictability and fairness.
Riders benefit from clarity on how their trips will be scheduled and may experience more consistent service depending on the chosen behavior.
By tailoring Time Rules Behavior, agencies can adjust their systems to prioritize flexibility, fairness, or a mix of both, ensuring alignment with their unique service goals.
What does Time Rules Behavior look like to customers?
Behavior Options:
Time Rules Behavior includes three configurations, each offering a different approach to handling windows and time rules. Let’s explore each option:
1. Windows can fall completely outside time rules
How it works: Only the requested time must fall within the time rules. The system does not enforce any restrictions on when the pickup or dropoff windows occur.
Example: If the requested time is near the end of the time rules, the dropoff window can be scheduled after the time rule ends.
Diagram:
(Insert diagram showing windows outside time rules here)Explanation:
In this behavior, time rules are the least restrictive. The pickup and dropoff windows can extend beyond the defined time rules, giving riders the most scheduling flexibility. This is particularly beneficial when maximizing service coverage is a priority. However, it may create situations where riders receive unequal window lengths or when windows occur significantly outside the operating period.
2. Relevant window can be trimmed to fit inside time rules
How it works: The relevant window (pickup for "Leave At/ASAP," dropoff for "Arrive By") is adjusted to fit within the time rules. If the relevant window overlaps only partially with the time rules, it will be shortened accordingly.
Example: If a rider requests a trip near the end of the time rules, the dropoff window might shrink to fit inside the time rules, while the pickup window can still extend beyond the time rules.
Diagram:
(Insert diagram showing trimmed windows here)Explanation:
This behavior balances flexibility and adherence to time rules. While the most critical window is guaranteed to fall within the operating period, shorter windows may occur, which can lead to challenges in fitting trips into busy schedules. This option is ideal for services looking to enforce partial time rule compliance while maintaining flexibility for less critical windows.
3. Relevant window must fit completely inside time rules
How it works: The relevant window must fit entirely within the time rules. For example, a "Leave At" request ensures that the entire pickup window is within the defined time rules.
Example: A rider requesting a trip at the very start of the time rules will have both the pickup and dropoff windows strictly contained within the time rules.
Diagram:
(Insert diagram showing windows fully inside time rules here)Explanation:
This is the strictest option, ensuring full compliance with time rules. It guarantees fairness by providing all riders with consistent window lengths and preventing windows from extending outside of the service’s defined operating hours. However, this strictness may reduce flexibility and make it harder to schedule trips near the boundaries of the time rules.
Comparison of the Options:
Option | Flexibility | Fairness | Scheduling Impact |
Windows can fall completely outside rules | High | Low | Most flexible, least predictable |
Relevant window can be trimmed | Moderate | Moderate | Balanced flexibility and fairness |
Relevant window must fit completely | Low | High | Strictest, ensures consistent service |
What are the current limitations of Time Rules Behavior?
Complexity in communication: Explaining the differences between behaviors to riders can be challenging, especially for users unfamiliar with scheduling concepts. Clear messaging is needed to set expectations.
Impact on system performance: Stricter options (e.g., requiring windows to fit entirely within time rules) can reduce scheduling flexibility and increase the risk of rejecting trip requests during peak times.
Fairness trade-offs: More permissive behaviors may create inconsistent rider experiences (e.g., some riders having longer windows than others).
How can we sell Time Rules Behavior?
Body: "For Product to fill in"
Where else can I read about Time Rules Behavior?
Body: "Any other relevant documentation that describes this feature or shows the impact it has on users"
Other FAQs
What happens if a request falls completely outside the time rules?
Requests made entirely outside of the time rules are rejected by the system, regardless of the selected behavior.
How do “Leave At” and “Arrive By” requests differ in terms of the relevant window?
For "Leave At" and "Leave ASAP" requests, the pickup window is the relevant window. For "Arrive By" requests, the dropoff window is the relevant window.
Can different Time Rules Behaviors be set for different services?
Yes, customers can configure different behaviors for individual services, allowing them to tailor the scheduling experience to the needs of specific rider groups or operational goals.
Does trimming the relevant window affect travel time?
No, trimming the relevant window does not impact the calculated travel time. The system will still compute the most efficient route between the pickup and dropoff points.