Tell Me About Your Volunteer Program (so I stop guessing)

• How many active volunteers do you manage today (approximate)? Options: Under 200, 200–499, 500–999, 1,000–2,000, Over 2,000, Unsure / varies
• What programs, sites, or event types are included under that umbrella (brief list)?
• Which months or seasons create the most scheduling pressure for your team? Options: Year-round similar, Seasonal surge (specify in next field), Annual event(s), Grant reporting cycles, Other
• How do you currently coordinate sign-ups and schedules (select all that apply)? Options: Spreadsheets, Email chains, Paper sign-up sheets, In-house system, Commercial scheduling tool, Donor/CRM with add-ons, Phone/text
• Walk me through a typical day in your role when schedules are going smoothly—what do you spend most of your time doing?

What if an empty shift was your loudest alarm?

• How often do unfilled shifts or last-minute no-shows force you to change services, pay overtime, or cancel activities? Options: Daily, Weekly, Monthly, Rarely, Unsure
• When an important shift goes unfilled, what usually happens next—who reacts and what are the concrete consequences?
• Which of these impacts have you actually experienced because of scheduling gaps (select all that apply)? Options: Paid staff overtime, Program cancellations, Reduced service hours, Volunteer burnout/attrition, Grant/reporting noncompliance, Reputational harm
• What current metric, if improved by 20–30% in three months, would make you feel this problem is being solved? Options: Fill rate, No-show rate, Verified volunteer hours, Time to fill a shift, Coordinator hours spent scheduling, Volunteer satisfaction
• Tell me about the last time you scrambled to fill a shift—what went wrong, who was involved, and how did it feel?

Who’s on your team when the stakes are high (and who’s not but should be)?

• Who are the internal stakeholders that must be involved or informed for scheduling, background checks, and hour-audit work? Options: Volunteer coordinator(s), Program directors, HR/Compliance, Finance/Grants, IT/Integrations, Executive leadership, Site managers
• Who signs off on procurement, pilot scope, or legal terms for new platforms in your organization? Options: Executive director/CEO, Director of operations, Finance lead, Board member, Legal counsel, I do
• Describe the volunteer population we’d be working with for a pilot (age ranges, language, tech comfort, mobility, access to email/smartphones).
• Which external partners/vendors play a role in your volunteer operations (background check vendors, learning platforms, payroll, CRM), and who owns those relationships?
• If we had to bring three people into a kickoff meeting to make decisions quickly, which roles should be in the room? Options: Volunteer coordinator, Program director/site lead, IT/sysadmin, Finance/grant manager, HR/compliance, Executive sponsor

Tell me about the last time things went sideways (we learn a lot from the messy stories)

• Share a concrete incident where scheduling, background checks, or hour-tracking created audit, safety, or service problems—what was the outcome?
• Which of these consequences have you faced after such incidents? Options: Grant reporting gaps, Legal risk or compliance notice, Increased insurance exposure, Volunteer churn, Operational downtime, Other
• How did the organization respond (both operationally and emotionally)—was there blame, process change, or leadership action?
• If a single underlying cause could be fixed to prevent similar incidents, what do you think it would be?
• How long have these kinds of problems been happening, and how have they influenced donor/grant or leadership conversations? Options: Less than 6 months, 6–12 months, 1–3 years, Over 3 years

What would success actually feel and look like for your team?

• Which outcomes would be non-negotiable to call a pilot successful (select up to three)? Options: Filled shifts / improved fill rate, Reduced no-shows, Audit-ready verified hours, Reduced coordinator time spent scheduling, Improved volunteer retention, Faster background-check turnaround
• Please provide your current baseline for any of the outcomes you selected above (numbers or percentages).
• What is the minimum improvement (in % or absolute terms) you would need within the pilot period to consider it a success? Options: 5–10%, 11–20%, 21–40%, Over 40%, Unsure / need help setting realistic targets
• Beyond metrics, how should volunteers and staff feel differently if things are working—give concrete examples of behaviors or feedback you'd expect.
• If we meet those measures but the program still feels administratively harder to run, would you consider that a partial success or failure? Options: Partial success, Failure, Depends on context, Unsure

