Define the change before changing the record
Common cases include a meeting away from the computer, a timer assigned to the wrong project or an entry accidentally left running. Start with the person’s explanation and the available record. Do not infer a missing work period from a calendar event alone, and do not silently remove time because a device was idle. The aim here is an understandable record, not an automated employment decision.
Use a compact correction log
For a fictional record W-014, the original value is 45 minutes against Project A. The proposed change is 60 minutes against Project B because the project was selected incorrectly and the meeting lasted longer than entered. Preserve both versions. Record the proposer, reviewer, decision time, reason and affected export. A project change and a duration change are separate facts, even when submitted together.
Scroll horizontally to compare every column.
| Record element | Fictional example |
|---|---|
| Stable reference | W-014 |
| Original → proposed | 45 min / Project A → 60 min / Project B |
| Reason | Wrong project selected; meeting duration corrected |
| Review state | Pending until the designated reviewer responds |
| Export consequence | Check whether the previous 45-minute row was already sent |
Make permissions an acceptance case
DeskTime documents manual/offline additions with administrator approval where configured. That establishes an available workflow, not your account’s actual settings. Demonstrate a submitted addition with a test user, inspect it as the reviewer and confirm what happens before and after the decision. Include a rejected proposal in the demonstration. Do not call a workflow approved merely because the proposer can save a value.
Close the loop with the recipient
Set an export cutoff and preserve the file that was actually sent. If a correction arrives later, agree whether the recipient needs a replacement file or a clearly identified adjustment. Avoid sending both without explanation; a recipient may count the record twice. Compare stable references and totals, then record which version they accepted. Never assume the tracker can retroactively repair another system.
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.
- DeskTime — manual — Vendor product page · desktime.com · checked 2026-09-23
- DeskTime — export — Vendor documentation · help.desktime.com · checked 2026-09-23