What it is

Ask The Beagle is a legal research tool for anyone who wants to understand UK law, not just lawyers. Most people go their whole lives being governed by rules they've never read: what a public body is actually allowed to do, what a piece of legislation really requires of them, what rights they hold under it. Ask The Beagle searches the actual text of UK legislation, case law, Hansard debates, and constitutional sources, and answers questions from what it finds there, with citations back to the original, so you can read the source for yourself rather than take the tool's word for it.

Why it exists

UK law is public. The Acts of Parliament, the Supreme Court's judgments, the constitutional documents that constrain how the state can treat you: none of it is secret. But "publicly available" isn't the same as "genuinely accessible." It's dense, scattered across dozens of separate sources, cross-referenced in ways that assume you already know where to look, and written in a register aimed at lawyers rather than the people it actually governs. That's true whether you're trying to understand a letter from HMRC, work out what a new Act actually changes for you, or check whether a public body has the power to do what it's just done to you. Ask The Beagle exists to close that gap, not by replacing legal advice, but by making the underlying sources themselves searchable, readable, and traceable, so that understanding your own rights and obligations doesn't require a law degree.

The core commitment

Every answer this tool gives traces to an actual, cited source: an Act, a judgment, a Hansard debate, a constitutional document. Never invented, never hardcoded, never filled in from general training knowledge dressed up as a citation. If the library doesn't contain something relevant to a question, the honest answer is that it doesn't, not a plausible-sounding guess. This isn't a footnote or a compliance disclaimer; it's the defining design principle the whole tool is built around, and it shapes every retrieval decision described on the How It Works page.

Why a beagle

A beagle is a dog bred for one job: pick up a scent and follow it, methodically, all the way back to its source, without losing the trail. That's the actual retrieval approach behind every answer here, not a mascot chosen for its own sake. "I sniff out the answers you need" describes what the tool does, not just how it's branded.

Source-first, not general knowledge

When you ask a question, the tool searches the actual text of legislation, UK Supreme Court judgments, Hansard debates, and constitutional documents already ingested into its library, and builds its answer only from what that search finds, with a citation back to the specific source for every claim. It does not answer from general legal knowledge dressed up as if it came from a source. Where a question touches something the library genuinely doesn't cover, the honest answer is that the tool doesn't have a source for it, not an invented one.

What's in the library right now

Legislation and constitutional documents (Acts of Parliament, treaties, common law principles, legal maxims, statutory oaths), Hansard parliamentary debates, and UK Supreme Court judgments from … onward. The court itself didn't exist before 1 October 2009, replacing the House of Lords Appellate Committee, so that isn't a gap in coverage: it's the court's own history.

What's not yet included: case law from courts below the Supreme Court, and (for the same reason) judgments from before the Supreme Court existed. Arguments identified by this tool may already have been considered by courts not yet in this system.

What "Plain English" means here

When a section of legislation is shown in Plain English, an AI model rewords that section into ordinary, everyday language, in one or two short paragraphs, using only what the section itself states. That's a genuine rewording, not a summary and not an explanation of legal doctrine: it's built to make dense statutory sentences easier to read, not to preserve or spell out the specific legal meaning of any technical term inside them.

That matters most for terms of art: words that mean something narrower, or different, in law than they do in ordinary speech. "Reasonable" in a statute usually invokes an objective legal standard, not just "seems fair to me"; "malice" in defamation law is a specific test about knowledge of falsity, not everyday spite; "consideration" in contract law is a specific bargained-for exchange, not just a reason for doing something. The Plain English version doesn't reliably flag any of that: it typically swaps the term for an ordinary-sounding synonym (as with "reasonable"), or drops the concept altogether where the surrounding sentence gets rephrased around it (as with "consideration"), rather than explaining what the word is actually doing in law.

So treat Plain English as a reading aid for the shape of a provision, not as a restatement of its legal effect. Where a term of art is doing real work in a provision that matters to you, the original legislative text, and any case law interpreting that specific term, remain the authoritative source, not the Plain English rewording.

What you can ask it

• Ask a question in plain English: the general-purpose starting point. No need to pick an Act first; ask about your situation and it searches across the whole library for what's relevant.
• Get an Act translated into plain English: turn dense statutory drafting into a plain-language explanation of what a provision actually requires, grounded in the Act's own wording and any official definitions.
• Check for a constitutional conflict: see whether a specific Act's provisions sit uneasily against the Human Rights Act, Magna Carta, the Bill of Rights, or other constitutional sources, with real case law on point where it exists.
• Find the exceptions: surface every stated exception, exemption, or defence in an Act, so you're not relying on the general rule alone if a carve-out actually applies to you.
• Assess judicial review grounds: understand the grounds on which a decision or a piece of legislation could be challenged (illegality, irrationality, procedural unfairness, human rights), the procedure, and realistic prospects, grounded in real case law.
• Find gaps in the drafting: undefined powers, provisions that let a Minister change the law without full Parliamentary process, rights with no stated remedy, and similar structural weaknesses in an Act.
• Find where two Acts conflict: surface provisions in different Acts that contradict each other or can't sensibly both apply, and whether a court has already resolved that tension.
• See who a law actually benefits: identify private interests an Act serves beyond its stated public purpose, grounded in the Act's own explanatory notes, the Parliamentary debate around it, and case law; useful wherever the real motive behind a power matters to your situation.
• Map out who owes what to whom: every duty an Act creates, who's meant to enforce it, what the penalty is for breaking it, and where that enforcement is missing entirely.
• See how an Act has been amended over time: which later Acts have modified an earlier one, and whether that was done openly or left to be inferred.

What it isn't