You know you need help.
Administrative work is taking up too much of your day. Customer messages are waiting. Important follow-ups depend on you remembering them. Your team frequently interrupts you because they are unsure what to do next.
Still, handing over work can feel harder than continuing to do it yourself.
You may have tried delegating before, only to receive incomplete work, answer more questions than expected or redo the task yourself. That experience can convince you that no one else will complete the work properly.
The problem may not be the person. It may be that the information needed to perform the task still lives almost entirely in your head.
Effective delegation requires more than telling someone what to do. The person needs to understand the expected result, the process, the resources available, the authority they have and when to seek your input.
A little documentation before you delegate can make the transition significantly easier.
Why delegation often fails
When you have performed a task for years, many parts of the process become automatic.
You may know:
- Which customers require extra follow-up
- Where particular documents are stored
- Which supplier responds most quickly
- What information must be checked before sending an invoice
- Which exceptions require your approval
- How to recognise when something is wrong
Another person does not automatically have that context.
You may say, “Prepare the weekly report,” because the task feels familiar to you. The person receiving it may still need to know:
- Which information belongs in the report
- Where to find the figures
- Which template to use
- Who receives the final version
- When it is due
- What must be checked before sending it
- Whether they are authorised to correct an error
Delegation breaks down when the owner transfers responsibility but not the information required to carry it.
Start with the right task
Not every task should be delegated first.
Begin with work that is:
- Repetitive
- Time-consuming
- Necessary but not dependent on your specialist judgement
- Easy to review
- Governed by a recognisable process
- Suitable for someone else to learn
Examples may include:
- Updating a customer tracker
- Preparing routine documents
- Organising receipts and records
- Scheduling appointments
- Following up on outstanding information
- Updating inventory records
- Preparing standard correspondence
- Compiling information for payroll
- Maintaining digital folders
- Producing a recurring administrative report
Avoid beginning with a highly sensitive or complex task that has never been properly organised. Early delegation should help you and the person receiving the work build confidence.
1. Define the expected result
Before explaining the steps, define what a satisfactory result looks like.
“Follow up with customers” is too vague.
A clearer instruction might be:
“Contact every customer with an invoice more than 14 days overdue, record the response in the payment tracker and send me a list of unresolved accounts by Friday.”
The second version identifies:
- Who should be contacted
- The reason for contacting them
- Where the result should be recorded
- What must be reported
- When the task is due
Ask yourself:
- What should exist when the task is complete?
- What information should be updated?
- Who should receive the result?
- What standard should the work meet?
- How will I know it was completed properly?
If you cannot describe the expected result clearly, the person receiving the work is likely to struggle.
2. Document the main steps
You do not need a lengthy manual for every task. A simple checklist may be enough.
Record the main steps in the order they should occur.
For example, a customer follow-up process might include:
- Open the current outstanding-invoice report.
- Identify invoices more than 14 days overdue.
- Check the customer record for previous communication.
- Send the approved follow-up message.
- Record the date and method of contact.
- Record the customer’s response.
- Set the next follow-up date.
- Escalate disputed invoices to the owner.
- Submit the unresolved-items report by Friday.
This gives the person a reliable starting point without requiring you to explain the task from the beginning every time.
Focus on steps that may not be obvious. Include warnings about common errors, required checks and important exceptions.
3. Show where the task begins
Many instructions explain what to do but not how to begin.
Tell the person:
- What triggers the task
- Where the request or information will arrive
- How often the task must be completed
- Who normally initiates it
- What must already be available
For example, does the task begin when a customer submits a form, when a manager sends an email or when a weekly report becomes available?
A clear starting point helps prevent work from being overlooked.
4. Identify the information and tools required
List what the person needs to complete the task.
This may include:
- Templates
- Forms
- Checklists
- Contact details
- Shared folders
- Calendars
- Trackers
- Software
- Previous examples
- Policies
- Approved message templates
- Account access
Do not make someone search across email, WhatsApp, notebooks and several digital folders for essential information.
Create a sensible location for the resources connected to the task.
Where passwords or confidential information are involved, use an appropriate and secure method of granting access. Avoid placing sensitive login information in an unsecured document or message thread.
5. Clarify who is responsible
Every delegated task should have a clear owner.
Avoid assigning responsibility to “the office,” “admin” or “the team.” Identify the person responsible for ensuring the task is completed.
Other people may contribute, but one person should know that they are accountable for moving the work forward.
Clarify:
- Who performs the task
- Who provides supporting information
- Who reviews the result
- Who gives final approval
- Who should be notified when it is complete
Clear ownership reduces duplication and prevents everyone from assuming that someone else is handling the matter.
6. Define the person’s authority
Responsibility without authority creates delays.
Explain what the person can decide independently and what requires approval.
For example:
- Can they respond directly to a customer?
- Can they correct an obvious error?
- Can they reschedule an appointment?
- Can they request missing information?
- Can they offer an alternative date?
- Can they authorise a routine purchase?
- At what point should a complaint be escalated?
- What information must remain confidential?
If every small decision must return to you, the task has not been fully delegated.
At the same time, the person should understand the limits of their authority. Clear boundaries protect the business while allowing the work to move.
7. Explain the exceptions
Most recurring tasks include situations that do not follow the usual process.
Document the most common exceptions.
For example:
- What happens if a customer disputes an amount?
- What should the person do if information is missing?
- Who handles an urgent request?
- What if a supplier does not respond?
- What if the requested action falls outside the employee’s authority?
- What happens if the task cannot be completed by the deadline?
You cannot anticipate every possibility, but documenting common exceptions reduces unnecessary interruptions.
8. Set deadlines and priorities
“Complete this soon” is not a deadline.
State:
- The date and time the task is due
- Whether it is recurring
- How urgent it is
- What should take priority if several tasks compete
- When the person should alert you to a likely delay
For recurring work, establish a predictable rhythm.
Examples include:
- Customer inquiries reviewed every morning
- Payroll information submitted by Monday at noon
- Outstanding payments followed up every Wednesday
- Records updated by the final working day of each month
- A weekly summary submitted every Friday
Predictable deadlines help the person plan instead of waiting for repeated reminders.
9. Decide how progress will be reported
Delegation should create visibility without requiring constant supervision.
Choose a reporting method suited to the task.
This may include:
- A shared tracker
- A weekly email
- A short scheduled check-in
- A dashboard
- A completed-task notification
- An exceptions report
Do not require several updates through different channels. Decide where progress will be recorded and use that method consistently.
A useful update should show:
- What was completed
- What remains outstanding
- What is delayed
- What requires your decision
- What will happen next
This allows you to stay informed without personally managing every step.
10. Provide a completed example
A previous example can communicate your expectations more clearly than a long explanation.
Show the person:
- A completed report
- A properly organised folder
- An approved customer response
- A finished spreadsheet
- A correctly prepared document
- A previous project tracker
Explain what makes the example acceptable.
If the previous version contains mistakes or outdated information, identify what should be done differently.
Examples are especially valuable when tone, formatting or presentation matters.
11. Build in a review stage
Delegation does not mean handing over a task and never looking at it again.
During the early stages, review the work and provide specific feedback.
Instead of saying, “This is not what I wanted,” explain:
- What was correct
- What was missing
- What should change
- Why the change matters
- What the person should do next time
As the person becomes more capable and consistent, reduce the level of review.
The goal is not permanent supervision. It is a gradual transfer of confidence and responsibility.
12. Update the process as you learn
The first version of a documented process does not need to be perfect.
The person completing the task may identify:
- Missing instructions
- Unnecessary steps
- Information that is difficult to access
- A faster way to complete the work
- Recurring exceptions you did not consider
- Areas where responsibility is unclear
Encourage useful feedback.
A process should become clearer and more efficient over time. Documentation is not meant to freeze the work permanently. It gives the business a stable foundation from which to improve.
A simple delegation template
Before handing over a task, document:
Task
What is the task called?
Purpose
Why does the task matter?
Expected result
What should exist when the task is complete?
Trigger
What event or date starts the task?
Frequency
How often must it be completed?
Steps
What are the main actions?
Resources
What files, systems, templates or information are needed?
Responsibility
Who owns the task?
Authority
What can the person decide independently?
Escalation
What situations require your involvement?
Deadline
When must the task be completed?
Reporting
How will progress and completion be communicated?
Review
Who checks the work, and how often?
This template can be used for administrative, customer-service, bookkeeping and operational tasks.
Delegation is a business system
If your business depends on you remembering every detail, answering every question and correcting every task, growth will continue to create pressure.
Documentation helps turn individual knowledge into a business process.
It allows another person to understand the work, perform it more consistently and improve it over time.
You may still remain involved in important decisions, but you should not have to personally carry every recurring administrative task.
The goal is not to remove you from your business. It is to make the business less dependent on your constant intervention.
Ready to Take More Off Your Plate?
Sage can help you identify recurring tasks, organise the information behind them and create practical checklists and procedures before you delegate.
We also provide ongoing administrative and virtual support for businesses that need reliable help keeping essential work moving.