volunteer-coordinator
Volunteer management system design with scheduling, skill matching, communication templates, recognition programs, and retention strategies. Use when building volunteer programs, coordinating volunteers, or improving volunteer engagement.
What this skill does
# Volunteer Coordinator Structured frameworks for designing, managing, and scaling volunteer programs with effective scheduling, communication, and retention strategies. ## Volunteer Program Design Template ### Program Foundation ``` VOLUNTEER PROGRAM BLUEPRINT: 1. MISSION ALIGNMENT - Organization mission: [statement] - How volunteers contribute: [specific value] - Volunteer value proposition: [what they gain] 2. PROGRAM SCOPE - Target volunteer count: [number] - Hours per volunteer/month: [range] - Program duration: [ongoing / seasonal / event-based] - Geographic scope: [local / regional / remote] 3. ORGANIZATIONAL STRUCTURE - Program manager: [role / FTE allocation] - Team leads: [number, ratio 1:8-12 volunteers] - Advisory committee: [stakeholder representation] - Reporting chain: [who reports to whom] 4. RESOURCE REQUIREMENTS - Budget: [training, recognition, tools, insurance] - Technology: [scheduling, communication, tracking] - Physical space: [training rooms, storage, workstations] - Insurance/liability: [coverage type and provider] 5. SUCCESS METRICS - Volunteer satisfaction score: [target] - Retention rate (annual): [target, benchmark 65%] - Hours contributed/month: [target] - Program impact metric: [mission-specific KPI] ``` ### Program Maturity Model | Stage | Characteristics | Key Actions | | --- | --- | --- | | **Startup** (0-20 volunteers) | Informal, founder-driven, personal relationships | Define roles, create basic onboarding, track hours | | **Growth** (20-75 volunteers) | Need structure, team leads emerge, systems required | Implement scheduling tool, formalize training, add recognition | | **Established** (75-200 volunteers) | Processes documented, culture defined, metrics tracked | Segment communications, leadership pipeline, impact reports | | **Scaled** (200+ volunteers) | Self-sustaining teams, alumni network, brand identity | Automate workflows, partner programs, advanced analytics | ## Role Description Template ### Standard Volunteer Role Document ``` VOLUNTEER ROLE DESCRIPTION: ────────────────────────────────────────────── ROLE TITLE: [Specific, descriptive title] DEPARTMENT: [Team or program area] REPORTS TO: [Team lead or coordinator name] LOCATION: [On-site address / Remote / Hybrid] ────────────────────────────────────────────── ROLE SUMMARY: [2-3 sentences describing the role purpose and impact] RESPONSIBILITIES: 1. [Primary task with frequency — e.g., "Greet and register participants at weekly Saturday events (9am-12pm)"] 2. [Secondary task] 3. [Tertiary task] TIME COMMITMENT: - Hours per week/month: [range] - Schedule: [fixed / flexible / shift-based] - Minimum commitment: [e.g., 6 months, 1 semester] - Start date: [date or rolling] QUALIFICATIONS: Required: - [e.g., "Must be 18+ years old"] - [e.g., "Reliable transportation to site"] - [e.g., "Pass background check"] Preferred: - [e.g., "Experience with event planning"] - [e.g., "Bilingual English/Spanish"] TRAINING PROVIDED: - [Orientation session — date and duration] - [Role-specific training — format and timeline] - [Ongoing learning opportunities] BENEFITS: - [Skills development] - [Community impact] - [Reference letters after X hours] - [Recognition program eligibility] - [Networking opportunities] PHYSICAL REQUIREMENTS: - [Standing/sitting duration] - [Lifting requirements] - [Accessibility accommodations available] ``` ## Skill Matching Matrix ### Volunteer-to-Role Matching | Volunteer Skill/Interest | Matching Roles | Priority | | --- | --- | --- | | Teaching / mentoring | Tutor, workshop facilitator, youth mentor | High | | Administrative / data entry | Office support, database manager, filing | Medium | | Event planning | Event coordinator, logistics lead, setup crew | High | | Social media / marketing | Content creator, photographer, outreach | High | | Technical / IT | Website maintenance, tech support, data analysis | Medium | | Fundraising / sales | Grant writer, donor outreach, event fundraiser | High | | Physical / outdoor | Habitat restoration, warehouse, delivery driver | Medium | | Medical / health | Health screener, first aid, wellness coach | High | | Legal / advocacy | Pro bono counsel, policy research, court accompaniment | Medium | | Creative / arts | Graphic design, mural painting, music instructor | Medium | | Language / translation | Interpreter, document translator, ESL tutor | High | ### Matching Process ``` SKILL MATCHING WORKFLOW: 1. INTAKE ASSESSMENT Collect during application: - Skills inventory (checklist + self-rating 1-5) - Interests and motivations - Availability (days, times, frequency) - Location preference and transportation - Physical limitations or accommodations needed 2. MATCHING ALGORITHM (manual or automated) Score each candidate-role pair: - Skill match: [0-30 points] - Interest alignment: [0-25 points] - Availability fit: [0-25 points] - Location proximity: [0-10 points] - Experience level: [0-10 points] Total: /100 — Match threshold: 60+ 3. PLACEMENT INTERVIEW - Confirm interest in top-matched roles - Discuss expectations and commitment - Address questions or concerns - Assign role and team lead - Schedule orientation date 4. TRIAL PERIOD - First 2-4 shifts as observation/training - Check-in with team lead at shift 2 - Formal feedback at end of trial (2 weeks) - Confirm placement or offer alternative role ``` ## Scheduling Framework ### Shift Planning Template ``` SCHEDULING MODEL: SHIFT TYPES: Regular — Same day/time each week (best for retention) Rotating — Varies by schedule cycle (fair distribution) On-call — Available pool for last-minute needs Event — One-time or seasonal commitment Remote — Location-independent tasks with deadlines SHIFT STRUCTURE: Morning: 8:00 AM - 12:00 PM (4 hours) Afternoon: 12:00 PM - 4:00 PM (4 hours) Evening: 5:00 PM - 8:00 PM (3 hours) Weekend: 9:00 AM - 1:00 PM (4 hours) COVERAGE PLANNING: Minimum per shift: [number] volunteers Ideal per shift: [number] volunteers Overschedule by: 15-20% (to account for no-shows) Confirmation window: 48 hours before shift Cancellation policy: 24 hours notice required SCHEDULING TOOLS: Simple: Google Calendar + shared spreadsheet Mid-range: SignUpGenius, VolunteerHub, When2Work Advanced: Better Impact, Galaxy Digital, InitLive ``` ### No-Show Reduction Strategy | Tactic | Expected Reduction | Implementation | | --- | --- | --- | | 48-hour reminder (SMS/email) | 25-35% | Automated via scheduling tool | | Confirm or cancel prompt | 15-20% | Reply-required message | | Buddy system (paired volunteers) | 10-15% | Match new with experienced | | Consistent schedule | 20-30% | Same day/time commitment | | Post-shift appreciation message | 10-15% | Sent within 24 hours | | Easy reschedule (not just cancel) | 15-20% | Swap board or waitlist system | ## Onboarding Checklist ### New Volunteer Onboarding Sequence ``` ONBOARDING TIMELINE: DAY 0 — APPLICATION RECEIVED - [ ] Acknowledge receipt within 24 hours - [ ] Background check initiated (if required) - [ ] Skill matching assessment completed WEEK 1 — WELCOME - [ ] Welcome email sent (see communication templates) - [ ] Orientation session scheduled - [ ] Volunteer handbook provided (digital or print) - [ ] Emergency contact form collected - [ ] Waiver/liability form signed WEEK 2 — ORIENTATION - [ ] Organization mission and history overview - [ ] Facility tour and safety briefing - [ ] Introduce team lead and fellow volunteers - [ ] Role-specific training session - [ ] Set up access: badges, systems, communication channels WEEK 3-4 — TRIAL SHIFTS - [ ] Shadow experienced volunteer (shift 1) - [ ] Supervised in
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.