If there are any excel experts out there I could do with some help for a little project for work.

I've just had to purchase

You'd probably be best doing it with a database - do you have MS Access?

Then all you need is a table with things like "Tool ID", "Employee ID", date and time out/in, and you can update that when things change...

Rob.

Yep - I'd go with Rob's suggestion of having a database to do this. Will work out better for you in the long run.

It should be relatively straight forward to create using a wizard with a recent version of Access. To me, it's probably easier to use and manage than a spreadsheet as well.

Steve

Might be more hassle than its worth. I have created databases and spreadsheets before. The creating is the easy part, its getting people to log in and out, and to keep the package updated thats the problem.

Your maybe better doing it longhand first as a trial run. Create an inventory of all the tools, and where they are kept. Laminate this and post it in the office, or some other obvious place.

Then have a log in/out sheet (one for each tool), where whoever uses the tool enters their name, job number, date and time of when they removed it from the store, then add a column for date of when the tool was returned, and a signiture of who returned it.

It might sound very simple, but in my last office, we where ISO quality assured, and this is the method we used for logging equipment in and out. (equipment was up to

Your maybe better doing it longhand first as a trial run. Create an inventory of all the tools' date=' and where they are kept. Laminate this and post it in the office, or some other obvious place.

Then have a log in/out sheet (one for each tool), where whoever uses the tool enters their name, job number, date and time of when they removed it from the store, then add a column for date of when the tool was returned, and a signiture of who returned it.

[/quote']

I'd agree with that one. Without implementing all sorts of complicated measures, anyone could pretend to be anyone else when signing stuff in or out using a database. If you have a paper-and-ink log in a ringbinder or whatever, then the personing signing stuff in and out has to do just that - sign. Having a written signature against expensive stuff gives better traceability, and tends to help jog the memory of the person signing it out when it comes to bringing it back. As regards stopping people just waltzing off with things (not that I'm saying anyone at your place would!), there's not a lot that any log (electronic or otherwise) can really do about that...

I agree with everyone above, there isn't really any benefit to computerising such records. It's also easier for the Techs to physically sign which means they are more likely to do it each time rather than simply not bothering to update the spreadsheet/database. Also good point raised above that should a problem arise a person can't really dispute his signature, as opposed to claiming that the database is wrong or has been fraudently updated by someone else.

and you don't get greasy fingerprints on your keyboard :-)