Outputting clean reports is one thing, but "normalizing" the time to make it look better, or as though I'm more busy, is something else entirely. I appreciate the effort, but this tool has the very real potential to get a contractor or employee sued for time fraud. I highly recommend against normalization of time data. The contractor either worked a full 30 or s/he didn't. It's black and white. Saying s/he worked for 30 when s/he worked for 25 is a lie, and subject to lawsuits and further legal action.

This sounds really cool. I have actually made something similar (unpublished and quite hacky though).

I work as a self-employed contractor and must report my times in varying standardised formats, depending on the client or agency I am working with. My input data comes from TimeWarrior (like yours) and I usually just output CSV data so I can copy-paste that into a provided excel template.

Quantizing the data is usually the most essential step as the templates often restrict accuracy. I find it strange that many of the comments here presume this kind of transformation to be fraudulent.

I don't get it.

Where's Saddam?

I'll head back to linuxmemes now.

I just say I worked X hours per day, above my log entries describing what I did that day. Why do they need anything more than that?

As someone who works atrocius times of their own volition & has to create a clean timesheet every end of the month, this is a great idea -buyt there are too many special rules to consider imo - also I never properly track time (keep forgetting) but reconstruct work times from emails, chats & calendar entries :)

OT: What program are these diagrams made with? I've seen them floating around recently and really like the looks of them.

I do my time tracking in org-mode, and export it to JIRA once a day or so. It is quite a specific/tailored setup, written in a mix of elisp and, well, org-mode (specific names and tags are used to configure some settings), but I'd love to look at this tool to see if I can extend my workflow by using it for the "massaging into a nicer shape" part. I might end up writing some extensions for either side (org-mode input format and JIRA REST calls output format).

My current tooling quantizes everything by rounding start and end times to the nearest full 15 minutes, and starting a new task at the end time of the previous one when clocking in, so that my team lead does not have to report so many fractions of hours to higher layers.

So this requires some kind of existing tracking software? Are there existing FOSS options for that part?

My current job doesn't need time tracking (yet?, some of my work is for the sister company) but a job I worked before had us clock in and out for specific projects on a computer, but the subscription ended and we were using a UI glitch to continue using it and literally cheat engine to make it still export the files for the office to use.

Org mode has a time tracking feature, dunno about report generation.

I would use it, let me know if you need any testing or feedback. What is it written in?

“FOSS” here doesn’t mean hosted exclusively on proprietary Microsoft GitHub, right?