Editorial standards and corrections

Who is responsible

Clocky field notes are published by the Clocky team. The named author may be the organisation when several people contribute to product verification, editing, and maintenance. We do not create fictional expert biographies.

How product claims are checked

Commands, plan boundaries, permissions, and workflow descriptions are checked against the current production bot, dashboard, and maintained documentation. When a guide compares approaches, we separate product facts from our recommendation and name important limitations.

Sources and evidence

We prefer primary sources for platform, search, privacy, and technical claims. Clocky-specific statements come from the maintained product and its documentation. We do not invent customer quotes, adoption numbers, benchmarks, or test results. A case study will identify whether evidence came from interviews, product data, or a controlled test.

Use of AI

AI may assist with outlines, editing, summaries, and identifying questions a reader may have. It is not treated as a factual source. Every indexable field note is reviewed by a human against the current product before publication. Pages are not generated and indexed at scale from keyword permutations.

Commercial independence

Clocky’s content naturally discusses Clocky. Comparisons must still explain scenarios where another method is a better fit. We do not accept payment for rankings, hide affiliate relationships, or describe a feature as available before it is in production.

Corrections policy

If a factual error affects setup, privacy, pricing, availability, or a recommendation, we update the page and its modified date. Material corrections should be explained on the page when a reader could otherwise act on the previous version. Minor spelling and clarity edits do not receive a separate notice.

Report an error to support@clockybot.com with the page URL and the statement you believe is wrong. We will verify it against the current product or primary source.

Review schedule

Commercial and setup pages are reviewed when their related product workflow changes. Field notes are reviewed at least annually and sooner when a command, permission, plan boundary, or referenced platform rule changes. Outdated pages are updated, consolidated, redirected, or removed rather than retained only for search traffic.