Contact

ToolsTime logged twice

How much of your team’s time is logged twice?

For teams that log time in Clockify or Toggl and bill or pay by the hour. Drop your detailed time export and see the time each person logged twice, where two of their own entries cover the same minutes, with every overlap listed and every sum shown. It counts what your file holds, not what was billed or paid, and it is not advice on your timesheets.

Sample time log

A small team’s month of time entries, all made up for this demo

Your settings

Overlaps shorter than this are left out, so a timer stopped a few seconds after the next one started does not count. Any overlap counts every one.

Logged twice

22:02:00

Between 1 and 30 September your 10 people logged 1,449 hours 16 minutes 52 seconds, and 22 hours 2 minutes of that was logged twice. 5 of the 10 have entries that overlap their own, 18 times in all, and 10 hours 50 minutes of it is Jessica Jenkin’s.

22 hours 2 minutes is the 18 overlaps below added up, each person’s in the bars.

An overlap can be on purpose, as an all-day entry with the day’s tasks logged inside it. Every one is listed below with its entries, so you can judge each.

3 overlaps shorter than 1 minute, 55 seconds logged twice in all, are left out. Pick Any overlap in the settings to count them.

Logged twice, by person

  • Jessica Jenkin7 overlaps added up10:50:00
  • Brittney Banyard5 overlaps added up7:37:00
  • Noah Freund0:36:00 + 0:27:00 + 0:22:001:25:00
  • Tabitha Huth0:43:00 + 0:34:001:17:00
  • Christopher Cruz0:53:00

Every overlap, the most logged twice first

PersonWhenthe overlapThe entrieseach one’s own start and endLogged twice
Jessica Jenkin2 Sep13.29 to 15.43Architecture, 12.46.23 to 19.02.29Estimates, 13.29 to 15.432:14:00the time both run
Jessica Jenkin8 Sep9.36 to 11.44Code review, 8.17.39 to 11.50.54Code review, 9.36 to 11.442:08:00the time both run
Jessica Jenkin3 Sep9.50 to 11.50Code review, 8.57.46 to 12.47.18Code review, 9.50 to 11.502:00:00the time both run
Jessica Jenkin4 Sep8.35 to 10.35Estimates, 8.03.59 to 10.35.45Code review, 8.35 to 10.352:00:00the time both run
Brittney Banyard24 Sep11.15 to 13.08On site, 8.04 to 16.58Requirements workshop, 11.15 to 13.081:53:00the time both run
Brittney Banyard24 Sep9.11 to 10.56On site, 8.04 to 16.58Notes write-up, 9.11 to 10.561:45:00the time both run
Brittney Banyard9 Sep12.00 to 13.39On site, 8.29 to 17.18User interviews, 12.00 to 13.391:39:00the time both run
Brittney Banyard9 Sep9.38 to 10.38On site, 8.29 to 17.18Requirements workshop, 9.38 to 10.38Client call, 9.48 to 10.231:35:002:35:00 logged in it− 1:00:00 long
Jessica Jenkin25 Sep10.01 to 11.17Admin, 8.33.17 to 11.17.29Architecture, 10.01 to 11.171:16:00the time both run
Christopher Cruz16 Sep14.02.41 to 14.55.41Team sync, 13.05.07 to 14.55.41Android build, 14.02.41 to 16.03.580:53:00the time both run
Brittney Banyard9 Sep13.55 to 14.40On site, 8.29 to 17.18User interviews, 13.55 to 14.400:45:00the time both run
Tabitha Huth1 Sep16.15 to 16.58Support tickets, 13.05 to 16.58Team sync, 16.15 to 17.460:43:00the time both run
Jessica Jenkin24 Sep9.35 to 10.12API work, 8.48.39 to 11.27.20Estimates, 9.35 to 10.120:37:00the time both run
Noah Freund4 Sep13.26 to 14.02Client call, 13.21 to 14.02Sprint planning, 13.26 to 17.290:36:00the time both run
Jessica Jenkin14 Sep10.52 to 11.27API work, 8.36.05 to 11.27.18API work, 10.52 to 11.270:35:00the time both run
Tabitha Huth23 Sep14.19 to 14.53Driver screens, 12.40 to 14.53Driver screens, 14.19 to 16.560:34:00the time both run
Noah Freund16 Sep12.17 to 12.44Team sync, 12.17 to 12.44Team sync, 12.17 to 12.440:27:00the time both run
Noah Freund29 Sep11.26 to 11.48Backlog, 9.00 to 11.48Client call, 11.26 to 12.200:22:00the time both run

Each person, the most logged twice first

PersonEntriesLoggedtheir entries’ lengthsLogged twicetheir overlapsOverlaps
Jessica Jenkin62190:01:0962 entries added up10:50:007 overlaps added up7
Brittney Banyard52162:00:3852 entries added up7:37:005 overlaps added up5
Noah Freund73153:09:0073 entries added up1:25:000:36:00 + 0:27:00 + 0:22:003
Tabitha Huth49142:21:0049 entries added up1:17:000:43:00 + 0:34:002
Christopher Cruz46100:10:1246 entries added up0:53:001
Nigel Jaeger53165:58:4653 entries added upNone0
Brandon Mee47158:50:2647 entries added upNone0
Iyesha Palacios47155:50:1747 entries added upNone0
Erin Booms52154:08:2452 entries added upNone0
Jonathan Maska2366:47:0023 entries added upNone0
Everyone5041,449:16:5210 people added up22:02:0010 people added up18

What this counts

  • An entry’s length is its end less its start, as your file writes them. Time logged is every entry’s length added up.
  • An overlap is a stretch of time when two or more of one person’s own entries run at once. Its time logged twice is the time those entries log in it, less the stretch itself, so the stretch’s length when two entries run, and twice that when three do.
  • Two people working at the same time never overlap. Nor do two entries that only touch, one ending as the next starts.
  • This is time logged twice in your file. Your file cannot say whether it was billed or paid twice.
  • Times are read as your export writes them, on the clock of whoever exported it.

Also in your file

  • Your file is the Clockify Detailed report, with 504 entries from 10 people, 1 Sep 2026 to 30 Sep 2026.
  • 5 people have no overlap.

Runs in your browser. Your file is never uploaded.Want your timesheets checked before every invoice run? Talk to us

More tools

All 30 tools