I think we might want to hear more requirements in order to understand
what you're trying to achieve, but one other idea to consider would be
seeing if your IT department uses a "ticketing" system for service
calls. I don't have huge familiarity with those systems, but they do
allow you to open a ticket (service request), track the time it takes
to close the request, and then builds stats on performance. Some of the
programs will allow you to automate ticket creation for recurring
events.

The main purpose would be using the system to track records requests
and you can always route a ticket, so tickets for charge outs would go
into a bucket for charge outs. If you mislaid a box, you could open a
ticket keeping track of the fact that you're looking for something. 

Just a thought...



Patrick Cunningham, CRM
[log in to unmask]

"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
Benjamin Franklin, Historical Review of Pennsylvania, 1759

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance