OAA Reporting & Data Requirements

Overview of OAA Reporting

OAA reporting serves multiple purposes: it documents the scope and reach of the aging services network, demonstrates compliance with targeting requirements, provides accountability for the use of approximately $2.3 billion in federal funds, and generates the data ACL uses to report to Congress and inform national aging policy. Unlike competitive grants where grantees submit individual progress reports, OAA reporting flows through the aging network hierarchy: providers report to AAAs, AAAs aggregate and report to SUAs, and SUAs compile and submit the State Program Report (SPR) to ACL.

The primary data collection framework is the National Aging Program Information System (NAPIS), which captures standardized data on registered clients, demographic characteristics, and units of service delivered. NAPIS data feeds into the annual SPR, which is the official federal reporting instrument for OAA programs.

The State Program Report (SPR)

The SPR is the annual data submission that each SUA makes to ACL. It is the single most important OAA reporting instrument, compiling data from all AAAs and service providers within the state into a comprehensive picture of OAA service delivery. The SPR captures data across several domains:

Client Registration Data

The SPR reports the number of registered clients receiving OAA services, broken down by service category and demographic characteristics. A "registered client" is an individual who has been enrolled in the NAPIS system with demographic data collected. Key registration data elements include:

• Age: Collected in age ranges (60–64, 65–74, 75–84, 85+) to track the age distribution of the served population and identify trends in service utilization by age cohort
• Income status: Self-reported as at or below the federal poverty level or above. This is the primary data point for measuring economic need targeting. Remember — this data is collected for reporting purposes only, not as a condition of service
• Race and ethnicity: Self-reported using categories aligned with OMB standards. This data measures social need targeting effectiveness for racial and ethnic minority populations
• Rural/urban residence: Classification of the client's residence for tracking adequate proportion compliance and rural service delivery effectiveness
• Living arrangement: Whether the client lives alone, with a spouse/partner, or with others — relevant to social isolation targeting
• Disability status: Self-reported physical and mental disability status, relevant to social need targeting for persons with disabilities
• Limited English proficiency: Whether the client has limited ability to read, write, speak, or understand English, relevant to language access and social need targeting

Units of Service Data

The SPR reports the total units of service delivered by service type. Units of service are the fundamental measure of OAA service output. The unit definition varies by service type:

Accurate unit counting is critical for SPR integrity. Providers must use consistent definitions — for example, counting one home-delivered meal as one unit regardless of whether it includes multiple food items, and counting each one-way trip (not round trips) for transportation. SUAs may provide additional guidance on unit definitions for less standardized services.

Expenditure Data

The SPR reports expenditures by funding source (OAA Title III by sub-title, state general funds, other federal, local, and program income) and by service category. This data allows ACL to analyze the cost per unit of service, the leverage ratio of federal to non-federal funds, and expenditure patterns across states. Expenditure data must reconcile with the AAA's financial records and the SUA's accounting system.

NAPIS Data Collection

The National Aging Program Information System (NAPIS) is the data infrastructure that underpins OAA reporting. NAPIS is not a single national database — rather, it is a standardized data collection framework that each state implements through its own data system. Some states use commercial aging services software platforms, while others have developed custom systems. All must collect and report the standard NAPIS data elements.

Client-Level vs. Aggregate Reporting

NAPIS data collection operates at two levels, and the distinction is important for understanding both the data's capabilities and limitations:

• Registered client data: For services where individual registration is practical (home-delivered meals, homemaker, personal care, transportation, caregiver services), NAPIS collects client-level demographic and service data. Each registered client has a unique record with their demographic profile and service history
• Aggregate service data: For services where individual registration is impractical (congregate meals where new attendees may drop in, information and referral calls, community education events), NAPIS may collect aggregate counts of service units and participant contacts rather than individual client records

States vary in how much client-level data they collect for congregate nutrition programs. Some states register all congregate meal participants individually, while others use a combination of registered client data and aggregate meal counts. Your SUA's data collection protocols will specify the level of detail required.

Data Collection at the Provider Level

Service providers are the primary data collection points in the OAA reporting chain. Providers are responsible for registering clients, recording service units, collecting demographic data from participants, and entering data into the state's NAPIS system (or submitting data to their AAA for entry). Data collection quality at the provider level directly determines the accuracy and completeness of SPR data at the state level.

Common data collection challenges at the provider level include staff turnover that disrupts data entry routines, participant reluctance to share demographic information (particularly income and race/ethnicity), inconsistent unit counting practices, and delayed data entry that creates backlogs. AAAs should provide ongoing training and technical assistance to providers on data collection procedures and quality expectations.

ACL Performance Outcome Measures

Beyond the basic SPR data on clients served and units delivered, ACL has developed performance outcome measures to assess the effectiveness of OAA services in achieving the Act's objectives. These outcome measures focus on whether OAA services are helping older adults maintain their independence and remain in their communities:

