RulesBook UK: AI Document & Policy Assistant
A document-assistance experience designed to help people understand contracts, policies and possible obligations more clearly.
RulesBook UK (rulebookuk.com) publicly describes a tool for uploading contracts, policies and agreements to receive plain-English summaries, risk alerts and UK law citations. This case study was requested for KTD’s Work section, but the public site does not independently establish KTD’s role, delivery scope or results. The discovery, design and technical approach below are illustrative considerations, not claims about how the live product was built.
RulesBook UK (rulebookuk.com) publicly describes a tool for uploading contracts, policies and agreements to receive plain-English summaries, risk alerts and UK law citations. This case study was requested for KTD’s Work section, but the public site does not independently establish KTD’s role, delivery scope or results. The discovery, design and technical approach below are illustrative considerations, not claims about how the live product was built.
Objective / problem
The public product addresses a familiar problem: contracts and policies can be difficult to read, compare and act on. Users need a way to identify key clauses and questions for further review without mistaking an AI summary for legal advice.
Discovery
For a product of this kind, discovery should identify the document types people bring, the questions they ask, the jurisdictions involved and the point at which qualified legal review is required. These are design considerations; KTD’s actual discovery work has not been documented.
Strategy
A responsible approach would make the original document the source of truth, put explanations in plain English, show relevant citations where available and make uncertainty visible. Users should be able to check a claim against its source instead of trusting an unqualified answer.
UX/UI
An interface should keep the document, summary, flagged passages and follow-up questions easy to distinguish. Clear labels, readable citations, error states and an explicit reminder that generated explanations require checking are especially important for legal material.
Technical approach
Potential implementation considerations include authorised uploads, document parsing, retrieval against appropriate legal sources, citation linking, access control, retention policies and checks for unsupported or outdated statements. These are illustrative architecture considerations, not confirmed details of the live system.
Architecture / workflow
Illustrative sequence showing how the proposed experience could connect. It is not a screenshot or a documented client implementation.
Solution
The public-facing RulesBook UK site presents document analysis with plain-English summaries, risk alerts and UK law citations. The workflow shown here is a conceptual explanation of this type of service; it is not a verified account of KTD’s implementation.
SEO considerations
A public product page can explain supported document types and limits in crawlable text. Uploaded documents, personal data and private analysis must not be exposed to search engines. Legal information should be reviewed for accuracy and currency.
Mobile considerations
Document review on a phone calls for legible passages, expandable citations, clear navigation between source and explanation and no cramped side-by-side comparison.
Lessons and trade-offs
For legal-document assistance, useful explanations are only part of the experience. Source traceability, privacy, uncertainty and routes to human expertise matter just as much. These are product-design lessons, not measured project outcomes.
Questions worth asking
Does RulesBook UK provide legal advice?
Its public website describes plain-English document summaries, risk alerts and UK law citations. Do not rely on an AI explanation as a substitute for advice from a qualified legal professional about your circumstances.
Was this product built by KTD?
This Work page was added at KTD’s request. The public RulesBook UK website does not independently verify KTD’s role or the scope of any work, so no delivery claim is made here.
Is the workflow diagram the live system architecture?
No. It illustrates considerations for this kind of document-assistance product; the live architecture has not been verified.
What would this look like for your business?
Tell us what needs to work better. We’ll help decide what is worth building.