IRB Ready

IRB for Community-Based Participatory Research

By ·

Community-based participatory research (CBPR) challenges several assumptions that federal IRB regulations were written around. The regulations assume a clear PI-participant distinction; CBPR blurs it. The regulations focus on individual consent; CBPR raises community-level consent questions. The regulations default to university data ownership; CBPR often requires shared or community-held data. None of this makes CBPR non-reviewable — but it does mean the protocol needs to name the departures from standard assumptions explicitly, or reviewers will flag them as omissions.

What CBPR is in practice

CBPR is a collaborative approach to research that involves community members and institutional researchers as partners at each phase: question formulation, design, data collection, analysis, and dissemination. Community partners are typically co-investigators, not participants or instruments. The research is designed to benefit the community, with findings owned and used jointly.

The typical arrangement involves a university research team, a community partner organization (nonprofit, clinic, school district, tribal government, community advisory board), and participants drawn from the community. The relationships among these three need to be spelled out in the protocol.

Listing community partners as personnel

Community co-investigators appear on the personnel list. This triggers two practical requirements:

  • CITI training. All listed personnel need current human subjects protection training. Some institutions allow abbreviated training for community co-investigators; others do not. Confirm early and budget time.
  • Role descriptions. Describe each person's responsibilities: recruitment, data collection, interpretation, dissemination. Reviewers want the roles clear.

Memoranda of understanding

A formal memorandum of understanding (MOU) between the university and the community partner organization should be in place before submission. The MOU covers:

  • Roles and responsibilities.
  • Data ownership and access.
  • Authorship and dissemination.
  • Compensation for community partners (often a subcontract or a stipend structure).
  • Dispute resolution.

The MOU is not the same as the IRB protocol, but the protocol should reference it and match its terms. For public health practicum and community health work at the boundary between service and research, The Public Health Practicum Logbook covers the community partnership documentation that often doubles as the MOU basis.

Community advisory boards

Many CBPR studies convene a community advisory board (CAB) that reviews the research at key milestones. The CAB is not an IRB — it does not replace formal review — but it provides community-level oversight that complements IRB review. Describe in the protocol:

  • CAB composition and selection.
  • Meeting cadence.
  • Scope of CAB input (protocol review, recruitment review, dissemination review).
  • How CAB feedback will be documented and acted on.

Community consent vs. individual consent

Individual consent remains required under 45 CFR 46.116; community consent does not replace it. What community-level processes do is add a layer above individual consent — community leaders or governance structures may authorize the research at the community level before individual recruitment begins.

For research involving tribal nations, tribal IRBs or tribal governments often have formal approval roles that sit alongside the university IRB. Both approvals are required. Factor tribal review timelines into your plan.

Data ownership and sovereignty

Standard university protocols default to university ownership of study data. CBPR often requires shared ownership or community-held data, especially with Indigenous communities applying CARE principles (Collective benefit, Authority to control, Responsibility, Ethics) and OCAP principles (Ownership, Control, Access, Possession).

Describe:

  • Who owns the raw data.
  • Who owns the de-identified analytic file.
  • Who controls access requests from outside parties.
  • What must happen before dissemination (community review of findings, right to comment, right to veto publication of specific findings in some agreements).

Our data management plan template has fields for shared ownership arrangements. For the broader structure of the protocol itself, see our protocol writing guide.

Recruitment through community partners

Community partners often do much of the recruitment. This has advantages (trust, reach) and IRB implications (gatekeeper dynamics, potential coercion). Describe:

  • How community partners will approach potential participants.
  • How the partner's role will be distinguished from the researcher's role.
  • How participants will understand that declining does not affect their relationship with the partner organization.

The coercion risk is real. Clients of a service organization may feel pressure to participate in research led by that organization. Explicit language about voluntariness, in both the recruitment script and the consent form, is necessary.

Dissemination and benefit sharing

CBPR dissemination usually extends beyond journal publication to include community-accessible reports, presentations to the community, and sometimes co-authored publications. State the dissemination plan explicitly. Reviewers appreciate, and sometimes require, a plan that returns findings to the community before or concurrent with academic publication.

Compensation at the community level

Beyond individual participant compensation, CBPR often involves compensation to the community partner organization. Describe both. If the university-community subcontract includes research activity, reviewers will want to confirm that the arrangement does not create coercion or conflict of interest at the organizational level.

What reviewers flag most

Recurring comments on CBPR protocols:

  • Community co-investigators not listed as personnel.
  • No MOU referenced.
  • No description of how voluntariness will be protected in recruitment through a partner organization.
  • Data ownership unclear.
  • Dissemination plan limited to academic publication.

Each is a drafting fix. CBPR protocols run through IRB review at the same pace as other minimal-risk research once the departures from default assumptions are named. For review level expectations, see our review categories overview.

The underlying alignment

CBPR and IRB review share a goal: protecting participants while enabling research that matters. The operational tensions come from federal regulations being written around a simpler researcher-participant dyad than CBPR actually involves. Naming the departures from that default — in the protocol, the consent, the data management plan, and the MOU — resolves most of the tension. Reviewers want to see that you have thought it through, and a CBPR protocol that addresses the structural questions head-on moves through review as smoothly as any other expedited study.