[CANUFNET] Tree Maintenance Backlog

Wed Apr 13 13:27:03 EDT 2016

Hi Paul,

In Saskatoon we have a preventative maintenance program (cyclical pruning schedule) and try to attain a 7 year pruning cycle of our boulevard and park  trees.  We are on track with our boulevard/street trees where we visit them every 7-9 years but In our parks this cyclical maintenance is stretched out and we are not on target.

We take calls from the public and respond to emergency or high priority work asap and depending on the situation (weather events result in delays even for high priority work). Generally high priority or high risk situations are attended to very quickly and normally within hours of the call.

We have developed criteria to use for less urgent service requests and this helps determine whether they get added to our queue of work. Sometimes we don't respond to tree maintenance issues that can be left reasonably until the next pruning cycle.

I've attached a copy of the form our Tree Inspector uses when he investigates tree service requests. A copy of this form is left with the citizen and a copy is provided to our Senior Arborist that coordinates the reactive work schedule. We tell the public it can take until the end of the year before all service requests are completed and for removals it can take a year before we are able to remove stumps as this is a separate operation.

Regards,

Michelle Chartier
City of Saskatoon
Community Services, Parks Division
Superintendent - Urban Forestry/Pest Management
Ph: 306.975-2537  Fax: 306.975.3034

From: CANUFNET [mailto:canufnet-bounces at list.web.net] On Behalf Of Giroux, Paul
Sent: Wednesday, April 13, 2016 10:10 AM
To: canufnet at list.web.net
Subject: [CANUFNET] Tree Maintenance Backlog

Good afternoon,

Currently the City of Windsor's Forestry Division is experiencing an 'all time high' back log of Forestry services for both tree trimming and tree removals. This back log is about 6 years in the making, mostly as a response to the management of EAB (from 2003 to 2010'ish) and to deep cut's to our Forestry's Operating Budget over the years.

I have recently put together and presented to Council, a plan to reduce the back log and for a way to get back to Area Trims/Cycle Pruning through the use of both Operating and Enhanced Capital dollars. Currently our back log for tree removals and trimming is around 400 days or 12 to 18 months, depending on the activity and its associated risk rating. I am proposing to have this back log cleaned up by the end of 2017.gulp.

For one of our Councillors here in the City, this plan is not specific enough. He is enquiring what the 'new' waiting period will be, once I have established a 'return to preventative maintenance' through cycle pruning and other best management practices. Specifically, he would like to know the number of days or the waiting period for tree maintenance once the back log is completed and preventative maintenance is occurring (2018 and beyond).

My question to the group is, if you have a preventive maintenance program or even if you do not, what is your City/Municipalities current back log/waiting period (if any) for tree maintenance (tree trimming or removal only please). My assumption is that even with a preventative maintenance program in place, there will always be a manageable back log of tree services, not unlike any other City Service.

For those able to respond, thank you for your time.

Paul Giroux, RPF
City Forester/Manager of Forestry and Natural Areas
Parks Department
2450 McDougall Street, Windsor, ON  N8X 3N6
Office: 519.253.2300. ext. 2760.
Email: pgiroux at citywindsor.ca<mailto:pgiroux at citywindsor.ca>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.web.net/pipermail/canufnet/attachments/20160413/186c8f9f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Tree Inspection Form - May 12 2015 (4).doc
Type: application/msword
Size: 67584 bytes
Desc: Tree Inspection Form - May 12 2015 (4).doc
URL: <http://list.web.net/pipermail/canufnet/attachments/20160413/186c8f9f/attachment-0001.doc>