<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://experience.fellowshipone.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Delivering Change : small groups</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/small+groups/default.aspx</link><description>Tags &amp; Topics: small groups</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61120.2)</generator><item><title>Using Group Manager for Care Ministries:  A Case Study</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/2008/07/16/using-group-manager-for-care-ministries-a-case-study.aspx</link><pubDate>Wed, 16 Jul 2008 05:34:00 GMT</pubDate><guid isPermaLink="false">87eee960-b871-44cb-8a98-02588a960c04:11602</guid><dc:creator>FTDeliverySvcs</dc:creator><slash:comments>6</slash:comments><comments>http://experience.fellowshipone.com/blogs/deliveringchange/comments/11602.aspx</comments><wfw:commentRss>http://experience.fellowshipone.com/blogs/deliveringchange/commentrss.aspx?PostID=11602</wfw:commentRss><description>Recently I was working with &lt;b&gt;CrossWinds church in Dublin CA&lt;/b&gt; and came across a situation I had
seen in the past but did not have a &lt;b&gt;great
solution to meet their needs&lt;/b&gt;.&amp;nbsp; Recent
advances in F1's ability to send contacts to small group leaders has provided a
solution that now easily meets a &lt;b&gt;care
ministry&lt;/b&gt; needs.&amp;nbsp; 

&lt;p&gt;&amp;nbsp;&lt;b&gt;The Issue:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;CrossWinds Church&lt;/b&gt;
has care teams that are &lt;b&gt;regionally based&lt;/b&gt;
around the Dublin City area and &lt;b&gt;provide services
to people in need&lt;/b&gt;.&amp;nbsp; They bring &lt;b&gt;meals to families&lt;/b&gt; that need them, they &lt;b&gt;visit&lt;/b&gt; people in the &lt;b&gt;hospital&lt;/b&gt;, and they provide &lt;b&gt;services&lt;/b&gt; such as &lt;b&gt;lawn mowing&lt;/b&gt; to single parents.&amp;nbsp;
Each team is comprised of a &lt;b&gt;leader
and an area coordinator&lt;/b&gt;.&amp;nbsp; The &lt;b&gt;leader is responsible&lt;/b&gt; for the group and
recruiting new volunteers into their ministry.&amp;nbsp;
The &lt;b&gt;area coordinator is
responsible&lt;/b&gt; for coordinating efforts of the team members to provide
services and report the information back to the church staff.&amp;nbsp; &lt;/p&gt;

&lt;p&gt;Prior to Fellowship One this was being done through &lt;b&gt;a network of Excel spreadsheets&lt;/b&gt;, email
notices, and phone calls which were all painstakingly tracked by the staff to
keep an idea of what was going on across all of the teams.&amp;nbsp; &lt;b&gt;The
pastor responsible for care groups also tracked volunteer activity&lt;/b&gt; (who was
providing the meals or visitation) to keep a list of top volunteers for the
purpose of thanking them and &lt;b&gt;promoting
the ministry&lt;/b&gt;.&amp;nbsp; &lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;b&gt;The F1 Solution:&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;The first need was to &lt;b&gt;track
who was involved in the teams&lt;/b&gt;.&amp;nbsp; Since
the church was regionally tracking the teams I proposed that the &lt;b&gt;Activity Groups be the regions of the area&lt;/b&gt;
that the groups were divided into.&amp;nbsp; &lt;b&gt;This would allow for expansion of the teams&lt;/b&gt;
or possible sub division of some of the larger teams which could include up to
80 people.&amp;nbsp; The Team Leader then could be
assigned at the Activity Group level and the area coordinators could be
assigned over smaller groups.&amp;nbsp; &lt;/p&gt;

&lt;p&gt;The second need was to be able to take &lt;b&gt;requests for ministry from multiple sources such as web, phone, and
information cards&lt;/b&gt;.&amp;nbsp; They would all be
input into the contact management system in Fellowship One as contact
items.&amp;nbsp; Each type of request would be
tracked as a separate contact item.&amp;nbsp;
(hospital visitation, meals ministry, service requests, etc) This would
allow the church to run reports and determine the &lt;b&gt;greatest need of the community&lt;/b&gt; at any given point and also perform
trend analysis.&amp;nbsp; (I.E. how many meals did
the church provide in 2007 compared to 2008?)&lt;/p&gt;

&lt;p&gt;After contacts were entered into F1 from the various sources
they all routed to an administrative assistant that would &lt;b&gt;validate the request&lt;/b&gt; and determine the best team to &lt;b&gt;handle the issue based on area and type of
service the team provided&lt;/b&gt;.&amp;nbsp; The
contact would then be transferred to the small group which triggers an &lt;b&gt;email alert to the Area Coordinator&lt;/b&gt;. (See
training video in eUniversity for how this occurs)&lt;/p&gt;

