2026 A-F Reporting Update Log

The reports currently available in the OnDataSuite Accountability Section are considered Preliminary.

• Early Data: Results are based on both preliminary and final locally uploaded files and TEA methodology.
• Ongoing Refinement: Expect values to fluctuate as we refine our programmatic code and ingest wider datasets from across the state.
• Projections only: These reports are intended for district planning and should not be considered final state ratings.

Calculations are only as accurate as the data provided. Districts are responsible for ensuring all uploaded files are complete and formatted per the 2026 TEA Data File Specifications used in the current year calculations.

Verification Tool: Domain File Status Report
Before analyzing your Domain reports, you must check your Domain File Status Report. This internal audit tool will tell you:

• Which required files are missing.
• Which files contain formatting errors that prevent calculation.
• If a vendor file needs to be removed and replaced.

Resource:Domain File Status Report

As we begin this year, we utilize the first few weeks to confirm that system-wide files and our internal code are working in harmony.

• Daily/Weekly Patches: We will be pushing updates frequently to ensure the accuracy of each domain. Districts are encouraged to print a copy of their summary report prior to patch items going out to help determine if a given patch had any effect on your projected results.
• Tracking Changes: Refer to the Daily Status & Update Chart below this section for a log of all technical changes.
• Manual Refresh: If you need a posted update applied to your reports immediately, you may submit a ticket with the subject: “Please refresh my A-F System.”
• We will be post an impact level after each patch description to indicate how much of a potential effect the patch may make on the overall report [Low] | [Med] | [High]
  
  We provide impact levels to help you prioritize post-patch reviews. However, please consider these as general guidelines. A “Low” impact patch may behave differently in larger districts or in instances where underlying data upload issues exist. We recommend reviewing your specific reports following any [Med] or [High] rated updates.
• [Reload Required] = Y The updates have been applied to the next patch that is scheduled to go out during your next system refresh which is typically the evening of or the following morning.

Once your files are verified as “Clean” in the Status Report, perform a “Reasonableness Check” to ensure the numbers align with your expectations:

• The “Sense” Test: If you have 300 testers but only see 100 in the report, your uploaded files are likely incomplete or filtered incorrectly.
• Drill-Down: Use the student list features to verify numerators and denominators.
• Sample Size: We recommend validating one campus first to confirm the logic “makes sense” before auditing the entire district.

If you have completed the reasonableness check and still find a discrepancy, we rely on your feedback to help us refine the system. Please submit a support ticket including:

• Specific Examples: Provide Student Name/Local ID for those who should or should not be included.
• Target Area: Identify the specific Domain and component (e.g., Domain 1, CCMR) you are inquiring about.
• Visuals: Attach screenshots showing the total values or student-level lists in question.