Work-record field guide

Close a reporting week with a reconciliation checklist

Release one clearly versioned, reviewed batch.

Last materially reviewed 2026-09-23

Quick answerClose a reporting period by reconciling the expected population, unresolved entries, approved state and outgoing file. Save a single release identity so later corrections can reference it.

Freeze the reporting envelope

Write the period start and end, reporting zone, included people, project filters and required review state. Use a half-open interval if the recipient accepts it: include the start and exclude the next period’s start. Keep that convention visible. A changing list of people or a different end-date interpretation can make two apparently identical weekly reports incomparable.

Resolve or list exceptions

Ask each reviewer to account for missing submissions, ambiguous projects, duplicate entries and late changes. Distinguish no work reported from no data received. Do not insert zero hours just to complete a row unless zero is the verified meaning. An unresolved record needs an owner and a decision about whether the recipient can accept a partial release.

Run the release checklist

Use this original checklist as a proposed control, adapting it to the actual recipient rather than treating it as a compliance certificate.

Scroll horizontally to compare every column.

CheckEvidence to retainStop condition
PopulationExpected and exported contributor IDsUnexplained omission
Period and zoneSaved report settingsDifferent boundary conventions
Review stateApproval/exception listUnresolved mandatory review
File integrityRow count, duration total, schema versionUnexplained difference
HandoffBatch ID and recipient acknowledgementUnknown accepted version

Keep the accepted batch retrievable

Store the untouched export, settings, mapping version and review record in the authorized location. Restrict access to people who need it. Record the actual release time and owner. When a late correction arrives, link it to this batch and follow the replacement-or-adjustment process; do not silently overwrite the file with the same name.

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