Topical Tuesday: Who Gets to Serve?

No Responses

  1. Jon T says:

    So you’re saying next week I get to wear an eyepatch and have a chainsaw?

    Thanks Danny!

    This is a good question because I feel like some people that come to the church that may not be covenant members feel like they are “off the hook” on serving. It is good to show them that they are still needed and they can grow in such great ways just by serving with others.

  2. Mike Gifford says:

    Danny,
    Thanks for the time you put towards this question. I agree and understand your reasoning. In addition when the twins come into this world, I can tell Mary that pirates can be Christians and they love serving at our church.

    I have one more question. Church discipline has been one of the topics that I don’t know a lot about. What is the biblical process that a church uses to keep the body safe and restore those that may be disciplined. By the way if you answer both of these questions, we may not need to get lunch! J/k my brotha

  3. Zack says:

    Danny,

    Careful how you answer Mike.

    His question seems innocent enough, but what he’s really asking is,

    “How much can I get away with before someone notices that I’m up to no good.”

    The kid’s one step away from the mafia man. Watch you back.

  4. Zack says:

    “Watch you back.”

    Oy… sarcasm works so much better when you spell the words you mean…

  5. Matt says:

    I understand what you’re saying about low-risk roles, but I’m just not sure they really exist, at least the ones you mentioned.

    The worship choir is a very public, “up-front” role. Even though you’re one of 100, people see you, and if you’re living unrepentant in some sin, people may know that, and see that you have the priviledge of doing one of the most important activities at Summit–not singing, but leading worship. And because you’re not a member, there’s no Biblical accountability.

    The same pretty much holds true for First Impressions–you are the face of the church. Newcomers don’t know that you’re not a “leader.” and of they saw you drunk the night before, that might reflect poorly on Summit. We can only really have authority and accountability over our covenant members, and therefore anytime someone is given the opportunity to honor or disgrace–not Summit, but Jesus Himself, don’t you think we should seek to have that authority over that person, and they should therefore be a member?

    • Danny says:

      Matt, that’s a great point, and it’s interesting you bring it up. I just came from a meeting with some of our staff team where we discussed this very thing.

      The key to all of this is “relationship.” As John Mulholland points out in his comment, we don’t want to throw “just anyone” in there. In all of our teams, there doesn’t need to be a mass processing of people to come in when they’re not known, not tested, and not accountable. People need to serve in the context of relationships – relationships with staff, other team members, etc. However, we also don’t want to restrict service to those who seem to have it all together. Sometimes volunteers have messy lives, and we want to disciple them as they go forward in faith.

      I would agree with you that there is a difference between someone leading worship and (I would add) someone parking cars or handing out worship guides. “Up front” roles do indeed carry a different weight here than “behind the scenes” roles. But with ANY role, and with ANY church attendee, we want to make sure that authenticity in relationships is being pursued.

  6. The rule of thumb for our ministry team for teachers is that they much be participating member, growing in their faith. We don’t just throw anyone in there with our kids…

    • Danny says:

      John, to clarify, we do require than anyone in a lead teaching role MUST be a participating member. However, people doing Summit Kids check in, assisting in a class, etc., may serve under the direction and in accountability to a covenant member. Thanks for your comment!

Start the conversation.

%d bloggers like this: