CME Activity Documentation: What Gets Approved and What Gets Returned

A CME program coordinator at a regional health system once described her team's process as "writing the activity twice" — once to plan it, and again three weeks later when the application came back with corrections requests. The second pass, she noted, was always more stressful than the first, because it happened under deadline pressure and required locating and revising documents that had already been filed.

This pattern is common enough to have a name in medical education circles: the return cycle. Applications come back not because the educational content is poor, but because the documentation around it fails to meet the specific evidentiary requirements that ACCME accreditation demands. The clinical content of a CME activity and the documentation that supports an accredited CME application are two separate bodies of work, and many program teams conflate them until a return arrives to remind them otherwise.

What the Standards Actually Require

The ACCME's Standards for Integrity and Independence in Accredited Continuing Education, which took effect January 1, 2022, reorganized years of accumulated requirements into five core standards. Understanding what those standards demand in documentation terms — as opposed to in practice terms — is the first step to avoiding returns.

Standard 1 addresses the identification of professional practice gaps and learning objectives. In documentation terms, this means an activity application must demonstrate a specific, defined gap between what the target audience currently does and what evidence or guidelines say they should do. "Physicians need to know more about X" does not satisfy this requirement. The application must describe a measurable discrepancy — ideally traced to a data source, a patient outcome measure, or a published needs assessment — and the learning objectives must be written to close that specific gap.

Standard 2 requires that content be valid, evidence-based, and free from commercial bias. Documentation must establish that faculty are qualified to present on the subject and that their financial relationships with commercial entities have been identified, disclosed, resolved, and documented before content is finalized. The paperwork trail here is granular: who disclosed what, when the disclosure was reviewed, what conflicts were identified, how each conflict was resolved, and who approved the resolution.

Standard 3 governs the management of commercial support. Activities that receive commercial support must document the receipt of that support in a written agreement that meets ACCME's specific terms. "Grant letter on file" is often not sufficient; the agreement must explicitly acknowledge the accredited provider's independence over content decisions.

Standards 4 and 5 address engagement with commercial interests and independence from commercial influence at the organizational level — documentation obligations that primarily fall on the accredited provider rather than on individual activity applications, but that still require specific records for each activity in a joint providership relationship.

Where Documentation Breaks Down

Most returns cluster around three documentation failures, not five. Understanding them makes the difference between a clean first submission and a return cycle.

1. The Practice Gap That Isn't

A practice gap statement must describe a specific, verifiable discrepancy between current and desired professional practice. The most common failure here is a gap statement that describes a topic rather than a gap. "Advances in the management of Type 2 diabetes" describes a content area. "A 2024 survey of primary care physicians in our health system found that 43% were not screening for cardiovascular risk using the most recent ACC/AHA guidelines" describes a practice gap. Only the second statement supports the development of SMART learning objectives and satisfies the documentation requirement.

When applications are returned for gap-related reasons, it is almost never because the gap doesn't exist. It's because the gap statement provided cannot be evaluated. It lacks a source. It lacks specificity about the target audience. It uses language that describes an educational topic rather than a measurable behavioral deficit in a defined population.

2. Disclosure Paperwork With Gaps in the Chain

ACCME's conflict of interest requirements create a documentation chain that runs from initial disclosure through final resolution. Every link must be present. In practice, what often happens is that the chain breaks at the resolution step: a faculty member discloses a financial relationship, the relationship is identified as relevant, and then the file contains no documented resolution — no record of what was done to mitigate the conflict before the faculty member presented content.

Accepted resolution mechanisms include peer review of content, attestation that the content was developed without commercial influence, changes to faculty assignments, or independent review of slides. Any of these can satisfy the requirement. What cannot satisfy it is an absence of documentation. An auditor reviewing a file with a disclosed conflict and no recorded resolution has no choice but to treat the activity as non-compliant.

The problem is compounded in activities with large faculty rosters, where tracking disclosure and resolution for ten or fifteen presenters creates real administrative burden. Applications with ten faculty members who all disclosed cleanly and whose resolutions are fully documented come back clean. Applications where eight are documented and two have gaps come back with corrections for all eight, because the documentation review is comprehensive.

3. Joint Providership Documentation That Doesn't Travel

