Month-end, and the timesheet is due. My hours were buried in a jumble of pasted rows from emails, chat messages and half a dozen spreadsheets, and adding them up by person and project by hand would have eaten half my morning. I have done it that way before. It ends with a calculator, a highlighter, and a total I do not quite trust.
The trouble with adding hours by hand is not the addition. It is the doubt. You get a number, then you add it again to check, and you get a slightly different number, and now you do not know which one is right. So you add it a third time, slowly, and the morning is gone. Meanwhile the invoice is waiting on a total you cannot swear by.
The fix is embarrassingly simple once you stop fighting the format. I use the Bulk Hours Log Rollup now. Paste the log, one row per line, written as date, person, project, hours, with tabs or commas between the columns. Then pick how to slice it. Group by person, by project, or person by project to see every combination. Pick the period too: roll all dates together, split by week starting Monday, or split by month. Everything recalculates live as you type.
A worked example with real numbers
Here is a small log to show what that looks like. Two people, two projects, two weeks. Alice put 4 hours on Mercury on 2 November, 6 more on the 3rd, 3.5 on Venus on the 4th, then 5 on Mercury and 4.5 on Venus in the week of 9 November. Bob put 8 on Mercury on the 5th, 7 on Mercury and 6 on Venus in the second week.
Group by person and split by week, and Alice gets 13.50 hours for the week of 2 November and 9.50 for the week of 9 November, a personal total of 23.00. Bob gets 8.00 and 13.00, totalling 21.00. The week subtotals come out at 21.50 and 22.50, and the grand total is 44.00 hours. Switch the grouping to person by project and those same rows regroup instantly: Alice by Mercury 15.00, Alice by Venus 8.00, Bob by Mercury 15.00, Bob by Venus 6.00. Still 44.00 in total.
That is the moment the tool earns its keep. The same eight rows, three different questions, three answers in seconds, and every one of them adds up to the same grand total. When the groupings agree, you trust the number. When you add by hand, you never get that check, because doing it three ways by hand would take the whole morning.
The input is forgiving about where the rows came from. Copy them from a spreadsheet, a text file or an email. Dates like 2026-11-02, 11/02/2026 or 02-11-2026 all parse, hours are plain numbers with decimals, and a header first row is fine as long as the header toggle is on. Press Load example in the tool and you get exactly the log above, so you can see the regrouping happen with your own numbers in front of you.
Messy rows never break your totals
Real logs are never clean, and that is fine. Any row with missing or non-numeric hours, or a date the tool cannot parse, is flagged by line number in a warning box and skipped from every sum. The skipped-row count sits right next to the grand total, so nothing is ever dropped silently and you will never see a NaN. Blank lines are simply ignored.
That matters more than it sounds. A silent drop is the worst kind of error in a timesheet, because the total looks complete and nobody knows a row is missing. Here the flagged rows are named by line number, so you can fix them in your source, paste the log in again, and the totals update on the spot. The check is part of the workflow instead of a separate job you have to remember to do.
I have had logs where a whole afternoon sat in a chat message with the hours written as words, and a row where someone typed a date as Nov 5th and the sheet refused it. Both rows got flagged, both got fixed in two minutes, and the total was right. Without the flag I would have invoiced the clean rows and never known the rest existed.
The weekly table is the view I actually check
Under the main rollup there is a dedicated weekly table that totals each person's hours week by week, with every week starting on Monday. A 50-hour week jumps out immediately, which makes this the view to check right before you approve timesheets or invoice a client. It is the one that catches the week someone quietly worked too much, and it is the one I look at before anything goes out the door.
That is a different question from the grand total, and it needs a different view. The grand total tells you what to invoice. The weekly table tells you whether the work was sane. Both matter, and both come from the same paste. Nobody wants to discover a 58-hour week from a client asking why the invoice is so high. You want to see it yourself first, while there is still time to ask what happened.
Copy it out and move on
Copy TSV puts the current rollup on your clipboard, ready to paste into any spreadsheet. Download CSV saves the same table as a file called hours-rollup.csv. Nothing is uploaded. The whole thing runs in your browser, so your log is never sent anywhere, and closing the tab wipes it from memory. That last part matters when the log has client names and project names in it. You paste it, you read the totals, you copy them out, and the log is gone when you close the tab.
If your hours are scattered across emails and chat threads right now, paste the log in and give the per-person weekly view a quick look before you invoice. The whole check takes less than a minute, and it is the minute that stops the second-guessing. I used to spend half a morning on this and still not trust the total. Now I spend a minute and I do.
Questions I get asked
Which log format does the rollup accept? One row per line, written as date, person, project, hours and separated by tabs or commas, pasted from a spreadsheet, a text file or an email. Dates like 2026-11-02, 11/02/2026 or 02-11-2026 all parse, hours are plain numbers with decimals, and a header first row is fine as long as the header toggle is on.
How are bad rows handled? Rows with missing or non-numeric hours, and rows with dates the tool cannot parse, are flagged by line number and skipped from every total, with the skipped-row count shown next to the grand total. Blank lines are ignored, totals never show NaN, and no bad row is ever silently dropped.
Is anything uploaded? No. The rollup runs entirely in your browser. Your log is never uploaded, stored or sent anywhere, and closing the tab wipes it from memory.
Month-end will come round again, and the hours will be buried again. The difference now is that I know where the shovel is.
Top comments (0)