THE ULTIMATE GUIDE TO CHOOSING VOLUNTEER MANAGEMENT SOFTWARE

INTRODUCTION

If you view spreadsheets as the superior way to manage your volunteer program or aren’t ready to consider a change, please stop reading this guide now. It’s not for you!

This guide is for those looking for a better way to work and to get things done for their organization. This includes a commitment to supplying the right tools to operate securely, efficiently, and effectively (for the betterment of all stakeholders involved), as realized with the implementation of a good volunteer management solution (VMS).

Afterall, aren’t volunteers supposed to be considered the life blood to an organization’s mission achievement?

Simply put, this guide is for leaders... and since you’ve read this far, leaders like you! It’s for those who will act to find solutions to problems because leadership is an action, not a position.

This guide will address a range of topics including:

• What’s a VMS and how can it help you?
• Why aren’t spreadsheets the right tool for the profession?
• How can a VMS keep your volunteer data safe?
• Is a VMS affordable?
• Where do we begin the journey to find a suitable VMS?

Featured Resource

The Ultimate VMS Guide & Worksheet

 

Download Now

We’re pleased you’ve found this guide.

It’s designed to be a simple resource. It’s packed with diverse and highly knowledgeable insights. It is direct. And, most importantly, it’s devised to help you and your team experience a smooth journey as you explore finding the right VMS for your organization’s unique needs.

Table of Contents:

1. Common problems plaguing volunteer services
2. What's a VMS & its benefits?
3. What’s Preventing Change? (…and how to overcome)
4. Your roadmap to choosing a VMS solution with confidence
1. Problem Statement & Goal
2. Project Team
3. Profile & Needs Assessment
4. Project Timeline & Task Assignment
5. Ready, Set, Go...Shortlist + Select!

1. Common Problems Plaguing Volunteer Services

The role of Volunteer Engagement Professionals (VEP’s) is an important one in supporting your organization’s mission and the community it serves. It involves engaging with many people, such as, volunteers, leadership, members of the Board, and community benefactors. It involves many responsibilities: recruitment, retention, selection, matching, training, compliance, communication, scheduling, advertising, management, etc.

In performing the role, these are some commonly cited challenges, when not having a suitable VMS in place:

• Too much data entry
• Duplication of data entries
• Reporting that takes an abundance of time to produce
• Lack of data integrity (resulting in an increased risk for poor decisions being made for the program)
• Too much time being spent on administrative tasks resulting in less time working in direct volunteer engagement and program progression.
• Using antiquated tools and systems or ones not designed specifically for volunteer services
• Using several disconnected tools to perform the role (e.g. one to help log hours; another for shift sign-up/scheduling; a third for email/newsletter communication, etc.)
• A lack of proper data security controls of confidential volunteer information
• Inability for staff to access the right data when needed
• Volunteer and staff disengagement and retention challenges

That’s a long (and concerning) list! The good news is that with any problem there lies a solution.

2. What's a vms & its benefits?

A VMS is an all-in-one, web-based software solution designed to serve the needs of volunteer services teams.

It’s a platform that includes all the tools to enable effective recruitment, screening, training, onboarding, scheduling, communications, time logging, reporting, and the tracking and recording of meaningful data on your volunteers. It also provides a method for volunteers to engage with the platform for the purposes of initial application, receiving communications, finding and filling vacancies, managing their own volunteer schedule, logging hours, reporting on their own contribution (e.g. hours/time) and so much more.

To be clear, it’s not a spreadsheet! 😀

In fact, it’s far more empowering than any spreadsheet you may be using.

While spreadsheets are powerful, often free, and serve a purpose, they expired long ago as the primary tool to be utilizing for your multi-faceted position as they are not specifically designed to perform the work that you do.

This guide is encouraging you to “ditch the spreadsheet!” #ditchthespreadsheetchallenge

Benefits realized when implementing the use of a VMS in your organization include:

• Better use of your time (…and everyone’s, including volunteers)
• Better reporting
• Better communications
• Better stakeholder engagement
• Better data security and confidentiality (mitigate risk)
• Better data integrity
• Better value due to consolidating the number of systems in use, without the big price tag
• Better visibility of your program through the use of modern technology
• Better accessibility to data
• Better volunteer and staff morale and retention
• …better, better, better!

