[msu_ops] 312 table scratches
Thanh Pham
tpham at kutztown.edu
Wed Apr 5 10:04:00 EDT 2006
Hi everyone,
The 312 tables have been reported as scratched on Monday at the far end of
the room (by the closet). The damage is extensive and I was having
difficulty targeting the users and it also reinforced another very important
issue about rounds, openings and closings. It's essential that rooms are
checked on rounds; that is, if a room has been empty and the event is almost
over, lock it up and start filling in a "no show" form (if you don't know
where this is, it's in the cabinets next to Di's desk). Closing and locking
a room may prevent unauthorized usage.
Is this a big deal? If the President was using 312 scheduled from 8-4 but
left early at noon and an unauthorized person used the room and created
those scratches on the tables. Is this fair to charge the President for
something he didn't do? I look at this as our responsibility to make sure we
keep the operations of our building as a big priority. Opening a room is far
more important than almost any task we ask of you. A good example is on a
manager report where a round can't be executed because they're busy setting
up a room for that night. This is a prime example of them doing what's most
important "now". So, yes, it is a big deal and a big part of our jobs.
Especially with Spring upon everyone, we need to focus until we finish and
summer will be here before we know it! For the most part, everyone does do
the closing and rounds, but our consistency for our entire staff can be
better especially considering the varying amounts of experience our staff
possess. It is something special to be part of a crew like this, but we also
need to work together to finish together. Thanks,
Thanh Pham
Student Union and Commuter Services
Kutztown University of Pennsylvania
274 McFarland Student Union
http://msu.kutztown.edu
ph. 610.683.4866 fx. 610.683.4723
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.kutztown.edu/pipermail/msu_ops/attachments/20060405/72d5f142/attachment.html
More information about the msu_ops
mailing list