Documentation Time Entries
Detailed guide

Time Entries

The operational workflow for capturing, validating, and maintaining billable and non-billable delivery effort across the entire workspace.

Time Entries is the labor evidence layer for the workspace. It connects day-to-day delivery activity to utilization, margin, and invoice support so downstream billing and reporting decisions are based on complete and explainable records.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Filter by period and status before auditing so you do not mix unrelated contributors, projects, or workflow states.
  • Use search and sorting to find suspect rows quickly before making any edits.
  • Escalate from list review to timesheet row editing when many entries require coordinated correction.
  • Validate billing readiness by confirming the right entries are submitted and attributable before invoice linkage.

Put it into practice

  1. Start by fixing scope: choose the date window and any status/resource filters before interpreting totals. This prevents false conclusions caused by mixed periods or hidden rows.

    InteractionsTime Entries page: set From/To dates, status filters, and any user/project controls in the filter toolbar.

  2. Use search to isolate one project, task, contributor, or note pattern when reviewing anomalies. Work in small slices so edits stay deliberate and traceable.

    InteractionsTime Entries table controls: enter a search term above the list and confirm matching rows only.

  3. Review status distribution before editing anything. Identify whether the issue is unsubmitted capture, pending approval, or incorrect approved rows so you correct the right layer of the workflow.

    InteractionsTime Entries list: compare row status badges and sort/group mentally by pending, submitted, approved, or invoiced state.

  4. Open only the entries that are objectively wrong and correct minimal fields (project, task, date, hours, notes). Keep edits narrow to preserve audit clarity.

    InteractionsTime Entries row actions: open the target entry and update only incorrect values, then save.
    Open workflow: Time Entry Form

  5. When many rows are affected, switch to Timesheet View for faster weekly repair, then return to this page to confirm the workspace-level result.

    InteractionsTime Entries navigation: open Timesheet View, complete weekly corrections, then come back to Time Entries index.
    Open workflow: Timesheet View

  6. If anomalies are isolated to one engagement, pivot into that project's time log and validate against project budget and billing context before final approval or invoice work.

    InteractionsFrom time rows tied to a project, open project context and review Project Time Entries for that engagement.
    Open workflow: Project Time Entries

  7. Finish by re-running filters and checking totals/status mix again. The final state should be coherent for reporting, margin analysis, and invoicing decisions.

    InteractionsTime Entries page: clear temporary search/filter noise, verify totals and statuses, then continue to invoice or reporting workflows.
    Open workflow: Invoice Workflow

What to review

Page header and context rail

Confirms you are reviewing workspace-wide time data and provides the fastest path into detailed entry workflows.

View and tab navigation

Switch between index and timesheet-style workflows while preserving working context for investigations and corrections.

Filters, date controls, and search

Use these first to isolate the exact population you need before interpreting totals or editing rows.

Workspace time table

Lists date, project, task, contributor, hours, and status so every correction can be justified from row-level evidence.

Status indicators and row actions

Show whether entries are pending, submitted, approved, or already committed downstream, and expose edit paths where permitted.

Timesheet handoff entry point

Provides a direct move into weekly row editing when list-level review reveals broad data quality issues.

See guide: Timesheet View

Project-level log linkage

Lets you pivot from workspace-level review into a single project's full log when the issue is project-specific.

See guide: Project Time Entries

Guardrails

  • Every saved row should preserve valid project, task, date, and hour relationships so reporting and billing remain consistent.
  • Status transitions should reflect real workflow progression; do not force approvals to hide unresolved data quality issues.
  • Large corrections should be reviewed after save to confirm totals changed as expected for the intended slice.
  • Some users can only edit their own entries, while managers or finance roles may review and correct broader workspace activity.
  • Approval, billing-link, or historical-edit actions may be permission-gated even when row visibility is allowed.

If it starts drifting

  • If rows look missing, clear filters and search first, then confirm you are in the expected time view and date range.
  • If totals look wrong after edits, re-open the corrected rows and verify status and project/task attribution rather than changing hours again blindly.
  • If edits are blocked, verify role permissions and whether the row is already in a locked downstream state.
  • If billing disputes occur, pivot to project-level time review so invoice evidence and time context can be validated together.