Legal02 / 03
Terms governing access to the Common Intelligence public website and its editorial material.
- Effective date
- 3 September 2026
01Agreement
By using this website you agree to use it lawfully and not to interfere with its operation.
02Information, not advice
The website describes Common Intelligence's approach and presents editorial material for general information. It is not legal, financial, operational or technical advice and does not create a client relationship.
03Accuracy and availability
We aim to keep the site useful and accurate but do not promise that every page will always be complete, current or available. Case studies and editorial material must not be treated as professional advice or as guarantees of future outcomes.
04Intellectual property
Unless another owner is identified, the website design, writing and original materials remain the property of Common Intelligence or its licensors. They may not be reproduced or distributed without permission, except where applicable law permits.
05Responsibility
To the extent permitted by law, Common Intelligence is not responsible for losses arising from reliance on general website information or from interruptions outside its reasonable control. Nothing in these terms excludes rights or liabilities that cannot lawfully be excluded.
Other legal documents
Frequently asked
Our work starts from the people already responsible for the operation. The aim is to remove repetitive search, comparison and drafting, while making their judgment easier to apply and keeping accountable decisions with named human owners.
They help map the real process, choose the difficult cases, test early versions and define where review or refusal is required. An internal group learns to operate and improve the system before handover.
One senior sponsor, access to the people and systems involved, and agreement on the business measure before building begins. Leadership also protects time for operators to participate, because their knowledge is part of the system.
It should be frequent, expensive, evidence-heavy and close to a measure the company already trusts. The two-week diagnostic compares candidate workflows and tests the strongest one on real company data.
That is why it is tested on real exceptions before production. Corrections become part of the evaluation set, and the system is designed to ask for review when evidence is weak rather than appearing certain.
We build in the client environment wherever possible, use the minimum permissions each action needs, and make activity auditable. Data boundaries, retention, human review and prohibited actions are agreed before a production release.
The engagement is designed to reduce that dependency. The client receives the source, prompts, evaluation cases, runbooks and controls, and proves the handover by running the next cycle with its own team.
We establish the current cost and operating baseline together, then review the same measure after each release. If the workflow does not produce a credible financial or operating improvement, we do not expand it.