|
?:reviewBody
|
-
Wisconsin Democrats such as U.S. Rep. Mark Pocan say they believe Republican Gov. Scott Walker will run again for president, even though his 2016 candidacy was short lived . And Walker, eying a run for a third term as governor in 2018, continues to stake out positions that draw praise from conservatives around the country, such as aiming to make Wisconsin the first state to drug test Medicaid recipients. Walker even touts his record as Milwaukee County executive, the job he held previously. He did so in a June 5, 2017 interview with Jerry Bader , a conservative radio talk show host in Green Bay, saying: Eight years in a row we pushed through budgets that did not increase the tax levy from the previous year. It’s true that Walker never proposed to increase the levy -- the total amount of property taxes collected -- and that he tried, with vetoes, to stave off levy increases approved by the County Board of Supervisors. But saying he pushed through budgets suggests he was successful, when in fact he largely was not: In eight of Walker’s nine years as county executive, the levy increased. Let’s take a look. Walker’s evidence Walker proposed nine county budgets, for 2003 through 2011, before taking office as governor in January 2011. Working with a left-leaning County Board, typically there was a tug-of-war in which Walker tended toward lower property taxes and less spending, while the board would aim for more. Often there were Walker vetoes and veto overrides by the board. To back Walker’s claim, his staff pointed us to figures from the Milwaukee County budget archive . For his first two budgets, for 2003 and 2004, Walker proposed a property tax levy lower than what the County Board had adopted the previous year. But for both budgets, the County Board adopted levies higher than what Walker proposed. Ultimately, the levy rose in 2003 and dropped in 2004. Then a routine developed: 1. Walker would propose for his new budget a levy that was the same amount as the previous year’s levy. 2. The County Board would override Walker vetoes and adopt a budget that included a levy higher than what Walker proposed. 3. Walker would use that increased levy as his proposed levy for the next year’s budget. For example: Walker’s proposed levy of $225.9 million for 2006 was exactly the same as the levy that the County Board had adopted for 2005. But the levy that the board approved for 2006 was higher -- $232.6 million. And that was the levy Walker then made in his budget proposal for 2007. Here are the figures for the county budgets during Walker’s tenure: Year Recommended property tax levy and change up or down from previous adopted levy Adopted property tax levy $ and change up or down from previous adopted levy 2002 218.7,734,713 2003 218,708,524 ↓ 219,494.183 ↑ 2004 219,425,702 ↓ 219,436.418 ↓ 2005 219.416,093 ↓ 225,883,651 ↑ 2006 225,883,651 -- 232,592,517 ↑ 2007 232,592,517 -- 241,047,846 ↑ 2008 $241,047,846 -- $249,889,950 ↑ 2009 $249,889,950 -- $257,637,284 ↑ 2010 $257,637,284 -- $263,264,740 ↑ 2011 $262,264,740 -- $269,554,701 ↑ As we noted, Walker frequently used his veto in an attempt to freeze the property tax levy. For example, he vetoed all of the increase in tax levy spending that the County Board added in the 2011 budget. But the board overrode the vetoes . Our rating Walker says that when he was Milwaukee County executive, eight years in a row we pushed through budgets that did not increase the tax levy from the previous year. It was actually nine straight years that Walker proposed budgets that did not increase the levy -- the total amount of property taxes collected. But, to say he pushed through budgets that did not increase the levy is wrong. In eight of the nine years, the budgets adopted by the County Board -- over Walker’s vetoes -- raised the levy. And each year, Walker would use that increased levy as his proposal for the next year’s budget. For a statement that contains only an element of truth, we rate Walker’s claim Mostly False.
(en)
|
![[This page as RDF]](http://data.gesis.org/claimskg/static/rdf-icon.gif){kind=icon}