New Data Coordinator Training

New Data Coordinator Training
Roadmap for the School Year Welcome to the New Data Coordinator Training, Part 2: “Roadmap for the School Year” My name is <presenter name and title>. Also co-conducting this training session with me is <ask presenter 2 to say name and title>. During this training session, please keep in mind that extraneous noise, such as shuffling paper, carries over the speaker phone, so put your phone on mute if necessary. Also, please DO NOT put your phone on HOLD as many phone systems carry background music, which is very disruptive. If necessary, hang up and then call back in, rather than use HOLD. Feel free to ask questions (directly) at any time. When you do, please identify yourself so we know who’s speaking. You can also post your questions in the chat box. ============= Presenter Notes: Documents to Share Flash #48: Error List: SINF 0213, 0216 DataQuest: (OPTIONAL depending on time) Confidentiality Agreement CALPADS Timelines: July 1, 2012 Copyright © 2010, FCMAT/California School Information Services

Agenda Introductions Objectives State Reporting Changes
CALPADS Roadmap Lessons Learned Successful LEA Practices Resources and Support Here is the agenda for this session. Data Management - Roadmap for the School Year, v1.1,

Introductions Name Local Educational Agency Title/Job Responsibilities
Now let’s do introductions, so as I go down the list of name in the participants list, we would like you to introduce yourself and cover the bullets shown on this slide. Data Management - Roadmap for the School Year, v1.1,

Objectives Understanding of : Changes in state reporting for 2012-2013
Data reporting calendar for Lessons learned from Consequences for not meeting reporting requirements Best practices for meeting reporting requirements The objectives for this training session are that you will have an understanding of (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Changes in State Reporting 2012-2013
So let’s begin with changes in state reporting for … Data Management - Roadmap for the School Year, v1.1,

State Reporting Changes
California Longitudinal Pupil Achievement Data System (CALPADS) California Teacher Integrated Data Education System (CALTIDES) California Basic Education Data System-Online Reporting Application (CBEDS-ORA) Online Public Update for Schools-County-District-School (OPUS-CDS) Assessment and Accountability School Accountability Report Card (SARC) These are the state reporting systems whose changes we will cover the next couple of slides (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

CALPADS Fall 1, Fall 2, and Spring 1 For CALPADS Fall 1, Fall 2, and Spring the follow changes apply this year. Data Management - Roadmap for the School Year, v1.1,

CALPADS Data Management - Roadmap for the School Year, v1.1,

CALTIDES Implementation cancelled due to budget cuts New legislation for similar system is pending CBEDS-ORA OPUS-CDS Funding for CALTIDES was cut in the budget. New legislation will be required for development of the system. It is expected to have the same or similar functionality, but will likely have a new name. For purposes of discussion, we will continue to refer to Statewide Educator Tracking System as CALTIDES. For CBEDS-ORA the following changes will apply (share out form and review highlighted areas). Also, a section has been removed from the form that collected data that will now be collected via ASAM. There are no changes for OPUS-CDS. Data Management - Roadmap for the School Year, v1.1,

Assessment and Accountability Assessment and Accountability data will be transferred to CALPADS this year (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Assessment and Accountability The CDE will analyze results from the answer documents and compare to data in CALPADS to determine potential problem areas. Overall, this will be implemented over multiple years and eventually will be done entirely through CALPADS. Data Management - Roadmap for the School Year, v1.1,

School Accountability Report Card Required for all schools Required components Available at no cost via Ed-Data system The SARC will be moved to the Ed-Data system this year, with November being the targeted implementation date. Data Management - Roadmap for the School Year, v1.1,

Data Management - Roadmap for the School Year, v1.1, 20111031
So now let’s review what you will be doing this year. Data Management - Roadmap for the School Year, v1.1,

CALPADS Roadmap 2012 Census Day Certification Deadline Throughout Year July August September General Maintain SSIDs Resolve Anomalies Retrieve Direct Certification Files Data Mgmt Team Planning Review CFS/Code Changes Perform Security Audit Create local DM calendar Train Local Users Fall 1 Oct 5, 11 Dec 14, 11 Exit Students Close NSLP Program Records Attend Refresher Training Get SSIDs for new students Exit No Show Students Fall 2 Jan 18, 12 Get SEIDs for new staff Coordinate w/ HR for HQT reporting Spring 1 Mar 1, 12 Mar 28, 12 EOY 1 N/A July 18, 12 EOY 2 EOY 3 EOY 4 Other Update OPUS-CDS On this and the next 3 slides we cover the reporting calendar for the year (casually cover the table text). Data Management - Roadmap for the School Year, v1.1,

Certify Level 1 And Level 2 by Dec 14
CALPADS Roadmap 2012 Certification Deadline Throughout Year October November December General Maintain SSIDs Resolve Anomalies Retrieve Direct Certification Files CAG Meeting Long Beach, CA Fall 1 Dec 14, 11 Submit SINF for all students Submit SPRG for students in GATE, Migrant Ed, Special Ed, NSLP Review Preliminary Reports Distribute Reports for Verification and Signature Make adjustments as needed Certify Level 1 And Level 2 by Dec 14 Fall 2 Jan 18, 12 Attend Training Review Master Schedule Review HQT Status Audit Required Elements Submit SDEM/SASS for all cert staff Submit CRSE/SCSE for courses/students Spring 1 Mar 28, 12 EOY 1 July 18, 12 EOY 2 EOY 3 EOY 4 Other CBEDS-ORA Data Due (casually cover the table text). Data Management - Roadmap for the School Year, v1.1,

CALPADS 2012-2013 Roadmap 2013 (casually cover the table text).
Certification Deadline Throughout Year January February March General Maintain SSIDs Resolve Anomalies Retrieve Direct Certification Files Fall 1 Dec 14, 11 Amendment Window open through Feb 22 Fall 2 Jan 18, 12 Certify Level 1 AND Level 2 By Jan 18 Amendment Window open through Feb 29 Spring 1 Mar 28, 12 Maintain student information Attend Training Update SINF w/ changes Review Preliminary Reports Certify Level 1 AND Level 2 by Mar 23 EOY 1 July 18, 12 Check with vendor for EOY updates EOY 2 EOY 3 EOY 4 Other SARC Due (casually cover the table text). Data Management - Roadmap for the School Year, v1.1,

Certify Level 1 AND Level 2
CALPADS Roadmap 2013 Certification Deadline Throughout Year April-May Jun-Jul Jul-Aug General Maintain SSIDs Resolve Anomalies Retrieve Direct Certification Files Spring 1 Mar 28, 12 Keep student info up-to-date Final Amendment Apr 18 EOY 1 July 18, 12 Submit CRSC/SCSC for 7-12 students* Review preliminary reports | Distribute Reports for Verification and Signature Certify Level 1 AND Level 2 Final Amendment Aug 15 EOY 2 Maintain student program records Submit SPRG for all students EOY 3 Maintain truancy and disciplinary records Submit SDIS for 7-12 students* EOY 4 Submit SWAV for eligible students Other (casually cover the table text). Data Management - Roadmap for the School Year, v1.1,

2012-13 Summer Activities July - August
Close out records – Exits Verify and post exit dates, exit reasons and completions status for all students who left during the school year Matriculating students Use exit reason E230 for students completing the highest grade offered at any school Use completion status 480 for K-8 students Students transferring to private schools, out-of-state or out-of-country, use Transfer exit code So now we are going to cover what you should be working on now to prepare for CALPADS this year. We will begin with the student exits that must be updated in CALPADS (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Close out records – Exits Completers Use exit reason E230 with appropriate completion code Update the UC/CSU flag for all graduates Verify Initial 9th Grade Entry Year for all graduates Initial 9th Grade Entry Year is used for calculating the four-year completion rate Here is how you should handle your completer student exits in CALPADS (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Verify Records are Complete Verify that student information (SINF) records are posted for all students that enrolled after 10/6/2010 and exited during the school year Update English Language Acquisition Status (ELAS) for students whose status has changed since last year (TBD, RFEP) Update program membership End Dates for Free or Reduced Price Meal (NSLP) records in It is not just enrollments/exits from that need to be updated and completed. This also applies to the Student Information and Student Program data for your students (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Submission Activities
September – early October Prep Work Attend vendor training and CALPADS training Meet with Data Management Team Create and distribute Data Submission Calendar to key staff Train local staff Install vendor updates for local systems Make sure all documentation is up-to-date Check Expected Schools in OPUS-CDS Verify Charter School Reporting Status This is the prep work that you should be doing for reporting (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

September – early October Prep Work (cont) Obtain SSIDs for new students Update No Show Dropouts with N use exit code if known Obtain SEIDs for new staff (demographics) Exit staff who are no longer employed Add/Revoke CALPADS accounts for users Add/Update security roles for users (i.e., Free/Reduced Meals, Direct Certification) Verify/map codes (casually cover each bullet) Data Management - Roadmap for the School Year, v1.1,

September – early October Prep Work (cont) Use ODS reports to check graduate and dropout lists Resolve Anomalies (ERDs, MIDs, CCEs) Anomaly Rate for combined MIDs and CCEs must be 2.0% or less for Fall 1 certification Be a good CALPADS citizen – Resolve anomalies in a timely manner Update exit codes if no information is available Analyze causes of anomalies to identify problems with local practices Train Users on best practices for assigning SSIDs This is the prep work that needs to be done to ensure that your anomalies are below 2%. (casually cover each bullet) Data Management - Roadmap for the School Year, v1.1,

September – early October Prep Work (cont) Complete Data Population Fall 1 Update student demographic changes Update program eligibility Ensure Initial 9th Grade Entry Year for all high school students Ensure Initial US enrollment date for ELs and students born outside of the US Complete Data Population Fall 2 Update demographic/job class/assignment changes Increment staff years of service After schedule is set - update course-section attributes For Fall 1 and Fall 2, this is the critical prep work that needs to be completed by early October (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines October – November 2012
Data Submissions – Fall 1 Information Day – October 3, 2012 Fall 2 snapshots available – October 4, 2012 If regular enrollment updates have been submitted to reflect enrollment changes (entries and exits) – NO SENR is required Submit Student Information (SINF) for all students enrolled on information day Effective date MUST be on or after July 1, 2012 and on or before information day Between October and November, this is the Fall 1 data submission work that needs to done (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Data Submissions – Fall 1 (cont) Submit Student Programs (SPRG) for all students eligible and/or participating in NSLP, GATE, Migrant Ed, & Special Ed Between October and November, this is the Fall 1 data submission work that needs to done (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Certification Reports Review – Fall 1 Certification Deadline: December ?, 2012 Analyze and resolve fatal certification errors Review preliminary reports and make corrections as needed Distribute reports to data stewards for verification and signatures Certify Level 1 and Level 2 Print reports for records And once the data submission work is done, this is the process to follow to certify your Fall 1 data (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Data Submissions – Fall 2 Information Day – October 3, 2012* Fall 2 snapshots available – October 4, 2012 Submit and post Staff Demographics (SDEM) for all certificated staff employed on information day* Submit and post Staff Assignments (SASS) for all certificated staff Full replacement Strategies for LEAs with multiple users submitting data Between October and November, this is the Fall 2 data submission work that needs to done (casually cover each bullet). * Plus 30 days for year-round schools that are off-track on information day Data Management - Roadmap for the School Year, v1.1,

Data Submissions – Fall 2 (cont) Submit and post Course Section (CRSE) for all courses offered on information day* Submit and post Student Course Section (SCSE) for all students enrolled on information day* (casually cover each bullet). * Plus 30 days for year-round schools that are off-track on information day Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines November 2012 – January 2013
Certification Reports Review – Fall 2 Certification Deadline: January ?, 2013 Analyze and resolve fatal certification errors Review preliminary reports and make corrections as needed Distribute reports to data stewards for verification and signatures Certify Level 1 and Level 2 Print reports for records And once the data submission work is done, this is the process to follow to certify your Fall 2 data (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines March 2013 Data Submission – Spring 1
Information Day – March 1, 2013 Spring 1 snapshots available - March 2, 2013 NO data submissions required if information is kept up-to-date in CALPADS Otherwise Submit SENR for new enrollments and exits Submit SINF for any new students or changes for continuously enrolled students Starting in March, this is the Spring 1 data submission work that needs to done (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines March 2013
Certification Reports Review – Spring 1 Certification Deadline: March ?, 2013 Analyze and resolve fatal certification errors Review preliminary reports and make corrections as needed Distribute reports to data stewards for verification and signatures Certify Level 1 and Level 2 Print reports for records And once the data submission work is done, this is the process to follow to certify your Spring 1 data (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines May – July 2013 Data Submissions – EOY
Collection Window: Academic Year Snapshot Reports Available – May ?, 2013 EOY 1: Course completion – 7-12 with exceptions Staff Demographics (SDEM) Course Sections (CRSC) Student Course Sections (SCSC) EOY 2: Program participation (SPRG) EOY 3: Student discipline (SDIS) EOY 4: Waivers (SWAV) Starting in May, these are the EOY data submissions that you will be doing (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Schools Which Need to Report EOY
Participants EOY 1 EOY 2 EOY 3 EOY 4 Crs Staff CTE Pgm Disc Waiv Sector Public Y Non-Public Private N Non-Public Nonsectarian School Instructional Level Pre-Kindergarten Elementary Intermediate/Mid/Jr. Y(1) High School K-12 School Y(2) Adult Education(7) Postsecondary Ungraded Participants EOY 1 EOY 2 EOY 3 EOY 4 Crs Staff CTE Pgm Disc Waiv School Type Traditional (non-educational options schools) Y Y(2) County Community N District Community Day Division of Juvenile Justice Juvenile Court Schools Continuation High Schools Opportunity Alternative Schools of Choice State Special Schools Home and Hospital Special Education Consortium Special Education Y(1) ROP/ROC(6) This table shows the schools that are expected to report data for the various EOY snapshots based on instructional level and school type. As you can see some schools are expected to report data for all EOY collections while others are expected to report some collections and others still are not expected to report any data at all. One reason the reporting rules vary is due to the grade level requirement for some of the collections. For example, because Waivers and Exemptions are limited to grades 10-12/US, schools without these grades will have nothing to report. Please note that Ed Options, Home/Hospital and SpecEd Consortium schools are expected to report the CTE portion of EOY1, but not the courses In general, most LEAs will have some data to report in EOY 2 (Program data) and in EOY 3 (Discipline data), and for that reason, our training will cover EOY 2 and 3 first. After a short Q&A, LEAs that have nothing to report for EOY1 and 4 will have an opportunity to leave the training session. Although an LEA may have nothing to report for a given snapshot, all LEAs must certify each submission, even if zero data is reported. (1) Students completing courses in grades 7-12 and US only (2) Only schools with students in grades and US only Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines May – July 2013 Data Submissions – EOY 1
Collection Window: Academic Year EOY 1: Course Completion – 7-12 Submit SDEM for all teachers reported in course completion Submit CRSC for all courses completed during the school year Submit SCSC for all courses completed during the school year For the EOY 1, this is the data that you need to submit (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Collection Window: Academic Year EOY 2: Program Participation (SPRG) Submit SPRG for programs students participated in during the school year For the EOY 2, this is the data that you need to submit (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Collection Window: Academic Year EOY 3: Student Discipline (SDIS) Submit SDIS for all Ed Code offenses and any truancies occurring during the school year For the EOY 3, this is the data that you need to submit (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Collection Window: Academic Year EOY 4: Waivers (SWAV) Submit SWAV for all 12th grade students requesting (CAHSEE) waivers during the school year For the EOY 4, this is the data that you need to submit (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

2012-13 Reporting Timelines May – July 2013
Certification Reports Review – EOY 1-4 Certification Deadline: July ?, 2013 Analyze and resolve fatal certification errors Review preliminary reports and make corrections as needed Distribute reports to data stewards for verification and signatures Certify Level 1 and Level 2 Print reports for records By July, this is the EOY 1-4 certification work that needs to be completed (casually cover each bullet). Data Management - Roadmap for the School Year, v1.1,

Lessons Learned We are now going to cover the lessons learned from last year with CALPADS reporting. Data Management - Roadmap for the School Year, v1.1,

Lessons Learned Attending training (and paying attention) will save you time in the long run Make sure your vendor software is up-to-date Verify your code sets every year Train your staff every year Review changes, common problems, shortcuts, critical dates Train every year at a minimum New Interpretations, processing rules, and “fixes” are implemented throughout the year Data Management - Roadmap for the School Year, v1.1,

Lessons Learned Keeping your data updated in CALPADS will save you frustration and saves time in the long run Things go wrong There are many single points of failure You may need a contingency plan CALPADS may not be available for last minute processing It may not even be your mistake Fall 1 – enrollment updates, making sure Student information records are always posted with new enrollments, date mismatches. If you keep your data updated throughout the year, no additional submissions are needed for spring To certify data, it must be complete for all the submission components and all schools. So there are many single points a failure. A school that has not exited all of their students causing MIDs may stop you from certifying Fall 1. Not having HQT status for all of your teachers will stop you from certifying Fall 2. Think about what were your biggest headaches the previous year and attack those early. If you are the sole person responsible for CALPADS submissions and certifications, what happens if you are out for whatever unforeseen reason? Who can step in? Do they have an account? Can they access reports? Statewide system – changes in someone else’s data can affect your status Data Management - Roadmap for the School Year, v1.1,

Lessons Learned Small changes can have a big impact
If you have to do a lot of data reconciliations for start date mismatches – you need to find out why and fix it Same thing for anomalies Sometimes it is the system’s fault Data does not changes on its own. There is a reason that dates don’t match. Some change has to take place to change a date. If people are changing dates locally that will affect CALPADS updates. Find out why the dates are being changed, train staff on the correct way to enter and maintain dates or put a process in to make sure the CALPADS dates are synchronized with local changes. The same holds true for anomalies. Look at local procedures. Do you need to update enrollment forms to gather more information? Is it a training problem for site staff. Getting the right SSID the first time can save hours of frustration fixing them later. Sometimes it is the system. Things go wrong, system fixes sometimes aren’t. Reports don’t work, network connections time out. Data Management - Roadmap for the School Year, v1.1,

Successful LEA Practices
We are now going to cover the Best Practices for completing your data reporting throughout the year. Successful LEA Practices Data Management - Roadmap for the School Year, v1.1,

Recognize that required reporting is an organizational effort, not an IT effort Have a functioning data management team Comprised of key staff members and data stewards Meet regularly to review requirements, timelines, responsibilities, status Establish, implement and refine local data management processes Have administrative support for data management Successful LEAs have shared responsibility for data management and reporting. The workload is distributed and coordinated. We have talked about the data management team concept, in the Best Practices project and in all of our other data management trainings. The data management team is the group responsible for establishing and implemented local data management practices, such as enrollment and exiting procedures. It is comprised of central office and site staff, data entry, technical, program and administrative staff. They are proactive and make sure they understand how their local systems work. They don’t need to make assumptions because they use the available resources such as user guides and online help to address any problems or issues. They have administrative support for their efforts. When issues arise, such as someone not getting all the data into the system correctly or in a timely manner, they are held accountable. Data Management - Roadmap for the School Year, v1.1,

Designate Data Stewards Data stewards are responsible for specific types or data and/or data elements, i.e. HR, Special Ed Identify System of Record for data elements Coordinate systems implementation and synchronization Participate in training opportunities Provide staff development for all involved in data collection, reporting and analysis Connect data with its use and impact on the LEA (performance indicators and fiscal implications, link to instructional programs and reporting requirements) Successful LEAs also: Data stewards are staff that are responsible for specific types of data or data elements. They have an in depth understanding the data they are responsible for, such as HQT and credentialing information. Staff are required to participate in training including opportunities such as local in-services, vendor, user groups, CALPADS, and CETPA training. When there are problems, there are efforts to evaluate the root cause. Is it a misunderstanding, a system limitation, lack of training, etc and determine options to address. Systems implementation They train users on how the data is used and the potential impact on their LEA or schools. They understand the data in their systems, including knowing when the data has errors. They are proactive and make sure they understand how their local systems work. They don’t need to make assumptions because they use the available resources such as user guides and online help to address any problems or issues. Data Management - Roadmap for the School Year, v1.1,

Establish a Support Structure Develop documentation and other support tools Customize and/or supplement vendor documentation Establish a yearly data management calendar Leverage software Reduce redundancies by linking data systems Limit entries to valid codes Require fields needed for reporting Use built-in help features Review forms to align with software There are many strategies that can be used to support the quality of your data. Successful LEAs have an established support structure for data collection and submission. This may include a local help desk, list of LEA contacts by data subject or content area, and regular meetings to discuss current issues and the solutions. Data Management - Roadmap for the School Year, v1.1,

Have a good understanding of data and requirements Know their data (and know when it’s wrong) Don't need to make assumptions or guess at the right answers Audit data regularly Analyze problems and make adjustments Continuous improvement process Have a backup plan Cross train staff Take advantage of available resources Successful LEAs also: They understand the data in their systems, including knowing when the data has errors. They are proactive and make sure they understand how their local systems work. They don’t need to make assumptions because they use the available resources such as user guides and online help to address any problems or issues. When there are problems, there are efforts to evaluate the root cause. Is it a misunderstanding, a system limitation, lack of training, etc and determine options to address. They have backup plans to address possible problems that may occur during the year, such as staff absences. Data Management - Roadmap for the School Year, v1.1,

Successful LEA Practices for CALPADS
Keep data up to date throughout the year Stay informed about changes Participate in training Review certification reports early in submission cycle Know how to use resources Develop sign-off procedures prior to certification Hold post-submission reviews You need to keep up to date on CALPADS be informed about changing requirements. We encourage you to register for the CALPADS listserv (more about how to do this later) and to review any new or changed requirements well before the submission window so you have time to prepare for these changes. At the end of each submission window, your superintendent or charter school administrator will be asked to “certify” the data, meaning he or she will indicate that the data are complete and correct. Prior to that certification, it is best practice to follow defined procedures that ensure school site and program staff (e.g. Special education staff) review the data for their students and ensure it is accurate. Holding post-submission reviews with all staff members who contributed to the submission is a best practice because it allows you to capture lessons learned to help improve the next submission. These debriefs do not have to take a long time, but can be invaluable because they allow you to record these lessons learned while they are still fresh in your mind. You can then review these notes when it is time for the next submission so you can implement your improvement ideas. Another best practice we wanted to highlight today is the need to collaborate on requirements for and the selection and implementation of new systems. There is no one perfect system that all LEAs should purchase. Each system has its strengths and weaknesses. All systems need to be properly installed and maintained and most require training to ensure staff are ready to leverage the system’s strengths. If you have a defined, collaborative process that involves staff from all levels of your LEA (data entry clerks, site principals, program staff, etc.), the more likely you are to identify what you need a new system to be able to do and to plan for effective training and ongoing support. In addition, if you consider the total cost of ownership (the initial cost plus costs for training and ongoing support), at the time of purchase, you will be better able to identify the actual cost of any new systems. One of the very best ways to promote data quality is to use the data you have. The more you use it, the more vested staff get in ensuring its accuracy. We will be discussing data audits as a tool in this process in just a few minutes. Data Management - Roadmap for the School Year, v1.1,

Resources and Support Data Management - Roadmap for the School Year, v1.1,

Resources DataQuest Ed-Data
Ed-Data Educational Results Partnership (formerly Just for the Kids) Santa Clara County Office of Education Kidsdata.org Share Application – Dataquest – CDE Site Point out parent page Good source for community/grant writers looking for ethnicity/ test scores, etc. for your district Site most everyone has used…but this year I found ready-made graphs that were very useful. Select: Level: School Subject: Adequate Yearly Progress (AYP) School Name: Hamilton Meadow Park SUBMIT Select: Adequate Yearly Progress Report On the top right hand side select “School Chart” View charts for ELA and Math – Subgroups Percent At or Above Proficient Changing for upcoming year – look at subgroups that might be impacted next year when the Percent Proficient requirement increases Ed-Data – partnership between EdSource/FCMAT/Alameda County Office of Ed Great source for financial information about school district. We are a low wealth district in a county of basic aid districts – of 19 school district Expenditures per pupil vary for last year from $8000/student to $42,000/student – this data is very useful when trying to pass a parcel tax or bond Under Reports – SELECT DISTRICT Then on next page…. Select Report: Compare District Finances County: Marin District: Novato Unified On the next page – District Financial Comparison - check the box for “all districts in this county: Point out the different criteria at the bottom available for comparison Leave defaults and “Click to Compare” Review displayed chart. EdResults.org (formerly Just for the Kids California) has data available for all LEAs. It looks at data from a different view and thus even if you have a third party analysis system such as DataDirector of Edusoft – it can still provide valuable data. It is a small non-profit and Ken Sorey is the head. He will come to your district and training teachers, etc. in using the site…free of charge. Data Management - Roadmap for the School Year, v1.1, 53

Resources CETPA TechSets CSIS http://www.cetpa-k12.org/
CSIS Here are some other resources that can help you (casually cover the bullets). Data Management - Roadmap for the School Year, v1.1,

Training Training Opportunities
Q&A Basic courses K-12 State Reporting Overview for Administrators Advance courses Self-Paced Training Modules To register for the CALPADS trainings that CSIS provides you go to the URL on this slide (casually cover the training list). Data Management - Roadmap for the School Year, v1.1,

Training Training Supplement
Job Aides: Fall 1 Report Mapping Fall 2 Report Mapping Spring 1 Report Mapping EOY 1-4 Report Mapping The Job Aides listed here will assist you in understanding the how the counts were calculated in your Fall 1 & 2 certification reports. Data Management - Roadmap for the School Year, v1.1,

Support Tips & Strategies
Help Yourself First Reference key documents before contacting support: Quick Reference Guides (Help function of CALPADS) System documentation on CDE website: Check the Upcoming Events on the main CALPADS portal Subscribe to the CALPADS one-way listserv Attend Training or Use Self Paced Trainings Attend Q & As Join SIS user group and/or listserv When you or your data management team have questions on CALPADS, here are the resources that will assist you in finding the answer to your questions (casually cover the bullets). Data Management - Roadmap for the School Year, v1.1,

CALPADS Documentation
CALPADS File Specifications (CFS) CALPADS Code Sets CALPADS Valid Code Combinations CALPADS Error CBEDS Assignment/Course Code Mapping CALPADS SSID and Enrollment Procedures CALPADS User Manual with Glossary Data Management - Roadmap for the School Year, v1.1,

Please Complete Our Survey
We are now going to share our training survey. We use the data from this survey to guide any needed corrections or improvements needed for the training. After the survey we will take questions. Data Management - Roadmap for the School Year, v1.1,

New Data Coordinator Training

Similar presentations

Presentation on theme: "New Data Coordinator Training"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

New Data Coordinator Training

Similar presentations

Presentation on theme: "New Data Coordinator Training"— Presentation transcript:

Similar presentations

About project

Feedback