Shayla Pickett
My feedback
6 results found
-
52 votes
Thanks to everyone on the feedback on this. We are discussing.. A lot of this is policy change more than tech, so I’ll have to await internal decision. Depending on decision, we would have to adjust the L2 validation etc. Thanks again for all the great input on this one. John.
Shayla Pickett
supported this idea
·
An error occurred while saving the comment -
12 votesShayla Pickett
supported this idea
·
-
6 votesShayla Pickett
supported this idea
·
-
6 votesShayla Pickett
supported this idea
·
-
11 votesShayla Pickett
supported this idea
·
-
43 votes
This is a great concept. Not sure how we would execute, but I see the need for it. We’ll think about some options from a tech standpoint. Thanks.
Shayla Pickett
supported this idea
·
This is also a concern in our district. For years, we have stressed the importance of accurate record keeping and our main message has been that nothing should be "fudged" to make it work/be compliant. We have always maintained the rule to go by as, "If you feel you have to "fudge" it to make it work, then it's not being done correctly.
If a student withdraws from our district and our only knowledge is that the family is moving out of state and the student is not known to be continuing, we exit them with a ISM code (DPI definition- ISM: Interstate move. Move to another state within the country. Not known to be continuing). This code accurately reflects the student's withdrawal status from the district and the record reported to the state is accurate.
If the student enrolls in another WI school at a later date (or in the following school year) we are then expected to go into our systems and change our records to use a withdrawal code that reflects the district was aware at the time of the student's withdrawal, that they were moving to another WI school, and that the district was aware of district the student was transferring to. This is not accurate and the record reported to the state is not "technically" accurate.
This process does accurately track the student's withdrawal from our district or the time withdrawn from school, in between enrollments. It also leads us to going back in and altering already completed and accurate records.
In response to John Raub - for this situation the student didn't re-enroll in our district, but rather another WI public school. We then get a WISEdata error when the other school enrolls that student with a code saying they are enrolling from an in-state public school (since the student never ended up attending an out-of-state district).