A nonprofit conflict policy needs a practical disclosure process

A nonprofit board can approve a conflict-of-interest policy and still struggle when a director's relationship becomes relevant to a proposed decision. The policy may be filed away while the meeting moves toward a vote. Practical preparation asks how a possible conflict reaches the right people before the organization acts.

This guide proposes governance questions. It does not determine whether a conflict exists, establish a legal duty or prescribe the correct handling of a particular transaction. Current law, the organization's documents and professional advice should guide the actual process.

Make the disclosure pathway understandable

Identify how a director, officer or other participant should raise a relevant relationship. Ask what information the organization needs and who should receive it. A process that depends on public confrontation during a meeting can discourage useful early disclosure.

Describe the pathway in plain language after appropriate review. Participants should know where the form or instructions live and what to do when a relationship changes. A one-time signature should not be assumed to resolve every later situation.

Distinguish disclosure from a decision

Receiving information about a relationship does not by itself decide how the organization should handle the matter. Record who will evaluate it under the applicable framework and which questions remain. Do not let a checkbox labeled disclosed become an automatic approval to proceed.

The IRS's 2008 governance guidance discusses conflict policies and organizational practices. [1] It is historical educational guidance, not a current Tennessee statutory standard or an approval of this organization's process. Counsel should identify the current rules and governing-document requirements that apply.

Prepare the transaction record

Describe the proposed transaction, participants and relevant relationship factually. Gather the information needed to evaluate alternatives and the organization's objective. Keep sensitive personal details limited to the appropriate review channel.

If the board is considering purchasing a service from a director's business, for example, a useful record identifies the service, proposed terms and relationship. It does not begin by declaring the arrangement improper or harmless. The responsible reviewers need facts before conclusions.

Plan meeting administration

Ask counsel how participation, discussion, voting and documentation should be handled in the circumstances. The chair and minute-taker need clear instructions. A general article cannot decide who should leave a meeting, what vote is required or whether an action is valid.

Separate operational responsibilities from legal judgments. Someone may prepare the materials and maintain the log without having authority to decide the conflict question. Make that limit clear so an administrative workflow does not become an unreviewed legal determination.

Preserve an accurate record

Document the action actually taken and the relevant process as advised. Do not manufacture a clean record after discovering that a step was missed. If the record is disputed or incomplete, bring that issue to counsel through the appropriate channel.

Keep the adopted policy, disclosures and relevant decision records in the organization's approved system. Ask about access and retention. A shared volunteer drive may be convenient without being appropriate for every sensitive governance record.

Revisit the process as the organization changes

New programs, vendors, fundraising arrangements or board members can create new questions. Periodically examine whether the instructions still fit the way the organization operates. Training can use fictional scenarios without exposing genuine private relationships.

A useful conflict process helps people raise a concern before it becomes a crisis. The goal is neither suspicion of every relationship nor casual reassurance. It is a fair, understandable way to bring relevant facts to the people authorized to evaluate them.

Make the first disclosure easy to route

Give participants a clear way to raise a relevant relationship before the organization is asked to act. Identify the recipient, appropriate channel, information needed, and process for a changed or newly discovered relationship. The instructions should be understandable to a volunteer who has not read every governance document. Ease of use does not mean automatic clearance. It means that a person can bring facts to the authorized reviewers without having to decide the legal consequence alone or announce sensitive details to an entire meeting.

Keep the requested information proportionate to the review. A disclosure may need to identify the relationship and transaction without collecting unrelated personal or family details. Ask counsel what information is appropriate and how it should be handled. A disclosure form should not become a public directory of private relationships. The organization can establish a useful routing process while preserving limited access and a separate method for information that should not be placed in ordinary board materials.

Explain that a periodic disclosure and a transaction-specific disclosure serve different purposes. A participant's earlier form may not address a new vendor proposal or changed relationship. The practical process needs a way to update the record when relevant facts arise. This article does not prescribe a disclosure duty or schedule. Current law, the governing documents, adopted policy, and counsel's advice should determine what the organization actually requires and how participants are instructed to comply.

Connect the relationship to the proposed transaction

Prepare a factual transaction description: what the organization wants to obtain, why, the proposed terms, the participants, and the relationship raised for review. Keep that description distinct from the conclusion about a conflict. A director's connection to a supplier is a fact to evaluate, not by itself a determination that the transaction is permissible or prohibited. The authorized reviewers need the actual arrangement and organizational objective rather than a label that assumes the result.

Preserve supporting materials and alternatives considered through the appropriate process. A proposal, comparative information, budget assumption, or professional assessment may help the reviewers understand the decision. Do not manufacture competing quotes or describe an informal conversation as a completed evaluation. If information is missing, mark it missing. The record should explain what was available when the organization considered the proposal and which questions still required attention.

