Skip to main content

CALPADS error brief · IVR

IVR0034

Duplicate Record within File
Severity Fatal
Error type Input Validation
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

Duplicate Record within File based on Operational Key

Focus fields

Fields validated

22.04 Reporting LEA 22.06 SSID 22.09 Reporting SELPA 22.11 Special Education Status Effective Start Date

Recommended correction path

Suggested resolution

SWDS validation

Severity: Fatal   Type: Input Validation

Fields validated

  • 24.04 - Reporting LEA
  • 24.06 - SSID
  • 24.09 - Reporting SELPA
  • 24.13 - Special Education Meeting Date
  • 24.14 - Pending As Of Date

SWDS is effective-dated status history. Correct the authoritative status relationship; do not create a convenient annual snapshot or overwrite valid history merely to clear an error.

The SWDS operational key

Key field QuestionCommon duplicate source
22.04 Reporting LEAAre both rows owned by the same LEA?Merged exports
22.06 SSIDDo both rows identify the same student?Duplicate student joins
22.09 Reporting SELPAAre both rows under the same SELPA context?Repeated organizational mapping
22.11 Status Effective Start DateDo two records claim to begin on the same date?API retry or competing status rows

Do not delete the second row until its non-key differences are compared. It may be a true duplicate, an API retry, or evidence that two competing statuses were assigned the same effective date.

Recommended correction path

  1. 1

    Preserve the rejected row

    Capture submission ID, row number, Reporting LEA, SSID, Reporting SELPA, status date, status and reason.

  2. 2

    Identify the exact failed field or relationship

    Inspect the raw 13-column row before spreadsheet conversion or manual editing.

  3. 3

    Reconcile enrollment and identity

    Confirm SENR ownership, SSID, LEA and the student’s effective-dated special education history.

  4. 4

    Verify the authoritative source

    Use the special education system, eligibility documentation, enrollment history and current code definitions.

  5. 5

    Correct the source and mapping

    Repair the supported value or relationship in the originating system; never patch only the finished upload when the source remains wrong.

  6. 6

    Resubmit and inspect history

    Confirm acceptance and review neighboring SWDS, MEET and PLAN records for chronology or duplication effects.

Retained official CALPADS guidance

