Start where refund preparation becomes ambiguous
Introduce the refund-preparation handoff where a specialist first has to choose between continuing, waiting, or asking for a decision. Define one observable trigger and one work lane; “use judgment” does not explain which judgment belongs to the role.
Record customer request, transaction, policy clause, evidence, classification, and decision owner. Keep the entry short enough for real work and complete enough that a reviewer can recover the state without private chat.
Draw the authority line
State what the specialist may complete, what may be prepared but not executed, and what must stop for approval. Pair an ordinary example with one consequential edge case.
Keep money, account authority, policy exceptions, sensitive data, and customer promises with the accountable owner. The remote role can assemble evidence without inheriting unapproved authority.
Make evidence easy to verify
Link the current system record, policy, or approved instruction and note its effective date. When sources conflict, show both and pause only the affected step.
Do not reward quiet guessing. Preserve the unknown, route a specific question, and update the authoritative instruction after the owner resolves it.
Test three real cases
Try one ordinary case, one incomplete case, and one exception. Ask a second person to resume from the saved record; every extra question reveals a missing field or unclear decision right.
Review accuracy and recoverability before speed. Then the owner can simplify the record, expand the lane, or retain individual review for consequential items.
Close the record and improve the routine
Close the refund-preparation handoff only when its acceptance condition, reviewer, and final state are visible. Otherwise name the next owner and next check.
Repeated corrections should improve the source, example, or boundary—not produce a vague request to be more careful. Preserve the evidence and require owner approval for wider process changes.