Petition update

Petition Update: Please Read Important Update on the Fairfax School Board

Lauren Shupp

Jul 20, 2019 — 

The Fairfax County School Board is meeting on Monday, July 22, to discuss proposed changes to Policy 8130.7.  This change is a cause for alarm.  It is the first major, direct step towards removing Great Falls schools from the Langley pyramid  [drawing new school boundaries without community input.]. This will affect every school and neighborhood in Fairfax County 

This is the change we have worried about.  We need you to show up on July 22 with your friends and neighbors and let the school board know we are watching, what you do matters to us, and we demand input.

Policy 8130 determines how and why local school boundaries are adjusted.  Per school board member Pat Hynes, they are preparing for some "seismic" boundary changes, especially targeting our area. They will use this policy as their guide and claim their hands are tied if we do not like their boundary changes that happen in the future.  

The proposed new policy for boundary changes removes the following criteria for consideration of boundary changes. In other words, they will be able to change boundaries without considering:

  • the overall impact on students and families
  • operating costs 
  • matching resources to needs
  • improving operating efficiency
  • the impact on neighborhoods
  • busing costs
  • considering school feeder alignments
  • long-term costs and
  • INSTRUCTIONAL EFFECTIVENESS.

So, what's left?

Here is the New Considerations in the New Boundary Policy which is their 1ststep in implementing the OneFairfax Policy.

  • “Socioeconomic and or racial composition of students in affected schools”
  • “The geographic location of affected schools in relationship to the surrounding student population”
  • “The safety of walking and busing routes”
  • “Operational efficiency to include long-range capital plans and busing costs”

“When Boundary changes are being considered by the School Board, changes shall not be restricted by boundaries of individual schools, administrative area, zip codes, or magisterial districts”.

Each successive policy has taken further steps to eliminate public hearings and community involvement but push forward the Onefairfax Policy.  The new proposed policy further erodes their requirements to hold public hearings or tell our community about "expedited boundary changes."  If they had their way, they wouldn't tell us about anything at all. Most of the current school board members are retiring, so they won't even be around to hear about it.

Let's not let our voices be eroded any further.

Please help make sure that the School Board knows that we value instructional effectiveness for our children and a community voice in these issues.  

WHAT CAN YOU DO?

  • Join neighbors at the July 22 meeting, (Monday, July 22, 2019

Gatehouse Administration Center I, 8115 Gatehouse Road, Room 1600, Falls Church, VA, 5 p.m.and bring a friend

  • Send an email to let your board members know that this policy should not be adopted: 
    Karen.KeysGamarra@fcps.edu

Ryan.McElveen@fcps.edu

ilryong.moon@fcps.edu

 Jane.Strauss@fcps.edu

  • Plan to vote in this upcoming election on November 5, 2019.
  • Join us in this fight at onegreatfalls.org and subscribe for updates
  • Change the Board not our Boundaries

Policy Page that shows draft

https://go.boarddocs.com/vsba/fairfax/Board.nsf/files/BDZRXX6E892C/$file/20190711_Draft_Policy8130.pdf

Onefairfax Policy

ttps://www.fairfaxcounty.gov/topics/one-fairfax

Sincerely, 

Laura Timmins

www.onegreatfalls.org


Keep fighting for people power!

Politicians and rich CEOs shouldn't make all the decisions. Today we ask you to help keep Change.org free and independent. Our job as a public benefit company is to help petitions like this one fight back and get heard. If everyone who saw this chipped in monthly we'd secure Change.org's future today. Help us hold the powerful to account. Can you spare a minute to become a member today?

I'll power Change with $5 monthlyPayment method

Discussion

Please enter a comment.

We were unable to post your comment. Please try again.