Thanks for sharing - like everyone's pointed out this is helpful info.
lisacawley4201963 wrote:
We use both Date of Hire and Termination Date but struggle with the Leave of Absence folks. How should you handle the person who's only gone for a month or so. If you leave the termination date blank when they come back you have a series of open timesheets that you don't know whether or not they should have been posted time. We can use the calendar to take them out of capacity and allocation but that doesn't tie to timesheets. If they mistakenly open a timesheet while they were out and cancel they can show up on the Missing timesheet report.
We have the same problem with our fixed bid where they are a fixed bid price and don't log time while they are off shore, but are hourly when they are onshore and this can change month over month.
Any recommendations?
We have the same problem here whenever someone goes on any sort of leave, departs the company but later comes back (which happens occasionally with external contractors and summer students / co-ops) or if someone changes roles. Currently for timesheets within these 'gap periods,' we either sweep them under the rug and pretend they're not there, or as Kevin suggests ask staff to submit timesheets ahead of time to an 'overhead' project we've created. Neither is a great solution though. It's an administrative headache - especially for things like maternity leave where we're essentially asking someone to submit a year's worth of timesheets at once (which further requires up to open up a year's worth of time periods ahead of time.) If anyone misses a timesheet within that span we either have to wait for them to return to work and then hound them, get our Clarity admins to fill it out, or just leave them unsubmitted, which affects and clutters up our RMs' "missing timesheets" stats and tracking.
It would be great if a future release had additional time fields that could be used to exclude timesheet created for certain resources, in addition to the current "start" and "stop" fields, is what I'm getting it :)