FDA Diversity Action Plans are changing how sponsors prepare certain pivotal clinical studies. For CROs, the impact reaches well beyond a new regulatory document.
A credible plan requires operational evidence: sites capable of reaching the intended population, recruitment measures designed around real barriers, and data systems that show whether enrollment is progressing towards demographic goals.
One distinction is essential. The statutory framework already exists under the Food and Drug Omnibus Reform Act of 2022, or FDORA. However, the FDA still identifies its June 2024 Diversity Action Plan guidance as a draft that is not for implementation.
The submission requirement will apply to specified studies whose enrollment begins at least 180 days after the final guidance is published. It is therefore inaccurate to say that Diversity Action Plans are already mandatory for most clinical trials.
Waiting for that date would nevertheless be a poor operational strategy. Recruitment networks, protocol assumptions, data structures and reporting workflows cannot be redesigned overnight. CROs that prepare early will be better positioned to help sponsors turn demographic objectives into an executable study plan.
What will the FDA Diversity Action Plan require?
Section 3601 of FDORA added Diversity Action Plan provisions to the Federal Food, Drug, and Cosmetic Act. The framework covers specific late-stage or pivotal drug studies and certain device investigations, not every clinical trial.
According to the FDA’s report to Congress on Diversity Action Plans, the affected studies include:
- Phase 3 studies of new drugs;
- other pivotal drug studies, when appropriate, excluding bioavailability and bioequivalence studies;
- device studies requiring an Investigational Device Exemption;
- certain other device studies used to support a 510(k), De Novo classification request or premarket approval application.
The same report explains that a plan must contain three central elements:
- The sponsor’s enrollment goals;
- the rationale supporting those goals;
- an explanation of how the sponsor intends to achieve them.
The goals must be disaggregated by race, ethnicity, sex and age group for the clinically relevant population.
The FDA draft also encourages sponsors to consider factors such as geography, socioeconomic circumstances, disability, comorbidities and other conditions that may influence access or representativeness.
When should the plan be submitted?
For drug development, the 2024 draft recommends engaging the FDA early and submitting the plan to the relevant IND as soon as practicable.
The proposed deadline is no later than submission of the Phase 3 or other pivotal study protocol.
For device studies requiring an IDE, the plan would be submitted with the IDE application. For applicable studies that do not require an IDE, it would accompany the relevant premarket submission.Waivers are contemplated by the statute but are expected to be exceptional. A difficult recruitment environment is not, by itself, a substitute for a strategy.
For CROs, the practical implication is clear: diversity planning must begin before sites are selected and before the recruitment forecast is finalised.
Why clinical-trial diversity matters beyond compliance
Representative enrollment is not simply a question of matching population percentages. It is about generating evidence that can be interpreted for the people likely to use the medical product.
Disease prevalence, disease presentation, treatment response, adverse-event profiles and access to care may vary across population groups. When relevant groups are underrepresented, uncertainty can remain around safety, effectiveness or product performance.
The FDA recommends broader eligibility criteria, more accessible trial designs and recruitment practices capable of reducing unnecessary exclusion.
The scientific concern is also visible across therapeutic areas. Published reviews continue to identify gaps in representation, including a systematic review and meta-analysis of racial and ethnic representation in nephrology trials.
The operational and business case
A more representative trial can give sponsors:
- evidence that better reflects the intended-use population;
- earlier visibility of subgroup-specific signals;
- stronger answers to regulator and payer questions;
- fewer uncertainties when planning post-authorisation evidence;
- results with broader clinical and commercial relevance.
This does not mean that every trial must reproduce national census proportions. Enrollment goals should be scientifically justified using the epidemiology of the condition, the product’s intended use and any evidence of potentially relevant differences.
Diversity should therefore be treated as part of study quality, not as a communication initiative added after protocol approval.
How CROs must adapt recruitment strategies
A Diversity Action Plan becomes credible only when its goals are connected to specific recruitment and retention measures.
Generic commitments to “reach diverse communities” will provide little operational value
Select sites using demographic evidence
Historical enrollment volume remains important, but it cannot be the only selection criterion. CROs should evaluate:
- the demographic profile of the site’s catchment area;
- disease prevalence within the relevant population;
- access to community health networks;
- the investigator’s previous enrollment by subgroup;
- language capabilities and cultural competence;
- transport, opening hours and visit burden;
- digital access where remote tools are planned.
A high-performing site that repeatedly reaches the same narrow population may not support the study’s enrollment goals. Conversely, a site in relevant community may still need additional resources, training or referral partnerships before activation.
The ACTide Ecosystem supports site and enrollment management using standardised country information and real-time reporting. This provides a foundation for consistent oversight, provided the study captures the variables and metrics required by its diversity strategy.
Build community engagement before recruitment
Trust cannot be created by a campaign launched on the first day of enrollment. CROs should work with sponsors to identify credible local partners early, including:
- patient advocacy organisations;
- community clinics and healthcare professionals;
- disease-specific support groups;
- local research networks;
- organisations serving linguistically or geographically isolated populations.
These relationships should help shape communication, identify participation barriers and establish realistic expectations. They should not be treated solely as channels for advertising a study.
Remove practical barriers to participation
Recruitment materials may be understandable and inclusive while the trial itself remains difficult to access.
Common barriers include travel time, lost income, childcare responsibilities, inflexible visit schedules, language limitations and lack of suitable technology.
Responses may include travel support, decentralised activities, translated materials, flexible appointments and provisioned devices.
Review eligibility criteria before they create exclusion
Overly restrictive criteria can exclude people without improving participant safety or the interpretability of results.
Sponsors retain responsibility for protocol design, but CRO feasibility data can show where proposed criteria are likely to affect particular groups.
An early operational review should examine age limits, comorbidity restrictions, laboratory thresholds, language assumptions, visit frequency and requirements for caregivers or personal devices.
Where patient-reported outcomes are required, ACTide ePRO provides a multilingual, responsive interface and supports real-time collection from smartphones, tablets and desktops.
Technology can reduce some barriers, but CROs should retain alternatives for participants affected by limited connectivity, low digital confidence or accessibility needs.
What changes in demographic reporting?
A Diversity Action Plan is not complete when the FDA receives the document. Sponsors will need to understand whether implementation is working, and CROs will be expected to supply timely, reliable evidence.
Track enrollment against goals in real time
Study teams should not discover a demographic imbalance when recruitment is almost complete.
Dashboards should compare screened, eligible, enrolled, randomised and retained participants with planned goals.
Useful views include:
- actual enrollment versus target by subgroup;
- screen-failure rates by demographic category;
- site-level contribution to each goal;
- withdrawal and retention patterns;
- trends over time;
- forecasted enrollment at study and site level.
Real-time monitoring enables corrective measures while they can still change the outcome, for example, adding referral channels, revising site support or investigating a disproportionate screen-failure rate.
Use controlled demographic data standards
Demographic fields should not be added informally to a CRF. Categories, terminology, permitted responses, unknown values and rules for multiple selections must be defined before study launch.
The US Office of Management and Budget revised its federal standards for race and ethnicity data in 2024, including a combined race-and-ethnicity question and a distinct Middle Eastern or North African category.
CROs should not assume that every FDA dataset or implementation timeline has already migrated to the revised model.
The correct version should be confirmed against current FDA submission requirements and controlled through the data-management plan, CRF specifications and metadata.
For global studies, source questions may also need local linguistic and cultural adaptation. Mapping should preserve the participant’s response while producing consistent analysis categories.
Connect recruitment and randomisation data
Demographic monitoring may require data from screening, EDC, enrollment and randomisation processes. Manual reconciliation across disconnected spreadsheets increases delay and error risk.
An integrated ACTide RTSM and eCRF workflow can help align subject status, enrollment activity and study data. Any demographic use must still follow protocol requirements, privacy controls, blinding rules and the principle of collecting only necessary information.
What if the targets are not met?
The plan should explain how progress will be monitored and how barriers will be addressed. Missing a goal should trigger documented analysis and proportionate corrective action, not retrospective rewriting of the target.
CROs should be able to show:
- when the deviation became visible;
- which sites or process stages contributed to it;
- what root causes were investigated;
- which measures were introduced;
- whether those measures improved recruitment or retention;
- what rationale supports the final outcome.
A transparent record of decisions is more credible than a late narrative assembled after database lock.
ACTide eCRF supports configurable user profiles, validation checks, audit trails, monitoring tools and real-time exports. Within a properly designed study, these functions can help CROs collect and review the demographic information needed for recruitment oversight.
What CROs should do now
The current regulatory transition gives CROs time to prepare, but not time to remain passive.
Audit the current operating model
Select recent or active studies and ask:
- Could we define enrollment goals using reliable epidemiological data?
- Do feasibility assessments include demographic reach?
- Can we monitor screening, enrollment and retention by subgroup?
- Are reasons for screen failure and withdrawal sufficiently structured?
- Can we document recruitment interventions and their outcomes?
- Can our systems export analysis-ready, traceable data?
The audit should identify both procedural and technological gaps.
Update SOPs and responsibilities
Diversity-related activities should be embedded in study startup, feasibility assessment, recruitment, monitoring, and data management. SOPs or work instructions may need to define:
- who translates sponsor goals into operational metrics;
- who reviews performance and how frequently;
- when escalation is required;
- how corrective measures are approved;
- how demographic data are protected;
- how plan changes and decisions are documented.
The sponsor remains responsible for regulatory submissions. The CRO’s responsibilities should be made explicit in contracts, plans and governance structures.
Assess the technology stack
A DAP-ready environment should support:
- configurable demographic fields and controlled terminology;
- consistent data capture across sites and languages;
- real-time enrollment reporting;
- subgroup-level filtering and export;
- site comparisons and trend analysis;
- role-based access;
- complete audit trails;
- integration between recruitment, EDC, ePRO and RTSM data;
- privacy-aware reporting that limits re-identification risk.
The goal is not to label software “DAP compliant”. Compliance belongs to the study process. Technology should make the strategy measurable, traceable and easier to operate.
Move from a plan to an operating model
FDA Diversity Action Plans are not yet mandatory under the implementation timetable described by the agency. But FDORA has already established the direction of travel, and the FDA has received hundreds of voluntary diversity plans.
CROs should use this period to improve site intelligence, community engagement, protocol feasibility, demographic data standards and real-time reporting.
The decisive question is not whether a CRO can help write a Diversity Action Plan. It is whether the CRO can execute the plan, detect shortfalls early and provide reliable evidence of the actions taken.
ACTide brings eCRF, ePRO, RTSM, site administration and reporting capabilities into a connected clinical data environment.
Request an ACTide demo to explore how your study team could monitor enrollment, standardise demographic data and turn recruitment goals into traceable workflows.