Data quality and governance

Trustworthy reporting starts with trustworthy source records. WhoWorked provides data-quality, activity, connection, anomaly, access, and period-close surfaces so a workspace can find gaps before they reach a client or invoice.

Define ownership

Assign owners for four parts of the record:

• Members own the accuracy of their time and descriptions.
• Delivery leads own project structure, budgets, and attribution context.
• Workspace admins own access, integration health, and shared conventions.
• Commercial reviewers own rates, billable state, and period close.

One person can hold several responsibilities, but each responsibility should still be explicit.

Review data quality

Open Data quality from the main navigation. Follow each alert back to its person, project, or time entry and correct the underlying issue.

Common review items include:

• Underlogging: A project has logged less than 80% of its weekly-hours budget for the review week.
• Duplicate entry: Two entries are identical or overlap in time.
• Long entry: One completed time entry is longer than 10 hours.
• Long day: A person's completed entries total more than 12 hours for a day.

An alert can indicate a real problem or an intentional exception. Resolve it with context rather than optimizing for an empty alert list.

Budget notifications, anomaly flags, missing categorization, and AI reporter coverage are separate checks. Review them in project views, entry details, Reports, and AI reporting rather than expecting them in the Data quality list. Data quality requires the insights_alerts workspace entitlement.

Review connections and access

Owners and admins can use Connections and AI reporting health to find stale or missing reporting sources. Use Feature access and the team views to review elevated roles, manager grants, and restricted project membership.

Also review API keys, personal access tokens, OAuth applications, webhooks, and browser extensions. Revoke credentials that no longer have an owner or active purpose.

Use the activity record

The Activity audit view helps explain material workspace changes. Use it when a rate, role, project setting, or integration changes unexpectedly. This compliance view is available to owners and admins.

Close a period

Before treating a reporting or billing period as final:

1. Resolve running timers and overlaps.
2. Review uncategorized and non-billable work.
3. Confirm project, workstream, rate, and currency context.
4. Review AI attribution coverage and exceptions.
5. Resolve budget and data-quality signals.
6. Produce the final internal and client-facing views.
7. Use the workspace period-close controls available to your plan and policy.

Document who approved the close and any known exceptions. Reopening a closed period should be intentional and reviewable.

Period close is available to owners and admins when the lock_periods_enabled entitlement is active.

Avoid surveillance patterns

Use governance to protect the quality of the shared record, not to score people from isolated activity. AI tokens, hours, and event volume require delivery context. Review the result, the person responsible, and the supporting evidence together.

Return to reports and insights after the record is ready.