Delegate to Volunteers With Scope and Support

Delegate a defined outcome
An assignment such as "take care of outreach" is too vague when it may include several channels, contact records, event attendance, and out-of-hours messages. Good delegation defines the required result, included work, authority, and boundaries.
Safeguarding concerns must use an actionable statutory route for the affected person's location. Do not investigate, test credibility, or decide internally whether a concern warrants a report. Contact local emergency services if anyone is in immediate danger. In England, use GOV.UK's child-abuse reporting service for a child or young person. For an adult who may have care and support needs and be at risk of abuse or neglect, use GOV.UK's local-council finder, open that council's official website, and find its adult-safeguarding report form or phone number. Outside England, search the official government website for "report child abuse" or "adult safeguarding report concern" plus the person's location, then use the published statutory form or phone number. An internal notice may occur in parallel but must not delay external reporting.
Start with a usable volunteer role description, even for a short assignment. State the outcome, tasks, time window, location, contacts, required checks or training, available expenses, and work that remains with the leader.
Match the assignment to fit
Ask about interest, availability, experience, access needs, and preferred support. Do not assume the person with the fastest response wants every urgent job. Apply relevant screening and safeguarding requirements consistently; friendship or long service does not substitute for them.
Offer the assignment rather than announcing it as a fact. Give the volunteer enough information to accept, decline, or negotiate scope. If saying no brings punishment, embarrassment, or loss of unrelated opportunities, the invitation was not meaningfully voluntary.
Define authority before work begins
Be explicit about what the volunteer may decide, what requires consultation, and what requires approval. Name spending limits, access permissions, public communication rules, and any boundaries around personal data. For money, contracts, regulated work, safety, or legal obligations, identify the accountable person and the point at which qualified advice is required.
Then provide what the assignment needs: access, equipment, templates, contacts, budget information, and a live demonstration where appropriate. Use the onboarding checklist when the work involves unfamiliar systems or sensitive responsibilities.
Agree on checkpoints, not surveillance
Set a small number of useful check-ins based on risk and complexity. A new or safety-critical task may need closer review; a familiar, low-risk job may need only an agreed milestone. Tell the volunteer what a progress update should contain and how quickly the leader will answer questions.
Do not reverse routine choices after granting authority. If a constraint changes, explain it promptly and revise the assignment together.
Respond to problems without dumping blame
When work slips, check the system first. Was the outcome clear? Did the volunteer receive authority and access? Was the time estimate realistic? Did another priority intervene? Correct the plan, provide support, and discuss observed behavior directly.
If the role is too large, split it, extend the deadline, or stop lower-priority work. The guide to preventing volunteer burnout is especially useful when delegation keeps flowing toward the same reliable few.
Close and learn
Confirm when the assignment is complete and what happens to files, access, expenses, and follow-up questions. Thank the volunteer specifically. Ask what was unclear, unexpectedly difficult, or worth repeating, then update the role description.
Delegation should protect the volunteer’s capacity as well as completing the work. Review workload and support before assigning the next task.
Keep a brief assignment record for work that spans several people or weeks. It should show the current outcome, owner, agreed authority, open decisions, and next checkpoint—not every conversational detail. That record protects continuity when someone is absent and prevents the returning leader from accidentally delegating the same task in three different directions.