My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2006/07/24
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2000-2009
>
2006
>
Agenda Packets - 2006/07/24
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:49:09 PM
Creation date
7/18/2018 5:07:58 PM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
7/24/2006
Supplemental fields
City Council Document Type
City Council Packets
Date
7/24/2006
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
286
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Mounds View City Council July 10, 2006 <br />Regular Meeting Page 18 <br /> <br />The vast majority of the positions, 90%, are at or slightly above market rate. He stated 1 <br />that Mounds View is very positive as far as the market is concerned and his 2 <br />recommendations will have very few monetary effects. 3 <br /> 4 <br />Mr. Laumeyer stated the firm is asking for acceptance of the report. He stated after approval, the 5 <br />firm would return to the Personnel Committee with specific recommendations and will then 6 <br />suggest some pay equity. 7 <br /> 8 <br />Mayor Marty asked about the sources of external data and why Forest Lake was removed. Mr. 9 <br />Lauymeyer stated that Forest Lake was included in error and the version handed out at the 10 <br />meeting without Forest Lake is correct. 11 <br /> 12 <br />Councilmember Thomas asked about the assumption of whether or not the pay system is 13 <br />appropriate. She stated she does not see it addressed in any of the material. Councilmember 14 <br />Flaherty stated that pay was discussed and it was not included in the report. Councilmember 15 <br />Thomas stated she would like the information. 16 <br /> 17 <br />Mr. Laumeyer noted that it was decided to defer such information to the Personnel Committee. 18 <br /> 19 <br />Councilmember Stigney asked about the title changes and the criteria on which they are based. 20 <br />Mr. Laumeyer stated that one was because one employee needs a re-classification due to duties. 21 <br />He stated that in the workforce, classifications are constantly updated. 22 <br /> 23 <br />Councilmember Stigney asked “who” is using such terms and where the new words come from. 24 <br />Mr. Laumeyer said the words come from research and surveys done with other cities. He 25 <br />suggested the titles changes would be more comparable to other positions with the same duties. 26 <br /> 27 <br />Councilmember Stigney asked about the Community Development Director and stated he did not 28 <br />see any changes. Mr. Laumeyer replied that it was a typo. 29 <br /> 30 <br />Councilmember Stigney asked for documentation supporting the recommendations. Mr. 31 <br />Laumeyer stated they would be available at the Personnel Committee meeting. 32 <br /> 33 <br />Councilmember Stigney stated he would like to make a motion indicating receipt, not 34 <br />acceptance, of the report with referral to the HR Committee. Mayor Marty stated it would come 35 <br />back to the Council for approval. 36 <br /> 37 <br />MOTION/SECOND: STIGNEY/FLAHERTY. To waive the reading and adopt Resolution 38 <br />6858, Indicating Receipt of the Salary Compensation Study and Referring it to the Human 39 <br />Resource Committee. 40 <br /> 41 <br />Mayor Marty asked about Desaree Crane, and the language regarding the “Assistant To” title. He 42 <br />stated he would like to keep the classification of “Assistant To the City Clerk/City 43 <br />Administrator” title and that some of the duties should be taken on by Administrator Ulrich 44 <br />rather than by the “Assistant To.” 45
The URL can be used to link to this page
Your browser does not support the video tag.