What’s actually standing in the way of making that change stick?

• Which barriers worry you most when adopting a new volunteer system (choose all that apply)? Options: Volunteer resistance / tech adoption, Data migration errors, Integration complexity, Staff capacity for implementation, Budget/contracting, Legal/compliance concerns
• Tell me about a previous attempt to change tools or processes—what was tried, and why didn’t it deliver the outcome you wanted?
• How would your volunteers most prefer to be onboarded (select up to two)? Options: In-person training, Video walkthroughs, One-on-one calls, Email step-by-step, Peer champions/volunteer ambassadors
• If adoption is a risk, what incentives or communications have converted reluctant volunteers before?
• How flexible is your leadership on trying a pilot that changes workflows for a subset of programs? Options: Very flexible, Open with conditions, Reluctant but possible, Not at all

Can your data and systems actually tell the truth (about volunteers, hours, and background checks)?

• Which systems currently hold volunteer records, schedules, or hour logs (select all that apply)? Options: Spreadsheet(s) (Excel/Sheets), Donor CRM, HRIS/payroll, Legacy volunteer platform, Paper files, Shared drives, Other
• What formats can you export for import (CSV, Excel, API, SFTP)? Options: CSV/Excel, API access, SFTP/FTPs, Manual entry only, Unsure
• How clean is your volunteer data for fields we rely on—skills, availability, unique IDs, date of birth, background-check status? Options: Mostly clean, Partial / some fields missing, Very inconsistent, We don't track some of these
• Who owns data governance (who can approve exports, handle PII, and sign a data-sharing agreement)? Options: IT, HR/Compliance, Volunteer coordinator, Executive sponsor, Other
• Do you have specific compliance or privacy requirements we should know about (HIPAA, state background-check rules, grant restrictions)? Please list.

If we built your pilot together, what would it need to include to be impossible to say no to?

• Which pilot scope best matches your appetite for risk and speed (pick one)? Options: Single program/site small cohort, Single high-impact event, Multiple programs across one site, Enterprise-wide trial
• How long should the pilot run to give you confidence (and why that length)? Options: 2 weeks, 1 month, 2–3 months, 3–6 months, Depends on program cadence
• What acceptance criteria should we use to evaluate the pilot (list top 3 with target numbers where possible)?
• What training cadence and materials would make rollout least disruptive (select all that apply)? Options: Live coordinator training, Recorded videos, Quick reference sheets, Volunteer office hours, Train-the-trainer model
• Who must sign off on pilot completion (roles and any required documentation)?

Are you looking for a tool — or for a partner who changes outcomes?

• What does a successful vendor partnership look like to you (implementation support, SLA, dedicated CSM, shared roadmap)? Options: Implementation support, Dedicated customer success manager, Service-level agreements, Joint product roadmap input, Quarterly business reviews
• What communications cadence would keep stakeholders comfortable during a pilot (weekly, biweekly, milestone-based)? Options: Weekly, Biweekly, Monthly, Milestone-based only, As-needed
• If we could remove one administrative burden from you in the next 30 days, what would it be?
• What are the must-have contractual or commercial guardrails you need before approving a pilot (insurance, indemnity, data terms, cancellation rights)?
• Who else should we speak with next to accelerate alignment (names, roles, and best contact method)?

• Pre-Session Alignment (Solution Experience Prep)
• Scenario Walkthrough — Automated Shift-Fill (Surge / Event)
• Scenario Walkthrough — Skills Matching & Background-Check Coordination
• Scenario Walkthrough — Hour Tracking, Reconciliation & Reporting
• Consolidation, Acceptance Criteria & Pilot Decision

