Re-contract Process Redesign
Summary
I redesigned the re-contract process to reduce the manual transfers and follow-up checks required after registering a new contract. I defined the automatic-transfer scope for collection records and schedules based on what changed, and planned for schedules in progress to transfer automatically after they ended.
- Role
- Product Owner (PlanningQA)
- Outcome
- Manual re-contract support 80 → 27 requests, together with bulk copy
Manual Work Remaining After Re-contract Registration
A change to the price, business entity, disposal facility or work location can require ending the existing contract and creating a re-contract. But having the CX team register the new contract did not automatically transfer collection tasks and schedules from the previous one. Accounting had to manually transfer unbilled collection tasks from the previous contract to the new re-contract, while operations had to update schedules for it. If missing tasks surfaced at settlement, settlement and sales staff also had to help investigate.
Schedules already in progress could not be transferred immediately. Because schedules usually ran at night, operations staff had to handle the transfer in the early morning or remember when the schedule ended and return to process it. If they missed that moment, schedules would not be linked to the new contract and collections could be missed. Improving contract registration alone would leave this problem unresolved, so the manual transfer after schedule completion also needed to be automated.
To address these operational issues, I led the project and planned the changes myself. During meetings with accounting, CX and operations, the main departments involved, I learned how transfers were being handled in practice and discussed when manual transfers were needed and what problems arose during processing. Based on those discussions, I defined the conditions for automatically transferring collection records and schedules, as well as the exceptions that needed separate review. I then worked with designers and developers to specify the screens and processing behavior.
Automatic Transfers Based on What Changed in the Contract
A re-contract required deciding both which contract should bill completed work and how future collections should continue. I used the changes between contracts to define separate automatic-transfer rules for collection records and schedules.
The effect on collection depends on what changes in the re-contract. Unlike a price-only change, a change to the hauler or work location requires checking whether the existing vehicle, driver and route can still be used. I therefore treated deciding which contract should bill completed work separately from deciding who would collect next and where, and defined separate conditions for transferring collection records and schedules. For hauler and work-location changes, I limited the planned transfer scope to collection records subject to additional checks, and excluded schedule reassignment because the dispatch arrangements needed review.
Re-contracts that changed the waste type or the Allbaro disposal plan required separate review. Waste-treatment permits specify the waste and activities covered, and Allbaro handover records must match the actual discharge, transport, and treatment relationships. Creating a new contract does not mean the existing permit scope and handover information can simply be reused, so I excluded these changes from automatic transfer.
I also distinguished adding a disposal facility from replacing one. Adding a new facility while retaining the existing one preserves the treatment route recorded in earlier work, whereas replacing it can remove the facility that actually handled the work from the new contract. I therefore limited automatic transfers to cases that retained the existing waste-treatment providers and required checking that the facility recorded for the work was also included in the new contract.
Permit-scope reference: Waste Control Act, Article 25 (Korean).
| Re-contract reason | Task-amount transfer | Schedule auto-reflect | Note |
|---|---|---|---|
| Price / plan change | ○ | ○ | Bag plan excluded |
| Business-entity change | ○ | ○ | - |
| Hauler change | △ | × | - |
| Operator change | × | × | - |
| Disposal facility added | ○ | ○ | - |
| Disposal facility changed | × | × | - |
| Work-location change | △ | × | - |
○ eligible for automation · △ review after checking conditions · × excluded
Keeping Billed Work and Reviewing What Can Transfer
Even when the contracts met the transfer conditions, not all previously performed work could be transferred. Transferring work to the new contract changes which contract bills it and which rates apply. I therefore kept already-billed work with the previous contract and limited transfers to unbilled work within the new contract term.
Operators often transferred work performed over a particular period in one batch, but billing agreements with customers or the type of work meant some items needed to be excluded. I used the new contract’s start date as the default date filter and allowed operators to adjust the period, review the waste type, work time and task amount, and exclude individual items. To reduce the burden of reviewing these exceptions while entering the contract, I separated the review into a step after the contract was saved.
I also reviewed transitions between bag-rate plans and other pricing plans separately. Bag delivery and waste collection are different types of work with different billing rules, so previously performed work could not simply be transferred to the new plan.
Missing an existing discount or surcharge could lead to underbilling or overbilling on the new contract. To prevent this, I specified that discounts and surcharges valid during the new contract term should carry over, including zero-value entries. I also specified that the re-contract could not be deleted while transferred unbilled work or invoices with incomplete payment processing remained. This restriction preserved the contract needed to complete settlement.
Uninterrupted Collection with Schedule Transfer on Completion
I made the transfer request part of contract creation and set its processing time according to the schedule’s status. For work already in progress, collection would finish under the existing contract before reassignment, reducing the need for operators to wait and process a second request.
Drivers use the work location shown in a schedule to identify what to collect in the field. Changing the contract link during collection could cause work to start under one contract and have its results recorded under another. I therefore based transfer timing on whether work had begun: schedules that had not started would transfer immediately, while those in progress would enter a pending queue and transfer automatically once they ended normally or were force-closed.
To reduce the need for a separate transfer request after creating a contract, I moved schedule reassignment into the contract creation process. Operators can select it directly below the contract period, review the affected schedules, and then save the contract.
I limited schedule reassignment to regular and ad-hoc work that continued an existing dispatch. Completed work and schedules before the new contract’s start date remained with the previous contract. I excluded one-off work requests, which might not yet have been assigned, and add-on work managed separately.
Transfer timing varied with the schedule’s status, so operators needed to know whether their requests were pending or complete. I specified that transfer status and history should appear in contract detail. I also defined separate permissions: admins could execute transfers, while partners could view the results.
| Schedule state | Handling |
|---|---|
| Not started | Work location switched to the new contract immediately |
| In progress | Queued → transferred automatically when the schedule ends (normal or force-closed) |
Successful Transfers with History Missing from the Interface
During QA, I checked the actual transfer results alongside the history shown in contract detail. When a scheduled re-contract became active, its schedules were correctly transferred to the new contract, but the history was missing from the interface. Although processing had completed, operators could not confirm the result on screen, so I compared the contracts linked to the schedules with the displayed history and requested a fix for the omission.
I also found that contract creation and edits could be saved even when schedule-transfer conditions were not met. I tested changes to the hauler, operator, service cycle, pricing plan and disposal facilities, and requested that disallowed combinations show the reason and block saving. QA covered both successful transfers and whether ineligible changes were blocked at the point of saving.
Manual Re-contract Support Down from 80 to 27 with Bulk Copy
I connected the transfer of collection records and schedules with result checks into a single flow after re-contract registration. Follow-up work that required operators to remember when an in-progress schedule ended and request the transfer again would be handled automatically.
After the re-contract redesign and bulk copy were introduced together, manual re-contract support requests, including schedule and Allbaro handling, fell from 80 to 27. The result combined fewer manual transfers and follow-up steps for individual re-contracts with creating and transferring multiple contracts in one bulk operation.
| Metric | Before | After |
|---|---|---|
| Manual support after re-contract creation | 80 requests | 27 requests |