This is a companion article to "Managing Technical Assistance Volunteers"
Many organizations want to use an online volunteer to initially build or maintain the agency's web site. This is an excellent way to involve an online volunteer; however, before you involve such a person, there are several factors to consider to ensure that the person in this volunteer role will meet your expectations:
POLICIES
Your organization needs to have a policy regarding its web site, and should communicate this policy to whomever helps you with your web site:
It's a good idea to give volunteers a template to follow when they have been assigned to create a new page. Even just saying, "It should look like such-and-such page that's already on our web site" is a big help.
Also, a web volunteer noted, "If you have specific programs you absolutely prohibit volunteers from using, do tell them up front. They may decline to join the project, but you will have saved yourself a big headache down the road."
All of this needs to be clearly communicated to web volunteers before they get started on an assignment.
All of these questions need to be explored before you start recruiting volunteers to help with your web site.
SCREENING & RECRUITING
It's fine to ask web volunteers for a sample of their work during your application process. Even a volunteer's personnel web site offers insight into their design capabilities.
Many people who volunteer to help with your web site won't be professional designers; they will have a learning curve that's more significant than a pro. However, that shouldn't keep you from involving them. Start a web volunteer with just a one-page assignment, and see how he or she does. From there, you can decide if this volunteer is ready for something more advanced.
More information on screening and orienting online volunteers is available on our web site.
See these resources for information on recruiting online volunteers:
AVOIDING OVER-RELIANCE
A web site volunteer will not be around forever. No matter how dedicated a person may be to a cause or organization, eventually, that person will need to move on, or won't be able to provide the level of service needed by an organization.
It's important, therefore, for an organization to make sure that it hasn't built an over-reliance on a web site volunteer, in case that volunteer needs to quit or postpone his or her service for a while.
A web site volunteer should build web pages that are easy for anyone on staff to modify, as needed. That means that:
A way to prevent over-reliance on one volunteer is to have more than one volunteer helping with the web site, so that if one leaves, there's always someone else to take up the slack. More information on using multiple web volunteers is offered later in this document.
APPROVAL AND ACCESS
Create a place on your web site just for viewing new and in-progress pages (a "beta" area). Volunteers should upload any new pages to this area first, and this material should be reviewed and approved by the appropriate staff person BEFORE they are uploaded onto the public portion of a web site.
If multiple volunteers are working on a site, they can either upload their work to the beta area, or send pages to a primary volunteer or staff person, who then reviews pages and uploads them to the public area of the web site.
Should your volunteer have the power to upload pages to the public portion of your web site? It depends on many factors. The VV Project suggests that this responsibility be given only to one person. The more people who are changing pages on a web site, the more likely it is that someone will accidentally delete someone else's work.
You can further share responsibility by giving each volunteer a specific directory on your Web site to supervise and contribute to. For instance, one volunteer could be in charge of the section dealing with online versions of your print publications (newsletters, annual reports, etc.), while another is in charge of the pages focused specifically on fund raising and donor relations, and still another is in charge of all of your interactive forms.
Be sure that there is one person who is keeping a record of volunteers and their web assignments. It's a good idea for volunteers to check in weekly with that person and submit the names of the web files they are working on, and the target dates for those files to be finished (to make sure that more than one person isn't working on the same file).
Also, encourage volunteers to view web files they are working on through their own web browser first before uploading them for your review. This allows volunteers a chance to catch and revise their own mistakes.
MANAGE THESE VOLUNTEERS!
Volunteers need to report in regularly about their progress on an assignment, obstacles they face, tools they are finding valuable, etc. Consider requiring volunteers to check in once a week during the assignment to update you on their progress (even if they haven't accomplished anything that week).
Requiring this regular communication lets you see potential difficulties well-before they become major problems, and reiterates the seriousness of the assignment to the volunteer.
Also, regularly encourage volunteers to provide feedback about the assignments you are giving them as well as suggestions for your web site. If a volunteer suggests a feature for your web site that you don't understand, ask the volunteer for an example of this feature on another web site, so you can see how it works.
For more detailed information about managing web volunteers, see our resource Managing Technical Assistance Volunteers.
CASE STUDY
At the VV Project, online volunteers build many of our pages. These volunteers can use whatever web-authoring software they wish so long as VV Project staff can open these documents with something simple, like Notepad on an IBM/Clone or simpletext on a Mac. They also have to adhere to our design standards (like complete accessibility for people using assistive technologies).
These volunteers with assignments must check in every week, either Monday or Friday, and tell me:
Online volunteers upload their completed work via FTP to a password-protected beta area; they have access only to this beta area, not the entire web site. The Project manager reviews submitted materials and, if all is well, uploads these to the public part of the site.