• Validate reconciliation workflows and confirm required approvals are captured for audit trails.
• Customer to assign an SME (operations/coordinator) and an approver for each scenario.
• Facilitator to produce a one-page meeting plan for each scenario tied to the future-state sentence.
• Identify and document acceptance criteria (numeric targets) to validate at the end of each scenario.
• Recap Current & Future State
• Demonstrate the automated shift-fill flow using the customer's data and show measurable reductions in unfilled shifts.
• Validate system behavior against the customer's real-world exceptions and confirm whether it meets the future-state sentence.
• Identify configuration, integration, and data requirements to achieve the demonstrated outcome in production.
• Capture configuration changes and rule logic required to mirror the customer's policies.
• List integrations (SMS provider, calendar, HR) and required credentials to enable live notifications.
• Assign owner to resolve any identified data-cleanup items affecting fill accuracy.
• Recap Problem & Desired Compliance Outcome
• Confirm that skills-based matching places appropriately qualified volunteers for credentialed roles.
• Validate that background-check coordination and gating satisfy the customer's audit and compliance needs.
• Identify taxonomy and integration gaps that would prevent live enforcement of role prerequisites.
• Customer to provide definitive list of required skills/certificates per role and acceptable substitutes.
• Integration owner to confirm background-check vendor APIs and onboarding steps.
• Create mapping document for skill tags between legacy records and platform taxonomy.
• Confirm Audit Requirements
• Prove hour-tracking produces traceable, audit-ready records that meet the customer's documented requirements.
• Introductions & Objectives
• Identify any volunteer adoption blockers and agree mitigation steps for the pilot.
• Define the exact report templates and fields required for grant/audit deliverables.
• Prepare a short volunteer-facing quickstart (phone + web) to reduce adoption friction during pilot.
• Assign owner to sample-compare platform hour data vs. legacy records for a pilot cohort.
• Summary of Each Scenario — Diagnosis -> Proof
• Obtain mutual agreement on pilot scope and the numeric acceptance criteria to be used for pilot validation.
• Assign owners and timelines for remediation items required to reach pilot readiness.
• Schedule the next Deployment-group readiness meeting and confirm immediate next steps.
• Finalize and distribute the pilot plan with scope, acceptance criteria, success metrics, and owners.
• Customer and vendor owners to complete documented remediation items before the Pre-Deployment Readiness milestone.
• Schedule Pre-Deployment Readiness meeting and provide required artifacts (cleaned data export, integration creds, training materials).
• Produce a one-sentence current state that all participants agree on.
• Quantify the operational and financial consequences of the current state.
• Produce a one-sentence future-state outcome that the experience will prove.
• Confirm scenarios, sample data, participants, and pre-work deadlines for the Solution Experience.
• Customer to provide anonymized sample roster, recent shift templates, and a small export of background-check statuses.
• One-sentence Current State
• Scenario Setup
• Open Issues & Remediation Actions
• Simulate Volunteer Time Capture
• Define Match Rules Using Customer Taxonomy
• Run Automated Fill Flow
• Reconciliation & Exception Handling
• Live Match Simulation
• Consequence Quantification
• Agree Pilot Scope & Boundaries
• Generate Audit-Ready Reports
• Map Results to Consequences
• Confirm Acceptance Criteria & Metrics
• One-sentence Future State
• Background-Check Workflow Simulation
• Validation Checkpoints
• Validate Accuracy Thresholds
• Confirm Scenarios & Priority Use Cases
• Risk Register & Mitigations
• Audit Trail & Evidence for Compliance
• Data & Access Checklist
• Validation & Forced Confirmation
• Volunteer UX & Adoption Risks

• Import and Clean Volunteer Records
• Provision Volunteer User Accounts
• Deploy Volunteer Self-Service Profile Portal
• Enable Hour Logging and Verification
• Install Onsite Check-In Kiosk with QR Codes
• Coordinate Background Checks with Vendor Integration
• Activate E-Signature Onboarding Documents
• Configure Role-Based Staff Permissions
• Set Up API/CSV Integration with HR/Donor Systems
• Generate Grant-Ready Volunteer Hour Reports
• Activate SMS and Email Volunteer Communications
• Track Certifications and Credential Expirations
• Issue Digital Recognition Badges and Certificates