With so many benefits, what could possibly be holding people and organizations back from choosing to change?

3. What's preventing change? (... And how to overcome)

Attitudes are our learned ways of responding to people and situations based on the beliefs, values, and assumptions we hold that are reflected in our behavior.

It’s quite possible that some folks at your organization may not be enthusiastic about the thought of exploring a VMS because it can spark feelings of anxiety, incompetence, and general uncertainty.

Brace yourself for this possibility when you lean on your team to embark on this project or if the thought of implementing a VMS makes you anxious; challenge yourself to push through. Be empathetic and ask questions to understand their (or your own) concerns. Most often, people’s knee-jerk reaction to feeling anxious can be alleviated by simply including them in the process so their questions get addressed and resolved. Inclusion leads to buy-in!

If your team wants to solve the problems being experienced, this must come with a change in how you’re currently operating if you’re going to reach your goals.

“We cannot solve our problems with the same
level of thinking that created them.”
- Albert Einstein

For some, it’s worth contemplating: Am I being part of the solution or problem?

Check out the list below. If any of these objections or attitudes are present in your organization, you may find these resources useful:

• There’s nothing wrong with the spreadsheet we’re using and it’s FREE (... but at what cost?)
• Just manage your volunteers in the HR, Donor or other CRM (Customer Relationship Management) solution we’ve already invested in (…which, by the way, isn’t designed for volunteer services - a.k.a. how about you go try to fit a square peg into a round hole, ok!)
• Software is too difficult for our volunteers to learn. (ummmm, really?)
• We can’t afford software. (Is that fact or assumption? What efforts have been made?)
• We’re already using several tools to help us manage our program and don’t need another one (have you considered how multiple tools could be hindering your operation?)
• Our practices don’t put the confidential volunteer data at risk. (or do they?)

Consider this your fork-in-the-road moment.

Does your team act towards finding a solution or remain complacent?

Your team’s next move is very telling.

Now that we’ve applied some tough love and addressed how our attitudes may be holding the program and team back from excellence, let’s take that new attitude along for the ride and begin the journey of finding the right VMS for your team.

4. Your roadmap to choosing a VMS solution with confidence

If you begin with the end in mind, your ultimate goal will be to select a VMS that your team is confident will solve the challenges you’ve been facing and thus elevate your program to new heights. To do this in the most efficient and effective way, you absolutely must plan, prepare, and then execute your plan. Treat this experience as a project. Projects come with steps to help you be successful in attaining your goals/objectives. Execution becomes a waste of time without proper planning and preparation and vice versa!

Plan. Prepare. Execute. - The 3 pillars to project success:

• Plan. Determining what to do to reach the desired goal.
• Prepare. Gather what you’ll need to help facilitate the plan.
• Execute. Action what you said you were going to do during the planning and preparation steps.

To help you build your plan and prepare to find a suitable VMS, please download the accompanying worksheet and follow the sections in the buyer’s guide below.

Featured Resource

The Ultimate VMS Guide & Worksheet

 

Download Now

1. Problem Statement & Goal

   This section will help you identify any problems being experienced by the team, define your goal, and convey this to Leadership to highlight the gap between the current state vs. desired state.

   Leadership is a critical teammate to have onboard from the get-go! Please do not begin the journey of finding a VMS solution until Leadership has been made aware of the problems being experienced and is 100% supporting the team project of finding a VMS.

   Since the volunteer department for most nonprofits is on the smaller size and typically runs a leaner operation (e.g. fewer staff), we find it’s typically not necessary that you spend an exorbitant amount of time involved in building a formal business case to present to Leadership in order to obtain support for this project. For that reason, we simply focus on creating your problem statement and goal.

   The Problem Statement.

   A problem statement is written at the beginning of a project. Its intent is to identify the project’s purpose in a clear, concise, and compelling manner such that when presented to Leadership, there’s no doubt that this problem requires attention and is vital to solve.

   There’s usually more than one problem that needs solving but some are of higher priority than others. List your team’s main challenges on the worksheet, indicate who on your team it affects (e.g. I.T., volunteer coordinator, volunteers, etc.) and what the consequences are if the problem should persist.

   Example.

   THE PROBLEMS	WHO IT AFFECTS	THE CONSEQUENCES
   Too much time spent on data entry	Volunteer coordinator, the community we serve (indirectly)	Takes away from building relationships with volunteers and progressing the volunteer program to better serve our org mission.
   Recruitment and data storage practices put the volunteer data vulnerable/ at risk	Volunteers, I.T., organization/program	Breach of confidential volunteer data; organization’s reputation damaged; volunteer program credibility damaged.
   …etc.

   Hint: If any of the problems relate to data security, you’ve found your #1 problem and likely the only one you need to focus on in your statement to obtain permission for this project! 😀

   It’s likely that leadership IS NOT going to ignore a data security risk because such inaction places your volunteer data in a very vulnerable position and puts your organization’s reputation and credibility in jeopardy. If Leadership is going to ignore a data security risk, well then…“Houston, we have a problem!” Please revisit the section on “What’s Preventing Change? (…and how to overcome).”

   Narrow your above list to identify your top 1-3 problems to focus on for creating your problem statement.

   Afterall, “a problem well written is a problem half solved.”
   -Charles Franklin Kettering (American Engineer)

   Fill in the blanks to create yours:

   The problem(s) is are: These problems affect these people/depts: The consequences should these problems persist include:

    

   Example.

   Since the inception of the program three year ago, the volunteer services team has been using multiple, antiquated, and disconnected tools which results in numerous inefficiencies, staff and volunteer frustrations, and data security concerns [the problem(s)]. This problem affects many stakeholders, including volunteers, volunteer services staff members, I.T. and our organization/program [who it affects]. To diminish such consequences as wasted time + money, staff/volunteer disengagement and turnover, and damage to the org/program reputation (eg. data breach) [the consequences], we’re proposing Leadership grant permission to form a project team to explore volunteer management software solutions to help solve these problems [the proposed solution]

   The Goal.

   You’ll define your goal to illustrate the desired state you’re striving to reach by solving the problem(s).

   Simply stated, the goal is to select a VMS that your team is confident will solve the challenges you’ve been facing and thus elevate your program to new heights (of mission achievement).

   You can re-write it how you wish on your worksheet, however, that’s the gist of it! 😀

   Now share your Problem Statement and Goal with Leadership.

   To be clear, approaching leadership at this point isn’t about having all the answers about a suitable VMS (eg. costs, support, etc.) or even recommending a specific VMS as the best solution. It’s simply about obtaining permission to form a project team to explore your VMS options.

   Was permission granted to form a project team? Congrats! Let’s move on to the next step…

2. Project Team

   Finding the right solution is a team decision.

   By involving others, the solution you choose will best serve your team’s diverse and specific needs, while resulting in greater buy-in from the various stakeholders, because they were included in the process.

   It may be cliché, but Together. Everyone. Achieves. More (T.E.A.M.).

   Below are some common roles/job titles involved in this project:

   • Volunteer Coordinator and/or Manager - Regular user of the software; thus, the solution needs to be intuitive and solve the challenges that this current team member faces that has led to looking into a solution.
   • Volunteers - Can be using the software too, so get their feedback on needs and buy-in. Include 1-2 volunteers based on their level of comfort with tech (low/medium to high). Involving a volunteer who may be less tech savvy can help address concerns and alleviate any fears of change while helping the project team gain perspective. Also, inquire if you have any volunteers with experience in vetting software solutions or has an I.T. background. Their guidance/input can be helpful in navigating this project, especially if your team doesn’t have I.T. expertise on staff or the budget to outsource that level of expertise for this project. Including a ‘high profile’ volunteer in this process can also help ‘sell’ the solution to the rest of you volunteer team later on as well.
   • I.T. - Your I.T. team (or person) will help you ensure that the VMS meets the organization’s technical requirements; particularly when it comes to data security and privacy of the information housed within. Additionally, they can help you determine which technical and privacy features should be must-haves as you develop your short list of VMS’s. This can save you from wasting time evaluation systems that do not meet the minimum level of security and privacy required by your organization. Sometimes I.T. may also have initial software configuration responsibilities when first setting up some aspects of your chosen VMS. If you have an I.T. Dept or staff member, include them!
   • Consultant / Project Manager - If any part or all of your journey will be outsourced under the guidance of a consultant or project manager, include this role in your worksheet. Some organizations are small and do not have an I.T. member on staff; however, may have a budget to outsource the I.T. expertise to a consultant who specializes in this area should the org feel less confident in decision making in this area on their own. You can also visit www.betterimpact.com/partnerships to consider leaning on a Better Impact Certified Consultant in your region (USA, Canada, UK, Portugal, Australia/New Zealand) who has supported nonprofits/organizations through the journey of finding a VMS.
   • Executive Director - Generally giving final approval for the selected VMS and may also want access to the software to view high level data about the program (eg. reporting).
   • Board of Directors - If your organization is run by an operational board, rather than governance board, it might have the last stamp of approval to move forward with the software subscription.

   Use your worksheet to help form your project team.

   Example:

   Name	Job Title	Purpose for involvement (Project Role)
   “Jamie”	I.T. Specialist	To review VMS’s for data security and meeting our org’s I.T. requirements
   "Wanda”	Volunteer Coordinator	Day-to-day mgmt of volunteers (recruit, onboard, schedule, communicate, report on, etc.)
   …etc.

   With your team in place, let’s now uncover their various requirements that are to be considered in selecting your organization’s VMS.

