Select a process that can be handed over
Bring representative source files, current instructions, arrival volumes and examples of rejected work. Identify who owns customer promises, business approvals and changes to operating rules.
Make acceptance observable
Specify what constitutes a completed record or resolved task, what evidence accompanies it, and how defects are corrected. Separate work awaiting client approval from work ready for acceptance.
Use a pilot to establish the proposal
Agree the pilot sample, fee and review method before starting. Use measured handling time, exception rates and quality results to assess ongoing scope; expansion requires a further capacity and commercial agreement.
Buy an operating boundary, not a list of activities
A proposal becomes useful when a buyer can follow one item from arrival to an accepted handover. Name the intake channel, required source evidence, permitted actions and receiving system. Then name the decision the provider cannot make. For example, updating an approved supplier address and approving a new supplier are different services even if both appear in the same procurement screen.
Use a scope sentence that can survive a disagreement: “For each request in queue Q, validate fields A–D against source S, prepare update U, and return evidence E to owner O.” Add exclusions beside the action they constrain. This prevents an attractive headline such as operations support from concealing unpaid approval work or an unassigned business risk.
Illustrative example: a supplier-record change queue
This hypothetical exercise starts with six supplier-change requests, a current supplier export and an approved field dictionary. Four requests contain signed address-change forms, one asks for a bank-account change, and one contains an unreadable address. The operator matches supplier IDs and prepares four address updates. Finance receives the bank request; the procurement owner receives the unreadable form request. Neither exception becomes an invented value.
Procurement approves the four proposed updates before import. The accepted delivery contains four successful update receipts and a separate two-item pending register, with original request IDs, reasons and owners. Six requests were received; four changes were accepted; two remain open. The batch is accounted for, but it would be misleading to report six completed supplier changes.
| Step | Evidence and action | Decision owner / acceptance |
|---|---|---|
| Intake | Six request IDs matched to supplier export | Client supplies authorized sources |
| Address preparation | Four source-linked proposed changes | Procurement approves the field changes |
| Bank exception | One bank request held outside address scope | Finance decides; no bank write permitted |
| Unreadable form | One missing-value request with source reference | Procurement supplies replacement evidence |
| Delivery | Four receipts plus two pending items | Receiving owner reconciles all six requests |
Compare proposals using retained client effort
Ask each candidate to process the same approved sample and expose the same acceptance boundary. Compare time spent preparing inputs, reviewing exceptions, maintaining instructions and accepting outputs, as well as quoted fees. A provider that returns many easy records while leaving difficult cases with the buyer may look productive while transferring little operational responsibility.
Keep capability questions concrete: which proposed permissions are needed, which system actions can be demonstrated, and who receives unresolved cases? Coverage, language requirements and capacity belong in the proposed operating agreement after assessment. A polished sample or an attractive location is not evidence of those arrangements.
Expand only when the next queue has a complete handover
Before adding a second queue, check whether it uses the same rules, permissions and business owners. Supplier address changes do not establish readiness for bank changes. Treat the new action as a distinct authorization question, with its own sources, review path and recovery procedure.
Retain a portable delivery register from the start: item ID, source, current state, last action, decision reference and next owner. That register supports daily oversight and a later exit. The useful sign of a mature handover is that another authorized operator can understand what happened without relying on private messages or an individual’s memory.