Many CSE hourly workers use a CGI tool to record and report their hours, (tersely) described in this document.
The basic idea of this tool is that workers visit a webpage to enter their hours as they work them, then press a button at the end of a work period (half a month) to email them to their supervisor and to the admin. For their point of view, the web page looks like a monthly calendar with text fields in the slot for each day in the pay period.
There isn't centralized administration of the data-- users register themselves, which includes typing in the fullname and email address of their supervisor (unless some other user has already done that for that supervisor). But registered administrators can visit the tool and "forge" data for workers, or delete "stale" workers.
There is no interface for supervisors. They get email and that's it.
There are a few different versions of the tool: a CSENetID-authenticated "production" version for workers with CSE computer accounts, a "production" UWNetID-authenticated version for those without CSE computer accounts, and test versions for both authentication types.
The test versions differ from the production versions in two ways: (1) they use a different data store, and (2) they don't send email-- rather, they just just display the email that would have sent.
There is another web interface to the data for the admin: a weekly report tool that staff requested to help fill out some report that I don't know the details of.
Finally, there is a cron job that runs once a month to email a simple summary to staff.
Everything is written in perl. The data store is a bunch of "tied hashes"-- per-day gdbm files.