Title is for any Steely Dan fans out there.
Seeing as this is a technical forum of sort, and I am sure most of us are in the IT field someway, shape, or form. I have been pondering something as my company takes on a new project/time/ticket tracking system. And it directly involves tracking time through a project/incident.
If you are tracking your time through the day for completing tasks (whether it be an Onsite task, Helpdesk task, Engineering, etc) would you count the time you spent downloading a large file, downloading updates, running a virus scan, etc towards your time in a ticket?
There are two sides being heard. One that feels it is simple... You track time for working, not waiting. The other arguement is you track the time from start to finish of a ticket with no stopping the time (as long as something is still happening with the incident).
For example, we have a reimage process for computers. It is extremely automated and typically takes about two hours, requiring nothing from the tech to do except start the computer. One tech thinks the client should be charged for two hours of work. Another tech feels only the actual amount of time (roughly 25-30 mins) worked should be charged. That 25 - 30 mins being starting the process, checking on it once in a while, and verifying it finished correctly.
Keeping in mind this is not time tracked to bill the client. The client has already paid for services. This is simply to track a techs actual work done throughout a day.
Any thoughts?
Seeing as this is a technical forum of sort, and I am sure most of us are in the IT field someway, shape, or form. I have been pondering something as my company takes on a new project/time/ticket tracking system. And it directly involves tracking time through a project/incident.
If you are tracking your time through the day for completing tasks (whether it be an Onsite task, Helpdesk task, Engineering, etc) would you count the time you spent downloading a large file, downloading updates, running a virus scan, etc towards your time in a ticket?
There are two sides being heard. One that feels it is simple... You track time for working, not waiting. The other arguement is you track the time from start to finish of a ticket with no stopping the time (as long as something is still happening with the incident).
For example, we have a reimage process for computers. It is extremely automated and typically takes about two hours, requiring nothing from the tech to do except start the computer. One tech thinks the client should be charged for two hours of work. Another tech feels only the actual amount of time (roughly 25-30 mins) worked should be charged. That 25 - 30 mins being starting the process, checking on it once in a while, and verifying it finished correctly.
Keeping in mind this is not time tracked to bill the client. The client has already paid for services. This is simply to track a techs actual work done throughout a day.
Any thoughts?