When an accredited CME provider co-produces an activity with a non-accredited organization — a specialty society, a hospital department that lacks its own accreditation, a pharmaceutical company's medical affairs team — the accredited provider bears full responsibility for demonstrating compliance on behalf of the entire activity. Documentation that lives only at the non-accredited partner's site, or that was collected by the partner using their own forms rather than the accredited provider's, creates a gap even if every actual requirement was met.

Joint providership activities are a significant source of returns because the accredited provider often learns about documentation gaps only when the application is submitted. The partner organization completed their version of the disclosure process. The partner organization ran the educational planning meeting. But the documentation from those processes is in the partner's filing system, not the provider's, and it was collected on forms that may not capture every field the accredited provider needs to demonstrate compliance.

Learning Objectives: The Drafting Problem Most Teams Miss

ACCME requires that CME learning objectives be written in SMART terms — specific, measurable, achievable, relevant, and timely. In practice, "measurable" is the requirement that causes the most revision. An objective is measurable when it describes what a learner will be able to do, not what they will know or understand.

The distinction sounds like semantics until you realize that unmeasurable objectives make evaluation design nearly impossible. If your objectives say participants will "understand" or "be aware of" the content, you cannot write an evaluation instrument that meaningfully tests whether those objectives were met. ACCME reviewers look for this because it signals that the evaluation plan and the educational plan are disconnected — a common sign of an activity that was assembled from existing materials rather than designed around a defined practice gap.

The fix is mechanical. Replace outcome-ambiguous verbs — understand, know, appreciate, be familiar with — with action verbs that describe observable behavior: describe, calculate, identify, select, apply, differentiate, demonstrate. "Participants will be able to calculate cardiovascular risk using the updated ASCVD Risk Estimator and apply appropriate preventive therapy based on risk category" is testable. "Participants will understand cardiovascular risk assessment" is not.

The Evaluation Documentation That Gets Forgotten

Post-activity evaluation is not optional, and documentation of the evaluation plan is required as part of the activity application in most accreditation systems. What is less well understood is that the evaluation must be designed to measure what the learning objectives said it would measure. An activity whose objectives address clinical decision-making cannot be evaluated solely through a satisfaction survey.

Applications that reach a reviewer with a satisfaction-only evaluation plan and measurable behavioral objectives are internally inconsistent. The objectives claim one thing; the evaluation measures something different. This disconnect is a documentation deficiency, even when the activity itself was educationally rigorous and the participants found it useful.

The practical implication is that objectives and evaluation design need to be developed together, not sequentially. If you write the objectives first and then attach a standard satisfaction survey, you will almost always produce an inconsistency that requires correction.

Commercial Support Agreements: What "On File" Actually Means

ACCME requires a written agreement for every activity that receives commercial support. The agreement must document the nature of the support, confirm the accredited provider's independence over educational content decisions, and be signed before the activity is presented. Applications that are submitted with a note that the agreement is "forthcoming" or "in process" are not compliant at submission, regardless of what is eventually produced.

The agreement also cannot be a grant letter alone. Grant letters confirm that money or other support was given; they do not always confirm the independence terms that ACCME specifies. Many organizations have learned this distinction after their first return for a commercial support activity: the grant letter was on file, the activity had already run, and the application came back because the letter didn't contain the ACCME-required language affirming content independence.

The resolution is to use ACCME's sample commercial support agreement as a template, ensure it is countersigned before the activity opens, and attach it to every application involving commercial support as a named exhibit rather than a generic reference.

Preparing Documentation That Passes on First Submission

Most first-submission returns are preventable. The applications that come back are not generally problematic because the education was poor or the activity was commercially influenced. They come back because the documentation was assembled under time pressure, with different team members handling different elements, without a systematic final review against the complete checklist of required elements.

A structured documentation review — not a content review, but a documentation review that asks specifically whether each required element is present, complete, and internally consistent with every other element — catches the majority of preventable returns before the application leaves the organization. The gap statement should be traceable to a source. The objectives should contain action verbs and should map to the gap. The disclosures should be complete for every faculty member. The resolutions should be documented for every identified conflict. The evaluation plan should match the objectives. The commercial support agreement, if applicable, should be countersigned and contain the ACCME-required language.

That checklist is not complicated. What makes it difficult is that it requires someone to read the application as a documentation reviewer rather than as a content planner — a different posture toward the same documents.