<style>.sdla-meet-guide{--sm-blue:#164f7a;--sm-sky:#eef7fc;--sm-gold:#a96500;--sm-gold-bg:#fff7df;--sm-green:#426b36;--sm-green-bg:#f1f8ed;--sm-purple:#76528f;--sm-purple-bg:#f6eff9;--sm-ink:#243746;--sm-line:#cfdae1;color:var(--sm-ink);line-height:1.65}.sdla-meet-guide *{box-sizing:border-box}.sdla-meet-guide .sdla-meet-timeline>li::before,.sdla-meet-guide .sdla-meet-steps>li::before{content:none!important;display:none!important}.sdla-meet-guide h2,.sdla-meet-guide h3{color:var(--sm-blue)}.sdla-meet-guide a{color:#075c91}.sdla-meet-guide .sdla-meet-impact,.sdla-meet-guide .sdla-meet-official,.sdla-meet-guide .sdla-meet-caution,.sdla-meet-guide .sdla-meet-related,.sdla-meet-guide .sdla-meet-disclaimer{margin:1.2rem 0;padding:1rem 1.15rem;border-left:5px solid;border-radius:0;box-shadow:none}.sdla-meet-guide .sdla-meet-impact,.sdla-meet-guide .sdla-meet-caution{border-color:var(--sm-gold);background:var(--sm-gold-bg)}.sdla-meet-guide .sdla-meet-official{border-color:#70b2d9;background:#f5fbfe}.sdla-meet-guide .sdla-meet-related{border-color:var(--sm-green);background:var(--sm-green-bg)}.sdla-meet-guide .sdla-meet-disclaimer{border-color:#8a98a3;background:#f3f5f6}.sdla-meet-guide .sdla-meet-fields{columns:2}.sdla-meet-guide .sdla-meet-timeline{display:grid;grid-template-columns:repeat(5,minmax(0,1fr));gap:0;padding:0;list-style:none;margin:1.2rem 0}.sdla-meet-guide .sdla-meet-timeline li{position:relative;padding:.3rem .55rem;text-align:center}.sdla-meet-guide .sdla-meet-timeline li:not(:last-child):after{content:"";position:absolute;top:1.2rem;right:-35%;bottom:auto;left:65%;width:auto;height:0;border:0;border-top:3px solid #70b2d9;background:transparent!important}.sdla-meet-guide .sdla-meet-node,.sdla-meet-guide .sdla-step-number{background:var(--sm-blue);color:#fff;font-weight:700;text-align:center;border-radius:50%}.sdla-meet-guide .sdla-meet-node{position:relative;z-index:1;display:block;width:2.4rem;height:2.4rem;line-height:2.4rem;margin:0 auto .5rem}.sdla-meet-guide .sdla-meet-timeline strong,.sdla-meet-guide .sdla-meet-timeline span{display:block}.sdla-meet-guide .sdla-meet-owners{display:grid;grid-template-columns:1fr 1fr;gap:.75rem;margin:1rem 0}.sdla-meet-guide .sdla-meet-card{padding:.9rem;border-top:6px solid var(--sm-purple);background:var(--sm-purple-bg)}.sdla-meet-guide .sdla-meet-card:nth-child(2){border-color:var(--sm-green);background:var(--sm-green-bg)}.sdla-meet-guide .sdla-meet-card h3{margin-top:0}.sdla-meet-guide .sdla-meet-steps{list-style:none;padding:0}.sdla-meet-guide .sdla-meet-steps li{position:relative;display:flex;gap:.9rem;padding:.85rem 0;border-bottom:1px solid var(--sm-line)}.sdla-meet-guide .sdla-meet-steps li:not(:last-child):after{content:"";position:absolute;top:2.85rem;right:auto;bottom:0;left:1rem;width:2px;height:auto;border:0;background:#cce3f0!important}.sdla-meet-guide .sdla-step-number{flex:0 0 2rem;height:2rem;line-height:2rem}.sdla-meet-guide .sdla-meet-steps h3{margin:0 0 .2rem;font-size:1.05rem}.sdla-meet-guide .sdla-meet-steps p{margin:0}.sdla-meet-guide .sdla-role-directory{columns:2}.sdla-meet-guide .sdla-role-directory li{break-inside:avoid;margin:.4rem 0}.sdla-meet-guide .uk-button-primary{background:var(--sm-blue)}@media(max-width:800px){.sdla-meet-guide .sdla-meet-timeline{grid-template-columns:1fr}.sdla-meet-guide .sdla-meet-timeline li{display:flex;gap:.7rem;text-align:left}.sdla-meet-guide .sdla-meet-timeline li:not(:last-child):after{top:2.7rem;right:auto;bottom:-.35rem;left:1.75rem;width:0;height:auto;border:0;border-left:3px solid #70b2d9;background:transparent!important}.sdla-meet-guide .sdla-meet-node{flex:0 0 2.4rem;margin:0}.sdla-meet-guide .sdla-meet-owners{grid-template-columns:1fr}}@media(max-width:560px){.sdla-meet-guide .sdla-meet-fields,.sdla-meet-guide .sdla-role-directory{columns:1}}</style><article class="sdla-meet-guide" aria-labelledby="ivr0034-guide-title"><aside class="sdla-meet-impact" aria-labelledby="ivr0034-guide-title"><h2 id="ivr0034-guide-title">Operational guide: MEET operational-key reconciliation</h2><p>Two records can appear identical to CALPADS even when they originated from different local rows. Determine whether the cause is a true duplicate, an incorrect date, or extract logic that generated the same operational key twice.</p></aside><section class="sdla-meet-official" aria-labelledby="ivr0034-rule-title"><h3 id="ivr0034-rule-title">Read the complete validation</h3><p><strong>CALPADS rule:</strong> Duplicate Record within File based on Operational Key</p><p><strong>Fields involved:</strong></p><ul class="sdla-meet-fields"><li>24.04 - Reporting LEA</li><li>24.06 - SSID</li><li>24.09 - Reporting SELPA</li><li>24.13 - Special Education Meeting Date</li><li>24.14 - Pending As Of Date</li></ul></section><section aria-labelledby="ivr0034-sequence-title"><h3 id="ivr0034-sequence-title">Read the event sequence</h3><ol class="sdla-meet-timeline" aria-label="MEET event sequence"><li><span class="sdla-meet-node" aria-hidden="true">1</span><div><strong>Identify</strong><span>Confirm the student and exact event.</span></div></li><li><span class="sdla-meet-node" aria-hidden="true">2</span><div><strong>Document</strong><span>Locate the authoritative record.</span></div></li><li><span class="sdla-meet-node" aria-hidden="true">3</span><div><strong>Reconcile</strong><span>Compare every validated field.</span></div></li><li><span class="sdla-meet-node" aria-hidden="true">4</span><div><strong>Correct</strong><span>Repair the owning system.</span></div></li><li><span class="sdla-meet-node" aria-hidden="true">5</span><div><strong>Verify</strong><span>Confirm chronology and downstream meaning.</span></div></li></ol></section><section class="sdla-meet-owners" aria-label="Correction ownership"><div class="sdla-meet-card"><h3>Primary participants for this error</h3><ul><li>CALPADS coordinator</li><li>Case manager</li><li>IEP/SEDS system owner</li><li>SIS, extract, integration, or vendor support</li></ul><button class="uk-button uk-button-primary" type="button" uk-toggle="target: #ivr0034-participants-modal">View the complete participant directory</button></div><div class="sdla-meet-card"><h3>Start with the authoritative record</h3><p>Confirm the complete local meeting history, submitted file, and CALPADS MEET history. Establish what occurred before deciding which system value should change.</p></div></section><section aria-labelledby="ivr0034-path-title"><h3 id="ivr0034-path-title">Recommended correction path</h3><ol class="sdla-meet-steps"><li><span class="sdla-step-number" aria-hidden="true">1</span><div><h3>Identify the exact event</h3><p>Match SSID, Reporting LEA, Reporting SELPA, academic year, evaluation type, plan-review indicator, and Meeting or Pending As Of Date.</p></div></li><li><span class="sdla-step-number" aria-hidden="true">2</span><div><h3>Reconstruct the chronology</h3><p>Compare referral, consent, pending, meeting, and outcome information as applicable; include prior and subsequent MEET records.</p></div></li><li><span class="sdla-step-number" aria-hidden="true">3</span><div><h3>Confirm the documented meaning</h3><p>Use authoritative program documentation and current CALPADS rules. Do not infer a date, outcome, review status, or delay reason solely from the error.</p></div></li><li><span class="sdla-step-number" aria-hidden="true">4</span><div><h3>Locate the true failure point</h3><p>Determine whether the issue belongs to documentation, IEP/SEDS entry, enrollment context, code mapping, extract logic, or an existing CALPADS record.</p></div></li><li><span class="sdla-step-number" aria-hidden="true">5</span><div><h3>Correct the owning system</h3><p>Use the authorized local process, regenerate the MEET record, and avoid a CALPADS-only edit that will be overwritten or misstate the event.</p></div></li><li><span class="sdla-step-number" aria-hidden="true">6</span><div><h3>Verify acceptance and meaning</h3><p>Confirm the complete MEET history, connected records, relevant monitoring reports, and whether the same workflow affected other students.</p></div></li></ol></section><aside class="sdla-meet-caution" aria-labelledby="ivr0034-caution-title"><h3 id="ivr0034-caution-title">Procedural accuracy check</h3><p>A value that clears IVR0034 is not necessarily the correct value. Confirm the underlying event, documentation, responsible team, and permitted reporting value before changing dates, outcomes, activity indicators, or delay codes.</p></aside><aside class="sdla-meet-related" aria-labelledby="ivr0034-related-title"><h3 id="ivr0034-related-title">Cross-record verification</h3><p>Review other MEET records with the same Reporting LEA, SSID, Reporting SELPA, Meeting Date, or Pending As Of Date.</p></aside><section class="sdla-meet-official" aria-labelledby="ivr0034-official-resolution-title"><h3 id="ivr0034-official-resolution-title">Official CALPADS guidance</h3><p>Understanding the Error: The Special Education Meetings (MEET) file submitted contains two records that CALPADS interprets as the same record. Both records have the same operational key: Reporting LEA, SSID, Reporting SELPA and Special Education Meeting Date, and Pending As Of Date. These are the fields that CALPADS uses to uniquely identify a record in the ODS. Therefore, there can&#x27;t be two records with the same unique identifiers.</p><p>Things to check for in submission: Verify that the fields listed in the Fields Validated column are correct in the submitted file.</p><p>Suggested Resolution:<br>1) Delete one of the duplicate records and resubmit the file.</p><p>OR</p><p>2) If file produced from local SES, contact vendor/technical resource to determine reason for duplicate record and to determine how to resolve the problem.</p></section><section aria-labelledby="ivr0034-close-title"><h3 id="ivr0034-close-title">Before closing the issue</h3><ul><li>Confirm IVR0034 no longer appears for the intended student and event.</li><li>Verify the accepted MEET values and chronology under the intended academic year.</li><li>Document the source evidence, responsible owner, correction location, and broader extract impact.</li><li>Confirm that the result is procedurally accurate—not merely technically accepted.</li></ul></section><p><a href="https://documentation.calpads.org/Troubleshooting/MEET/IVR0034/" target="_blank" rel="noopener noreferrer">Official IVR0034 troubleshooting page</a> &nbsp;|&nbsp; <a href="https://documentation.calpads.org/OnlineMaintenance/StudentDataMaintenance/StudentDetailsMEET/" target="_blank" rel="noopener noreferrer">MEET online-maintenance guidance</a> &nbsp;|&nbsp; <a href="https://documentation.calpads.org/Reports/Accountability/Report16.24_StudentswithDisabilities%E2%80%93MeetingsStudentList/" target="_blank" rel="noopener noreferrer">Report 16.24 — Meetings Student List</a></p><aside class="sdla-meet-disclaimer"><strong>Important:</strong> This SDLA operational guide does not replace IDEA, California special education requirements, CDE, CALPADS, SELPA, vendor, or local procedural guidance. Confirm documentation, ownership, and correction authority before changing student information.</aside><div id="ivr0034-participants-modal" class="uk-flex-top" uk-modal><div class="uk-modal-dialog uk-modal-body uk-margin-auto-vertical"><button class="uk-modal-close-default" type="button" uk-close aria-label="Close participant directory"></button><h2 class="uk-modal-title">MEET cross-team participant directory</h2><p>Engage the roles needed for the specific student, event, ownership question, or system issue.</p><ul class="uk-list uk-list-divider sdla-role-directory"><li class="sdla-meet-role sdla-role-calpads-coordinator"><!-- <a href="/job-descriptions/calpads-coordinator">CALPADS coordinator</a> --><span>CALPADS coordinator</span></li><li class="sdla-meet-role sdla-role-case-manager"><!-- <a href="/job-descriptions/case-manager">Case manager</a> --><span>Case manager</span></li><li class="sdla-meet-role sdla-role-school-psychologist-assessment"><!-- <a href="/job-descriptions/school-psychologist-assessment">School psychologist or assessment staff</a> --><span>School psychologist or assessment staff</span></li><li class="sdla-meet-role sdla-role-special-education-teacher"><!-- <a href="/job-descriptions/special-education-teacher">Special education teacher</a> --><span>Special education teacher</span></li><li class="sdla-meet-role sdla-role-school-site-administrator"><!-- <a href="/job-descriptions/school-site-administrator">School-site administrator</a> --><span>School-site administrator</span></li><li class="sdla-meet-role sdla-role-parent-engagement-procedural-support"><!-- <a href="/job-descriptions/parent-engagement-procedural-support">Parent-engagement or procedural-support staff</a> --><span>Parent-engagement or procedural-support staff</span></li><li class="sdla-meet-role sdla-role-district-special-education-administrator"><!-- <a href="/job-descriptions/district-special-education-administrator">District special education administrator</a> --><span>District special education administrator</span></li><li class="sdla-meet-role sdla-role-selpa-data-compliance"><!-- <a href="/job-descriptions/selpa-data-compliance">SELPA data or compliance staff</a> --><span>SELPA data or compliance staff</span></li><li class="sdla-meet-role sdla-role-registrar-enrollment"><!-- <a href="/job-descriptions/registrar-enrollment">Registrar or enrollment staff</a> --><span>Registrar or enrollment staff</span></li><li class="sdla-meet-role sdla-role-iep-seds-system-owner"><!-- <a href="/job-descriptions/iep-seds-system-owner">IEP/SEDS system owner</a> --><span>IEP/SEDS system owner</span></li><li class="sdla-meet-role sdla-role-sis-extract-integration-vendor"><!-- <a href="/job-descriptions/sis-extract-integration-vendor">SIS, extract, integration, or vendor support</a> --><span>SIS, extract, integration, or vendor support</span></li></ul></div></div></article>

Official references