The other night on Church Tech Weekly, we were talking about assimilating new volunteers into the tech team. One of the ways we start that process is with job descriptions. As we talked about those, it prompted some people to inquire about getting copies of our files. So here you go.
I’ve created a position description for each volunteer tech position I have right now. The reason for this is twofold. First, it helps the prospective volunteer understand the commitment we are asking him or her to make. Second, it shows that we’re serious enough about what we do in the tech department to create job descriptions. I’ve found that people generally rise to the level of expectation. I like to start high, and I think this is one way to do it.
Feel free to use these as guides, but I encourage you to take some time and really think through what your volunteer positions entail. What do they do every week (more importantly, what to you expect them to do), and what are the time commitments.
I use these pages when I meet with a prospective volunteer for the first time. It gives us a good launching off point, and allows me to tell them about what we do. Having the expectations in writing makes it easy for a volunteer to say, “Yes, I can do that,” or “No, I don’t think this is for me.” Personally, I’d rather know as early as possible that someone is out; it’s much easier than spending a lot of time in training and getting to know them only to have them bail (though that still happens).
Documentation is a good thing, and if you currently have nothing in writing for your tech team, job descriptions are a good place to start. From there, you can start working on training processes, check lists and operational guides.
Do you currently have job descriptions for your tech team? If so, how do you use them?
Click to download these files: