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 > Support Center - Administrators
Support Center - Administrators
print icon

Administrator / SEDS Coordinator Support Guide

This guide is a starting point for SELPA, district, school, and SEDS administrators. Use the sections below to find help by responsibility or workflow.

For page-by-page help with SIRAS menus and screens, see the SIRAS User Manual. Teachers and service providers should also see the Provider Support Guide.

New to SIRAS or taking on a new administrator role?
Start with Getting Started, Training & Office Hours. That section includes administrator orientation, SEDS Coordinator onboarding, live training, practice servers, office hours, current schedules, and ongoing communications.

Contents

1. Getting Started, Training & Office Hours

New to SIRAS, taking on an administrator or SEDS Coordinator role, or looking for training and live assistance? Start with these resources.

Administrator and SEDS Coordinator orientation

Training, practice servers, and live assistance

Use Article 380 for the current office-hour schedule.
Article 389 explains the available training and support paths. Article 380 owns the dates, times, meeting links, and schedule changes.

Stay current after onboarding

2. Role, Calendar & Ongoing Responsibilities

Use these resources to organize recurring administrator and SEDS Coordinator work.

4. Meetings, Plans & Archived Transactions

Meeting and parent-response workflows

Archived reporting transactions

New event and correction are different workflows.
Create a new archive for a later real event or newly reportable information. When an existing transaction sent bad data, correct Current as needed and correct the archived transaction that originally reported the error.

5. Preventive Compliance Monitoring & Projections

Use upcoming and future-looking tools to prevent missed timelines, then use overdue and reporting tools for investigation and correction.

Start with what is approaching.
Run Upcoming Next Annual/Triennial regularly and use an Overdue-As-Of projection for month-end, Census Day, school breaks, or June 30. Do not wait for CALPADS to identify the overdue population.
AudienceExpected monitoring
Providers and Case ManagersUpcoming meetings for assigned students; notify administrators of incorrect dates, missing responsibility, or scheduling barriers.
School administratorsWorkload by Case Manager/site; projected meetings as of local target dates.
District/SEDS administratorsDistrictwide projections, current and previous overdues, delay reasons, open meetings, and CALPADS reconciliation.
A monitoring list identifies records for review.
Confirm what happened in the field and whether the issue belongs in Current, Meeting, Archived, SIS, or CALPADS data before making a correction.

6. CALPADS Reporting & Error Resolution

Reporting cycle and certification

Validation, errors, and submission history

A correction should preserve the actual event history.
Verify the source event and the transaction that reported it before deleting, replacing, or resending CALPADS data.

7. DRDP, TOMS/ELPAC & PSTS Reporting

These reporting responsibilities use SIRAS but are separate from the CALPADS SWDS, MEET, PLAN, and SERV transaction process.

Reporting area Administrator responsibility and help
DRDP Coordinate DRDP ratings for applicable young children, complete and validate the SIRAS DRDP record, and submit the required data to DR Access.
TOMS / CAASPP / ELPAC Maintain statewide-assessment accommodations and designated supports in SIRAS, then use the applicable student-level API or batch-export workflow to update TOMS.
PSTS Identify eligible former students, coordinate survey outreach, record responses on the MIS Summary, and submit PSTS data to CALPADS.

8. User Accounts, Permissions & Access

Do not create a duplicate account for someone who already uses SIRAS in another district.
Use the user-account transfer process so the person retains one SIRAS identity.

10. Troubleshooting, Communications & Support

When contacting SIRAS Support:
Include the student’s SIRAS ID, what happened in the field, the workflow being attempted, relevant dates, and the exact error or unexpected behavior. Do not include confidential student information in an unsecured email.

Return to the top

scroll to top icon