You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > Support Center > CALPADS Reporting > MEET Component: Evaluation and Review Events
MEET Component: Evaluation and Review Events
print icon
MEET Component Reference Use this page to understand how SIRAS MEET fields describe evaluation and review events. When a Data Monitoring task sends you here, use this reference to interpret the component, then return to the task article to investigate or correct the record.

What Are You Trying to Understand?

What the MEET Component Represents

MEET preserves a reportable evaluation or review event. In the current SIRAS article, the principal MEET events are Initial Evaluations, Annual Plan Reviews, and Triennial Reevaluations.

Other Review is not a replacement MEET event. The current source article treats an Other Review as an amendment to an existing plan regardless of a secondary purpose; it does not replace the governing Initial Evaluation, Annual Plan Review, or Triennial Reevaluation history.

Depending on the event, review the applicable referral date, parent consent date, evaluation date, meeting/review date, meeting-delay code and label, evaluation outcome, and the Report Event Date stored in the archived transaction.

The archived MEET information should represent the actual completed event and should align with the associated meeting when the archive was created from IEP Manager.

Initial Evaluation

The MEET component establishes the completed Initial Evaluation, its timing information, and the applicable eligibility outcome.

An Initial Evaluation does not automatically require PLAN and SERV. If the student is found not eligible, the source article describes MEET with the applicable SWDS outcome and no PLAN/SERV. If the evaluation establishes eligibility and a participating plan, MEET can be accompanied by SWDS, PLAN, and SERV.

SIRAS Initial Evaluation MEET example

Initial Evaluation example retained from the prior MEET article.

SIRAS archived MEET transaction example

Use the archived transaction to review the reportable meeting event and dates.

For Initial Evaluation monitoring, return to Meeting Compliance Quick Actions, CALPADS 16.25 / DINC 2, Indicator 12 / DINC 3, or New Referral List Quick Actions as appropriate.

Annual Plan Review

The MEET component establishes the reportable Annual Plan Review event associated with the student's plan history. The source article describes an Annual Plan Review with unchanged participation status as MEET with PLAN and SERV, without duplicating an unchanged SWDS.

SIRAS Annual Plan Review MEET example

Annual Plan Review example retained from the prior MEET article.

For DINC 1/current Annual monitoring, use Meeting Compliance Quick Actions and CALPADS 16.21.

Triennial Reevaluation

The MEET component establishes the reevaluation event and applicable plan-review information. If the Triennial Reevaluation ends eligibility, the source article describes MEET with the applicable SWDS status change; PLAN and SERV depend on the actual outcome.

SIRAS Triennial Reevaluation MEET example

Triennial Reevaluation example retained from the prior MEET article.

For a Triennial that is currently overdue, use Meeting Compliance Quick Actions. For CALPADS-side DINC 1 monitoring use CALPADS 16.21. For a meeting held late that now needs reconciliation, use DINC 1 Previously Overdue Meetings.

MEET with Other Components

OutcomeTypical relationship retained from the current source article
Initial Evaluation finds student not eligibleMEET plus the applicable SWDS outcome; no PLAN or SERV.
Initial Evaluation establishes eligibility and participating planMEET with SWDS, PLAN, and SERV.
Annual Plan Review with unchanged participation statusMEET with PLAN and SERV; no duplicate unchanged SWDS.
Triennial Reevaluation ends eligibilityMEET with the applicable SWDS status change; PLAN and SERV depend on the actual outcome.
Evaluation or review reported without IEP ManagerManual archive containing the MEET and any other components required by the event.
SIRAS MEET fields and dates example

Review referral, consent, evaluation, meeting, delay, and outcome information together as applicable.

SIRAS MEET history example

Compare the archived MEET information with the associated meeting and actual event history.

Review and Correct a MEET Component

  1. Verify that the evaluation or review actually occurred.
  2. Confirm the correct event type and date.
  3. Review referral, consent, evaluation, delay, and outcome information as applicable.
  4. Open the archived transaction and compare it with the associated meeting.
  5. Correct the meeting when the finalized meeting document itself is wrong and an authorized correction is required.
  6. Correct the archive directly when the issue is limited to report-only historical fields.
  7. Return the transaction to Pending when it must be resubmitted and confirm CALPADS acceptance.
Do not use a monitoring label by itself as proof of what the MEET history should say. When SIRAS, CALPADS, or field information disagree, establish the actual event timeline first with Data Monitoring Help.

Common Data Monitoring Uses

Monitoring questionReturn to
DINC 1 Annual / Triennial461, 279, or 462
DINC 2 Initial Evaluation >60 days461 / 280
DINC 3 Part C-to-B / 3rd birthday295
New Referral / Initial Evaluation work queue467

Related references: Archived Transaction Components · Archived Transactions · Initial Evaluation Process · Archive for Reporting

Back to top

scroll to top icon