N

NetDocuments

The models power a core capability on a product that stands without them. NetDocuments is a cloud document and email management system sold for twenty five years. The ndMAX suite adds a Legal AI Assistant, AI Search, Tabular Review, an App Builder and a library of ready made legal apps. Smart Answers, which began rolling out to ndMAX Enterprise customers on 31 March 2026, answers questions from the firm's repository with citations.

The vendor frames this as bringing AI to the content rather than taking content to AI. Its press material says more than 800 firms began using the AI capabilities in 2025 and over forty percent of new customers choose AI at purchase, which describes an option on a platform rather than the platform itself. Remove the models and the document management, email management, search, security and collaboration product remains, and that is what most of the 7,000 organizations bought.

Measured accuracy is published, with the test set described and failure modes named. The Legal Context Engineering Benchmark, published 18 August 2026 by the VP of Product, reports quality scores out of 100 for the vendor's own AI answers across three model tiers. Without the Legal Context Graph they are 64.0, 67.4 and 73.9; with it, 65.1, 69.0 and 75.4. Correct answer counts out of 300 and the cost of a correct answer are also given.

The test set has 300 questions across ten real matters, five transactional and five litigation, built from public filings and court dockets partly outside the models' training cutoff. It covers 874 documents and about sixty million characters, with nothing synthetic, six named question types including Unanswerable, and a rubric for each question. Citations are checked automatically against the documents, with human spot checks.

A worked example shows the product's own answer failing all three criteria without the context layer and still failing one with it. The method is published for firms to rerun. It is the vendor's own benchmark, not third party validation, and the appendix with per matter scorecards was not opened.

Autonomy is described, and oversight rests on product features rather than a published control structure. The vendor says the best AI apps run automatically in the background based on a user's actions, and MCP connectivity lets external agents run workflows across systems, which is a real claim of unattended operation. On the oversight side, answers carry citations a lawyer can open, and Exhibit B commits to document level activity logs reviewable for ninety days.

Administrators control which users and applications reach what through the Customer Service Account. The benchmark report tells readers to read some of the answers themselves before believing any of the numbers. No located material says the models work alongside a supervising lawyer, names the point at which an app acts without one, or says what happens when an output is wrong. The Our Approach to AI video on the Legal AI page was not viewed and may say more.

Customers are named with a figure, but deployments are undated and the method is not given. On the Legal AI page, Jared Gullbergh of Buchanan says a single AI app was calculated to save over 1,500 hours of work a year while producing better work product. Charly Duffy of Coghlan Duffy speaks on the App Builder, and Jeff Sabado, Director of Knowledge Management at Davis Wright Tremaine, says the tools already respect the firm's client and matter based security and ethical walls.

Company figures are published without reference to any deployment: more than 7,000 organizations served, more than 800 firms starting to use the AI in 2025, over forty percent of new customers choosing AI at purchase, and more than 150 integrations. No deployment is dated, and the basis for the 1,500 hour figure is not published, so a reader cannot assess how it was reached.

Binding commitments cover most of the ground, and privilege is not addressed. Under the agreement, Customer Repository Data is confidential and NetDocuments disclaims ownership of it (5.2.1). Use is limited to providing the Services, supporting third party applications the customer selects, help desk support the customer starts, and legal demands (5.2.2). Ethical walls are a documented product with access controls at user, document and workspace level, and the vendor says the AI works inside a firm's existing permissions and walls.

The ndMAX FAQ says inputs and outputs are not kept beyond producing the answer and are not used to train the model. The position on the model provider is explicit, including an agreement with Microsoft that keeps customer content out of abuse monitoring. Two gaps remain. Privilege and work product are not addressed anywhere located. The training statement covers the LLM rather than NetDocuments' own use, which is the narrower promise.

