Use understandable categories
Choose areas and time bands that your team actually uses. A location list should not require a precise home address when a broad service area is enough. Keep free-text clarification available in an approved internal process for exceptions. Avoid an elaborate field set that nobody maintains after the first enquiry.
Add a checked date
A preference without context can become misleading. Record when it was supplied or last reconfirmed and who owns the next review. Do not invent an expiry rule as if it were universal; choose a cadence appropriate to your activity. A stale preference belongs in a review queue rather than being silently treated as current capacity.
Separate invitation and acceptance
Use preferences to shortlist people to contact, then send a specific invitation through the approved route. Record acceptance separately in the actual scheduling process. If someone declines, update the relevant invitation—not necessarily all future availability. A single declined date may tell you very little about their broader interest.
Worked example
A fictional volunteer usually helps in the north district but accepts a one-off event elsewhere. The coordinator records the exception for that event and asks whether the general preference changed. Without that distinction, the next coordinator might repeatedly send unsuitable invitations based on a single past commitment.
Add scope and freshness to a preference
“Weekday mornings” becomes more useful when accompanied by the activity or location it concerns and when it was last confirmed through the approved process. It still does not authorize a particular assignment. When reviewing old preferences, distinguish unknown freshness from a definite change. Do not contact every historical volunteer solely to fill a dashboard. Start with people involved in current authorized coordination and follow the organization’s communication rules. A specific invitation should carry its own date, place and response record rather than inheriting acceptance from a general preference.
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.
- LACRM custom fields — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01
- LACRM group filtering — Merchant documentation · lessannoyingcrm.com · Merchant-controlled · checked 2026-10-01
- POINT volunteer platform — Merchant documentation · pointapp.org · Merchant-controlled · checked 2026-10-01