Managing Conflicts of Interest and Related-Party Risk in Community Services

MIke Harrison
2026-02-06T13:03:20+00:00

Conflicts of interest are rarely about obvious wrongdoing—they’re about unmanaged influence that quietly distorts decisions. This article sets out practical governance and operational controls to identify, disclose, manage, and audit conflicts and related-party transactions in U.S. community services organizations.

More

Conflicts of interest are an integrity risk because they usually present as “reasonable” decisions made under pressure: a familiar vendor, a board member’s referral, a senior leader’s side consultancy, or a staff member’s second job in the same local market. The challenge is not eliminating human relationships; it is ensuring decisions remain defensible, documented, and insulated from undue influence. In U.S. community services, conflict controls underpin Ethics, Integrity & Public Trust and must be demonstrably governed through Board Governance & Accountability—particularly where public funds, Medicaid/Medicare-adjacent pathways, grants, or county contracts require audit-ready assurance.

Why conflict-of-interest risk is operational, not just “policy”

Most organizations have a conflict-of-interest (COI) policy. Fewer have a functioning COI system. The operational risk arises when conflict disclosures are treated as annual paperwork rather than a living control: decisions happen weekly, relationships change, and pressures escalate during procurement, staffing shortages, or emergency service continuity actions.

Related-party risk is a specific subset of COI risk. It includes transactions, referrals, contracts, employment, leases, or consulting arrangements involving board members, executives, owners, family members, or entities where insiders hold financial interests. Even when lawful, related-party arrangements can erode public trust unless governed with heightened transparency, market testing, and documented rationale.

Core controls that funders and regulators expect to see “in practice”

Oversight bodies typically do not accept “we have a policy” as assurance. They expect to see: (1) timely disclosure, (2) effective recusal, (3) independent review, (4) documented market testing, and (5) evidence that the board can detect patterns (repeat vendors, repeat sole-source justifications, unusual price variances, and weak separation of duties). These expectations are increasingly relevant when organizations face labor gaps and rely on staffing agencies, consultancy support, or rapid procurement for safety-critical needs.

Operational Example 1: Event-based disclosure and decision gating

What happens in day-to-day delivery
A workable COI system uses event-based disclosure, not just annual forms. When any purchasing request, hiring action, referral arrangement, sponsorship, or partnership is initiated, the requester completes a short COI check within the workflow (often embedded in procurement or HR systems). If a potential conflict is identified—e.g., the vendor is owned by a board member’s spouse—the system automatically gates the decision: it triggers a compliance review, requires supporting documentation, and blocks approval until recusal and independent sign-off are recorded. Supervisors are trained to ask the COI question routinely during approvals, and finance/HR teams have a standard checklist to confirm the gate has been cleared.

Why the practice exists (failure mode it addresses)
Annual disclosure alone fails because it does not intersect with the moment decisions are made. Event-based gating prevents “reasonable exceptions” from bypassing control points when time pressure or familiarity biases a choice.

What goes wrong if it is absent
Organizations drift into informal awarding of work: a familiar consultant is rehired without competition, a staffing agency tied to an insider becomes the default, or a lease renewal is approved without market validation. When auditors or journalists later scrutinize contracts, the organization cannot show how it tested value or protected impartiality—creating reputational harm even if services were delivered.

What observable outcome it produces
Event-based gating produces an audit trail: COI checks tied to each transaction, documented recusals, independent review notes, and evidence of market testing. Over time, it reduces sole-source usage, improves pricing discipline, and increases board confidence that decisions are defensible.

Operational Example 2: Independent procurement review for related-party transactions

What happens in day-to-day delivery
For any related-party transaction, the organization applies a heightened standard. Procurement staff run a structured market test—quotes, rate benchmarking, or an RFP scaled to the risk. A reviewer with no connection to the parties (often the compliance officer or an external procurement advisor for high-value items) validates comparability: scope, deliverables, rates, and performance terms. The board (or a designated committee) reviews and approves related-party arrangements, with the conflicted member fully recused and absent from discussion. Documentation includes the rationale for selecting the related party, why alternatives were not chosen, and how performance will be monitored.

Why the practice exists (failure mode it addresses)
Related-party arrangements create a perception of self-dealing unless the organization can show the deal is at least as favorable as the market and that decisions were insulated from influence.

What goes wrong if it is absent
Even well-intended arrangements become indefensible: a lease appears overpriced, a consulting contract looks open-ended, or a vendor relationship persists despite service issues. Staff may feel pressured to accept poor performance because “the board likes them,” weakening quality control. Public trust deteriorates quickly if beneficiaries believe resources are being diverted.

What observable outcome it produces
Independent procurement review yields measurable assurance: price benchmarking records, committee minutes showing recusal, performance KPIs tied to contract terms, and periodic review points. This strengthens funder confidence and reduces the risk of contract termination or corrective action demands.

Operational Example 3: Workforce conflicts and secondary employment controls

What happens in day-to-day delivery
Workforce COI is common in community services: staff may work second jobs for another provider, a hospital-adjacent contractor, or a private client. A mature control approach treats secondary employment as a managed risk. HR requires disclosure at onboarding and whenever circumstances change. Supervisors review disclosures for risks like schedule conflicts, fatigue, confidentiality exposure, competing referrals, or inappropriate solicitation of service users. Where risk exists, managers set clear guardrails: limits on overtime, restrictions on client contact outside role scope, rules about referrals, and periodic check-ins. Compliance teams monitor incidents and complaints for signals of boundary drift, and timekeeping audits identify fatigue risk patterns.

Why the practice exists (failure mode it addresses)
The practice prevents hidden conflicts that can compromise safety, confidentiality, and impartiality—especially where staff have access to vulnerable people, financial data, or referral pathways.

What goes wrong if it is absent
Secondary employment can drive unsafe fatigue (missed visits, medication errors, poor documentation), or it can become a boundary risk (staff soliciting private work, using inside information to redirect referrals, or sharing confidential details across employers). When harms occur, organizations struggle to demonstrate they exercised reasonable oversight.

What observable outcome it produces
With controls in place, organizations can evidence reduced fatigue-related incidents, clearer documentation quality, and earlier detection of boundary concerns. Staff also report greater clarity on expectations, reducing inadvertent breaches.

Assurance mechanisms that make COI controls credible

COI systems become credible when leaders can demonstrate routine testing. Effective assurance commonly includes: sampling transactions to confirm COI checks were completed; reviewing sole-source justifications for repeat vendors; auditing approvals for segregation of duties; and comparing contract rates to benchmarks. Boards should expect periodic reporting on COI themes (not just single events) and should challenge whether management incentives—speed, cost, growth—are inadvertently weakening control discipline.

Explicit oversight expectations

Expectation 1: Audit-ready transparency
Funders, inspectors, and oversight partners commonly expect documentation that decisions were impartial and value-driven. This includes written recusals, independent review evidence, and demonstrable market testing for higher-risk arrangements.

Expectation 2: Board-level independence
Boards are expected to ensure COI controls are independent from the people who benefit from decisions. This means clear committee authority, conflict registers that are actively used, and a willingness to pause decisions until assurance is in place.