I would like to be able to limit leave requests to only allow leave to be requested against specific Projects / Tasks / Pay Types that the administrator assigns to each user. We have had situations where employees who had intended to request & take unpaid leave, requested the time against the wrong Pay Type and were inadvertently paid for time they were out of the office.

In addition, it would be *EXTREMELY* helpful if managers could export the leave calendar to Outlook, or if the system administrator could export the leave calendar as an Outlook data file and distribute to all team leads and project managers on a periodic basis.

The current User Interface (UI) is outdated (relative to current web technologies). In addition, there are many areas that could benefit from behavior improvements. For example, when an approver receives a notification, it should not matter whether they're a backup or a primary when they go into their approvals. It should show all pending approvals (maybe with color coding if you want to differentiate them). As it is, if a backup approver doesn't know they're a backup, they may not think to click the radio button and it will appear that the product isn't working correctly. There are other areas similar where the default actions are not intuitive. It is not necessary to remove functionality, but there are ways to change the defaults and modify the UI to be more friendly.

It would be great if project managers (defined by the project owner and backup owner fields) could receive an email notification when a user that is assigned to their project has had their leave requests approved (if the leave will be in a timeframe that would affect the project). So, if User A requests 16 hours of time off for Christmas Eve and Christmas Day, and they are assigned to two projects during that time, the project managers for those two projects would get an email notification saying that User A has had leave approved for Christmas Eve and Christmas Day. This is in the middle of their assignment on their respective projects. Maybe even some sort of calculation about duration change required or overtime needed to complete the assignment on time, given that the user will be out on leave.

Let's make timesheet approvals and controlling costs a fun and engaging experience for our managers. Roll out a sharp-looking web 2.0-style page of mini-stats about projects or their employee's use of time that they can use to better manage their domains. Make it customizable by the user, and offer up a whole bunch of default examples that just "work" out of the box based on what's already there in their subordinates' historical figures.

I don't have any supervisors that have taken the initiative to figure out how to program the custom reports in the current reporting menu, so we have to spoon-feed them and force it upon them almost. An attractive, at-a-glance overview at login would have the software selling itself!

How about a screen where supervisors could review and approve expenses by looking at a grid of thumbnails with detail text below them. Click to expand for more detail. Also, allow us to run reports on expenses submitted that look more image oriented. There's currently no way to do this efficiently to bill customers back for expenses incurred without manually going back and retrieving the images at billing time. Also: check out an app on Google marketplace called "Expensify". It's an expense management tool that actually generates IRS-compliant receipts below a certain threshold so that employees don't have to bother with scanning and uploading every taxi cab receipt for 3 dollars and forty-two cents. I watched the CEO of my company compiling his timesheet receipts the other day and thought...BOY this could be done better!

PS: the "upload records" button right next to the "upload receipt images" button is totally confusing by the way take it off please!)

Why is the interface reminding permanently in red in the leave tab of the menu bar that a holiday request has been rejected, without giving the possiblity to hide this once it has been aknowledge. I had user complaints about it.

Somehow it should be like for timesheets: when a timesheet is rejected, it appears in red in the menu bar. Then user correct it, resubmit it – everything solved – case closed – it is not visible anymore unless you check the timesheet history.

A similar logic could be applied here: holidays submitted, not approved, user acknowledges – case closed (no need for a permanent reminder of that frustration :-) ).