Scheduled Suspension
Summary
Suspensions had to be handled by hand on the day itself even when the date was known in advance; this work lets them be scheduled for a future date. Pickups continue until the booked date, the suspension applies automatically on that day, and the same suspension period carries through to billing and re-contracts.
- Role
- Product Owner (PlanningQA)
- Outcome
- Holiday suspension change rate (per 1,000 contracts) ≈3.09 → 0.74per change record down 89.1%
A Known Pause Date Still Required Weekend Handling
Temporary suspension pauses a contract before service resumes. Previously, changing the contract status to suspended took effect immediately, and the start date could only be today. Operators had to remember the date and change the status when it arrived, including working on weekends when a pause began then.
A contract status change also affects billing for accounting, contract operations for CX and collection schedules for the operations team. Moving from same-day status changes to advance reservations required defining both how to enter future pause dates and how that period would apply to collection and billing.
I planned the feature and checked the necessary conditions with accounting, CX and operations. Based on those discussions, I reviewed effects on contract status, billed amounts, work shown in the driver app and re-contracts. I translated the conditions into rules for entering reservations and transitioning contract states, then worked with designers and developers to specify the screens and processing behavior.
Future Suspension Reservations without Stopping Today’s Collection
I first separated the current contract state from the future suspension schedule. The previous form showed suspension dates only after the contract status was set to suspended, and changing the status paused the contract immediately. Allowing a future start date alone would therefore still stop today’s collection while reserving next week’s pause.
I therefore specified a separate setting for the suspension period, non-payment status and reason, leaving the current contract status unchanged. For a pause starting next week, collection continues until then, and a scheduled job transitions the contract status on the reserved start date. The interface also distinguishes the reserved period from the actual contract state.
The driver app follows the same date rules. Schedules before the pause starts remain available for normal execution, while those during the suspension are hidden and cannot be performed. Reserving a future pause therefore leaves the collection that needs to run now unaffected.
I defined the end date as the last day included in the suspension. If it is October 10, collection remains paused through that day. The scheduled job on the following day releases the suspension, and collection resumes on October 11. Without an end date, the contract remains suspended. Separate records of repeated pauses and resumptions preserve the actual suspended periods for billing.
Contract and Schedule Changes between Reservation and Suspension
The contract state at reservation may not last until the pause date. Contract changes and collection already underway also belong in the transition rules.
A provisional contract, for example, has not started service. Changing it to suspended solely because a date arrived would lose that distinction. It stays provisional, with the pause dates evaluated again on activation. Ended contracts are excluded because their service can no longer be paused and resumed.
I defined rules to keep contract status changes from disrupting collection already underway. At the time of planning, I restricted immediate suspension and release for contracts with schedules in progress.
| Condition | Behavior |
|---|---|
| Normal creation or start-date editing | Choose today or later; end date must be on/after the start or unspecified |
| An active contract reaches its start date | Transition to suspended immediately |
| Start date in the future | Keep current state + "suspension scheduled" flag → auto-transition on the start date |
| A provisional contract reaches its start date | Keep provisional status; evaluate suspension when it becomes active |
| Day after the end date | Scheduled job releases suspension; collection resumes |
| No end date set | Open-ended suspension |
| Contract has a schedule in progress | Can’t flip straight to/from suspended (protects work underway) |
A Billing Safeguard That Also Blocked Future Schedule Changes
A suspension period determines both when collection pauses and how billed amounts are calculated. Changing its dates after an invoice is issued changes the operating days for that period while leaving the issued amount unchanged. I therefore initially prevented edits to an entire suspension record if it overlapped a billing period with an issued invoice.
This restriction also blocked future schedule changes that did not affect billing. If December has been billed and a pause runs from December 15 to March 31, bringing the end forward to January 19 leaves December’s paused dates unchanged. Moving the start to December 20, however, changes the billing basis for December 15–19. The policy needed to distinguish the effects of these two changes.
I therefore refined the policy to protect dates already reflected in billing. Comparing paused dates within each billing period before and after a change allowed changes affecting issued invoices to be blocked while dates outside those periods could be adjusted. I specified the same safeguard for reservations, edits and releases.
Deducting Actual Paused Days Instead of Choosing Whether to Bill
Alongside protecting dates already reflected in billing, I clarified how suspension periods should be billed. In practice, paused periods were not billed, but the interface still offered "continue settlement," so the selection could change the billed amount.
Accounting needed information that distinguished pauses caused by non-payment for receivables management. I therefore removed the choice of whether to bill during a pause and retained non-payment status as separate information. I improved billing for plans with a fixed base fee, such as subscriptions, so the base fee is prorated by operating days excluding the suspension period, regardless of the reason for the pause.
I limited deductible days to those in the suspension period that overlap each billing period. Deducting an entire pause spanning two months from a single invoice would also remove dates outside that invoice’s period, causing underbilling. I kept the same calculation rule for repeated pauses and pauses crossing month boundaries.
Keeping Pause Settings So Re-contracting Does Not Restart Collection
The rules for applying suspension periods to collection and billing also needed to carry through re-contracting and renewal. If the new contract lost its suspension setting, collection could restart while the pause was still in effect.
For re-contracting, I therefore specified that the previous contract’s suspension settings are copied, while history is created separately for the new contract. Copying past history would mix the previous contract’s dates into the new contract’s billing basis. The design distinguishes settings that still apply from history that has already passed.
An inherited pause that has already started may have a start date in the past. New settings allow today or later, but re-contracts and renewals can inherit the existing start date to continue an ongoing pause.
For renewals, suspension status is evaluated when the contract becomes active, and a new history entry is created at that point. When a re-contract or renewal includes a suspension setting, a warning dialog asks the user to confirm it. This makes the continued pause clear to the operator as the contract changes.
Replacing Same-day Manual Suspension with Advance Reservations
Separating the date a suspension is requested from the date it takes effect replaced the need for operators to change the contract status again on the day itself with advance reservations.
Operators can now prepare weekend or public-holiday suspensions during the working week. The same suspension period carries through CX contract management, collection schedules for operations and billing for accounting, reducing the work each team does to align the contract’s dates and status separately.
Suspension changes on weekends and public holidays fell from approximately 3.09 to 0.74 per 1,000 active contracts per month. Their share of all suspension-related changes also decreased by 89.1%, so both their frequency relative to contract volume and their share of all changes were lower.
| Metric | 2025 | 2026 | Decrease |
|---|---|---|---|
| Holiday suspension change rate (per 1,000 contracts) | ≈3.09 | ≈0.74 | 76.2% |
| Holiday suspension change rate (per change record) | 16.00% | 1.75% | 89.1% |