Most small groups never write anything down. They meet, they like each other, and for the first few months that is enough. Then someone misses four weeks in a row without a word, or a story shared in confidence turns up in a hallway conversation, or two people in the group have a falling-out nobody knows how to address, and the group realizes it never actually agreed on what it expected from its own members.
A covenant is not a legal document and it is not a membership contract. It is a short, plain page that says out loud what a healthy group silently assumes — that people will show up, that what is shared stays in the room, that conflict gets addressed rather than avoided. Below is a template you can adapt, section by section, along with why each piece earns its place.
Start with why the group exists
Before any commitment, name the purpose in a sentence or two: are you studying scripture together, supporting each other through a season of life, discipling new believers, or some mix of all three? This sounds obvious, but groups that skip it end up with quiet friction later — one member wants deeper Bible study, another wants more personal sharing, and neither is wrong, because the group never said which it was for. Write the purpose plainly: “this group exists to study scripture together and support each other through whatever the week brings.” One sentence. Everything else in the covenant follows from it.
Name attendance and communication expectations
This is the commitment groups need most and write down least. State how often the group meets, and what a member does if they cannot make it — a text to the leader, not silence. Something like: “we meet weekly, and if you cannot come, you will let the leader know beforehand rather than simply not showing up.” That single line changes a lot. It turns an unexplained absence into a known one, and it gives the leader something to act on — a check-in text — instead of a guessing game about whether someone is fine or fading.
Name a rough attendance bar too, without making it punitive: “we aim to be here most weeks, and we tell each other when life makes that hard for a season.” A group that treats every absence as a crisis is exhausting to belong to; a group that never notices absence at all quietly loses people. The covenant is what keeps a leader from having to guess which response fits.
Make confidentiality specific, not just implied
“What's said here stays here” is the line every group says and the one most poorly defined. Spell out what it actually covers: personal struggles, prayer requests, family situations, and anything shared during discussion time. Spell out the one honest exception too — if someone discloses something that puts them or someone else at risk of harm, the leader may need to involve a pastor or, where required, report it. Naming that exception up front is not weakening the covenant; it is the thing that makes the confidentiality promise trustworthy rather than absolute in a way nobody actually means.
Say what care looks like when someone is struggling
A group covenant should name, briefly, what the group does when a member is going through something hard — a job loss, a health scare, a family crisis. It does not need to promise casseroles and a schedule; it needs to say the group notices and responds, and how. Something like: “when someone in the group is struggling, we will check in, pray specifically, and offer practical help where we can, and we'll let the leader know if it's something beyond what we can carry as a group.” That last clause matters — it gives members permission to hand something to a pastor rather than quietly carrying more than a small group was built to hold.
Address conflict before it happens
Every group eventually has friction — a disagreement in discussion that lingers, two members who rub each other the wrong way, a leader who feels unsupported. Name in advance how the group will handle it: talk to the person directly first, bring it to the leader if a direct conversation does not resolve it, and agree that disagreements in discussion are normal and welcome, not something to avoid. A group that has never discussed how it handles conflict tends to handle it badly — either an explosion nobody saw coming or a slow, silent drift as people simply stop showing up.
Set expectations for participation, not just presence
Showing up is not the same as showing up well. A short line about participation — “we come ready to listen more than we talk, and we make room for the quieter voices in the room” — sets a tone that a purely attendance-based covenant misses. This matters most in groups where one or two people naturally dominate discussion; naming the expectation of shared space in writing gives a leader something to gently point to, rather than having to invent the correction in the moment.
Put it in front of the group, not just the leader
A covenant that lives only in the leader's notebook does none of this work. Read it together at the first meeting of a new group or a new season, let people push back on any line that does not fit, and revisit it once a year or whenever the group's makeup changes — a group that started as four single adults and grew to include three families may need to revisit what confidentiality and attendance actually mean now. This is also a natural moment to talk about how new people join the group at all, which is worth pairing with a look at what makes a small group one people keep coming back to.
Once your group has a covenant it actually uses, it is worth keeping the group itself — who is in it, who leads it, who has come and gone — somewhere more durable than a leader's memory. SundayBridge keeps groups with their members and leaders in one record alongside the rest of a person's history at your church, so a covenant conversation this fall does not depend on anyone remembering who was actually in the room.
A one-page version to start from
If you want something to hand out this week rather than build from scratch, here is a skeleton: a sentence on purpose, a line on meeting frequency and what to do if you cannot make it, a paragraph on confidentiality with its one honest exception named, a few sentences on how the group cares for someone struggling, a short note on resolving conflict directly before escalating it, and a line on participation that makes room for quieter voices. Fill in your group's specifics, read it together, and treat it as something you can revise — a covenant that never changes as the group changes stops describing the group it was written for.