3. Vendor Profile & Needs Assessment

   It’s essential to compile the list of needs from your various Project Team members. Each of them comes with a different perspective or area of expertise which should be considered.

   When creating your list of needs, consider organizing them under these categories:

   • Vendor Profile
   • Technological
   • Support
   • Budget
   • Functional
   • Usability
   • Scalability

   As done with your list of problems in an earlier section, you will end up prioritizing your list of needs by their level of importance. We suggest using these:

   Must Have (M). This need is mandatory. If a VMS candidate does not meet this need it’s immediately disqualified. Be unwavering. If you find that no vendor meets all of your must-haves, you can revisit your list and edit it down so that it’s actually possible to find matching vendors. Identifying these dealbreaker items is critical in helping your team efficiently move through the initial vendor shortlisting phase, which is discussed in “Ready, Set, Go…Shortlist + Select!”

   Should Have (S). This need is important, adds value and should be found; however, it will not disqualify a VMS if not found.

   Nice to Have (N). This need is a bonus if found; however, has little impact if left out.

   Below are some examples of things to consider and include in your worksheet as your team builds its unique list of needs.

   Vendor Profile

   Know your tech partners. How well the company operates is an indicator of their reliability to your team long term. There are a variety of questions you could ask to get to know the profile of your vendor better and determine how well they may align with your team’s expectations and needs.

   • How long have you been in business?
   • How does your company make product decisions?
   • When was your last software release?
   • When is the next one planned?
   • How many customers do you have?
   • What’s your customer retention rate?
   • Do you offer product demonstration options? (eg. video, personal demo)
   • Do you offer a free software trial option and how long is the trial period?
   • Etc.

   Technological Requirements

   Don’t be distracted by the cool bells and whistles that come with a VMS and forget to prioritize the security and privacy of your data within. You should not ignore the responsibility you have in protecting the data with which your volunteers have entrusted you. Eliminate VMS options that fall short of aligning with your organizations values and put your organization reputation at risk. If you do not have an I.T. staff member or volunteer with an I.T. background to lean on for these requirements, consider outsourcing it via an I.T. Consultant. If none of these are options, arm yourself with some general education related to the list below or via our blog on this very topic.

   ISO 27001 Certification 2FA (Two-Factor Authentication) Back-ups Data Access Penetration Tests Brute force protection

   Data encryption Compliance with WCAG 2.0 AA Regulatory Compliance Server intrusion detection and prevention Historical uptime in the last 5 years? Etc.

   Support

   How your team likes to receive their support matters. A support team at the VMS vendor you choose is an extension of your team and will be leaned on throughout your software lifecycle. How well are they measuring up to meeting the learning styles of your team?

   • Responsiveness / Response time
   • Helpfulness / Relevant support or suggestions
   • Phone
   • Online Chat
   • Email
   • Videos
   • Help articles
   • Training options (free vs. paid; onsite vs. virtual)
   • Services (eg. data imports, configuration services)
   • User Groups / Peer Support options
   • Location of Support
   • Etc.

   Budget

   The price tag associated with an out-of-the-box VMS solution may be far less in cost than you think, since vendors must cater their pricing predominately for volunteer departments in the nonprofit sector - the primary consumers. For this reason, it’s extremely rare that an RFP (Request for Proposal) be necessary from your team to have vendors bid for your business. That time-consuming step is typically reserved for very large organizations with processes in place that require an RFP when the annual subscription may exceed thousands of dollars (e.g. $5,000). Gather pricing from qualified vendors. Remember that value is of greater importance than cost. Should a VMS exceed any budget you may have set for this project, consider its value, provided the gap from your upper budget to actual cost doesn’t put it fully out of contention. Alternatively, if software is free, beware of the axiom, ‘You get what you pay for’.

   • What’s the subscription cost for my organization? (Get yourself a quote from the vendor and keep the details the same when comparing vendors so that you’re comparing apples to apples)
   • Is that billed monthly or annually?
   • In which currency are we invoiced?
   • How might the number of administrators (e.g. staff members) accessing the software impact subscription fees?
   • How might the number of volunteer profiles in the software impact subscription fees?
   • How might an increase or decrease in our number of volunteers during our subscription period impact subscription fees?
   • How might Archived volunteer profiles in the software factor into subscription fees?
   • What are the fees for any optional add-ons (eg. trainings, services, etc.)?
   • Are software upgrades/new releases included with the subscription?

   Functional Requirements

   You need your VMS providing numerous functions that help your program to operate more efficiently and effectively for both your organization’s members and your volunteers. Below is a list of some areas to consider; however, each area can be broken down into more granular needs within.

   • Recruitment (e.g. create online application forms, automated welcome email sent to volunteers upon submission of form, etc.)
   • Onboarding (e.g. Background checks, eLearning modules for training/orientations, tracking other screening)
   • Volunteer Profiles (e.g. contact info, qualifications and skills, interests, assignments, hour, etc.)
   • Communications (e.g. emailing, texting, mailing labels, document library, etc.)
   • Schedule Management (e.g. view schedule in list and calendar format, easily find vacant shifts and assign qualified volunteers, etc.)
   • Reporting (eg. volunteer hours, feedback, outputs, profile data, etc.)
   • Volunteer Rewards (e.g. years of service, hours milestones, etc.)
   • Volunteer Portal (e.g. volunteers can sign up, get shift reminders, take online trainings, etc.)
   • Branding (e.g. inclusion of your organization’s logo, colours, preferred font style, etc.)
   • …and so on.

   Usability Requirements

   Usability is based on the perception of a user and their interaction with the software. Getting to know if a system is intuitive and easy to use is generally best assessed when testing out the software via a trial period.

   • Visually appealing interface
   • Ease of system navigation
   • Efficiency of carrying out tasks (e.g. minimal clicks to run a report)
   • Easy to learn / intuitive
   • Performing tasks delivers the expected result

   Scalability Requirements

   Consider what happens if your program increases or decreases in size or needs generally just change over time. Is the VMS you select providing you with a short term or long-term solution?

   • What happens if we add/remove Admins?
   • Add/Remove volunteers?
   • Add/Remove programs, departments, or locations to use the system?

   Once your team’s list of prioritized needs is compiled, meet with your team to discuss the prioritization (Must Have, Should Have, Nice to Have) to ensure it makes good sense before utilizing the list in determining your best VMS contenders.

