Work-record field guide

Find duplicate time records before merging files

Distinguish duplicate identity from merely similar work.

Last materially reviewed 2026-09-23

Quick answerIdentify duplicates using a stable source key and version context. Similar descriptions or equal durations are not enough to delete a record.

Define what makes one record unique

Prefer the source record ID plus its source system and version where those are available. If a report aggregates by person and date, that combination may identify a summary rather than an underlying entry. Write the key for the actual file. A spreadsheet row number changes when the file is sorted and is not a reliable source identity.

Classify duplicates before acting

Use these fictional cases to distinguish repeated delivery from separate work.

Scroll horizontally to compare every column.

Observed pairInterpretation to testSafe first action
W-010 appears twice with identical valuesSame record delivered twiceCompare batch/source identity
W-010 has 30 and 45 minutesTwo versions of one recordFind the accepted correction version
W-010 and W-011 both say meeting, 30 minutesPotentially separate workAsk for context; do not auto-delete
Daily total plus its detailed entriesMixed granularitiesChoose one aggregation basis

Keep repeated imports from creating new totals

Maintain a handoff register of batch ID, period, file version, recipient and acceptance status. Before retrying an import, establish whether the first attempt applied any records. A timeout or missing success message does not prove nothing happened. Test the receiving system’s duplicate behavior using fictional data rather than assuming it safely ignores repeats.

Resolve the record without erasing its history

Once a duplicate is confirmed, follow the authorized correction process and retain the reason, affected IDs and resulting total. Preserve the original file so the decision can be explained. If identity is ambiguous, isolate the records for review instead of selecting one arbitrarily. Do not use a generic “remove duplicates” command across descriptions or names as a substitute for understanding the key.

Sources and boundaries

These pages were read on 2026-09-23. Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method.

  1. Clockify — detail — Vendor product page · clockify.me · checked 2026-09-23
  2. Microsoft — import — Vendor documentation · support.microsoft.com · checked 2026-09-23