Import and Clean Volunteer Records

• Do you have existing volunteer records to import for the pilot? Options: Yes, No
• What format are your current records in? Options: Spreadsheet (CSV/XLSX), Volunteer database export, HR/donor system export, Paper/Scanned, Other
• Approximately how many volunteer records do you intend to import for this pilot? Options: Less than 500, 500-2,000, 2,001-10,000, More than 10,000
• Which of the following fields are present in your records (select all that apply)? Options: Full name, Email, Phone, Date of birth, Address, Skills/roles, Background check status, Volunteer ID
• Do records contain duplicates or conflicting entries that require deduplication? Options: Yes, No, Not sure - need review
• Are there known data quality issues we should clean (e.g., missing emails, inconsistent names)? Please list.
• Do you need assistance mapping legacy fields to platform fields during import? Options: Full mapping assistance, Partial assistance, We will map ourselves
• Are there privacy, consent, or grant-related constraints on which records can be imported? Options: Yes, No, Unsure - need assessment

Provision Volunteer User Accounts

• Will volunteer accounts be created in bulk or individually by coordinators? Options: Bulk (imported), Individual (coordinator creates), Self-signup by volunteer, Mixed
• What will be the primary login identifier for volunteers? Options: Email address, Phone number/SMS OTP, Volunteer ID, SSO/AD
• Do you require account provisioning via SSO/AD integration for staff or volunteers? Options: Yes - staff only, Yes - volunteers and staff, No
• Should accounts require activation steps (welcome email, password set, acceptance of policies)? Options: Yes, all steps, Only welcome email, No activation required
• Which default roles should be assigned at account creation (select all that apply)? Options: Volunteer, Coordinator, Program Manager, Admin, Trainer
• Do you want automatic role assignment based on imported attributes (e.g., program membership)? Options: Yes, No
• Are there naming or account ID conventions we must follow?

Deploy Volunteer Self-Service Profile Portal

• Do you want volunteers to have access to a self-service profile portal in the pilot? Options: Yes, No
• What profile fields should volunteers be able to view or edit? Options: Contact info, Availability, Skills/certifications, Emergency contact, Photo
• Should volunteers be able to upload documents (licenses, certificates) in the portal? Options: Yes - allow uploads, No - uploads restricted to staff
• Is mobile-first responsiveness required for volunteer portal usage? Options: Yes, No
• Do you require multi-language support for the portal? If yes, which languages? Options: English, Spanish, Other
• Should the portal include step-by-step onboarding guidance or a checklist for new volunteers? Options: Yes - checklist and tutorials, Yes - checklist only, No
• Do you want the portal to show scheduled shifts, open shifts, and hour history to volunteers? Options: All three, Only scheduled shifts, Only open shifts, No shift information

Enable Hour Logging and Verification

• Will hours be logged by volunteers, coordinators, or via automatic check-in? Options: Volunteer self-log, Coordinator log, Automatic via kiosk/check-in, Mixed
• Do you require an approval workflow for logged hours (e.g., supervisor verification)? Options: Yes - supervisor approval required, Optional approval, No approval required
• What granularity of time tracking is needed? Options: By shift (start/end), By task, By minute/decimal hours
• Should edits to logged hours include an audit trail and reason for change? Options: Yes - audit trail required, No - simple edits allowed
• How frequently do you need hour reconciliations or reports? Options: Daily, Weekly, Monthly, Per event
• Do you require automated alerts for missing or unverified hours? Options: Yes, No
• Are there grant or payroll rules tied to hour rounding or minimum shift lengths we must enforce? Options: Yes - specify rules, No

Install Onsite Check-In Kiosk with QR Codes

