Logging hours and time off
The calendar, submitting a week, changes requested, and asking for days off.
1 min read
Nothing watches you
No screenshots, no keystroke logging, no activity score, no camera. Your hours exist because you wrote them down.
Writing an entry
Add hours from the calendar. An entry is a client, a date, a start and a finish, and optionally a reference: a line about what the time was for.
Times are stored as the local times you wrote, with the zone you wrote them in. That is why a daylight-saving change later cannot silently move hours you have already agreed with somebody.
An entry cannot span midnight, and two entries cannot overlap in real time, across all your clients, not just one. If two overlap, the refusal names the other entry's date, times and zone and whose it is, so you can fix the right one.
Logging on an approved day off warns once and never blocks.
Four views
Day, week, month, and by client, all in the address bar so any of them is a link. Each client has a colour, with their name beside it, and the colour is theirs for good: it does not reshuffle because somebody was renamed.
Submitting
Approval is per client per week. A draft week is yours: the client sees nothing at all until you submit it, and that is enforced by policy rather than by the screen choosing not to show it.