A queue is a policy document
If you want to know how Chicago decides which parkway trees get trimmed, don’t start with the tree. Start with the phone call. Since 311 launched in 1999, the Department of Streets and Sanitation’s Bureau of Forestry has trimmed trees on a reactive, request-based system: residents call, the request is logged, and non-emergency work is handled in the order it was received. That is the city’s own description of the program, and it is the single most important fact in this story.
It means the wait time for a trim is not set by the tree’s condition. It is set by who calls 311, how many of their neighbors call, and how far a crew has to drive to reach them. That is a distributional choice dressed up as a service model. And the receipts for what it produces are in a 2019 advisory from the City of Chicago Office of Inspector General, which is the document every alderman and every block club should have on the table.
What the OIG found
The October 2019 advisory (OIG File #19-0719) is blunt. Before 311 existed, DSS used a grid-based approach: crews were dispatched to trim all the trees in grid-sized sections of the city, which allowed a five-year rotating schedule. The OIG says that system was replaced by the reactive model, and that the city now relies on residents’ calls to identify trees in need of trimming rather than on a systematic, arboriculturally based approach.
The OIG also reached back to a 2009 review by the Monitor Group, a consulting firm the Bureau of Forestry hired to study the 311 program. According to the OIG’s account of that review, the Bureau spent 75% of its time addressing 311 requests, and 40% of parkway trees — roughly 206,000 — had not been trimmed in 10 or more years. The Monitor Group found that a grid-based approach would cut average crew travel time by 35% and average cost per trim by 60%, and would let crews complete 147% more trims per day.
Those are not small operational tweaks. They are the difference between a maintenance program and a complaint-response program. The city has more than 500,000 parkway trees, each maintained by the Bureau of Forestry, according to the department’s own forestry page. A reactive system means the condition of most of those trees is unknown to the city until someone picks up the phone.
The ward-level receipts
Here is where the queue becomes a map of who holds power and who waits. The OIG analyzed completed 311 tree trim requests and found wide variation between wards. Between January 1, 2011 and December 18, 2018, DSS completed 10,431 tree trim service requests in the 34th Ward — more than the 46th (1,808), 48th (3,020), and 49th (2,522) wards combined.
The wait times tell the same story. Between January 1, 2016 and December 18, 2018, the average time to completion for a tree trim request was 63.5 days in the 23rd Ward. In the 46th Ward it was 151.4 days. In the 43rd Ward, 139 days. In the 44th Ward, 133.4 days.
Read those numbers again. A resident in the 46th Ward waited, on average, more than twice as long as a resident in the 23rd Ward for the same city service. The OIG did not attribute that gap to tree condition, because the system does not measure tree condition. It measures requests. The variation is a function of call volume, crew routing, and whatever else shapes dispatch — and the OIG’s point is that a grid system would flatten it, because every tree would be trimmed on a cycle rather than on a complaint.
The seasonal squeeze
The backlog has a calendar built into it. The OIG reported that the Bureau of Forestry trims trees only from approximately June through December and spends the rest of the year removing trees. That means any non-emergency request that arrives after the trimming window closes waits until the next one opens. The OIG put it plainly: requests received after June 30, 2019, outside of tree emergencies, would not be addressed until 2020.
That is not a staffing surprise. It is a known structural constraint that the city has operated with for years. If you call 311 in January about a low-hanging branch that is not an emergency, you are not in a queue that moves in weeks. You are in a queue that moves in seasons.
What one ward office says now
The OIG advisory is from 2019, and the sources retrieved for this piece do not establish current citywide practice. But one ward office’s public description is worth reading as a labeled illustration, not a citywide finding. The 40th Ward office states on its website that the city no longer accepts individual tree trim requests via 311 and has moved to a grid system. The same page says the ward has roughly 15 grids and the city is committed to trimming 2-3 grids per year.
Do the arithmetic on that ward-office description: at 2-3 grids per year across roughly 15 grids, a full ward cycle spans multiple years. That is the ward office’s own account of the pace, and it is the kind of number residents should be putting to DSS directly. Is the grid system citywide? How are grids sequenced? What does a ward’s cycle actually look like on a map? Those are answerable questions, and the answers should be public.
The dataset is the thread to pull
You do not have to rely on anecdote about your block. The city publishes a 311 Service Requests – Tree Trim dataset, described on the city’s data page as covering all open tree trim requests and all requests completed between January 1, 2011 and December 2018. The OIG’s ward-level figures were built from that kind of record. Residents can use the same record to check their own block’s request history — when requests were filed, when they were closed, and whether they were labeled duplicates.
That is the practical move. Pull your address. Pull your block. Compare what you find to what your neighbors were told. If the record shows a request sitting open for months while a ward across town cleared its queue in weeks, you have a document, not a complaint.
Who has the power to fix it
The OIG addressed its advisory to DSS Commissioner John Tully and copied the mayor’s chief of staff, the chief equity officer, and the chief risk officer. The recommendation was specific: review the 2009 Monitor Group report and take the necessary steps to optimize the use of city resources and serve residents more equitably. The OIG did not order a fix. It named the office with the power to make one.
What the sources retrieved here do not show is DSS’s response to that 2019 advisory. That is the open question, and it is the one to put to the commissioner’s office and to your alderman: what changed after the letter, and what does the trimming schedule look like in your ward this year? The queue is not weather. It is a decision. Ask for the document that shows who decided.
FAQ
Can I still request a tree trim through 311?
The 40th Ward office states that the city no longer accepts individual tree trim requests via 311 and has moved to a grid system. Because that is one ward office’s description, confirm current practice with DSS or your own ward office before relying on it.
What counts as a tree emergency?
According to the 40th Ward office, the city considers a tree emergency to be a tree that is split, a branch that is broken but still dangling, or a tree that is uprooted. Trees touching or close to house or street light wires are not, by that description, emergencies. For emergencies, contact your ward office.
Where can I check my block’s trim history?
The city publishes a 311 Service Requests – Tree Trim dataset covering open requests and requests completed between January 1, 2011 and December 2018. Start there, and note that the retrieved dataset page describes that historical period rather than current data.
Why do wait times vary so much by ward?
The OIG found that the reactive, request-based system produces wide variation in completed requests and average days to completion across wards. The OIG attributed the variation to the request-based model itself and recommended a grid-based approach to reduce inequities.