Decide what a time record should contain.
Define purpose, access and exclusions before enabling automatic activity tracking. A practical worksheet for a transparent small-team rollout.
Define collection boundaries, contributor instructions, identity and permissions before records become reports.
Collect what the task requires, keep the contributor and project identity clear, and make uncertainty easy to report.
Begin with what must be recorded and which collection boundaries apply. Then establish contributor and project identity, role access and a route for manual or uncertain entries. The guides distinguish device activity from work and keep unsupported interpretations out of the record.
Record what passed, failed or remained unknown. Product features depend on the selected plan and configuration, and these guides do not establish employment, payroll or legal requirements. If the current process already meets the need reliably, keeping it remains an option.
Define purpose, access and exclusions before enabling automatic activity tracking. A practical worksheet for a transparent small-team rollout.
Give contributors a usable rule for capture, correction and escalation.
Separate viewing, editing, approving and exporting rights.
Maintain identifiers through renames, archived work and downstream mappings.
Add justified offline work without reconstructing activity from guesses.
Separate device inactivity from the meaning of a work record.
Test boundaries around pausing collection and retained metadata.
Prevent ambiguous identity and accidental cross-person attribution.
Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method, not observed product results.