Thanks for this great system. It is a very good start into
the right direction.
It would be useful for many organizations to have
another level of authorization setup, that has to
approve a timesheet before it can be invoiced and
blocked for maintenance by the owner.
In process 'lingo':
After completing a timesheet, e.g for the week, the
owner submits it for approval to his/her supervisor.
Supervisor receives (listing) all timesheets to be
approved. Supervisor opens each timesheet for review
and approves or rejects timesheet.
All rejected timesheets are 'sent' back to the owner
(maybe e-mail notification) with comment why it has
been rejected.
Owner can maintain and re-submit.
All approved timesheets can be invoiced, non-approved
timesheets cannot.
Invoiced timesheets cannot be maintained at all; only
archived.
These processes are pretty much standard in any
commercial timesheet system as used by consulting
firms, large or small.
Thanks again.
Klaus Schmidt
klaus@webschmidt.ca