Initial Evaluation Process – Part B / IEP
Use this guide for the standard Part B Initial Evaluation process—from referral and assessment consent through the eligibility and participation outcome.
This article does not replace the specialized Part C / IFSP workflows. A child approaching age three from an IFSP uses Transition IFSP to IEP Meeting Procedure – Part C to Part B. New Part C referrals, IFSP transfers, and Regional Center/SIRAS dual-service onboarding begin with New, Transferring & Incoming IFSP Students.
An existing U.S.-based IEP is normally handled through the incoming-student and Plan Adoption workflows. A student who is still eligible but not participating does not receive another Initial Evaluation merely to restart services.
1. Choose the Correct Evaluation or Arrival Workflow
| Student situation | Use this workflow |
|---|---|
| No existing U.S.-based special education eligibility has been established, and the district is evaluating the student for Part B eligibility. | Continue with this Part B Initial Evaluation guide. |
| Child is receiving Part C / IFSP services and is approaching the age-three transition. | Use Transition IFSP to IEP Meeting Procedure – Part C to Part B. |
| New Part C referral, incoming IFSP transfer, or Regional Center/SIRAS dual-service arrangement. | Use New, Transferring & Incoming IFSP Students. |
| Student already has an existing U.S.-based IEP or prior CALPADS eligibility history. | Begin with New or Returning Students. Use Plan Adoption Guide when the district is adopting an existing plan. |
| A prior Initial Evaluation already occurred. | Use Starting Another Initial Evaluation After a Prior Evaluation to determine whether another Initial Evaluation is appropriate. |
| Student was referred from a private school or is parentally placed in a private-school setting. | Use this guide together with Private School Scenarios. |
2. Find, Transfer, or Create the SIRAS Record
Search before creating a new record
- Use Tools > Request Transfer to search for an existing record and avoid creating a duplicate.
- If a record exists elsewhere, follow Request Student Transfer Help.
- If no record exists, follow Creating a New Student Record.
- Update the district, school, demographic, contact, and provider information appropriate for the referral.
Review the existing record status
- Active: Determine whether the student is already eligible. A reevaluation, review, amendment, or incoming-plan workflow may be more appropriate than an Initial Evaluation.
- Inactive / Not Eligible: Preserve the inactive date and reason. That prior status may be required for SIRAS to allow a subsequent Initial Evaluation.
- New referral with no eligibility history: Keep the record status Pending while the Initial Evaluation is underway.
Removing an inactive reason or changing a previously reported status can prevent SIRAS from recognizing the correct subsequent-evaluation workflow.
Preserve the Special Education Initial Entry Start Date
If the student was previously found eligible and later exited, preserve the original Special Education Initial Entry Start Date. A later Initial Evaluation resets the new referral information; it does not replace the student's historical first-entry date.
See Starting Another Initial Evaluation After a Prior Evaluation for second Initial Evaluation rules.
SIS integration note
Districts using an SIS-to-SIRAS referral integration should complete the local SIS referral indicator before expecting the SIRAS record, transfer request, or demographic update. For example, Aeries districts may use the SPED Evaluating? indicator according to their district integration procedure.
3. Create the Initial Evaluation & Enter Referral Information
- Open the student's IEP Manager / Forms Manager.
- Create an Initial Evaluation meeting.
- Enter the referral date, referral source, permission-to-assess information, assessment-consent dates, and scheduling information in the meeting workflow.
- Do not enter the new referral and assessment-consent fields directly on the MIS Summary when SIRAS provides them through the Initial Evaluation meeting.
- Attach or document the referral, assessment plan, communications, consent records, and other supporting information according to district procedure.
A new referral ordinarily remains Pending. A student who was previously reported Not Eligible should ordinarily retain the existing inactive date and reason while staff create the subsequent Initial Evaluation.
If SIRAS will not allow the Initial Evaluation, review the student's existing eligibility/status history and see Starting Another Initial Evaluation After a Prior Evaluation. Contact SIRAS Support when the record history and requested meeting do not align.
4. Record Assessment Consent & Obtain an SSID
Parent Consent Date
When the district receives signed permission to assess, enter the date the permission was received as the Parent Consent Date. The record remains Pending while the evaluation is underway.
SSID requirement
The district should proceed with the evaluation even when an SSID has not yet been obtained. However, an SSID is required to submit the resulting special education records to CALPADS, so the district must obtain one through the applicable CALPADS enrollment process.
Coordinate with the district SIS/CALPADS staff so an SSID and the enrollment information needed for reporting are established in time to submit the evaluation outcome.
Enrollment specifics are governed by current CALPADS documentation and local district/SIS procedures. See:
5. Archive the Pending As Of MEET Record
Create the Pending As Of archive from the MIS Summary before the Initial Evaluation meeting occurs.
The archive functions as a record that the district has received assessment consent and has an Initial Evaluation still in progress.
When CALPADS specifically requires it
The Pending As Of MEET record is required when:
- the Parent Consent Date is before an applicable Fall 1 or EOY 1 census/reporting date; and
- the expected Initial Evaluation meeting will occur after that census/reporting date.
For Fall 1, this includes the case where consent is received before Census Day and the evaluation remains pending afterward. The record may also include the applicable meeting-delay information when the evaluation becomes late.
A Pending As Of record represents an evaluation that was still pending as of the reported date. Once the meeting has occurred, it is too late to create that historical pending condition through the normal workflow.
Related reporting-period guidance:
6. Document Consent Not Received or Later Rescinded
Parent never provides assessment consent
The open meeting event may be used to document communications, attempted contacts, notices, and the actual field history. When the Initial Evaluation will not proceed:
- complete the notes and attach the appropriate supporting documentation;
- close the meeting as not completed using Force Finalize or Abandon a Meeting;
- make the record Inactive using the applicable SIRAS initial-evaluation / no-evaluation reason; and
- follow When Students Leave or Stop Participating – Inactive for the status procedure.
Assessment consent was received and later rescinded
If the Parent Consent Date was entered but the parent later withdraws assessment consent before the evaluation is completed:
- document the withdrawal and all related communications in the meeting event;
- change the permission-to-assess indicator to reflect that consent is no longer available;
- force finalize / abandon the meeting after documentation is complete;
- make the record Inactive using the applicable initial-evaluation / no-evaluation reason;
- clear the Parent Consent Date from the MIS Summary; and
- remove any Pending As Of MEET record that was submitted to CALPADS.
Mark the SIRAS Pending As Of archive Do Not Report and remove the corresponding MEET record from CALPADS so the statewide record does not continue to show an assessment-consent promise that was withdrawn.
7. Manage the Timeline, Meeting & Delay Reason
The district generally has 60 calendar days from the Parent Consent Date to complete the Part B Initial Evaluation, subject to the applicable rules and exceptions.
Before the meeting
- Monitor the Parent Consent Date, expected meeting date, and Pending As Of archive.
- If the meeting becomes late, enter the appropriate Meeting Delay code and label.
- Preserve supporting documentation when the reason is not self-evident.
- Do not replace the original meeting date with a continuation date merely to make the timeline appear compliant.
At the meeting
- Document the evaluation type as MEET [10] Part B Initial Evaluation.
- Record the eligibility outcome and the parent's response accurately.
- Use Plan Effective Date, Service Start Date & CALPADS SERV Reporting for plan/service date concepts.
- Use Parent Response – Definitions when selecting the response to the proposed eligibility and plan.
For current statewide delay codes and reporting combinations, consult the current CALPADS System Documentation and Special Education File Submission Scenarios.
8. Choose the Correct Initial Evaluation Outcome
The Part B Initial Evaluation has five primary SIRAS/CALPADS outcome paths. Preserve both the code and the label whenever a coded value is documented.
A. Eligible & Participating
Use this outcome when the team finds the student eligible, the parent accepts the initial provision of special education and the plan, and participation will begin.
- SWDS [1] Eligible and Participating
- MEET [10] Part B Initial Evaluation
- Evaluation Outcome [20] Eligible
- PLAN and SERV are reported when the plan has been approved.
- The SWDS effective date is typically the meeting date when the parent agrees that day; when approval occurs later, use the later parent-agreement date.
B. Eligible – Future Plan or Participation Expected
Use this outcome when the student is eligible, but the plan or participation will not begin yet—for example, approval remains pending or the student is expected to begin at a known future school date.
- SWDS [2] Eligible, Not Participating
- NONPART [12] Eligible - No Education Plan Currently (Future Plan Expected)
- MEET [10] Part B Initial Evaluation
- Evaluation Outcome [20] Eligible
- No PLAN or SERV is reported until the applicable plan/participation event occurs.
When the parent later approves the plan or the future participation begins, SIRAS reports the new SWDS [1] Eligible and Participating status and the applicable PLAN/SERV records. The original Initial Evaluation MEET does not need to be duplicated.
C. Eligible – Parent Declined FAPE
Use this outcome when the parent accepts the eligibility determination but declines the offered FAPE/services.
- SWDS [2] Eligible, Not Participating
- NONPART [11] Eligible - No Education Plan (Parent Declined FAPE)
- MEET [10] Part B Initial Evaluation
- Evaluation Outcome [20] Eligible
- No PLAN or SERV is reported for the declined offer.
If the family later wants to discuss beginning services, do not create another Initial Evaluation. Use Starting Another Initial Evaluation After a Prior Evaluation.
D. Not Eligible – Did Not Qualify
Use this outcome when the Initial Evaluation is completed and the team determines the student does not meet eligibility requirements.
- SWDS [4] Not Eligible
- NONPART [21] Not Eligible based on Initial Evaluation (DNQ)
- MEET [10] Part B Initial Evaluation
- Evaluation Outcome [25] Not Eligible
- No PLAN or SERV is reported.
Parent disagreement or an Independent Educational Evaluation does not automatically mean staff should reset the referral and open another Initial Evaluation. Use IEE Independent Educational Evaluation Help and Starting Another Initial Evaluation After a Prior Evaluation.
E. Not Eligible – Parent Does Not Accept Eligibility / Initial Provision
Use this outcome when the team finds the student eligible, but the parent does not accept the eligibility or does not consent to the initial provision of special education and related services in the manner represented by this outcome.
- SWDS [4] Not Eligible
- NONPART [27] Not Eligible - No Consent for Eligibility
- MEET [10] Part B Initial Evaluation
- Evaluation Outcome [25] Not Eligible
- No PLAN or SERV is reported.
9. Finalize & Review CALPADS Reporting
- Preview the complete meeting document and verify the referral, assessment, eligibility, parent-response, plan, service, and date information.
- Confirm the selected outcome matches what occurred in the field.
- Finalize the meeting using the normal workflow. See Finalizing a Meeting.
- Review the archived transaction on the MIS Summary.
- Confirm that SIRAS created only the applicable SWDS, MEET, PLAN, and SERV records.
- Resolve CALPADS validation errors by correcting the source data and resending the transaction rather than changing the historical story.
MEET is reported for a completed evaluation. PLAN and SERV exist only when an eligible plan is approved. The SWDS status and NONPART reason depend on the eligibility and participation outcome.
See Initial Evaluation Reporting for additional reporting review.
10. Part B Initial Evaluation Checklist
- ☐ Confirm this is a standard Part B Initial Evaluation, not IFSP onboarding, Part C-to-B transition, Plan Adoption, or service re-entry for a student who remains eligible.
- ☐ Search for an existing SIRAS record before creating a new one.
- ☐ Preserve valid inactive history and the Special Education Initial Entry Start Date.
- ☐ Create the Initial Evaluation and enter the referral/consent information in the meeting workflow.
- ☐ Enter the Parent Consent Date when signed assessment consent is received.
- ☐ Coordinate with SIS/CALPADS staff to obtain an SSID without delaying the evaluation.
- ☐ Create the Pending As Of MEET archive before the meeting.
- ☐ If consent is never received or is rescinded, document the process, abandon the meeting, clear the Parent Consent Date, and reverse any Pending As Of reporting.
- ☐ Monitor the 60-day timeline and use the correct Meeting Delay code and label when applicable.
- ☐ Preview the completed meeting document before finalizing.
- ☐ Select the exact eligibility/participation outcome and preserve every code with its label.
- ☐ Review the resulting SWDS, MEET, PLAN, and SERV records after finalization.

