Start with preparation work that repeats and produces something your team can inspect. A task is ready to delegate when the source, expected output, reviewer and exception route are clear. A vague request to take care of the admin leaves those choices unresolved.
Match the task to a concrete output
| Task | Output for the reviewer | Stop and ask when |
|---|---|---|
| Collect supplier invoices | Register with source links and missing-reference flags | Supplier details conflict or approval is missing |
| Update customer records | Draft changes linked to approved sources | Two sources disagree or a required field is absent |
| Follow up onboarding documents | Checklist of received and outstanding items | A policy or eligibility decision is required |
| Organize project files | Index of current versions and access requests | Retention, deletion or restricted access is unclear |
| Prepare meeting follow-ups | Action list with owner, deadline and source note | Discussion did not establish a commitment |
Separate preparation from authority
An assistant may gather documents, check required fields and prepare a review list without being authorized to approve the underlying transaction. Write that distinction into the procedure and match permissions to it. Give each exception a named reviewer rather than an open instruction to use judgment.
Try one bounded queue
Choose a small set of work that the owner can inspect before it moves downstream. Demonstrate a completed item and an item that must be held. Have the assistant explain what evidence is missing and what they would send to the reviewer. This checks the handoff more effectively than asking whether the instructions seem clear.
Example: turn attachment chasing into a register
Suppose supplier documents arrive in several email threads. The assistant gathers them through the approved route, links each file to the supplier reference, checks required fields and records missing items. A daily handoff separates ready-for-review records from exceptions. The supplier owner approves the final record; the assistant does not infer approval from a complete-looking folder.
Decide when to expand
Review correction requests, unresolved age and missing-source patterns. If the same ambiguity recurs, fix the procedure before increasing volume. Add another queue when the current output is traceable and its reviewer can keep up. Assign specialist decisions and independent approvals explicitly.
Prepare a useful scope conversation
Bring an anonymized input, an example output, approximate workload and retained decisions. Compare data entry, HR administration and document management, then discuss a starting role.