Skip to main content

SDLA Compliance Resource

Reconcile CALPADS School-Program Data with CARS Before Related Submissions Close

An operational guide for aligning Title I Schoolwide Program and Targeted Assistance School status across the Consolidated Application and Reporting System, local records, and CALPADS before certification deadlines collide.

  • CALPADS
  • Federal Programs
Date(s)At each applicable CARS release; reconcile before the CARS form closes and before CALPADS EOY 1 certification
Applies toLEAs receiving Title I, Part A funds and reporting Schoolwide Program or Targeted Assistance School participation

In Plain Language: CARS—the Consolidated Application and Reporting System—tells CDE which Title I schools are funded and which are authorized to operate a Schoolwide Program (SWP). CALPADS uses the certified CARS status. If the systems disagree, CALPADS may treat a school as a Targeted Assistance School (TAS), expect pupil-level Program 122 records, produce fatal errors, and block EOY 1 certification.

Why this matters

SWP and TAS are different reporting models. An SWP school generally does not submit individual Title I Program 122 records. A TAS school must submit those records for pupils receiving Title I services. The school’s local plan, board approval, CARS certification, SIS setup, CALPADS records, and certification reports must describe the same reality.

Joint ownership

Program authority: Title I/federal-programs lead. CARS owner: CARS user and LEA User Administrator. CALPADS owner: CALPADS administrator. Local source owners: SIS/program staff and school leadership. Governance evidence: board-approved SWP plan or other required authorization.

The authoritative chain

1 · Local decisionConfirm Title I funding, program model, eligibility, and required board approval.
2 · CARS certificationCertify School Allocations and, for SWP, the Notification of Authorization form.
3 · State transferCertified SWP status is populated from CARS into CALPADS on the state schedule.
4 · CALPADS reportingVerify school status and submit TAS Program 122 records only when required.
5 · CertificationReview Reports 5.1, 5.2, and 5.3 and resolve differences before EOY 1.

Reconciliation workflow

  1. Before the CARS windowInventory every Title I school.Record CDS code, allocation, local SWP/TAS decision, board authorization, effective year, and program contact.
  2. During CARS data entryCertify the related forms in sequence.Complete the applicable Title I School Allocations form, then the Notification of Authorization of Schoolwide Program form for approved SWP schools.
  3. After CARS certificationVerify the state handoff.Allow for the published population schedule, then confirm CALPADS reflects the certified SWP status; save screenshots or exports from both systems.
  4. Before EOY 1Reconcile pupil-level reporting.For TAS schools, compare the service roster and SIS to Program Code 122 records. For SWP schools, investigate unexpected Program 122 expectations or records.
  5. Before each system closesResolve the responsible source.Correct local authorization, CARS certification, SIS records, or CALPADS submissions according to which fact is wrong; do not wait for the later system’s deadline.

If the data do not reconcile

MismatchLikely checkResolution
Local records say SWP; CALPADS says TASBoard authorization, School Allocations certification, SWP Notification certification, CDS code, academic year, and nightly transfer timing.Correct or certify CARS when its window permits; document the state handoff and verify CALPADS afterward.
CARS says TAS; SIS has no Program 122 pupilsTitle I service roster, school program model, local program coding, and extract rules.Program owner determines the correct pupils; SIS owner creates accurate records; CALPADS owner submits and verifies them.
CERT097 or related fatal errorsSchool SWP/TAS status and missing TAS Program 122 records.Resolve the authoritative status or missing pupil records, post the correction, regenerate the revision, and rerun reports.
School absent or wrong in a formCDS/OPUS status, CARS form applicability, allocation setup, and LEA selection.Contact the appropriate CDE program or ConApp Support Desk; do not fabricate a local workaround.

Where to find the CARS forms

Use the CARS Data Collection Forms Calendar to see each release, form, submission window, certification deadline, amendment window, and final close date. Use the CARS program page for login, user guidance, training, and current-year form instructions. Do not reuse dates from a prior cycle.

Evidence to retain

  • Title I school inventory, CDS codes, SWP/TAS determinations, and governing-board authorization.
  • Certified CARS School Allocations and SWP Notification forms with dates and user.
  • Before-and-after CARS and CALPADS status evidence.
  • TAS pupil service roster, SIS Program 122 records, upload results, and Reports 5.1–5.3.
  • Error-resolution log identifying the authoritative source, owner, correction, and verified posted state.
  • Certified ConApp, signed Certification of Assurances, and retained local file.

Official guidance and help

Source review completed August 30, 2026. Verify current CARS forms and dates, CALPADS deadlines, local Title I authorization, and the posted state in both systems before acting.