• Nutrition outcomes: Percentage of home-delivered and congregate meal clients who report that OAA nutrition services help them eat healthier, stay in their homes, and avoid institutionalization. Measured through client surveys administered by states
• Transportation outcomes: Percentage of transportation clients who report that the service enables them to remain independent in their community, access medical appointments, and participate in social activities
• Caregiver outcomes: Percentage of family caregivers who report that Title III-E services help them provide care longer, reduce stress, and access community resources
• Health promotion outcomes: Completion rates for evidence-based disease prevention and health promotion programs under Title III-D, and self-reported health improvements by participants

ACL uses these performance outcome measures in its annual reports to Congress and in evaluating the overall effectiveness of the OAA investment. States are expected to incorporate outcome measures into their state plans and encourage AAAs to use outcome data for program improvement.

Title III-E Caregiver Survey

The National Family Caregiver Support Program (Title III-E) has additional data collection requirements beyond the standard NAPIS elements. ACL periodically administers a national caregiver survey through SUAs to assess the needs, experiences, and outcomes of family caregivers served by Title III-E. The survey collects data on:

• Caregiver demographics (age, relationship to care recipient, employment status)
• Care recipient characteristics (diagnosis, functional limitations, living arrangement)
• Types and hours of care provided by the family caregiver
• Impact of caregiving on the caregiver's physical health, emotional well-being, and financial status
• Services received and satisfaction with Title III-E services
• Self-reported outcomes — whether services helped the caregiver continue in the caregiving role

Title VI Tribal Reporting

Title VI tribal organizations report directly to ACL rather than through the state SUA system. Title VI reporting requirements include:

• Annual program report: Documentation of services delivered, participants served, meals provided, and other service units, submitted to ACL's Office for American Indian, Alaskan Native, and Native Hawaiian Programs
• Financial reporting: SF-425 Federal Financial Reports documenting expenditures of Title VI funds, typically required on an annual basis
• Single Audit: Tribal organizations expending $750,000 or more in federal awards must complete a Single Audit under 2 CFR 200 Subpart F

Title VI reporting is generally less complex than Title III SPR reporting due to the smaller scale of individual tribal programs. However, tribal organizations must still maintain accurate records of clients served, units of service, and expenditures. ACL provides technical assistance specific to Title VI reporting requirements.

Data Quality and Completeness

NAPIS data quality is a persistent challenge across the aging network, and ACL has increasingly emphasized data quality improvement as a priority. Common data quality issues include:

• Missing demographic data: High rates of "unknown" or missing responses for income, race/ethnicity, and other demographic fields. This undermines the ability to measure targeting effectiveness. Some states report "unknown" rates exceeding 20–30% for key fields
• Unduplicated counts: Ensuring that clients receiving services from multiple providers or at multiple sites are counted as one unduplicated individual in the state's data system. Duplicate counting inflates client numbers and distorts per-capita service metrics
• Inconsistent unit definitions: Providers within the same PSA counting service units differently — for example, some counting transportation by trip and others by mile, or some counting a half-hour homemaker visit as one unit and others counting it as 0.5 hours
• Timeliness: Delayed data entry resulting in incomplete or inaccurate snapshots at reporting deadlines. Many providers enter data in batches rather than in real time, creating gaps and backlogs

AAAs should establish data quality standards with their providers, conduct regular data audits to identify and correct errors, and provide ongoing training on data collection procedures. Some states have implemented data quality scorecards that rate AAAs on completeness, timeliness, and accuracy metrics.

Reporting Calendar and Deadlines

The OAA reporting calendar follows the federal fiscal year (October 1 through September 30). Key dates in the annual reporting cycle:

The cascading nature of OAA reporting — providers to AAAs, AAAs to SUAs, SUAs to ACL — means that delays at any level cascade upward. AAAs should build internal deadlines that give adequate time for data cleaning and review before their SUA submission deadline.

Reporting Best Practices

Based on common challenges in OAA reporting, these practices can improve data quality and reduce reporting burden:

• Train staff on the "why": Explain to frontline staff and volunteers why demographic data is collected (for reporting and program improvement, not gatekeeping) so they can communicate this clearly to participants
• Standardize unit definitions: Provide written guidance to all providers specifying exactly how to count each unit of service, with examples covering common edge cases
• Conduct regular data audits: Review provider data submissions at least quarterly for completeness, consistency, and accuracy. Address issues before they accumulate into systemic data quality problems
• Reduce "unknown" rates: Set internal targets for reducing missing or unknown responses on key demographic fields. Use multiple touchpoints to collect missing information rather than relying on a single intake form
• Reconcile data and financials: Ensure that reported service units are consistent with reported expenditures. If the cost per meal is dramatically different from the state average, investigate whether a data entry error exists