Laserfiche WebLink
CC Work Session <br />Meeting Date: 10/13/2015 <br />Information <br />Title: <br />Discussion Regarding the Proposed 2016 Staffing Changes <br />Purpose/Background: <br />2.1. <br />The purpose of this discussion is to provide the City Council with an opportunity to address each of proposed <br />staffing changes effecting the upcoming budget. All of the proposed staffing changes have been proposed in order <br />to meet the strategic goals of the City. In addition, this discussion includes an immediate need in the Community <br />Development Department related to the current Permit Technician Assistant position, currently budgeted for 20 <br />hours per week. <br />Types of Changes and Current Policies <br />There are four types of proposed changes which will be explained in detail, including the associated budget impact, <br />services provided, and strategic imperatives that can be achieved as a result. This includes, additional hours to current <br />positions, new positions, reclassifications, and market rate adjustments. <br />The City's Personnel Policy, adopted in August 2014, and scheduled for updating and re -adoption, has policies in <br />place governing reclassifications and market rate adjustments. Staff would like to address any possible changes to <br />those policies in the coming months. The reclassifications and market rate adjustments planned for 2016 fall within <br />the current policies. Note, that previous iterations of the budget had a reclassification request for the Public <br />Information and Events Specialist. This reclassification request has been withdrawn due to the fact that this is a new <br />position and that was recently established in 2015. Staff would like to examine a policy in regard to the purpose and <br />frequency of reclassifications and market adjustments prior to recommending any change to this position. <br />The remaining proposed market rate adjustments for consideration this evening impact two groups: the City's <br />Paid -on-call Firefighters, and selected AFSCME employees under a wage study that was committed to during the <br />last round of negotiations for the 2015 - 2016 AFSCME contract. <br />Additional Hours - Current Need <br />Community Development Director Gladhill would like to provide the City Council with an update on his <br />Department's immediate need regarding additional hours now and continuing into the future due to current and <br />ongoing workload demands. He would like the City Council to consider approval for changing the current Permit <br />Technician Assistant to a full-time employee, taking action at the October 27, 2015 meeting. Within the proposed <br />2016 Budget, this position is proposed to be re-classified as a Permit (or Community Development) Technician, a <br />regular full-time employee. Staff recommends that the 2016 change in title follow the standard process. Increasing <br />the Permit Technician Assistant's hours to 40 hours per week for the remainder of 2015 will increase expenditures <br />by $13,511. This assumes an additional 560 hours with health insurance waived. The increase in expenditure is <br />offset by the increase in actual revenue from Building Permits. The increase in hours has already been factored into <br />the proposed 2016 Budget and has a net effect of an increase of $4,480 following other line item reductions. This <br />increase cost is also offset by additional revenues over and above the original forecasted levels for 2015. Permit <br />levels in all sectors are exceeding original expectations for 2015 and are outlined in the attached spreadsheet. <br />Additional Hours - 2016 Proposal <br />The IT Manager would like to increase the hours of its IT Support Tech in response to the increasing number and <br />complexities of technologies requested and utilized by City staff. Since 2011 the City has continued to add <br />technologies, but has actually reduced staff hours in the IT department. Without an increase in hours, staff <br />technology needs may be prioritized under larger projects or vice versa. Either scenario could cause delays to <br />requests from the public. <br />