• Will the pilot include onsite check-in using kiosks and QR codes? Options: Yes, No, Maybe - evaluate
• How many physical check-in locations or devices will you need for the pilot? Options: 1, 2-5, 6-20, 20+
• What device types will you use for kiosks? Options: Tablet (iOS/Android), Laptop, Dedicated kiosk hardware, Volunteer mobile phones
• What is the expected internet connectivity at check-in locations? Options: Always connected, Intermittent, No connectivity (offline mode required)
• Do you need printed badges or on-site badge printing tied to check-in? Options: Yes - badge printing, No
• Should check-in capture a photo or signature for verification? Options: Photo capture, Signature capture, Neither
• Do you want check-in events to automatically populate hour logs and attendance reports? Options: Yes, No

Coordinate Background Checks with Vendor Integration

• Are background checks required for volunteers in scope of this pilot? Options: Yes, No, Some roles only
• Which background-check vendors or services do you currently use or prefer? Options: Checkr, Sterling, HireRight, Local/state vendor, Other/None
• What level of screening is required (select all that apply)? Options: Identity verification (name/DOB), Criminal history (national/state), SSN trace, Motor vehicle records, Fingerprinting
• How should volunteer consent for checks be collected? Options: E-sign via portal, Paper consent, Hybrid
• Do you need automated status updates from vendor to populate volunteer profiles? Options: Yes - real-time updates, Batch updates, No - manual update
• Are there specific jurisdictional or international considerations (multi-state, international volunteers)? Options: Yes - multi-jurisdiction, No
• What retention or data-sharing policies must we enforce for background check results?

Activate E-Signature Onboarding Documents

• Do volunteers need to sign onboarding documents electronically for the pilot? Options: Yes, No
• Which document types need e-signature support (select all that apply)? Options: Volunteer agreement, Liability waiver, Background consent, Code of conduct, Training acknowledgement
• Which e-signature provider do you prefer or already have contracts with? Options: DocuSign, Adobe Sign, Platform built-in, Other
• Do you require templated documents with variable fields (e.g., program name, dates)? Options: Yes - templating required, No - one-off documents
• Should signed documents be automatically saved to volunteer profiles and retained for audits? Options: Yes - auto-save and retain, Save but manual retention policy, No
• Do you want automated reminders for unsigned or expiring documents? Options: Yes, No
• Are there legal or governance approvals required before enabling e-signatures? Options: Yes - legal review needed, No

Configure Role-Based Staff Permissions

• How many distinct staff roles need permissions defined for the pilot? Options: 1-2, 3-5, 6-10, 10+
• Do any roles require restricted access to PII or background-check results? Options: Yes - restrict access, No - open access
• Should permissions be scoped by program, location, or both? Options: By program, By location, Both, No scoping required
• Do you need temporary elevated access (time-limited admin roles) during the pilot? Options: Yes, No
• Is integration with your SSO/identity provider required for staff permissions? Options: Yes, No, Planned later
• Do you require audit logging for staff actions (exports, edits, deletions)? Options: Yes - detailed audit log, Basic logging only, No
• Are there any compliance or internal policies we must reflect in permission settings?

Set Up API/CSV Integration with HR/Donor Systems

• Which HR, donor, or CRM systems must integrate with the platform for the pilot? Options: Salesforce, Raiser’s Edge/NXT, BambooHR, Workday, Custom/Other
• Preferred integration method for each system? Options: Realtime API sync, Scheduled CSV/flat file, Manual CSV import, SFTP batch
• What sync frequency do you require for volunteer data and hours? Options: Realtime, Hourly, Daily, Weekly, Manual

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW) - Pilot & Rollout
• Commercial Terms & Pricing Schedule
• Payment Authorization & Invoice Schedule
• Data Processing Agreement (DPA)
• Volunteer Data Use & Consent Addendum
• Background-Check Authorization & Vendor Access
• Integration & API Access Agreement
• Service Level Agreement (SLA) - Pilot Support
• Roles, Responsibilities & Escalation (RACI)
• Acceptance Criteria & Sign-off
• Change Order & Scope Amendment
• Renewal, Extension & Termination Terms
• Security, Insurance & Indemnification Addendum
• Training & Enablement Confirmation