No position on the advice line is published on any page read, for a product whose AI apps analyze NDAs, assess contract risk, produce judge analytics and answer questions about a matter. The Software as a Service Agreement, read in full, covers use restrictions, AI restrictions on the customer, warranties and liability without touching advice, competence or supervision. Section 9.4 disclaims that results will meet any requirement, which is a warranty disclaimer, not a statement of what the product is and is not.

The Legal AI, App Builder and Ethical Walls pages carry no disclaimer. The audience is clear: every segment page addresses law firms, corporate legal departments and public sector legal teams, and the agreement limits use to internal business purposes by named users, so there is no consumer surface. The full Terms of Use were seen only in a search excerpt and may say more.

The published material has an owner and a testing regime, but no governance framework and no bias disclosure. The Legal Context Engineering Benchmark is a signed technical report by the VP of Product describing what is tested and how. It includes a test harness that compares the two tool setups before a run and refuses to proceed if they differ in anything but the capability under test. Citations are checked automatically against the source documents, with human spot checks, and the method is published for others to apply.

The report also states its own limits. It does not yet measure change over a matter's life, it withholds the context build cost because that varied about sixfold across ten matters, and it was drafted with AI assistance. No responsible AI framework, policy or standard such as ISO 42001 is published. Nobody is named as accountable for AI governance, as distinct from authoring the benchmark, and nothing addresses uneven output across matter types or populations. The appendix PDF with per matter scorecards was not opened and may say more.

Exhibit B of the Software as a Service Agreement covers most of the ground in binding terms, but no subprocessor list is published. NetDocuments must report confirmed Unauthorized Access to the customer without unreasonable delay and within 24 hours, with a root cause analysis and mitigation plan. Customer Repository Data is encrypted in transit and at rest, and access follows least privilege, removed when employment ends.

Independent penetration tests run at least twice a year, with monthly internal and external vulnerability scans. Document and administrative activity logs are reviewable by the customer for ninety days, and NetDocuments keeps log information for at least a year. Data is stored across two or more geographically separate data centers, with a two hour recovery point and six hour recovery time. Under section 7.4 the customer is responsible for export, and NetDocuments may destroy remaining data thirty days after the term ends.

Section 12.2 permits Common Subcontractors and promises notice of material changes without naming them; Microsoft, for the AI, is the only processor named anywhere.

What the vendor stands behind is published and specific. Section 11.1 of the Software as a Service Agreement gives a defense and indemnity against third party claims that the Services infringe intellectual property, with three named exclusions and modify, license or terminate remedies at 11.3.3. Section 10.3 caps each party at the annualized subscription fee paid or payable at the time of the event, with indemnities carved out of the cap.

Section 10.1 excludes indirect and consequential loss, and 10.4 preserves liability for death or personal injury caused by negligence and for fraud. Section 9.2 warrants professional and competent performance, and Exhibit A publishes a 99.9 percent availability target with graduated service credits. No insurance is stated. One asymmetry is worth reading before signing. Section 10.1 removes every liability limit for a customer's breach of the AI Restrictions in section 3.5, so NetDocuments may recover lost profits and all indirect and consequential damages without a cap, while the customer's own recovery stays capped at a year of fees.

Real, documented integrations are named across the systems legal work uses, but not what moves in which direction. The vendor says the platform integrates with more than 150 technologies, including Microsoft 365, Teams and DocuSign, and publishes an App Directory and partner locator. It ships ndOffice and mobile access software defined in the agreement. The 2026 additions matter most. Model Context Protocol connectivity lets external AI applications and agents reach NetDocuments content and run workflows without downloads or manual transfers.

The vendor names ChatGPT, Claude, Claude Cowork and its legal plugin, Microsoft Copilot, Perplexity, Google Gemini Enterprise, Harvey and Legora, and says this works within existing permissions, ethical walls and audit controls with no content leaving the platform. The agreement sets out API access: it is not included in the subscription, is granted on request after registering an application, may not be shared, and may carry further terms.

Depth for each integration is not on the pages read; the App Directory and support documentation were not opened and may say more.

