Work-record field guide

Trace missing entries through capture and export

Localize absent rows using counts, filters, identity and state.

Last materially reviewed 2026-09-23

Quick answerTrace one missing record through capture, review, report filters and the receiving file. Locate the stage where it disappears before changing the source or recreating it.

Write down the expected record

Start with a known contributor, record ID if available, date, project and expected duration. Record why you expect it to exist. A scheduled meeting is not proof that a time entry was captured. If the source itself is uncertain, ask the contributor through the agreed process; do not manufacture an entry to match an anticipated total.

Compare the same view and permissions

Check whether the record is visible to its contributor, the reviewer and the export role. DeskTime documents role-scoped exports, so a restricted view can look like missing data. Also compare selected people, teams, projects, date boundaries and review states. Avoid fixing access by broadly granting administrator privileges when a narrower authorized export would solve the task.

Follow a staged diagnostic

Use a fictional W-602 entry to test the chain.

Scroll horizontally to compare every column.

StageQuestionEvidence
CaptureDoes the original entry exist?Contributor/source view
ReviewIs it still draft or returned?State and reviewer notes
ReportIs it inside the exact filters?Saved period, zone and population
ExportIs the row or aggregate present?Untouched file and row count
RecipientWas it rejected, merged or coerced?Import result and mapping

Repair only the demonstrated failure

If the source is correct but excluded by a filter, regenerate the appropriate report with a new batch identity. If the recipient rejected a code, repair the mapping and reconcile the retry state before resending. If the source really needs correction, preserve the original and review the change. A new manually created record can become a duplicate if the original later appears after synchronization.

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. DeskTime — roles — Vendor documentation · help.desktime.com · checked 2026-09-23
  2. Time Doctor — export — Vendor documentation · support.timedoctor.com · checked 2026-09-23