Volunteer Intake Howto

The purpose of volunteer intake is to:

• determine the best program (Adoption or Build) for the volunteer
• enter their info into the database
• tell them what logistics to expect
• point them to the right person (if no obvious match with the Adoption or Build program)

Volunteer intake is full of logistics. Most people will expect this, but some may not. So:

• take your time
• explain yourself clearly
• repeat information if necessary
• ask for help if you need it

Intake can take 45 minutes with lots of new volunteers. Or you might be done in 5 minutes. Plan on at least 25 minutes.

determine the best program

Ask individuals what they want to do. Expect some confusion, even if the programs have already been explained on the tour; they're trying to take in lots of new information. Often, people think that the Adoption program is the only way to earn a PC.

Generally, if a volunteer wants to:

• quickly earn a computer: Adoption Program (24 hours of work)
• learn about computers (and earn one too): Build Program (60-100 hours or more)

Now, you're ready for intake.

• If you're doing this alone, the best order is: Adoption, Build, Unknown. Tell non-Adoption volunteers they'll need to wait a little while, and start with Adopters.
• If you have a big group, or are new to doing intake, see if the Front Desk person (or somebody else) is available to help. Let them handle the Adopters, and start right in with the Builders.

The next section describes the database entry you need to do for all volunteers; after that, some specific notes for Adoption, Build, and other volunteers.

database (contact manager) entry

NOTE: For a big group, ask if the Front Desk person is able to intake the Adopters. If so, you can enter data for Builders while they do Adopters.

• open a browser (Firefox, Konqueror) to http://data (on any Free Geek computer)
• click Front Desk along the top bar
• click Volunteers on left side of the screen
• this is the Contact Manager
  • search for the person's name (in case we already have a record for him/her)
    • list at the top: do they represent an organization in their dealings with Free Geek? No: choose Person. Yes: choose Organization.
    • Fill in first name, last name, ZIP code. Press search.
  • If a name (or names) appear below the little green box, ask if it's theirs.
    • If so, click the radio button by the name and press Edit. Make sure all their info is current.
    • If not, or if no names appear, press Create contact.
• contact info
  • checkbox: Adopters: Wait; Builders: Build; Other: Volunteer
  • First name, last name
  • ZIP code (used to estimate demographic info for grants)
  • Phone number
  • For an organization, fill in that field as well (the address and phone should be for the organization.)
  • for Builders: note their new ID number on their builder status sheet.
• Ask them if they'd like to receive announcements and newsletters by mail, phone, email. Uncheck boxes accordingly. Remind them they will still be contacted about the wait list. For mail or email, be sure they filled in the appropriate fields.
• Press "Save record". Hooray!

Adoption intake

explain about waiting list

Tell the volunteers they will be put on a waiting list. We'll call them in about 2 weeks to schedule their first shift.

Doesn't this vary, depending on current conditions? Let's update this. --Pete 22:25, 28 Dec 2005 (PST)

Answer any additional questions

And be sure to say "thanks for coming!"

Build intake

There's a lot to build intake, and there are many ways to proceed. Below is what needs to be covered in a suggested progression. Feel free to add to it and change the order, but please be sure to cover all of it.

One thing that's good to emphasize while you do build intake is how much of a time commitment the program takes. We estimate that it takes 60-100 hours of volunteer time to work through the program and build 6 computers. We want people in the program that have an understanding of how much of a commitment this is and are comfortable with it and with volunteering frequently (people forget details easily if they don't come in at least every week or so).

• Give each person a builder status sheet and build packet. They're in the green folder at the front desk.
• Explain the build packet to them, especially including:
  • Step by step, the flow of the build curriculum
  • The last page, including where documentation lives, the build email list, and class and workshop times. Emphasize that those times don't apply to card/mobo sorting and system eval.

Encourage them to read the rest on their own time. There's lots of cool info in there! Also, be sure to solicit questions.

• Ask if anyone has hardware or Linux command line knowledge. If anyone says they do, they may be able to test out of card and motherboard sorting and/or the command line class. If you have time, take them to the card and mobo sorting room for a short knowledge assessment. Guidelines are at Testing Out.

• (if you have more than one or two new volunteers, you may want to take them all back to the lab and have each person sit at their own computer and enter their own information).

• Fill out the rest of the builder status sheet (or have them do it). Be sure to sign them out of all the applicable steps.
• Have them file away their builder status sheet in the book at the front, and explain that they need to havesomeone sign them off on each step.
• Sign them up for their first shift on the clipboard. If they've tested out of card sorting or card and mobo sorting, be sure to take that into account.
• In the midst of all this intake, you may have realized that some people who are interested in the Build Program may not have quite the level of technical knowledge necessary. Can they use a keyboard and mouse? Are they relatively familiar with the browser fields and buttons? We encourage everyone to join the Build Program regardless of their computer experience, but sometimes it may be beneficial for a volunteer to work their way through the Adoption Program, receive a FreekBox, and practice using it a little before starting Build. If this is the case with someone, please pull them aside and tell them kindly.
• Any more questions?
• Hooray! They're in! Thank them for coming.

Intake for everyone else

• Ask them what they're interested in doing, and have them talk to the proper person.
  • coding or network administration: Richard
  • teaching classes: Laurel (out of date?)
  • collab: Ron (out of date!!)
  • writing grants: Oso
  • unsure: Shawn (during her volunteer intake time. It's on the staff schedule, usually right after the noon tour.)