Deployment options and residency are published and contractual, and processing is addressed separately from storage. Services Region is a defined term in the Software as a Service Agreement. Section 2.4 commits NetDocuments to store Customer Repository Data in the region on the Order Form and not to transfer or access it except at the customer's or a user's direction or as law requires; sharing and access by users outside the region are excepted where the customer sets them up.

The site lists five regional entry points: United States, United Kingdom, Germany, Australia and Canada, and the contracting entity follows the region. Tenancy is described as the customer's private repository on the ND Network. Customer Managed Storage Locations using ndFlexStore or ndMirror let a customer keep repository data on servers NetDocuments does not host. Processing is addressed expressly: section 4.2 says help desk staff or subcontractors may work from regions outside the customer's Service Region, and the customer must say in advance if its policies or law restrict that. Where Azure OpenAI inference runs for a customer in a given region is not published.

Certification is real, named and committed in the contract, without evidence that could be reached. Exhibit B of the Software as a Service Agreement commits NetDocuments to an annual SOC 2 Type 2 audit for security, availability and privacy and to maintaining ISO 27001 certification or a comparable successor. It says all data centers fall within the annual ISO 27001 audit and that the listed controls are verified in both.

That is a named scope and cadence in a binding document, not a badge. No auditor, audit period or report date is published. The trust website named in the agreement, trust.netdocuments.com, is a TrustShare portal that returned an empty JavaScript shell, so whether its Due Diligence Response material is self serve or gated could not be established, and it may say more.

The provider is named and the architecture described, but the models are not named and notice of change is reserved rather than promised. The Legal AI page says ndMAX is powered by Microsoft Cognitive Services and Azure OpenAI and their suite of OpenAI models. Only inputs and outputs are shared with the LLM, they are not kept beyond the exchange, and an agreement with Microsoft keeps customer content from triggering Microsoft's abuse monitoring.

The same FAQ reserves the right to change what sits underneath. The solutions are described as model agnostic, so better models may be used as they are developed, after internal testing. No specific model is named and no inference location is stated. The only notice mechanism located is the general notice of material changes to Common Subcontractors in section 12.2 of the agreement, which is not a commitment about models.

MCP connectivity, which lets a firm's own ChatGPT, Claude, Copilot or Harvey reach NetDocuments content, reflects the customer's model choice, not the vendor's supply chain.

The shape of the charge is published and no number is, at any tier. Every purchase path on the site ends at Contact Sales or a demo request, and no price, band or unit figure appears on any page read. The agreement supplies the structure. Fees are set in an Order Form as recurring Subscription Fees with a Billing Commencement Date. Under section 4.2, a customer exceeding the user, lawyer, document or other license metrics in the Order Form is invoiced for the overage.

Section 4.4 caps annual increases at CPI plus five percent, no more than once a year, section 8.1 requires disputed invoices to be raised within thirty days, and Exhibit A sets service credits as a share of the annual fee. Tier names appear in product material, with ndMAX Enterprise named as the plan that receives Smart Answers and expanded MCP connectivity. A buyer can learn the unit, the cap on increases and the plan structure before a sales call, but not the price.

Segment coverage is described precisely, and the boundaries are left open. The site has separate pages for small, midsize and large law firms, corporations, in house legal departments, public sector, federal government, and state and local government and higher education. Regional pages cover Asia, Australia and New Zealand, North America, South America, and the UK and Europe. The vendor says it supports more than 7,000 law firms, corporate legal departments and public sector organizations.

Practice coverage is described through tasks rather than areas. The ndMAX Studio library covers automatic profiling, NDA analysis, contract risk analysis, playbook creation and application, deposition preparation, judge analytics, offer letter workflows and translation. The benchmark is split evenly between transactional and litigation matters, the closest thing to a statement of where the AI has been tested. Nothing says what is not supported: no practice area, jurisdiction or language is named as out of scope, and the eDOCS line for on premises customers has no stated boundary with the cloud product.