L
Legal Decoder
Legal Decoder analyses legal invoices for corporate legal departments, law firms and bankruptcy fee examiners. Its technology reads the billing narrative itself rather than the UTBMS code, breaking each line item into structured data and checking it against more than 45 proprietary compliance flags grouped into staffing efficiency, workflow efficiency and billing hygiene, so a reviewer can see block billing, skill-set mismatches, internal conference time, file churning and vague entries at line-item level.
Compliance Decoder enforces outside counsel guidelines and flags billing anomalies before invoices are approved; Pricing Decoder benchmarks rates and builds pricing and budget models from historical invoice data; and Aperture, released in 2026, is a natural language interface over the same structured data, where AI agents work out which data and calculations a question needs while a separate deterministic engine does the arithmetic, and identifying fields such as matter, client and attorney names are tokenised before anything reaches the model.
The company publishes retrospective analyses of public Chapter 11 fee applications, including the Allied Nevada Gold and Toys "R" Us cases. Legal Decoder, Inc. is a Delaware corporation based in Falls Church, Virginia.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The models turn billing prose into data, and a rules engine does the judging. Legal Decoder's own framing is that UTBMS codes tell you what was billed but not what happened, so its technology reads the narrative itself: entries are parsed, categorised, enriched, standardised and then evaluated against more than 45 proprietary compliance flags. Aperture adds a natural language interface on top, and the vendor is explicit that the AI agents decide what data and calculations a question needs while a separate deterministic engine does the arithmetic.
Underneath the language work sits an analytics platform of flags, benchmarks and indices that would still run on structured invoice feeds without any model reading prose. Verified 20 September 2026.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
The method is described in detail and the performance is not measured. Aperture's published answers show an Analysis Request Breakdown setting out the data used for the response, every figure is computed by a deterministic engine rather than the model, and the underlying flags are documented down to the individual rule, with worked examples in the published bankruptcy retrospective showing which entries triggered which flag and why.
What is asserted rather than tested is quality: the site describes the methodology as court-validated and says Legal Decoder is the only invoice review technology accepted at the federal court level, without citing a decision or naming a court, and no accuracy, false-positive or agreement rate for the flags is published. Verified 20 September 2026.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
The product flags and a person decides, and the review surface is the flag itself. Every flag attaches to an individual line item with the rule that fired, and users drill from an index category to a timekeeper to the entry, so each conclusion can be checked against the billing record behind it. Aperture is described as sticking to observations and suggested next steps by default and producing a specific action plan only when asked, and users hold read-only permissions, so nothing in the analysis can alter the underlying billing data.
What is not published is any threshold or confidence level at which a flag fires, or guidance on what a flagged entry may not be used for when it becomes the basis of a fee objection or a write-down. Verified 20 September 2026.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
The numbers are real and the customers are not named. The published Allied Nevada Gold retrospective analyses a named Chapter 11 case: over fifty invoices and 2,000 pages covering 10.7 million dollars in fees, 14,755 line items and 135 timekeepers across eight named law firms, with over 21,000 flags and roughly 2.4 million dollars identified as unrealised savings, and firm-by-firm findings set out with percentages. That is a demonstration on public court filings rather than a customer deployment; the firms analysed are the subjects, not the buyers.
The other success stories, including an AmLaw 100 firm's risk management programme and the Toys "R" Us fee review, describe the customer only by segment, and the homepage quotes are attributed to roles rather than people. Verified 20 September 2026.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
The confidentiality commitments are specific to the one thing this product handles, and they live outside any agreement a buyer can read. Invoice narratives describe matters, clients and strategy, and Aperture's published answers address that directly: identifying fields such as matter, client and attorney names are tokenised before any data reaches the model, so the model sees strings like Matter_ABCDEF, tokens cannot be reverse-engineered, and new identifiers are generated per session rather than held in a persistent vault; results are remapped inside Legal Decoder's own environment.
The vendor also states that data is never used to train models and that users hold read-only permissions. Nothing published addresses separation between customers, privilege or work product in the narratives, and both the Terms of Use and the Privacy Policy state that client processing is governed by separate master services and data processing agreements that are not published. Verified 20 September 2026.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
The line between analysis and judgement is drawn in the vendor's own words. The published methodology states that the technology neither provides legal advice nor operates as a referendum on the quality of legal services provided or the outcome delivered by outside counsel, which is the relevant disclaimer for a product whose output is used to challenge another lawyer's fees, and the Terms of Use dated 21 January 2026 add that website content is not legal advice and creates no attorney-client relationship.
What is missing is the other half: nothing addresses the duty of the person acting on a flag, whether a fee examiner, a general counsel or a billing partner, or what review a flagged entry should get before it becomes an objection or a write-off. Verified 20 September 2026.
AI Governance and Bias Disclosure
Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
How the system works is explained; how it is governed is not. The Aperture material is unusually open about mechanism, setting out that the model plans the analysis and never calculates, that tokenisation happens before processing, and that the underlying data is parsed, categorised, enriched, standardised and evaluated in sequence. Nobody inside Legal Decoder is named as accountable for the flags or the models, nothing describes what is tested before a rule or release ships, no evaluation results are published, and nothing addresses whether flags fall unevenly across practice areas, firm sizes or timekeeper seniority, which matters for a product whose output is used to question individual lawyers' bills.
Checked the homepage, the Aperture, Compliance Decoder and Partners pages, the success stories, the Terms of Use and the Privacy Policy on 20 September 2026. Verified 20 September 2026.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
One question is answered precisely and the rest are not. The Aperture material says the product is not a system of record and does not store, own or act as the repository for billing information, which should remain in the customer's e-billing or matter management system, and that users have read-only access. Beyond that, no retention period for what Legal Decoder does hold, no deletion commitment, no encryption statement, no subprocessor list and no incident practice was located; there is no security or trust page anywhere on the estate, and the Privacy Policy dated 21 January 2026 covers website visitors and marketing only, stating that client processing sits under separate agreements that are not published. Verified 20 September 2026.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
Nothing published says who bears the loss if a flag is wrong. The Terms of Use dated 21 January 2026 govern the website: they disclaim warranties, exclude indirect and consequential damages and require the user to indemnify Legal Decoder, and they address the website rather than the analysis a customer buys. The Privacy Policy points client processing to master services and data processing agreements which are not published, and no warranty, indemnity, cap or insurance position covering the product was located.
For a product whose output is used to reduce another party's fees, nothing addresses the consequences of a mistaken flag. Checked the Terms of Use, the Privacy Policy, the product pages and the Partners page on 20 September 2026. Verified 20 September 2026.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
No integration into the systems legal billing already runs through was located. Aperture is described as a complementary analytics layer rather than a replacement for an e-billing or enterprise legal management system, and the customer's system is expected to remain the system of record, but nothing names a single one of those systems, describes how invoice data reaches Legal Decoder, or documents an API, file format or connector.
There is no integrations page and no developer documentation; the Partners page describes commercial partnerships with alternative legal service providers and consultancies rather than technical connections. Checked the homepage, the Aperture, Compliance Decoder and Partners pages, the success stories, the Terms of Use and the Privacy Policy on 20 September 2026. Verified 20 September 2026.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Nothing published says where the software runs or where invoice data is held. The product is reached through a web portal, and no tenancy model, hosting provider, region or residency option appears anywhere; the Privacy Policy addresses website data and says nothing about where client processing happens. Buyers in this market routinely send an entire outside counsel spend file, which makes the absence a live question for a procurement review.
Checked the homepage, the Aperture, Compliance Decoder and Partners pages, the success stories, the Terms of Use and the Privacy Policy on 20 September 2026. Verified 20 September 2026.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
No independent security attestation was located. There is no security page and no trust centre on the estate, and no SOC 2, ISO 27001, penetration test or named auditor is mentioned on any page; the only security language is the Privacy Policy's statement that reasonable administrative, technical and physical safeguards are maintained and that no system is completely secure. Checked the homepage, the Aperture, Compliance Decoder and Partners pages, the success stories, the news and blog indexes, the Terms of Use and the Privacy Policy on 20 September 2026. Verified 20 September 2026.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
The model is referred to and never identified. The Aperture material describes data being sent to an LLM after tokenisation and says potentially sensitive fields are protected before any data reaches the AI model, which tells a buyer that a third-party model is in use without saying whose. No model, version or provider is named, nothing states where inference runs, and no commitment to notify customers when the model changes was located.
The vendor's own distinction, that the model plans and explains while a deterministic engine computes, limits what the unnamed model actually decides. Verified 20 September 2026.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
No price, rate or unit of charge is published. Checked the homepage, the Aperture, Compliance Decoder, Pricing Decoder and Partners pages, the three buyer pages, the success stories, the news and blog indexes, the Terms of Use and the Privacy Policy on 20 September 2026: there is no pricing page, no tier, no per-invoice or per-dollar-reviewed rate and no trial, and every route ends at a scheduled call. Pricing Decoder is a product for pricing legal work, not a statement of what Legal Decoder costs. Verified 20 September 2026.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Three buyers are addressed with separate pages and different arguments: corporate legal teams justifying outside counsel spend, law firms defending rates and realisation, and bankruptcy fee examiners reviewing fee applications, with the bankruptcy work documented in detail against the US Trustee Program's 2013 guidelines. The analytical coverage is specific too, with the flag set organised into staffing efficiency, workflow efficiency and billing hygiene and individual rules named.
What is not stated is the boundary: nothing says which billing formats, jurisdictions, languages or alternative fee arrangements the analysis handles poorly, or what happens with non-hourly billing. Verified 20 September 2026.
5 public documents
The public pages on file for Legal Decoder, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
legaldecoder.com/aperture3 signals
Client Data in Training, Prompt and Output Retention, Court Disclosure Support
Read Sep 20, 2026
-
legaldecoder.com/privacy-policy2 signals
Third Party Request and Subpoena Notice, Outside Counsel Guideline Readiness
Read Sep 20, 2026
-
Fabricated Citation Record
Read Sep 20, 2026
-
legaldecoder.com1 signal
Billing and Fee Posture
Read Sep 20, 2026
-
Bar Guidance Alignment
Read Sep 20, 2026
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A public policy or trust page states no training on customer content, with no matching term located in the published agreement.
The Aperture page answers the question directly: data processed through Legal Decoder's analytics engine and Aperture is used solely for the customer's own business purposes and is never used to train models. The commitment sits on a product page; the agreements that govern client processing, named in the Privacy Policy as master services and data processing agreements, are not published.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Retention is acknowledged in public materials with no stated period.
Retention is acknowledged and no period is given. Legal Decoder says Aperture is not a system of record and does not store, own or act as the repository for billing information, which should stay in the customer's e-billing system, and that tokens identifying matters and people are regenerated each session rather than kept in a persistent vault. No retention window for the analysis, the queries or the structured data Legal Decoder does hold is published, and no deletion commitment on termination was located.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
No located public material addresses walls or matter level segregation.
Checked the homepage, the Aperture, Compliance Decoder and Partners pages, the success stories, the Terms of Use and the Privacy Policy on 20 September 2026. Users are described as having read-only permissions, which prevents changes to data rather than restricting what they can see. Nothing addresses separation between matters, teams or customers, which matters where one platform holds spend data for multiple clients of the same firm.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Published terms or policy address disclosure to authorities or in response to legal process, and no commitment or reservation regarding customer notice is located anywhere. The vendor has told the customer that data can leave and has said nothing about whether the customer hears of it.
The Privacy Policy dated 21 January 2026 says information may be disclosed to comply with legal obligations or lawful requests and to protect Legal Decoder's rights, and makes no commitment about notifying anyone. It applies to website visitors and marketing only, so nothing published addresses what happens if Legal Decoder is served for a customer's invoice data.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
Checked the homepage, the Aperture, Compliance Decoder and Partners pages and the success stories on 20 September 2026. The product analyses the customer's own invoices against benchmarks the vendor says are built from tens of billions of dollars in legal fees analysed; no primary law corpus is involved, and the composition, sourcing or permissions behind the benchmark data are not described.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
Checked the same pages on 20 September 2026. The product analyses billing data rather than citing legal authority, so no subsequent-history check arises and none is described.
Refusal and Uncertainty Behaviour
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
Checked the homepage, the Aperture page and its published questions and answers, the Compliance Decoder page and the success stories on 20 September 2026. Nothing describes what Aperture does when a question cannot be answered from the data, and no confidence level is attached to a flag or an answer. The related published control is that the model never calculates: an Analysis Request Breakdown shows the data used and a deterministic engine produces the figures.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
Searched the AI Hallucination Cases database maintained by Damien Charlotin on 20 September 2026 on the names Legal Decoder and Aperture. No court order, opinion or disciplinary record naming the product was located. This is a statement about the public record rather than a finding about the product.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Public materials refer to professional responsibility in general terms without naming guidance.
The published bankruptcy material works through the fee standards its buyers answer to: the six-factor reasonableness of compensation test in section 330 of the Bankruptcy Code and the US Trustee Program's 2013 guidelines for reviewing fee applications in larger Chapter 11 cases, with the vendor mapping each problematic billing practice named in those guidelines to a flag in its own system. That is engagement with named professional standards on fees rather than with an ethics opinion on the use of AI, and no bar opinion is named anywhere on the estate.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
The buyer is the payer, not the biller. The product exists to review, author or benchmark legal fees, so the record of fees is the product itself rather than a byproduct of AI assisted lawyering. Typically sold to in-house teams paying outside counsel.
The fee record is the product. Legal Decoder exists to examine what was billed and whether it was reasonable, for corporate legal teams paying outside counsel, for fee examiners reviewing Chapter 11 applications, and for firms testing their own invoices before a client does. The published output is an account of billing behaviour at line-item level rather than a byproduct of AI-assisted lawyering, and both sides of the invoice are addressed on their own pages.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The material exists behind a sales conversation or an executed agreement.
The Privacy Policy states that client processing is governed by separate master services and data processing agreements, so the material exists but only for a customer who is already in a contract. No subprocessor list, model provider list or client-facing disclosure pack is published, and there is no trust page or self-serve route to request one.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Some elements of the record are available, short of a document level export.
Some elements of a record are published, built for a fee proceeding rather than for an AI disclosure. Every flag ties to the line item and rule that produced it, Aperture shows an Analysis Request Breakdown of the data behind each answer, and responses export to PDF, Word or CSV with the underlying data included. Nothing records which model was involved in producing an answer or who reviewed it before it was used.