Volunteer Options

I'm guessing you do not have the volunteer module as that could be an easy solution for your question.  



Notes is always an option but usually not the best one if it's data you want to report, pull etc.  Do you have any idea how many entries you would need on average? If the number is not huge, a good opton might be a constituent atttibute.  I'd use something like category: volunteer opp, description - create a table of your main types, then for date and comments add detail of date and specifics.  



If you are just talking about volunteering as member of a civic org you could always create a relatonship to the org if they have a record in your RE database.  



Just a couple thoughts.

You are tracking their OPPORTUNITIES or the actual SERVICES they are volunteering for?  I don't know that I would put something they could possibly do in RE, but never do.  Hmm.  When I have not had the Volunteer Module I have done a Constit Attribute that is Volunteer Services, Description is the service they provided (event help, telethon committee etc) and the comments had the fiscal year and any addition info like Chair or cleanup crew or set up or decorations



I think Jo Ann's suggestions of opportunies in the Notes may work.

It will be easier to pull lists from Attributes than it would be Notes, and you can define a dropdown of each Volunteer Position so that they will be consistently named moving forward.  Notes is more loosey goosey.



Actions (I wish it was named Interactions)  Because that is really how I see folks utilize Actions for the most part.  You could put them in Actions, the dropdowns could be there also.  The the reporting on Actions is very specific to tasks involving cultivation and stewardship in a general sense.



My vote is still Constitiuent Attributes

 

Ditto Christine's response.  I see actions more as contacts/interactions.