3

I have a table which sums up worked hours for each project. When the ammount of hours is huge, has still sense use hh:mm format, or decimal format could be more clear?

Reading, for example 7650:30, looks (in my personal impression) strange.

+-----------+-------------+
|  PROJECT  | HOURS SPENT |
+-----------+-------------+
| Project 1 |     5640:00 |
| Project 2 |      740:30 |
| Project 3 |      340:00 |
| Project 4 |      110:30 |
| Project 5 |       40:00 |
+-----------+-------------+

OR

+-----------+-------------+
|  PROJECT  | HOURS SPENT |
+-----------+-------------+
| Project 1 |     5640,00 |
| Project 2 |      740,50 |
| Project 3 |      340,00 |
| Project 4 |      110,50 |
| Project 5 |       40,00 |
+-----------+-------------+
  • 1
    Does it have to be hours only? Can you not represent it as days? (So 235 days (5640hrs) )? – JonW Apr 12 '18 at 10:40
  • @JonW no cause unit of measure are hours – WalterV Apr 12 '18 at 10:56
  • 3
    @JonW - if it is a project, 1 day can either be 8 hours (working day) or 24 hours (wall clock day) and this creates ambiguity. – Mike Apr 12 '18 at 12:23
3

You probably see this type of table in a Time Tracking app. Its purpose to track time, so you can understand how much money you do/spend.

In this context hours are like any other resource like money or beer or whatever. You probably don’t need to display minutes at all and round the numbers up.

If you cant round numbers, decimal representation 1.75 is better than 1:45 (1h, 45m) because you can multiply 1.75 * 10$/h and get results right away.

This will make table clear and easier to read. Aligning to the right is the best thing you can do.

enter image description here

  • 1
    I'd say aligning decimals is the best thing you can do. They are in your example, but you wouldn't want 4{decimal}280 to look like a visually larger amount than 236. – maxathousand Apr 12 '18 at 15:55
  • Yes, using 1.75 instead of 1:45 is so much easier to work with from a comprehension and reporting standpoint. I stopped using an invoicing app specifically for this reason :) – Refe Apr 12 '18 at 21:18
0

Depending on the granularity of the time (the smallest amount of time you can assign to a task) I would suggest the following formats (assuming the granulation is one quarter of an hour):

  • the most explicit

    5640h 00'
    740h 30'
    340h 15'

    showing also how many minutes the total includes. And everyone knows that 30 minutes is half an hour (for the financial cost calculation)

  • visually descriptive

    5640 h
    740½ h
    340¼ h

    where a fraction (depicting anything between 0 and 1 hours at first glance) is shown in a fraction of a font size

  • calculation friendly

    5640.00 h
    740.50 h
    340.25 h

    (or omit the units description for even more "plain" look) is the easiest for quick calculation (copy/paste into a spreadsheet) but the least appealing for the human.

In all cases I'd keep the unit descriptor, even if it is repeating the table header row - it helps to understand that we are still talking about the hours in the table.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.