Hi,

We're currently updating our Time Tracking Object Model, and have to decide if we continue to re-scale any percentages that do not add up to 100%.  Values for some individuals can often be as low as 10% and we don't want costs being over-inflated on projects and applications.

- Does any one else correct their data in this way?

- Do you use a threshold, say 80%+ which can be corrected?

- we currently have default assumption allocations that we apply to the unaccounted for balance on some individuals - but not everyone.

We as a rule do not normally build the model to allow for bad data and always aim to correct the raw data at source.

We have a report that tells us who is not totaling 100% and chase up individuals to confirm - but this can take a while to get a response, so this keeps the money flowing in the meantime - if we leave it to get stuck in the model it can be a considerable amount missing from the reporting. 

I was just wondering how others deal with this issue?

HI Martyn,

We use Time Tracking data as well and do face similar issues. However, as a best practice guideline and to encourage the right behavior we do not correct the data in the way you mentioned as we prefer getting it done at source.

You are right that it can take time to chase up people and is sometimes futile doing it retrospectively. Hence, what we are currently working on is to show on the reports itself on the Unallocation %. Since these reports will have wide-spread visibility across various stakeholders, it has already started to change the behavior in people. 

Regards

Suresh

Hi Martyn, just to echo what Suresh said, we don't correct the data either, we let the Operational Managers and Finance Leads see the data issues for themselves this helps to encourage the right behaviors in their areas. It is in their interest to make sure that individuals are filling out their time sheets correctly. Over time, the quality of your data will improve.

Cheers,

Francis

Thanks @Suresh Sawlani and @Francis Chinkwande, glad to hear its not just us that has the problem. Sounds like highlighting the missing data in the reports is the way to go.  It will put a spotlight on the problem and create the necessary pressure 'from above' to get the data right at source.   

Thanks both

Martyn

Hi Martyn - We also created a customized Missing Hours report that can be used by our leaders to enforce better behavior. It is a simple report to create, but effective.

Thanks @Matt Erickson - a report I shall have

Martyn,

We do not scale raw timekeeping data.  We take it as is and send costs to projects in based on a percent to total for a cost center.  We expose hours coded to IT leaders so they can manage their people and have visibility. 

At one time we did spread costs evenly by individual and then the timekeeping quality became more of a factor.  Low hours coded sent high dollar/hr rates to some projects for example.  Finance became the focus instead of time coding so we do not do that any longer.

Regards,

Robert

Thank you @Robert Blackwell