Limitations

An honest list of what CommonBench can do, what it can't, what it shouldn't be used for, and where coverage is partial. We'd rather you read this and decide we're not the right tool than subscribe and feel misled.

Reading this page costs us short-term conversion. We publish it because the alternative — discovering a limitation by relying on a wrong answer in a real matter — costs you more.

What we do well

What we don't do

Jurisdiction coverage

Coverage is not equal across our five jurisdictions. The corpus is being expanded; this table reflects the current state.

JurisdictionCoverageNotes
England & WalesFullCPR, statutes, leading case law across civil practice areas.
Hong KongFullRHC/RDC, ordinances, CFA/CA/CFI authorities.
SingaporeStrong on commercialSICC and High Court commercial. Family and admin partial.
AustraliaFederal + NSW/VIC/QLD/WAOther states partial. Family Court of Australia covered.
United StatesFederal + NY/CA/DE/TXOther state law partial. State-by-state expansion ongoing.

What we shouldn't be used for

How fresh is the corpus?

The "Corpus as of" line beneath every chat response shows the most recent last_verified date in our authorities database — the real signal of when the corpus was last refreshed. Statutory amendments and very recent first-instance decisions may not be reflected. For time-critical questions, verify recency.

If we get it wrong

Every response in the chat has a "Report error" button. Clicking it captures the response and your correction into a moderation queue we read. We do not promise to amend the corpus on every report, but we read all of them and feed them into the tagging pipeline.

For a serious or urgent issue, email cases@commonbench.ai.


For the technical architecture, see the architecture page. For data protection, see Privacy. For commercial terms, see Terms of Service.