How to use a Righthand with Clockify

Quick answer

Use Righthand to prepare a Clockify project-hours review from a report snapshot. Preserve duration units and the selected workspace so totals can be checked.

Start with a reviewable deliverable, keeping Clockify as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Clockify documents reporting views and report configuration. See the official Clockify reference. Provider capabilities and Righthand's available tools are separate checks.

Use the owner's project-scoped time export with entry IDs, employee identifiers, dates, durations, and approved billable definitions. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: workspace, user, project, task, date, duration, billable flag, report filters. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Tracked time is not necessarily billable or approved. Rate decisions and client invoicing stay with the project owner.

Illustrative first-run brief

Use the owner-provided Clockify snapshot or approved read-only view. Review the supplied weekly detailed report for two projects. Flag uncategorized entries and inconsistent billable labels; draft questions without changing time. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the project administrator to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A time entry without a project appears in the exception list, while valid nonbillable work remains separate rather than being dropped.

Reconcile a project's duration total with the identical source filters, using hours consistently. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Rounding or duration strings can distort totals. Parse the source units and document rounding before comparing reports.

If a running timer or incomplete entry lacks an end time, mark duration provisional and request owner reconciliation before totaling accepted hours.

FAQ

What should the reviewer verify first?

Check entry and project IDs, timezone, duration source, and billable flag. A recorded duration does not by itself establish invoice eligibility or approval.

How should a repeat run be scoped?

Preserve reporting window and project mapping across runs. Recheck edited or open entries at the cutoff, and separate billable classification from authorized invoicing.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.