I
iManage
iManage is a cloud document and email management platform for law firms, corporate legal departments, financial services, accounting and government, built around iManage Work and extended by Share for external collaboration, Drive, Security Policy Manager for information barriers, Threat Manager, Records Manager and Disposition Manager for retention, Conflicts and Intake, Insight+ for knowledge search, Closing Folders for transaction management and Tracker for checklists. Its AI layer, sold as separate products on top of a standard cloud subscription and available only on the cloudimanage.com endpoint, is made up of AI Enrichment, which classifies documents and extracts data points at scale, and Ask iManage, a generative assistant that takes a natural-language question, interprets the intent, retrieves the relevant material from the firm's own repository and returns an answer with citations the user can open; it also extracts clauses verbatim, compares redlines, summarises documents, structures results into tables and applies a firm's own contract playbook, all without documents leaving the platform. A Model Context Protocol connection lets outside AI tools reach the same content under the firm's existing permissions. iManage states that by default neither it nor its third-party model providers use customer data in the iManage Cloud, including AI inputs and outputs, to train or retrain models, that content is encrypted and iManage does not have access to it, and that customers may separately opt in to services that collect limited insights. The published Cloud Services Agreement carries the security exhibit and the data protection agreement in full, commits to notice before compelled disclosure and sets out an unusual law-enforcement protocol. iManage LLC contracts from Chicago for customers outside Europe, the Middle East and Africa, and iManage EMEA Limited, registered in England and Wales, contracts for those regions; customer data is stored in the region named in the order.
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 are the engine of a core capability layered on a platform that stands entirely without them, and the vendor draws the line itself. The FAQ on the AI page states that Mailbox Assistant, AI Services and Ask iManage are not included in a standard cloud subscription and must be purchased as additional products, and that iManage AI is available only on the cloudimanage.com endpoint, with customers still being moved there. The platform underneath is a document and email management system with security, governance, records, conflicts, knowledge search, transaction management and workflow products, sold for decades and bought for that. AI Enrichment classifies and extracts at scale and Ask iManage answers questions from the repository; remove both and the DMS is unchanged. AI page and Ask iManage page read 7 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.
Grounding is real and documented with a described retrieval method, short of any published accuracy figure. The vendor sets out Ask iManage as a three-step process: it interprets intent and context from a natural-language prompt rather than keywords, identifies the most relevant material within iManage Work by relevance and context, and generates a natural-language answer anchored with citations so users can verify the sources. The product page states that answers are backed by citations to the firm's own work, that documents never leave the platform, and, in a comparison against general chatbots, that outputs are grounded rather than hallucinated because the system draws only from real documents. Nothing published measures how often that holds: no accuracy figure, no test set, no evaluation of any kind was located. The hallucination claim therefore stands alongside a described architecture rather than alone, so the bottom limb does not fire, and the missing measurement is what separates this from the top band. Two limbs do not apply to a product that cites the firm's own files rather than reported authority and are named rather than penalised. Ask iManage page, AI page and the January 2026 release coverage read 7 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.
Oversight rests on review surfaces rather than on a published control structure. What exists is real: every answer carries citations the user can open to verify the source, all AI interactions stay inside the governed platform with native enforcement of permissions and information barriers, and the vendor describes the result as explainable and auditable in regulated settings. What is not published is any statement of what the system does without a lawyer, any threshold at which it stops, or what happens after an output is wrong, and the May 2026 playbook analysis release describes the feature applying a firm's positions automatically to every contract review without addressing where review sits in that loop. Ask iManage page, AI page and the January and May 2026 release coverage read 7 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.
Real deployment evidence with substance, split between a measured deployment of the platform and unmeasured statements about the AI. The strongest item is the vendor's own release of 12 June 2025: Rio Tinto's legal function replaced a SharePoint-based system with iManage Work 10, Threat Manager and Share, more than 200 users across Australia, Singapore, the United Kingdom and North America, 4.5 million documents migrated, 80 per cent user engagement within four months of go-live with half the department classified as active users, and a named Digital Transformation Lead quoted. That is named, dated and quantified, but it measures the document management deployment, and the same release records Ask iManage as something the customer is exploring rather than running. For the AI itself the evidence is attributed and unmeasured: the Director of Information Technology at Jones Walker LLP on the January 2026 release, a manager at Rio Tinto in trade press, and a Senior Associate at Simpson Grierson describing a trial on the product page. No figure attaches to an AI outcome and no method is published for the 80 per cent. Rio Tinto release, Ask iManage page and January 2026 coverage read 7 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.
Substantive published commitments across most of the ground, short of the privilege limb the top band names separately. Customer Data is the customer's Confidential Information under section 6.1 and must be safeguarded in perpetuity under 6.3(c)(ii), which is a longer commitment than the five years the agreement gives other confidential information; the customer remains sole owner under 5.2; the AI page states that by default neither iManage nor its third-party model providers use customer data to train or retrain models, that data is encrypted and that iManage does not have access to the underlying content; segregation is documented at the level a firm requires, with Security Policy Manager selling information barriers as a product and the January 2026 release stating that AI interactions carry native enforcement of permissions, information barriers and security policies; retention and deletion are set out in the DPA; and Exhibit B records that each customer's data is logically separated from other customers'. Privilege and work product are not addressed on any surface located, which R33 treats as a required limb rather than a formality, and the training promise is prefaced "by default" with an opt-in whose scope is unpublished. Agreement, DPA and AI pages read 7 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.
No position on the advice line was located, for a product that answers legal questions from a firm's documents, extracts clauses, compares redlines and applies contract playbooks. The Cloud Services Agreement was read in full: it addresses acceptable use, warranties, indemnities and liability and says nothing about advice, competence or supervision, and its warranty disclaimer at 8.5 is a warranty disclaimer rather than a statement of what the product is and is not. The AI and Ask iManage pages carry no disclaimer. The website terms of service are not treated as the product's instrument, following the standing position that a website's terms do not grade the platform. One limb points the right way and is recorded rather than credited: the audience is unambiguous, since the agreement confines use to Authorized Users for the customer's internal business operations and every segment page addresses law firms, corporate legal, compliance and other professional functions, with no consumer surface. This records what is establishable on the date; a product-level acceptable use or AI policy, if one exists behind the trust centre, is the rebuttal route. Surfaces checked 7 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.
Principles are published without a mechanism a buyer could audit. The AI page states that the platform-based approach enables organisational data to be used securely, responsibly and ethically, whether by iManage or a third party, and the vendor publishes an ESG report and a diversity statement; trade coverage records the appointment of a Vice President of AI Engineering in 2026. Nothing located names who inside iManage is accountable for AI governance, describes what is tested before an AI capability ships, or discloses any finding about uneven output across matter types or populations, and no governance standard such as ISO 42001 was located. The Vanta-hosted trust centre would be the route to more and returns page metadata with no body on this channel, which is recorded as a retrieval limit and named as the rebuttal route rather than counted against the vendor. AI page and trust centre attempted 7 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.
Retention, deletion, access control, subprocessors and incident practice are all published, current and specific enough to hold the vendor to, and all of it sits in the agreement rather than on a marketing page. The DPA commits to notifying the customer of a Security Incident without undue delay and in any event within 48 hours, with investigation, information in phases, mitigation and assistance with the customer's own notification duties. Deletion is dated: the customer can access, extract and delete Customer Data at any time during the term, iManage retains it for 90 days after expiry so the customer can extract it, then disables the account and deletes within 30 days, certifying where law requires, with backups overwritten in the ordinary course and never held beyond 90 days. Exhibit B carries AES-256 encryption at rest, encrypted transit and backups, least-privilege access with unique usernames that are never recycled, lockout on repeated failures, monthly vulnerability testing, annual independent assessment against ISO 27001 and ISO 27017, annual third-party penetration testing, Tier 3 or better data centres and logical separation of each customer's data. Subprocessors are the limb most vendors miss and the one iManage publishes: a maintained list, 60 days' advance notice before a new subprocessor touches customer data, a 30-day objection right, four named cure routes and a termination remedy with pro-rata refund if the objection is not resolved. Agreement, Exhibit B and DPA read in full 7 September 2026; the subprocessor list itself refuses automated access and was read through the search index.
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.
What the vendor stands behind is published and specific, and in one respect it is better than the corpus norm. Section 9.1 gives a defence and indemnity against third-party claims that the Services infringe intellectual property rights, with three named exclusions, and 9.4 sets out the mitigation ladder of procuring the right, modifying or replacing the service, or terminating with a refund of the prepaid balance. Section 10.2 caps each party at the greater of twelve months' fees or fifty thousand US dollars, so a small customer has a floor rather than a cap equal to a small invoice, which is unusual in this corpus. Section 10.1 excludes consequential loss for both parties, and 10.3 lifts both the exclusion and the cap for fraud, for the indemnities, for negligence causing death or personal injury and for wilful misconduct. Section 8.3 warrants performance by qualified personnel to industry standards, that the Cloud Services are free of harmful code, and that they will perform substantially in accordance with the documentation. Exhibit A adds a 99.9 per cent availability commitment with a published service credit schedule and a right to terminate where availability falls below 99.0 per cent in three months of any six. No insurance is stated, and nothing addresses liability for a wrong AI output specifically. Agreement read in full 7 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.
Real integrations are named and their boundary is described, short of an implementer's account of what moves in which direction. The vendor publishes a Microsoft partnership page and describes a plug-in connecting Microsoft 365 with iManage while keeping the repository as the single source of truth, sells a Model Context Protocol connection as an open standard that lets AI and legal technology tools reach iManage content without custom connectors, and states in the January 2026 release that the same underlying AI services expose content to third-party applications through MCP with permissions and information barriers enforced and content never leaving the platform. Access software (ndOffice equivalents, mobility clients) is defined in the agreement, and the Rio Tinto release describes API integration between iManage and that customer's own digital legal hub with iManage as the core content layer. The agreement is candid that third-party products and any data transfer to them are between the customer and that provider, with no iManage warranty. What is not published on the surfaces read is per-integration depth; the MCP product page and partner directory were not read and are the route to more. Agreement, AI pages, MCP references and Rio Tinto release read 7 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.
The deployment model is stated clearly with partial residency detail, and the processing question is answered with unusual candour. Region is a defined term in the SLA, availability is measured and credited per region, and DPA 12.4 states that all Customer Data is stored in the geographic region set out in the applicable Order. The same clause then discloses what most vendors leave unsaid: iManage may provide the Services from regions other than the one in the Order, naming the United States, the United Kingdom, Canada, Australia and India, so iManage personnel in those locations may have access to Customer Data, and DPA 12.1 warns that this applies even where the customer has agreed to hosting in the EEA or the United Kingdom. Transfers out of the EEA and UK run on the 2021 Standard Contractual Clauses with the UK Addendum, incorporated by reference in Schedule 1. Tenancy is addressed in Exhibit B as logical separation of each customer's data. What is not published on the surfaces read is the list of regions a buyer can actually choose from, which sits behind the Order and on the unread Cloud page; the AI adds a further constraint the vendor states plainly, that iManage AI runs only on the cloudimanage.com endpoint. Agreement, DPA and AI page read 7 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.
Certification is real and contractually committed, short of evidence a buyer can reach without asking. Exhibit B binds iManage to adhere to information security practices at least as protective as ISO 27001 and ISO 27017 or equivalent standards, to have an independent third party assess those standards annually, to undergo annual independent penetration testing, and to maintain a business continuity plan compliant with ISO 22301. The route to proof is stated and gated: on request, not more than once a calendar year and subject to the agreement's confidentiality terms, iManage will make available its ISO 27001 certification and SOC 2 or SOC 3 reports; a customer may also commission its own audit once a year, at its own cost, through an accredited firm on twenty days' notice. No auditor, certificate number, audit period or report date was located, and the trust centre at compliance.imanage.com is a Vanta-hosted portal that returns page metadata with no body on this channel, so whether anything there is self-serve could not be established. That is recorded as a retrieval limit and the portal is the rebuttal route; the lower tier is graded with the reason stated. Exhibit B read in full and trust centre attempted 7 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 architecture is described and change notification is contractual; the model providers themselves are never named. What is published: AI processing stays on the iManage platform with content not moved outside it, the AI is available only on the cloudimanage.com endpoint, the subprocessor list names Microsoft Corporation (Azure), and the DPA commits to 60 days' advance notice before any new subprocessor touches customer data with an objection right and a termination remedy, which is a stronger change-notice mechanism than most records in this corpus carry. What is absent is the identity of whose models run: the AI page refers throughout to "our third-party model providers" without naming one, no model is named anywhere, and naming Azure identifies where processing happens rather than whose model it is. The Microsoft relationship is described in product terms, a Copilot plug-in and AI Services feeding Copilot, which is a different fact from the provider of the models behind Ask iManage. The B is earned on the architecture limb rather than the provider limb, and the gap is the one a client's AI clause asks about. AI page, agreement, DPA and subprocessor list (via search index) read 7 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.
The shape of the charge is visible and the number is not. Every path on the site ends at Book a Demo, and no price, band or unit figure appears on any page read. What is published is structure. The AI FAQ states that Mailbox Assistant, AI Services and Ask iManage are not included in a standard cloud subscription and must be purchased as additional products, which tells a buyer that AI is a separate line before any conversation. The product catalogue splits the platform into named modules a buyer can map to a quote. The agreement adds the mechanics: fees are set in the Order in a named currency, orders are non-cancellable and payments non-refundable, each order renews automatically for one-year terms unless either party gives 30 days' notice, late payment accrues 1.5 per cent per month, disputed fees must be raised within 30 days, and the SLA sets service credits as a percentage of one twelfth of the annual subscription fee. Section 3.2 confirms the licence is per-user by prohibiting multiple users sharing a per-user feature. Fees may also be set by a Partner rather than by iManage, which a buyer purchasing through a reseller should read. No VendorPricing row is written, since a row belongs to vendors graded A or B on this axis. Agreement and site read 7 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.
Segment coverage is described with real substance and the boundaries are left open. The site publishes separate pages for global, midsize and small law firms and for financial services, accounting, government, media and entertainment and other knowledge workers, alongside department pages for corporate legal, compliance, finance, human resources and knowledge management, and the customer evidence spans both a US law firm and a global corporate legal department. Practice coverage is described through the work the AI does rather than by practice area: repository-wide question answering, clause extraction, redline comparison, summarisation, structuring results into tables by attributes such as judges and jurisdictions, and applying a corporate legal team's contract playbook, with transaction work covered by Closing Folders. Nothing published states what is not supported: no practice area, jurisdiction or language is named as out of scope, and the one real limit the vendor does state is technical rather than practice-based, that AI capabilities exist only on the cloudimanage.com endpoint and that customers are still being migrated there. Segment pages, Ask iManage page and release coverage read 7 September 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.
A product page states no training and the published agreement carries no matching term. The AI page answers the question directly for both iManage and its model providers and extends the promise to AI inputs and outputs, adding that data in the cloud is encrypted and that iManage does not have access to the underlying content. Two qualifiers travel with it and are recorded here rather than smoothed over: the sentence is prefaced "by default", and the same answer discloses that customers may voluntarily opt in to certain services that let iManage collect limited insights for the sole purpose of improving those services, described as optional and disclosed at the time of use, with no published statement of what an insight is or whether it can reach document content. The Cloud Services Agreement and its Data Protection Agreement were read in full and never name training: processing is confined to Documented Instructions and to incidental business operations listed as delivering functionality, fixing problems and providing support, with a separate undertaking not to derive information from customer data for advertising or similar commercial purposes and never to sell personal data. A clause that does not name the thing is not evidence about training in either direction, so the policy statement carries the value. Agreement, DPA and AI page read 7 September 2026.
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 published for what a lawyer types. The vendor states that data processed by iManage AI stays on the platform under the same governance as everything else, which answers where it goes and not for how long. The document regime around it is precise and is recorded so a reader can see the gap rather than assume it is filled: under the Data Protection Agreement the customer can access, extract and delete Customer Data at any time during the term, iManage keeps it for 90 days after the subscription ends so the customer can extract it, then disables the account and deletes within 30 days, with backups never retained beyond 90 days, and the platform sells Records Manager and Disposition Manager for the customer's own retention policies. None of that is stated to apply to Ask iManage prompts and generated answers specifically, and no zero-retention option is offered anywhere located. Reading the repository regime across to the prompt question would be an inference the record should not make. AI page, agreement and DPA read 7 September 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Retrieval enforces the source system access model at query time, per user, and the vendor documents it.
Retrieval enforces the firm's own access model at query time and the vendor documents it, in the case where the vendor is itself the source system. The January 2026 Ask iManage release states that all AI interactions stay inside the governed platform with native enforcement of permissions, information barriers and security policies, that content is not moved outside the environment, and that the same applies to third-party tools reaching content through the Model Context Protocol. Security Policy Manager is sold as a product for building those barriers with multi-level security, and the product page describes the assistant as permission-aware and respecting access and metadata. What is not published is the enforcement point: whether a barrier is applied before the index is searched or filters results afterwards, which decides whether an agent can infer that walled content exists. Release text of January 2026, Ask iManage page and Security Policy Manager page read 7 September 2026.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Terms commit to notice where lawfully permitted. No transparency report located.
The agreement commits to notice where lawfully permitted, and goes considerably further than the value requires. Section 6.4 obliges the receiving party, before disclosing compelled confidential information, to notify the disclosing party in writing so it can oppose the disclosure or seek a protective order, and to give reasonable assistance in doing so, with any disclosure limited to the portion legally required. Section 6.5 adds a law-enforcement protocol specific to iManage: it will not disclose to law enforcement unless required by law, will attempt to redirect the agency to request the data from the customer directly, and if compelled will notify the customer and provide a copy of the demand, assess the legitimacy of the request including the sender's identity, seek clarification of scope and oppose blanket requests, while refusing to give any agency unfettered access, the platform encryption keys or the ability to break the encryption, or access where iManage knows the data is to be used for purposes other than those stated. No transparency report or request statistics were located, which is the only thing separating this from the top value. Agreement read in full 7 September 2026.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Sources are identified without stating the licence or rights basis.
The source behind the answers is identified and no licence basis is stated because none is the vendor's to give. Ask iManage answers from the firm's own repository and cites back to it, and the vendor's comparison against general chatbots turns on exactly that, that it uses the firm's actual documents and never leaves iManage Work. No external corpus of law, filings or public material was located anywhere in the product, and no third-party content source is named. The rights basis for the material the AI reads sits in the agreement rather than in a licence: section 8.4 has the customer warrant that it has the necessary rights and consents in the Customer Data, and section 5.2 leaves ownership with the customer. The signal's law-corpus limbs do not bite for a product whose corpus is the buyer's own filing system, and that is recorded rather than graded around. Ask iManage page and agreement read 7 September 2026.
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.
No located public material addresses whether authority is checked for subsequent history. The assistant answers from the firm's own documents and emails and cites to them; nothing read describes a citator, a treatment signal or a prompt to verify legal authority, and the product does not claim to retrieve reported cases. A firm using Ask iManage to find a precedent in its own files would still be relying on a separate research tool for good-law status. The signal's limbs bite only partly for a document management assistant, and that is stated rather than treated as a failure. Ask iManage page, AI page and January 2026 release coverage checked 7 September 2026.
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.
No located public material describes what the product does when it cannot ground an answer. The published three-step method covers interpreting the question, retrieving the most relevant material and generating a cited answer, and stops there; the product page asserts grounded outputs rather than hallucinations because the system draws only from real documents, which is a claim about the corpus rather than a described abstention path. No confidence score, no no-answer state and no evaluation showing either was located. Ask iManage page, AI page and release coverage checked 7 September 2026.
Fabricated Citation Record
Does a public court record exist involving output from this product?
No court order, opinion or disciplinary record naming this product has been located as of the date shown. This is a statement about the public record, not a finding about the product.
No court order, opinion or disciplinary record naming iManage or Ask iManage was located as of 7 September 2026. The AI Hallucination Cases database maintained by Damien Charlotin was searched on both names together with a general search of the sanctions coverage; the decisions that name legal-specific products name other vendors. This is a statement about the public record, not a finding about the product. Exposure is structurally low for an assistant that answers from a firm's own repository and cites to documents the firm already holds rather than generating legal authority.
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.
Professional obligations are engaged in general terms and no AI guidance is named. The vendor frames the AI around explainable and auditable outcomes in regulated settings, information barriers and conflicts management, and states that its platform approach lets organisational data be used securely, responsibly and ethically; its essay series addresses how law firms should approach AI adoption. None of it names an ABA formal opinion, a state bar opinion, a regulator's AI guidance or a court's standing order. The professional-responsibility material that does exist is about confidentiality and conflicts, which is credited where it belongs on the walls signal and on confidentiality rather than counted twice here. AI page, Ask iManage page, essay listings and January 2026 release coverage checked 7 September 2026.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
The product sits inside law firms' fee relationships with their clients and the published position on the bill is a savings claim. The AI is sold on accelerated productivity, reduced manual effort and time reclaimed for higher-value work, and the January 2026 release describes attorneys reaching an answer instead of wading through search results; the platform is sold to law firms that bill clients for the work it speeds up. Nothing located addresses how AI-assisted work is recorded against a matter, whether compressed time is disclosed to the client, or what a firm should say when research that took hours now takes minutes. The vendor sells time-recording adjacent products and a conflicts and intake product, and neither is presented as answering the fee question. Ask iManage page, AI page and release coverage checked 7 September 2026.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
A current subprocessor or model provider list is published.
A current subprocessor list is published with contractual change notice, and the model provider is not named. What a firm can forward today: a maintained subprocessor page naming Microsoft Corporation (Azure) with an email subscription for change notices; a Data Protection Agreement published in full as Exhibit C to the public Cloud Services Agreement, with the 2021 Standard Contractual Clauses and the UK Addendum incorporated in its schedule, which is drafted to be passed to a client; and a security exhibit setting out the controls. The DPA commits to 60 days' advance notice before a new subprocessor touches customer data, a 30-day objection right and a termination remedy if the objection is not cured, which is stronger than most agreements in this corpus offer. The limb that fails is the one a client's AI clause turns on: the AI page refers to "our third-party model providers" and never names them, and naming Azure states where processing runs rather than whose model reads the documents, so a firm can prove its contracting position and cannot answer the model question. Agreement, DPA and subprocessor list (via search index) read 7 September 2026.
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.
Elements of a record exist without an export built for disclosure. Each answer is anchored with citations so a user can verify the sources it rests on, the vendor describes AI outcomes as explainable and auditable in regulated settings, and the platform sells Threat Manager for monitoring user activity and audit reporting across the repository. Between them a firm can show which documents an answer drew on and who accessed what. What is not published is a per-document export covering the model used, the retrieval performed and the human verification applied, and no disclosure template or guidance for a court's standing order on AI use was located. January 2026 release coverage, Ask iManage page and product catalogue checked 7 September 2026.