Practical guide

Keep a volunteer pause separate from a permanent departure

Last materially reviewed 2026-10-01

Quick answerRespect the stated preference and preserve only the context you need.
What to know

Use the person’s actual message

A pause can mean unavailable until a date, uncertain future availability or no further invitations for now. Do not turn it into a permanent departure without evidence. Equally, do not keep contacting someone who asked you to stop. Record the relevant preference through the organization’s approved process and avoid speculative explanations.

What to know

Remove misleading active-work signals

Review open invitations and tasks so another coordinator does not act on an outdated active label. A pause in one role may not apply to every activity. Keep the scope clear and route any ambiguous request to a person who can clarify it. Do not bulk-delete useful records just to make the active list smaller.

What to know

Plan an appropriate return route

Where the person has agreed to a later review, record that review date and owner. Returning may require reconfirming preferences or role-specific prerequisites; the old ready state should not silently carry forward forever. The responsible program decides those requirements. This site supplies a record framework, not eligibility policy.

What to know

Worked example

A fictional volunteer pauses weekend activities for two months but remains interested in occasional weekday work. The team records that distinction and removes the pending weekend invitation. It does not label the person inactive everywhere or create repeated reminders to persuade them to return sooner.

What to know

Record the scope without guessing a reason

Useful fields are the activity affected, the person’s stated preference, an agreed review point if any, and the owner of any remaining commitment. A pause may leave an already accepted session needing a separate answer. Clarify that question through the appropriate route instead of silently cancelling or retaining the booking. Do not add speculative health, family or employment explanations to a general note. When the person returns, review current preferences and any applicable role requirements; the earlier active label is historical context, not automatic current permission.

Continue when useful

Next: Communication boundaries

Being in your CRM is not blanket permission for every message.

Open Communication boundaries →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. LACRM inactive-contact handling — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01
  2. LACRM group filtering — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01
  3. LACRM tasks — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01