The IRS governance document cited here dates to 2008 and supplies historical educational context. [1] It is not current Tennessee statutory authority, a determination about this transaction, or approval of this process. The organization should ask counsel to identify the applicable current framework and any additional source review needed. Preserving the document's date and limited role prevents a general governance reference from becoming an unsupported claim that a particular procedure is legally sufficient.

Separate administrative intake from evaluation

The person receiving disclosures can check whether the expected fields are present and route the record without deciding the substantive question. Define that role clearly. A staff member may need to acknowledge receipt, identify a missing transaction description, and notify the designated reviewer. None of those actions should be displayed as approved or cleared. The organization needs an honest state distinction between submitted, incomplete, under review, and an outcome reached through the appropriate process.

Identify who is authorized to evaluate the issue and what happens when that person is involved in the relationship. The answer should come from the applicable framework and professional advice, not an improvised workflow. A process can fail when every disclosure routes to the person whose participation is the question. Ask counsel how the actual organization should address that circumstance and document the adopted instructions so the administrative owner is not forced to make a governance decision under meeting pressure.

Record the outcome and its scope through the reviewed process. A decision about one proposal should not become blanket approval for all future transactions with the same participant. A change in price, scope, relationship, or available information may require renewed consideration. The practical log can identify the relevant change and return it to the reviewer. It cannot decide that the original outcome remains valid or create an exception to the organization's policy.

Prepare the chair and minute-taker before the meeting

Ask counsel what participation, discussion, voting, and documentation are appropriate in the specific circumstances. The chair needs instructions that can be applied to the actual item, and the minute-taker needs to know what should be recorded. Do not rely on a template that directs every participant to leave or abstain regardless of the applicable framework. A general educational article cannot establish who may participate, the required vote, or the validity of the resulting decision.

Keep meeting materials factual and appropriately limited. Participants may need to understand the proposal and relevant process without receiving every private detail in the disclosure file. Ask the responsible reviewers to distinguish the material needed for deliberation from material retained separately. This supports an accurate decision record without turning the board packet into an uncontrolled archive of sensitive personal information. Convenience in sharing materials should not decide who receives them.

If a disclosure arrives during the meeting, follow the reviewed escalation process. Do not pressure the participant to withdraw the concern so the agenda can move ahead. Likewise, do not declare the transaction improper from the chair's initial reaction. The organization may need more information or advice before acting. Record the state honestly, including any deferral or next task, rather than producing minutes that suggest a completed review the participants did not actually perform.

A fictional supplier relationship disclosed early

Imagine a fictional nonprofit considering a technology support contract. A director explains that a relative has an ownership interest in the proposed supplier. The disclosure reaches the designated recipient before the meeting. The organization gathers the proposal, describes the relationship factually, and asks the authorized reviewers to evaluate the applicable process. The example does not determine whether a conflict exists or whether the proposed contract is acceptable. It shows how early disclosure makes review possible before the board is under pressure to sign.

The reviewers ask for additional information about scope and available alternatives. The record remains under review while that information is collected. The director's disclosure is not treated as a confession of wrongdoing, nor as an automatic permission to proceed. The chair and minute-taker receive appropriate instructions for the actual decision process. This separation helps preserve fairness to the participant and fidelity to the organization's obligations without turning a disclosure into a predetermined result.

Suppose the supplier later proposes a materially larger scope. The administrative owner links the changed proposal to the earlier record and routes it for renewed review as appropriate. The original outcome is not silently stretched to cover a different transaction. A useful process keeps the approved scope, relevant facts, and later changes connected so that staff administering the contract can identify when the basis of the review has changed.

Preserve records and repair gaps honestly

Maintain the adopted policy, disclosures, supporting materials, and decision records through the organization's approved access and retention process. Ask counsel about legal communications and sensitive records. An ordinary shared volunteer drive may not be appropriate for every category. A record can point to the protected disclosure without copying all its details into the meeting minutes or a general task board. The organization should be able to retrieve the relevant history without multiplying unnecessary copies.

If a step was missed, preserve the facts and obtain appropriate advice. Do not backdate a disclosure or rewrite minutes to create a review that did not occur. A correction process should identify what is being corrected and what remains unresolved. The organization can address an administrative defect without pretending the original record was complete. Counsel should assess the actual consequence and response; this article does not authorize a retroactive cure or determine the validity of a transaction.

Training can use synthetic scenarios to show how the process works without exposing genuine relationships. Ask participants to locate the disclosure instructions, explain the recipient's role, and identify when a changed proposal needs attention. The practical standard is whether people can route relevant facts before action and preserve an accurate outcome afterward. A policy stored in a folder is only part of that result. An understandable, reviewed workflow makes the policy usable while leaving substantive conflict judgments to the proper process.

Ask the disclosure recipient to demonstrate the routing path using a fictional changed relationship. The exercise should show where the record goes when the usual reviewer is involved, without inventing that reviewer's authority. Any missing instruction is a governance question to resolve with counsel before participants depend on the workflow.