• Success Validation Review
• Lessons Learned Workshop (Retrospective)
• Enhancement Backlog Triage & Prioritization
• Support & Shared Channel Handoff
• Executive Success Review & Next-Phase Alignment

• Put a clear, documented support and escalation model in place with SLAs and named contacts.
• Set Context & Working Rules
• Capture a clear set of actionable lessons and improvements with owners and timelines.
• Create a prioritized list of process and product changes to prevent recurrence of key issues.
• Establish a single repository and format for lessons learned that can be referenced for rollout and training.
• Create a lessons-learned document with categorized issues, root causes, and assigned owners.
• Schedule focused working sessions for each high-priority improvement to define implementation plans.
• Update deployment runbooks and onboarding materials based on identified training gaps.
• Review Incoming Requests & Issues
• Convert scattered requests into a qualified, prioritized backlog with clear owners and timelines.
• Ensure high-severity operational issues have immediate remediation paths and SLAs.
• Agree governance and cadence for the shared issues/enhancements channel.
• Publish the prioritized backlog with owners, estimated delivery windows, and status tracking link.
• Create quick-fix tickets for high-severity items and assign to engineering/support with SLAs.
• Document channel rules for submitting, triaging, and escalating enhancement requests.
• Support Model Overview
• Opening & Objectives
• Deploy and govern a shared communication channel for real-time issues and enhancement requests.
• Agree on reporting and review cadence to keep transparency on outstanding issues and backlog progress.
• Create and seed the shared channel, invite named stakeholders, and publish channel guidelines.
• Publish the support roster with primary and backup contacts and SLA commitments.
• Schedule recurring support-review meetings (e.g., weekly/monthly) and publish calendar invites.
• One-slide Current State & Trigger
• Secure a clear executive decision or commitment on the next commercial or rollout step.
• Ensure executives understand the quantified value and remaining risks so resourcing decisions are informed.
• Align on any funding, timeline, or governance changes required to scale the solution beyond the pilot.
• Provide an executive one-page briefing summarizing outcomes, ROI, and recommended next steps within 48 hours.
• If approved, draft the high-level rollout plan and resource request for executive review.
• If more data is requested, define the specific additional metrics or analyses and owners to deliver them.
• Confirm whether the pilot met the agreed acceptance criteria and obtain formal customer validation.
• Quantify business impact (time saved, risk reduced, dollars avoided) and ensure stakeholders understand the consequence.
• Agree on remediation actions and ownership for any gaps preventing acceptance.
• Document next commercial or rollout decisions (renew, expand, additional pilots) based on validated outcomes.
• Publish validated outcomes report (metrics, ROI, gaps) and circulate to stakeholders within 3 business days.
• Assign owners and deadlines for each remediation action identified in the gap analysis.
• If accepted, draft/update the rollout/commercial agreement reflecting pilot outcomes and proposed next phase.
• Current-state Baseline Recap
• Qualification: Reproducibility & Impact
• What Worked (Evidence)
• Topline Outcomes & ROI
• Shared Channel Setup & Purpose
• Risks & Mitigations
• What Didn’t Work (Evidence)
• Categorize & Severity Assignment
• Acceptance Criteria & Future State Reminder
• Issue Triage & Escalation Flow
• Change Request & Enhancement Path
• Recommended Next Steps & Options
• Prioritization Exercise
• Root Cause & Pattern Identification
• Metrics Review: Adoption & Usage
• Prioritize Improvements
• Define Delivery Paths
• Metrics Review: Operational Outcomes
• Roles & Contacts
• Decision & Commitment
• Consequence & ROI Quantification
• Confirm Shared Channel Governance
• Action Planning & Owners
• Reporting & Review Cadence