We are planning to enhance it further in our coming releases.
So, I am in the process of collecting inputs/suggestions from various sources.
As part of this effort, I have asked below question in LinkedIn.
What is the best way to handle Employee per hour rate in Time sheet application?
We are developing and selling web based time sheet application. Currently our application won't allow changing per-hour-rate of the employee. Because if we change the per-hour-rate, then it will affect the budget calculation of his previous projects.I am getting good answers for this questions. Find below some of them.
Suppose if I want to allow the feature for changing the rate, what is the best way to handle?
(I think this feature is required in some situations, such as employee promotion)
I am thinking various approaches.
1. Just overwrite the existing rate. But it will affect previous project budget calculations.
2. Store the employee rate for each project individually. i-e store rate - project lookup.
3. keep note of date on which the rate has changed. Use the previous rate or current rate based on the date. i-e store the rate -date lookup.
Which is best approach or give any other good suggestion.
I am still looking for more inputs from various users. Especially I am looking for suggestions/comments from our free Time Sheet Users and from the people who bought our earlier versions of our Time sheet.
As of now, we are planning to do below things.
- Store the "per hour Rate" of each employee in separate database table along with starting date and Ending date.
- And, while allocating the employees to an project, an option will be provided to overwrite the default "per hour rate" of the employee for the specific project.
- In Report page, actual budget will be calculated based on project specific rate if the default rate is over written, otherwise use the default rate corresponding to that particular date (i-e hours worked on which date)
It may add slight complexity to the code and flow. As we are planning to keep our Time Sheet Simple and powerful, I am still looking for better design to implement this feature effectively.
You can share your suggestions thro' the comments.
You can bookmark this blog for further reading, or you can subscribe to our blog feed.