Bulk Copy
Summary
I planned a feature that creates many re-contracts at once by copying existing contracts, to cut the repeated re-entry and after-the-fact fix requests needed even when only a few values changed. Operators edit only the changed fields in a familiar spreadsheet-like way and catch invalid input before contracts are created.
- Role
- Product Owner (PlanningQA)
- Outcome
- Async batches of up to 300 contractsmanual support 80 → 27 requests, together with the re-contract redesign
Multiple Re-contracts Needed, Repeating Creation One at a Time
Price or disposal-facility changes often meant creating multiple re-contracts while retaining most existing information. The CX team listed the target contracts in Excel, then either created the re-contracts individually or asked developers to insert the contract data. Operators handling creation manually had to repeat the same steps for every contract, and information missed during registration became individual requests for developer corrections.
POs retrieved the existing contract information through Metabase and passed it to operators, who manually copied collection manuals, notes and tags into the new contracts. The Allbaro disposal plan did not carry over either and needed separate attention. Creating multiple re-contracts therefore involved repeated data retrieval and re-entry, along with correction requests and reviews for information missed during registration.
I reviewed the CX team’s re-contract workflow and learned how operators used Excel to list target contracts and manage changes for each contract. While considering bulk editing, I needed to distinguish requests to modify existing contracts from requests to create multiple re-contracts using information from their predecessors. I also expected that completely changing the familiar Excel workflow would require more time and effort to learn the new feature and adopt it in their work. I therefore focused on handling multiple contracts at once while retaining the familiar editing workflow.
Adding Contract Copying and Validation to Familiar Excel-style Editing
Most requests involved creating multiple re-contracts while retaining most existing information. I therefore prioritized bulk copy over bulk editing: loading existing contracts, editing only the changed fields, and creating the new contracts together.
Operators can load the contracts to copy by searching on screen or entering previous contract IDs in Excel. Collection manuals, notes and tags carry over, so they can edit only the changed fields and create multiple re-contracts at once. Each new contract links to its predecessor, and I limited the feature to collection contracts. Transfers of unbilled work and schedules follow the rules defined in the re-contract process redesign.
I focused most on letting operators continue their familiar Excel workflow in bulk copy. With designers and developers, I specified an editing screen where operators could compare contracts in rows and columns and copy or paste cells. Shared values, such as a re-contract start date, could be changed in bulk, while prices that differed by contract could be adjusted individually.
When preparing multiple re-contracts on one screen, operators needed to know exactly which contract and value they were changing. That is why I reviewed the copied values, the selected editing position and input errors together. Design QA flagged selected cells that were hard to distinguish, so the issue was included for correction. I also checked the requirements for settlement and contract operations with accounting and the CX team.
Validation from Cell Editing to Contract Creation Results
If input errors still led to repeated correction requests after bulk creation, the work I had set out to reduce would remain. I defined the validation scope so operators could find and correct errors while editing in a familiar way, then check the actual creation results.
An end date entered earlier than the start date needs to be corrected before the contract is created. I specified checks for required fields, date formats and the relationship between start and end dates, with invalid cells highlighted so operators could locate corrections even while editing multiple rows.
Moving to the basics tab still leaves the invalid end date in the period tab. To catch errors outside the current view, I made rechecking every tab part of the creation step. If an error is found, the request is blocked before submission, and operators can correct the affected tab and cell before trying again.
Once input validation passes, the request reaches the server. Creation can still fail if the source contract cannot be found or the creation conditions are not met. I therefore specified independent processing with a recorded reason for each failed contract, so one failure would not stop the others.
After processing finishes, operators can confirm the actual creation results through the total request count and success and failure counts. Using those results to identify and follow up only on failed contracts lets them continue the work without duplicating contracts that were already created.
Editable Fields Still Need Separate Transfer Checks
Even with valid inputs, whether existing collection work and schedules could transfer to the new contract needed a separate assessment. Changes to contract information could affect the processing relationships of existing work or subsequent dispatch.
Unlike changing a contract name or signing date, changing the waste type or the discharger’s registration information requires checking whether previous collection work and Allbaro handover information still fit the new contract. I therefore specified separate automatic-transfer checks even for fields that could be edited on screen.
Adding a processor can preserve the processing route recorded for existing work. Replacing or removing one could leave the facility that actually handled the work absent from the new contract, so I limited automatic transfers to additions that retain the existing processors. Switching between bag delivery and other plans was also excluded because it changes the work type and billing criteria.
| Area | Transfer allowed after change | Conditional | Change excludes transfer |
|---|---|---|---|
| Basics | Name, approval state, nature, e-contract ID | Processor (only if added) | Waste type, discharger registration info |
| Period | Sign date, term (start/end), auto-renew flag | - | - |
| Rate | Discounts / surcharges | Plan type, plan fields | - |
| Billing / tax | Taxable & VAT-included flags | - | - |
Separate Choices for Contract Creation and Collection-work Transfer
Some re-contracts do not require collection-work transfers or schedule changes. I therefore made collection-work transfer and schedule reassignment separate choices when creating the contracts.
When a re-contract is created in advance, the transfer choices are recorded, and transfers are processed when its actual start date arrives and the contract transitions. Even when multiple new contracts share a predecessor, only one can receive its automatic transfers. Moving the same work to multiple contracts would make the basis for billing and collection unclear.
Discounts and surcharges valid for the new contract term carry over. I also required an attempt to copy the Allbaro disposal plan because it is needed for later handover documents. However, cancelling an already-created contract because its disposal-plan copy failed would make operators repeat completed work. I therefore kept the created contract and made the two results available separately.
| Option | Application | Description |
|---|---|---|
| Task-amount transfer | Opt-in | Move unbilled work to the new contract (same logic as re-contract transfer) |
| Schedule reassignment | Opt-in | Link the previous contract’s courses and schedules to the new contract |
| Discount/surcharge copy | On | Carry over discounts/surcharges valid for the contract period |
| Allbaro disposal-plan copy | Mandatory | Copy it to the new contract (contract still succeeds if it fails) |
Handling Disposal-plan Copy Failures After Successful Contract Creation
Keeping the created contract is not enough if a single overall success or failure status leaves operators unsure what needs further action. Contract creation and disposal-plan copy results needed to be separate so operators could leave completed work intact and follow up only where needed.
With up to 300 contracts processed at once, I worked with developers to define independent processing so an error in one contract would not block the others. If contract creation fails, its reason is recorded and the rest continue. If only the disposal-plan copy fails, the created contract is kept so operators can review the uncopied plan and follow up on it.
I also structured the results so operators could cross-check what had been processed. The interface shows progress during execution and total request, success and failure counts afterward. The Excel result includes source and new contracts and failure reasons, along with changed schedules and transferred work for review.
Exclusion from automatic transfer because the contract conditions are not met requires different follow-up from an error during an attempted transfer. I specified separate reasons in the results so operators could distinguish eligibility exclusions from processing errors.
From Re-entry and Correction Requests to Editing Only Changed Fields
The workflow changed from creating re-contracts one by one from a list in Excel to loading existing contracts together, editing only the changed fields and creating multiple re-contracts in one batch. Collection manuals, notes and tags carry over, and invalid inputs can be corrected before creation. Familiar editing in rows and columns remains, while copying the same information and repeating creation steps for each contract are reduced.
When collection-work transfers and schedule changes are needed, operators select them during contract creation, with processing tied to the actual contract transition. They can review per-contract creation results and failure reasons in Excel to continue follow-up work. After the re-contract process redesign and bulk copy were introduced together, manual support requests fell from 80 to 27.