4. Project Timeline & Task Assignment

   It is reasonable for your team to complete this project within a two to four-month timeline, with proper planning and preparation practices. This may seem long for smaller organizations but the cost avoidance of making the wrong decision and getting stuck with an inadequate system or having to go through the process all over again makes this worthwhile.

   Outline the stages and steps of your project, which team members will be assigned to these steps and what the realistic deadline would be to complete each. Now you will have the execution phase of your project mapped out to reach your timeline goal.

   Here are some common stages and steps in which your team would likely engage:

   Stage 1: Determine VMS Contenders

   1. Needs Assessment. This was discussed in the above section. Give your project team up to a week to devise their needs and prioritize each one.
   2. Needs Assessment Review. Meet to discuss to ensure the prioritization makes sense to the team. This may be a 1-2 hour meeting, depending on the length of your list. The final version of your list of needs will become the measuring stick utilized to shortlist and select your VMS.
   3. Vendor Research. Start with the vendor websites and customer reviews. You can find a list of VMS’s along with the review sites that have postings on them at www.volunteersoftwarecomparisons.com/. Contact the vendors directly to get your team’s ‘must have’ requirements addressed if you can’t find them on the vendor’s website. This can be done in a week.
   4. Vendor Review & Shortlisting #1. Meet with your project team to discuss findings and determine your shortlist of VMS contenders moving on to the next stage. Meeting is likely up to 1 hour.

      
      Stage 1 can be accomplished in two to four weeks, depending on your team members’ availability.

   Stage 2: Demo

   1. Demo. This is your opportunity to watch a product demonstration. This may occur by watching a pre-recorded video and/or joining a live personal and/or group demo by the vendor. This can vary in time commitment from 30 minutes to a few hours, depending on the demo options available to you and the number of questions your team may have at this point of the journey.
   2. Vendor Review & Shortlisting #2. Meet with your team to review how your vendor candidates performed during the demo stage and disqualify any that don’t measure up (to your functional requirements). It’s ideal to land on two VMS contenders following this shortlisting stage as these will become the solutions you’ll spend time exploring more deeply via the next stage of trialing solutions.

      
      Stage 2 can be accomplished in a couple of weeks, based on everyone’s availabilities. When possible, it is recommended to take in all the demonstrations consecutively and without large time periods between each to keep each system clear in your mind as you review the others.

   Stage 3: Trial

   1. Trial. It’s highly recommended that you “try before you buy.” Getting a trial account to test out the solution will help your team gain insights into the solutions usability and have any of your team’s remaining questions addressed at this time. It also gives you the opportunity to test out the support offered by a vendor. A trial period can range from 7 to 30 days generally.
   2. Vendor Review & Selection. Meet and discuss with your team how the solution(s) performed during the trial stage. This meeting is likely no longer than 1 hour. Ideally, you’re able to clearly determine which solution resonated the best with your team at this point and make the final decision.

      
      Stage 3 can be accomplished in one month.

   Stage 4: Subscribe

   1. Recommend Solution to Leadership. Share a summary of your team’s recommended VMS for approval. Leadership may want to review the vendor’s software/license agreement before granting their approval.

      
      Stage 4 could take as little as a day or as much as a month or more, depending on the approvals process at your organization.

   Tip: Block off calendar time (eg. research, trial, review mtgs, etc.) based on the project steps you’re assigned and respective deadlines. If you haven’t made the time for it, something else will take that space in your calendar, right? 😉 Protect it by reserving it for your project commitments now.

   Here’s an example of a project plan that you can create in the accompanying worksheet.

   Month 1: March		Month 2: April		Month 3: May		Month 4: June
   Task	Responsibility	Task	Responsibility	Task	Responsibility	Task	Responsibility
   Needs Assessment	Project Team	Demo	Members with outstanding functional questions	Trial	Members with usability questions	Place/order Subscription	Executive Director / Signing Authority
   Needs Assessment Review	Project Team	Vendor Review & Shortlisting #2	Project Team	Vendor Review & Selection	Project Team
   Initial Vendor Research	I.T., Volunteer Coordinator/Manager	Project Commitments
   Vendor Review & Shortlisting #1	Project Team

   Now let’s go find your VMS!

