in reply to Timesheets: What are they good for?

we do it in my company for accountability and to bill clients. Everyone in the company telecommutes so it's important for the suits to keep tabs on how we spend our days. 15 minute intervals. Our system is divided into client-project-task-activity. It's actually a cool system, I wrote it as my first job for the company :) Activity is stuff like ('other','development','correspondence','meeting','template coding',...). The rest are pretty self explanatory I think. Accuracy isn't per se verified, the important thing is that we get the job done.

There's an internal company project for research that I use to record the time I spend here :)
  • Comment on Re: Timesheets: What are they good for?

Replies are listed 'Best First'.
Re^2: Timesheets: What are they good for?
by steelrose (Scribe) on Apr 18, 2005 at 14:00 UTC
    My last job we filled out paper time sheets, and accountability/verification was very lax. The data was used for payroll only.

    My current job requires programmers to punch in and out. I haven't been here long enough to figure out what they're using the data for.

    If you give a man a fish he will eat for a day. If you teach a man to fish he will buy an ugly hat. If you talk about fish to a starving man, you're a consultant.
      Used for payroll? Lucky you!

      At my last job everybody was required to fill out a (badly done) html page which emailed the payroll person your hours. They were supposed to use that in paying us - yet the tech staff were all on a salary so no matter what we put it never matched up to what we got. The stupid thing is that we were even told not to "rock the boat" by putting our real hours down.

      So faced with the dodgy task of having to fill out a time sheet that nobody took of, with incorrect data .... I whipped up a script that submitted the timesheet for us.

      Weekly reports were a joke as well .... but that's a completely different story!