Grumbledook, what did it actually take to get this in place? I'd love to get this kind of procedure and accountability implemented at my work - the resistance to it thus far has been rather odd.Quote:
Originally Posted by GrumbleDook
Usually, it's either that the departmental budgets are too small to absorb this kind of damage-billing, and thus IT support's budget is used for it.
In other instances, the damage occurs during registration periods, when the departments refuse to take responsibility for the damage and theft that occurs.
While finance is well aware of the amount of money we waste on new keyboards, mice, etc, and have all the figures to support this, the SMT make all the right noises when this is brought up as an issue, but when push comes to shove, it's quietly dropped. I'm really not sure why, as it's undeniably a chronic waste of money, but the feeling seems to be that it's what the IT Support budget is for, so why bother shifting things around?
Any convincing points or leverage that you utilised to get this in place at your site would be most useful!
(Aside from the cost issue, it's horribly depressing/demoralizing for the team to have to replace items day after day, with the teaching staff standing idly by when damage occurs, knowing full well that the same mice will be gone within a week, again)