Extending MP to onboard volunteers - From the Trenches

MinistryPlatform is flexible, and there are several different ways to approach a topic. Here are examples of how some churches in our community handle this topic. Adapt MinistryPlatform's functionality and these ideas to fit your ministry context.

Extending MP to Onboard Volunteers

Possibly one of the most valuable and used extensions for several churches is in handling the screening, training, and other requirements of new volunteers. 
This often includes creation of multiple pages and sub-pages as well as some internal stored processes to handle the approval of these volunteers.
Here are some of the key and more universal components to these extensions:
  • A table to store the actual application of the individual (usually tied to the Participant or Contact record).
  • A table to store the reference responses for the potential volunteer.
  • A table to store the steps to volunteer (application, interview, background check, training, etc) and when the steps are accomplished.
  • A process to ask for and store staff approval/feedback for the individual volunteering and to help move them through the various steps of applying to serve.
It is important that all of the ministries who utilize volunteers understand how the process is going to work and have the appropriate reports/Processes in place to access the information they need.

Managing Motor Vehicle Records

Several of our churches manage driver records so that they know who is approved to drive in various scenarios. 
You can also reserve vehicles and manage their usage. Simply add vehicles that can be reserved as a resource to a "parking lot" or similar room.
At least one of our churches has developed a few custom pages to record this information. Here is a screenshot of the Page they built:

NOTE: The pages/fields shown here are custom and may not exist on your system.

Naming Custom Stored Procedures

Several churches who develop their own stored procedures have created naming schemes to track progressive versions.
Here are some common practices shared by these churches: 
  • Prepend all custom stored procedures with a church specific set of initials. This allows custom stored procedures to stand out from those developed and deployed by ThinkMinistry.
  • Append the stored procedure name with a version number to mark new iterations. 
  • Add comments within the stored procedure's code noting when changes were made and by whom. 

Last Modified: 4/16/2018

Did this article help?
× Thank You for the Feedback