A conflict of interest policy exists because personal, financial, or professional interests can compromise objectivity in a decision someone is supposed to be making for someone else. On a church board, this comes up more often than people expect — a director whose company could supply a service the church needs, a board member’s family member being considered for a paid staff role, a vendor contract with someone connected to leadership. A written conflict of interest policy is how a church board handles that reality instead of hoping it never comes up.
Why a Conflict of Interest Policy Isn’t Optional in Practice
Under California Corporations Code § 9243, which governs nonprofit religious corporations, a “self-dealing transaction” is one where a director has a material financial interest and the transaction doesn’t fall within specific statutory exceptions. Unapproved self-dealing exposes the interested director to being ordered by a court to pay damages or take other corrective action.
The statute does carve out transactions that are simply part of the church’s ordinary religious or charitable program, approved in good faith and without unjustified favoritism — so not every benefit to a connected person is automatically prohibited. But that exception depends on the church being able to show good faith and a lack of favoritism, which is exactly what a documented conflict of interest policy and disclosure process is designed to demonstrate.
There’s also a practical reason beyond the statute: the IRS’s own Form 1023 application for 501(c)(3) tax-exempt status includes a sample conflict of interest policy, and reviewers generally view an organization more favorably when it has adopted one. A church without a written policy isn’t necessarily doing anything wrong, but it has nothing to point to if a disclosed conflict, or a challenge to one that wasn’t disclosed, ever needs to be defended.
What a Conflict of Interest Policy Needs to Cover
A workable policy addresses a specific set of elements, not just a general statement of good intentions. It should define who it applies to — board members, staff, and anyone involved in decisions with financial implications — and define what actually counts as a conflict: a personal, financial, or professional interest that could compromise objectivity. It needs a disclosure requirement, so a conflict has to be raised before the related decision is made, not after. It needs a process for evaluating a disclosed conflict, typically through a committee or designated person who isn’t the one with the conflict. And it needs clear recusal procedures: once a conflict is disclosed, that person doesn’t vote on, or use their influence over, the matter.
Beyond the disclosure and recusal mechanics, a complete policy documents the decisions made — who disclosed what, how it was evaluated, and what was decided — since that record is the actual evidence of good faith if the transaction is ever questioned later. It should also be reviewed periodically rather than adopted once and forgotten, with board members and staff periodically reminded it exists and reaffirming they’ve read it.
Putting the Conflict of Interest Policy Into Practice
The policy only does its job if it’s actually used. That means a real annual (or more frequent) disclosure process, not a document that sits in a binder. It means board minutes that actually reflect when a conflict was disclosed and how it was handled — recusal noted, vote count without the interested director, rationale recorded. And it means treating a disclosed conflict as a normal, expected part of governance rather than something to quietly work around, since the appearance of favoritism can damage trust in a church’s leadership just as much as an actual improper transaction would.
Related Articles
Conflicts of Interest
Church Officer and Director Liability
Disclaimer: Every situation is different and particular facts may vary thereby changing or altering a possible course of action or conclusion. The information contained herein is intended to be general in nature as laws vary between federal, state, counties, and municipalities and therefore may not apply to any given matter. This information is not intended to be legal advice or relied upon as a legal opinion, course of action, accounting, tax or other professional service. You should consult the proper legal or professional advisor knowledgeable in the area that pertains to your particular situation.