&lt;p&gt;The Area Coordinator then assigns the task to one or
multiple Care Team members who then provide services/meals/visitations to the
requesting party.&amp;nbsp; &lt;b&gt;Notes are entered on the contact&lt;/b&gt; through the Group Manager &lt;b&gt;by the Area Coordinator&lt;/b&gt; for each
instance of service. &lt;b&gt;The Area
Coordinator also posts "attendance" for the team members who are providing the
services.&lt;/b&gt;&amp;nbsp; This allows the Church
staff to &lt;b&gt;track their top volunteers&lt;/b&gt;
for the purposes previously mentioned.&amp;nbsp;
Through the process the Area Coordinator is &lt;b&gt;setting the proper disposition&lt;/b&gt; for the contact item which allows
for tracking "&lt;b&gt;success&lt;/b&gt;" vs "&lt;b&gt;failures&lt;/b&gt;" which are difficult to
determine without contact dispositions.&amp;nbsp; &lt;/p&gt;

&lt;p&gt;The church staff runs regular reports tracking open, in
progress, and closed contacts.&amp;nbsp; They
track open and in progress contacts to &lt;b&gt;verify&lt;/b&gt;
that the area coordinators are &lt;b&gt;properly
documenting&lt;/b&gt; and following up with service requests.&amp;nbsp; They also track closed contacts for the same
purpose as well as to see if any &lt;b&gt;staff
follow up&lt;/b&gt; is needed.&amp;nbsp; &lt;/p&gt;

&lt;p&gt;This same scenario can easily be replicated at your
church.&amp;nbsp; Levels of security for this type
of ministry can also be adjusted to allow all team members to update the contact
items.&amp;nbsp; &lt;b&gt;Training&lt;/b&gt; of staff and volunteers &lt;b&gt;is important&lt;/b&gt; &lt;b&gt;to&lt;/b&gt; the
success of this &lt;b&gt;ministry&lt;/b&gt;.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Matthew McMaster&lt;/p&gt;&lt;p&gt;Passionate for People Because Christ Is&lt;/p&gt;&lt;img src="http://experience.fellowshipone.com/aggbug.aspx?PostID=11602" width="1" height="1"&gt;</description><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/small+groups/default.aspx">small groups</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Pastoral+Care/default.aspx">Pastoral Care</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/WebLink/default.aspx">WebLink</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/Best+Practice/default.aspx">Best Practice</category></item><item><title>Take A Census</title><link>http://experience.fellowshipone.com/blogs/deliveringchange/archive/2008/06/25/take-a-census.aspx</link><pubDate>Wed, 25 Jun 2008 11:00:00 GMT</pubDate><guid isPermaLink="false">87eee960-b871-44cb-8a98-02588a960c04:11467</guid><dc:creator>FTDeliverySvcs</dc:creator><slash:comments>2</slash:comments><comments>http://experience.fellowshipone.com/blogs/deliveringchange/comments/11467.aspx</comments><wfw:commentRss>http://experience.fellowshipone.com/blogs/deliveringchange/commentrss.aspx?PostID=11467</wfw:commentRss><description>&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Attendance carries the stigma from your school days where everyone had to be in class and everyday attendance was taken.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Census means that on some interval of your choosing you stop and count how many people are actually involved in this activity.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Like the US census taken every ten years you can choose any interval you want and ask "how many people are in small groups?"&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;To do this you need to setup your activity schedule to reflect when you want your census taken and not which days of the week your small groups meet.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Consider a census on a quarterly basis; you would create an activity schedule that occurs on March 31, June 30, September 30 and December 31.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;The idea is you communicate with your small group leaders to post attendance 4 times in the year.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;the small group leader can still use the manager tool weekly for email, contacts and membership purposes within the group but you as a church only want a quarterly census to track if the groups as a whole are growing or not.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;You can adjust the census dates to any duration or interval.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Maybe monthly or bi-monthly is more in line with how often you want your census.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;You can even build the schedule on an as needed basis.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Suppose you launch a new small groups’ series in September and you want a census in December you can add that date to your activity schedule for the leaders to post attendance to.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;Then you can add another date the following spring to see how the groups are doing again.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;At this point you may be thinking how do I know when my groups are meeting if my activity schedule is set up for census taking and the not weekly meetings?&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;If you need to know what day a group meets or even what time of day you can use Room Location Properties to track this information.&lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;By defining properties and choices and then making the associations between them and your small groups you know who meets when, where and even why (special interests).&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;If you are not taking attendance today with your small groups consider taking a census instead.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0pt 0pt 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Jeremy Jackson&lt;/FONT&gt;&lt;/P&gt;&lt;img src="http://experience.fellowshipone.com/aggbug.aspx?PostID=11467" width="1" height="1"&gt;</description><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/small+groups/default.aspx">small groups</category><category domain="http://experience.fellowshipone.com/blogs/deliveringchange/archive/tags/attendance/default.aspx">attendance</category></item></channel></rss>