PCMH Annual Reporting Submission Checklist
Use this PCMH Annual Reporting Submission Checklist to gather NCQA attestation materials, verify required measures, and submit everything in Q-PASS before the deadline. It helps primary care teams avoid missing evidence, incomplete fields, or last-minute submission errors.
Trusted by frontline teams 15 years of frontline software
Built for: Primary Care Clinics · Family Medicine · Internal Medicine · Community Health Centers · Medical Groups
Overview
This PCMH Annual Reporting Submission Checklist is for primary care teams that need to complete the annual NCQA Patient-Centered Medical Home attestation and submit required measures in Q-PASS. It gives you a structured way to collect evidence, verify each reporting item, route approvals, and confirm the final submission before the deadline.
Use this template when the work is deadline-driven, evidence-based, and easy to delay until the last minute. It is especially useful if multiple people contribute to the filing, if data comes from different systems, or if you need a clear audit trail of who reviewed each item. The checklist format keeps the work atomic: each item should be independently verifiable and assigned to a DRI.
Do not use this as a vague annual reminder or a broad quality program tracker. If your goal is ongoing PCMH improvement, monthly scorecard review, or general compliance monitoring, create a separate recurring task for that purpose. This template is specifically for the submission workflow itself, including pre-submission validation and final upload. It is also not the right fit if your organization has no NCQA PCMH reporting obligation.
The best results come from using it as a controlled handoff between reporting, clinical, and administrative owners, with clear blocking and non-blocking items flagged before the filing window closes.
Standards & compliance context
- This template supports NCQA PCMH annual reporting by organizing the attestation and measure submission workflow into auditable checklist items.
- Use the checklist to preserve evidence of review and approval, which helps with internal governance and external audit readiness.
- Mark items critical only when a missed step could affect compliance, submission validity, or the ability to meet the reporting deadline.
- Keep patient data out of checklist notes unless it is necessary and permitted, and store sensitive source material in approved systems.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Add the exact reporting period, submission deadline, and Q-PASS owner so the checklist reflects the current annual filing cycle.
- 2. Break the submission into atomic checklist items for evidence gathering, measure verification, internal approval, and final upload.
- 3. Assign each checklist item to a DRI and mark only deadline-sensitive or compliance-impacting items as critical.
- 4. Run the checklist in order, attaching source documents or links to each verification step and marking any blocking issues immediately.
- 5. Complete a final review of the attestation fields and measure set in Q-PASS, then record the submission confirmation and closeout notes.
Best practices
- Keep each checklist item to one verifiable action, such as confirming a measure file or validating an attestation field.
- Use one owner for the final submission step so the handoff does not split accountability across reporting and clinical staff.
- Flag only true deadline or compliance blockers as critical, and leave routine prep work at normal priority.
- Attach the source report, policy, or evidence file to the relevant checklist item instead of storing proof in a separate thread.
- Add a verification step for the final Q-PASS review so a second person confirms the submission before it is sent.
- Schedule an internal pre-deadline checkpoint early enough to resolve missing data, access issues, or approval delays.
- Separate blocking items from non-blocking items so the team knows what must be fixed before submission and what can be documented later.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is included in this PCMH Annual Reporting Submission Checklist?
This checklist covers the annual PCMH attestation workflow from gathering source documents to final submission in Q-PASS. It is meant to track each checklist item needed to confirm measures, review evidence, and complete the filing before the deadline. It does not replace NCQA guidance, but it helps your team execute the process in a repeatable way. Use it as the working record for who verified what and when.
Who should run this checklist?
The DRI is usually the PCMH program manager, quality manager, or practice administrator, with input from clinical leadership and reporting staff. In smaller practices, one person may own the task type end to end, but each checklist item should still have a clear verifier. If multiple sites are involved, assign site-level contributors for evidence collection and one central owner for final review. That reduces blocking at submission time.
How often should this checklist recur?
This is typically a yearly recurrence tied to the NCQA reporting cycle and the organization’s internal deadline. Many teams also run a pre-close review several weeks before submission so missing items surface early. If your practice has multiple locations or staggered data pulls, add interim checkpoints rather than waiting for the final week. The checklist should reflect the actual cadence your team uses.
Is this checklist only for NCQA PCMH submissions?
Yes, this template is scoped to the annual PCMH reporting submission workflow and the Q-PASS filing process. It is not a general quality reporting template or a broader compliance register. If you need a different workflow, such as onboarding, gap closure, or ongoing monthly monitoring, customize the checklist items to match that use case. Keeping the scope narrow makes the submission path easier to follow.
What are the most common mistakes this checklist helps prevent?
Common failures include missing evidence, using the wrong reporting period, leaving a field incomplete in Q-PASS, and assuming a measure was verified without a named reviewer. Another frequent issue is treating the submission as one task instead of a sequence of independent checklist items. This template helps you break the work into verifiable steps so a single missed item does not block the whole filing. It also makes review handoffs clearer.
How should we customize the checklist for our practice?
Add the exact measures, documents, and internal approvers that apply to your organization, and remove anything that does not affect your submission. If you have multiple clinics, include site-specific verification steps and a final consolidation step. You can also adjust priority so only deadline-sensitive or compliance-impacting items are marked critical. Keep each checklist item atomic so it can be answered yes, no, or N/A.
Can this checklist connect to other systems or workflows?
Yes, it works well alongside document storage, task tracking, and reporting tools used by quality and operations teams. Many teams link evidence folders, EHR reports, and Q-PASS preparation notes to each checklist item. If your process includes approvals, add a verification step for the final reviewer before submission. Integrations are most useful when they reduce manual searching for source files.
Should this be used as an ad-hoc task list or a formal compliance workflow?
It should be treated as a formal compliance workflow because the submission has a deadline, evidence requirements, and an audit trail. An ad-hoc list often misses ownership, recurrence, and verification steps, which creates avoidable rework. This template gives you a structured record of what was checked, by whom, and whether anything was blocking. That makes the process easier to repeat next year.
Related templates
Go deeper on the topic
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compliance is the practice of ensuring employee behavior meets regulatory, contractual, and internal-policy requirements — and of producing the evidence to...
-
Compliance training automation is the software-driven process for assigning, tracking, and evidencing required training (HIPAA, harassment prevention,...
-
HR case management is a structured system for handling employee questions, requests, and issues — with routing, SLAs, an audit trail, and a knowledge base...
Ready to use this template?
Get started with MangoApps and use PCMH Annual Reporting Submission Checklist with your team — pricing built for small business.