Most small churches do not have a conflict of interest problem in the sense of anyone trying to cheat the offering plate. What they have is a board member whose brother-in-law does the church's HVAC work, a treasurer married to the part-time bookkeeper, and a building committee chair who also owns the only fencing company in town. None of that is scandalous. All of it is a conflict of interest, and none of it has ever been written down anywhere.
A conflict of interest policy is not an accusation aimed at your board. It is a short document that says, in advance, what happens when personal ties and church decisions overlap, so that when the moment comes nobody has to improvise. It takes one evening to draft and saves you the much longer evening spent explaining, after the fact, why the contract went to the pastor's cousin without a vote.
What the policy is actually protecting against
A conflict of interest policy is not primarily about stopping theft. Outright theft is rare, and when it happens a policy rarely stops a determined person anyway. What the policy protects against is the far more common failure: a decision that was probably fine, made by someone with an obvious personal stake, with no record that anyone noticed the stake or thought about it. Three years later, when a new member asks why the church's insurance has always gone through the board chair's agency, nobody can answer with anything better than “that's just who we've always used.”
A written policy converts that shrug into a record. It says the board knew about the relationship, decided the arrangement was fair anyway, and the person with the conflict did not vote on it. Whether the price was actually fair is a separate question the policy does not answer. What it answers is whether the church looked at the question honestly when it had the chance.
The situations the policy needs to name
A short policy that names real situations gets used. A long policy full of legal boilerplate gets filed and forgotten. Name the ones your church actually faces:
- Vendor relationships. A board member, staff member, or their spouse owns or works for a company the church pays — landscaping, printing, insurance, construction, IT.
- Hiring and pay. A board member is related to a candidate for a paid staff position, or sits on the committee that sets that person's salary.
- Property and real estate. The church is buying, selling, or leasing property from or to someone connected to the board.
- Loans and gifts. The church is lending money to, or receiving an unusually large or restricted gift from, someone on the board or their family.
- Two hats on one committee. The same person recommends a vendor or a hire and also votes to approve it, with no one else in the room who would catch the overlap.
If your board can look at that list and immediately think of a name, that is the point. The policy exists for the situations you already have, not hypothetical ones.
What a workable policy actually says
A conflict of interest policy for a church this size does not need to run more than a page. It needs four things: a definition broad enough to catch real situations, a duty to disclose before the discussion starts, a recusal rule for the vote, and a place the disclosure gets recorded. Everything past that is decoration.
1. Define it plainly
Write the definition in the language your board actually talks in, not legal language borrowed from a nonprofit boilerplate site. Something like: “A conflict of interest exists when a board or staff member, or their spouse, parent, child, or sibling, could gain financially from a church decision, or has a personal or business relationship with someone who would.”
2. Require disclosure before the discussion, not during
The rule works best when disclosure is a standing agenda item, not something someone has to remember to bring up. At the start of any agenda item involving money, a contract, or a hire, ask directly: does anyone here have a connection to this decision. Waiting until halfway through the discussion to mention it defeats the purpose.
3. Recuse from the vote, not just the discussion
The person with the conflict can usually stay in the room to answer factual questions, but they should not vote, and in most cases they should step out while the board deliberates and decides. This is the part boards resist most, especially when the conflicted person is the most knowledgeable one in the room about the topic. Resist the resistance. Knowledge and neutrality are different things.
4. Record it
The minutes should note that a conflict was disclosed, who recused, and the vote count without them. This is the piece that actually protects the church later, and it is the piece most often skipped because it feels awkward to write down that Pastor Dave left the room. Write it down anyway. The awkwardness is smaller than the alternative.
Where the policy lives, and who signs it
The policy itself belongs in your governing documents, alongside your bylaws, but it only works if it also lives somewhere people actually look: a shared folder, a printed copy in the board binder, or attached to the annual board orientation packet. A policy nobody can find is the same, practically speaking, as no policy.
Each board member, and any staff member with signing or hiring authority, should sign an annual disclosure form — a half-page listing any known business or family ties to church vendors, contractors, or paid positions. New board members sign one when they join. This is less about catching a hidden conflict and more about making disclosure a habit rather than a confession. When it happens every year, disclosing a new relationship next year does not feel like an admission of guilt.
How to introduce it without implying anyone did anything wrong
The hardest part of adopting this policy is rarely the drafting. It is presenting it to a board that has functioned informally for years without anyone feeling accused. The way through is to frame it as protecting the people it applies to, not policing them. A board member who recuses from a vote involving their own family's business is not confessing to anything — they are the one person in the room whose integrity is now on the record, in writing, before anyone had reason to ask about it.
It also helps to bring the policy up at a calm moment, not in the middle of an actual conflicted decision. Adopt it in a quiet month, apply it starting the next time it is relevant, and it becomes routine rather than a reaction to a specific person or vote.
Keeping the record straight once you have one
A conflict of interest policy is only as good as the paper trail behind it. Recusals need to show up in the same place as everything else about your people and your board — not in a separate binder that only the secretary can find. If your church keeps its directory and board records in one place already, adding a disclosure form and a note field for recusals is a small addition, not a new system. Some churches build this into the same cleanup they do when they move off spreadsheets for the first time, since both are really the same project: replacing things everyone remembers informally with things anyone can check.
If your board is also thinking through how it handles money more broadly — not just conflicts but the everyday discipline of tracking giving carefully — a conflict of interest policy is a natural companion piece. Both are about the same underlying instinct: writing down, in advance, the rule you would want to have followed if anyone ever asked.
A one-page starting point
If your board has never had this conversation, do not wait for a perfect policy. Draft one page: a definition, a disclosure requirement tied to the agenda, a recusal rule for votes, and a line about where disclosures get recorded. Bring it to the next board meeting as new business, not as a reaction to anything current. Vote to adopt it. Then use it the very next time it applies, even if that feels soon. A policy that sits unused for a year is easy to forget exists exactly when you need it.