5. Ready, Set, Go…Shortlist + Select!

   You’ve planned. You’ve prepared. It’s time to execute the plan!

   If you’re following the suggested stages and steps from this guide, you will shortlist twice and select once. To do this successfully, you’ll be referring to your Needs Assessment often. It represents the measuring stick to which each vendor must be compared.

   Be open to the fact that you are unlikely to have every need fully met to every project team member’s level of satisfaction, but the goal is to have all MUST HAVE needs 100% met and as many SHOULD HAVE needs met as possible. This will increase your team’s level of satisfaction with the selected vendor and build confidence in choosing the best vendor at the end. Any NICE TO HAVE items that are met are just pure bonus/icing on the cake.

   Consider the tips below to help you navigate the shortlisting phases of your project and record details on your worksheet.

   Stage 1, Vendor Review & Shortlisting #1

   What to assess? All the Must Have items from your team’s Needs Assessment. Starting with the Technological Requirements first, as you’ll likely start narrowing your list more quickly by doing so. If vendors are passing your tech requirements, move on to measure them against your Support, Functional and Budget requirement ‘must haves.’ Vendors not meeting even one of your identified ‘must have’ items should be disqualified from further consideration as these are mandatory requirements. Record those reasons for disqualification so your team can refer back.

   How to assess? Visit www.VolunteerSoftwareComparisons.com. It’s a compiled list of solutions/ vendors in the VMS category. You’ll be able to link to their website, read customer reviews and generally just learn more. Do your own independent research by visiting vendor websites. Contact the vendor directly for any hard-to-find answers or those you’re not 100% clear on so you can base your assessment of a need from having heard it straight from the horse’s mouth.

   How many to assess? There are several VMS options available on the market, but given differences between each one, only a handful are worth a formal review. Try to arrive at a minimum of two qualified VMS solutions your team can compare and ideally no more than five to take into Stage 2.

   Example.

   Name of Vendor / Product Name	Qualified / Disqualified	Reason(s) for Disqualification
   "ABC Solutions"	Qualified
   "XYZ software"	Disqualified	No ISO27001 certification: Pricing is too far out of scope to be considered.
   "VMS R Us"	Qualified
   "The Best VMS"	Qualified

   Stage 2, Vendor Review & Shortlisting #2

   What to assess? Primarily focus on Functional Requirements (particularly the ‘must haves’).

   How to assess? If a comprehensive demo video is available to watch from the vendor’s website, watch it. You may find all or most of your questions are answered. For any outstanding questions, either book a personal demo, call, or email the vendor to gather those answers, depending on what you feel makes your team most confident/reassured with functional needs being met (e.g. seeing, hearing, or reading those answers). If booking a personal demo, share your team’s outstanding questions/functional needs with the vendor, in advance, as this will make for a more focused and productive meeting for all. Have your Needs Assessment handy for your demo experience(s) to record how well VMS’s are measuring up at this point.

   How many to assess? While there’s no magic number here, you definitely don’t want to demo every VMS; whether that be via watching a demo video or partaking in a personal demo. If your team did a good job with the Needs Assessment and identifying several MUST HAVE items (particularly in the category of Technological Requirements), you will ideally be demoing no more than five VMS’s.

   Example.

   Name of Vendor / Product Name	Qualified / Disqualified	Reason(s) for Disqualification
   "ABC Solutions"	Qualified
   "XYZ software"	Disqualified	Team found the solution to look clunky and outdated; lacking in reporting capabilities
   "The Best VMS"	Qualified

   Stage 3, Vendor Review & Selection

   What to Assess? Primarily focus on Usability & Support Requirements (particularly the Must Haves). At this point, I.T. may want to take a closer look at testing some security functionality to ensure it meets your standards (e.g. 2FA/Two-Factor Authentication, limiting admin access to data, etc.). It’s also worth gathering evidence of some technical claims. For example, if a claim has been made about third party penetration tests, ask for a copy of the latest report. If a claim has been made that ISO 27001 standards are being followed, ask for a copy of their certificate.

   How to Assess? It’s highly recommended that you “try before you buy.” How else are you to know if the solution you may end up subscribing to is easy to use or how well the vendor support measures up to your team’s standards unless you gain access, use it, and ask support some questions? It’s risky to skip this step or to consider VMS solutions that do not offer a trial experience and potentially face buyer’s remorse. Request a trial from the vendor. Some vendor websites allow you to directly sign up from their site so you have immediate access. Don’t forget to include your volunteers in the testing phase as well. Block time off in your calendar to dedicate to accessing your trial account and sticking to your plan of what you need to explore based on your project timeline.

   How Many to Assess? Given the time required for this stage of an evaluation, you may want to limit this to two VMS’s.

   Example.

   Name of Vendor / Product Name	Qualified / Disqualified	Reason(s) for Disqualification
   "ABC Solutions"	Disqualified	Majority of project team who trialed the solution (3 out of 5 people) found the navigation of the software more challenging.
   "The Best VMS"	Qualified

Your ideal VMS is selected!

By the end of this project, you will have found the best VMS for your organization that will elevate your program’s operation to a new level of mission achievement.

We hope you’ve found this guide helpful in developing your team’s plan and has built up your confidence in successfully navigating this project and journey.

Featured Resource

The Ultimate VMS Guide & Worksheet

 

Download Now