LegalSifter vs Pactly: how they compare in 2026
LegalSifter ReviewPro combines standard and custom playbooks with redlining in Word and Google Docs. Pactly offers Word review as part of a contract system and sells Projects separately for portfolio analysis. These are overlapping purchases, not a choice between review and repository: ReviewPro also includes a repository, assistant and intake ticketing. For deployment effort, AI Legal Index identifies LegalSifter's included standard implementation and separately scoped custom playbook services as a useful commercial distinction. Pactly's setup work can carry additional fees, and its larger CLM plans have minimum user counts. Teams seeking many reviewers on a defined annual contract allowance can use LegalSifter's consumption model; a small Pactly Projects subscription instead buys storage and analysis runs. Both leave legal judgment with the people reviewing the output.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. 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.
ReviewPro uses models to interpret contract language, detect playbook issues, propose edits and answer questions through a contract assistant. The playbook provides the organization's positions and fallback instructions, so interpretation and generation are essential to the review service. The current product also includes a versioned contract repository, intake ticketing and controlled playbook management. Those organizational functions still have a use when an AI review is not running. LegalSifter's human services can customize playbooks or handle redlining and extraction, while Contract Logix is a separate contract management offering within the company. The broader workflow now extends beyond the original automated review engine.
Models identify clauses and concepts for playbook review, generate proposed revisions and extract values across contract collections. Assist adds questions about a contract's text and history, with proposed edits and comments in Word. Projects applies the same questions to many agreements and returns a structured table with reasoning and source passages. These are core analysis functions alongside the conventional platform: questionnaires generate approved templates, workflows route approvals, signatures execute agreements and reminders track renewals. Those administrative features do not depend on generative output. Projects is available separately, while Growth and Ultimate include it within an unspecified fair use allowance.
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.
ReviewPro 2.0 evaluates clauses against a selected playbook and returns proposed edits with rationale for the reviewer. Its July 2026 study used 30 NDAs, 16 positions and three runs per agreement, comparing results with attorney approved edits. With the engine and agreements fixed, richer playbook instructions raised issue detection from 91% to 95%, selection of the right action from 77% to 93%, and edit fidelity from 55% to 93%. These are distinct measures of contract review, not a general guarantee of legal accuracy. The benchmark does not establish citation treatment, an abstention threshold or performance across other agreement types.
Projects connects an extracted value to reasoning, a quoted source passage and a document view that highlights the relevant text. Users can correct a value, preserve the original AI extraction and mark a result as verified. The guidance names concrete failure modes, including confusion between effective and commencement dates, loss of qualifiers in compound liability caps and missing values in drafts with placeholders. Word review also exposes the clauses behind each playbook assessment. No reproducible benchmark or measured error rate accompanies these mechanisms. The terms expressly warn that AI answers can be incomplete or wrong and require checking against the source.
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.
ReviewPro runs a first pass against the selected playbook and returns redlines and explanations in Word or Google Docs. The customer must vet standard or custom playbooks before using them, and reviewers remain responsible for checking and accepting the result. The terms impose an additional categorical boundary on Trial Features: they are solely for evaluation and testing, and cannot be used in production. Named seat plans also require interactive human use rather than unattended batch processing. Routine business review can follow the legal team's approved standards, but the terms recommend legal counsel and leave responsibility for the final agreement with the customer.
Assist never applies a contract edit or comment silently: proposed changes require acceptance and enter Word as tracked changes. A reviewer can reject, revise or copy the proposal, and a support message is not sent without the user's choice. Playbook results can be Uncertain, returning the decision to a human; accepted deviations carry a written justification. Projects preserves corrected and verified values during reruns and identifies outdated results when a column question changes. The external MCP connection is read only and cannot create, modify, delete or send signature requests. Standalone Word generation remains described as an upcoming release rather than an existing unrestricted action.
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.
A July 2026 study describes a field observation involving 15 complex agreements, where an unnamed legal team reached 90% alignment with its intended edits and reduced a roughly 90 minute review to about five minutes. That account is separate from the controlled 30 NDA benchmark used to test playbook instruction quality. The field result indicates a concrete workload and reported change, but gives neither the customer's name nor a detailed timing protocol. The internal benchmark explains its agreements, positions and repeat runs; it does not turn the field observation into a reproducible customer deployment study across different contract portfolios.
A September 2022 case study identifies Virtuos and its Senior Legal Counsel, Johnathan Yong, and describes an NDA process before and after adopting Pactly. Requests previously took several days or sometimes a week across Word, shared drives and email. Following template questionnaires, legal review and DocuSign execution, reported median finalization fell to two hours and median completion of a signed agreement to twelve hours. Yong describes feedback more than two months after implementation. The account explains the workflow change and measured contract type, although it does not provide the sample size. It measures contract automation rather than the accuracy of today's generative review features.
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 ReviewPro agreement treats customer contract content as confidential and expressly intends disclosure to preserve attorney client privilege and work product protection. Access by service providers is limited to those who need the information and owe confidentiality duties. Tenant records are isolated from other customers, with role and feature controls inside the service. Training third party AI models is prohibited, but the terms grant LegalSifter a perpetual right to train and improve its own models with anonymized customer content. The security FAQ describes training as a choice made in the agreement. This default permission and the absence of a stated internal matter wall limit the confidentiality position.
The service agreement protects nonpublic customer data as confidential information and preserves customer ownership. Its improvement license nevertheless permits analysis of service information involving customer data during the term and use of anonymized aggregate customer data for lawful business purposes afterward. Public marketing says contracts never train AI models, without the same express restriction in the agreement. Sensitive groups can hide contracts from nonmember administrators, but deliberate sharing and project membership can widen access. The provider list explains where contract data travels. No specific attorney client privilege, work product or accidental disclosure protection is stated for lawyers using these features.
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.
LegalSifter identifies ReviewPro as software, disclaims legal advice and an attorney client relationship, and strongly encourages review by legal counsel. Customers must vet their playbooks and verify the resulting work. Business personnel can use standards approved by their legal team, while the agreement leaves legal decisions with the customer. Subscription scope also matters: named seat plans are restricted to internal contracts and matters, while legal services for external clients require express authorization under a consumption plan. The product supports supervision through explained redlines and reusable standards, but does not set jurisdiction specific practice limits or determine whether a particular user may give advice.
Pactly's agreement says the company is not a law firm, use creates no attorney client relationship and the service does not solicit legal advice. It separately warns that AI answers may be wrong and makes the customer responsible for comparison with the source. Product guidance describes the reviewer accepting edits and resolving uncertain playbook findings, and the company explicitly rejects a fully automatic robot lawyer role. Corporate legal departments are its principal audience, with business users working through forms and approvals. The material does not map the controls to named bar guidance or publish jurisdiction specific professional responsibility limits.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
LegalSifter separates issue detection, selection of the appropriate action and edit fidelity when evaluating ReviewPro. Its July 2026 study holds the review engine and NDA set constant while varying the specificity of playbook instructions, with attorney approved edits as the comparison. It also compares releases and describes recurring assessment of thoroughness, accuracy and readability. These mechanisms connect product changes to defined review tasks rather than a general responsible AI promise. The terms prohibit discriminatory consequential decisions and malicious attempts to manipulate models. A named accountable AI governance owner and results on uneven behavior across populations or contract categories remain unspecified.
Published AI guidance explains how customers verify results, handle uncertain findings and correct extraction mistakes. Release notes describe feature changes, and security materials identify a data protection officer and engineering responsibilities for incidents. These do not establish an AI governance program with an accountable model owner, release testing criteria or results on uneven behavior across languages, populations or contract categories. Positive and negative playbook examples help customers configure review, rather than disclose Pactly's own evaluation program. No formal bias assessment, model card or governance framework accompanies the descriptions of Assist, Projects and playbook review.
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.
ReviewPro uses encrypted contract storage, AWS key management, role and feature controls, and tenant isolation at the record level. Auth0 supports SAML and OIDC single sign on, with the customer's identity provider enforcing multifactor policies. Contracts are deleted within 30 days after subscription termination, while no ordinary retention period is stated for the full prompt and output history. OpenAI and Anthropic are listed as model processors in the United States, and the terms prohibit their training on customer content. Confirmed customer data or model integrity incidents trigger notice without undue delay, including incidents involving poisoning or model extraction. Retained anonymized material has separate contractual treatment.
Pactly describes encrypted storage and transport, monitoring, backups, vulnerability testing and separate production and test environments. Administrators can require two factor authentication, and high criticality incidents trigger notice to affected customers or all customers when the affected group cannot be identified. A public supplier register details processing functions and regions with advance change notice. The terms provide sixty days to retrieve data after termination, followed by requested deletion with an anonymized aggregate exception. Assist attachments expire after seven days, but ordinary chat history, backup deletion and underlying AI provider retention lack a complete fixed schedule. No definite breach notification deadline is stated.
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.
The ReviewPro terms provide a vendor defense and indemnity for specified claims against the authorized service, but expressly exclude AI output, reviewed contracts and customer playbooks from that protection. LegalSifter disclaims output accuracy and liability for decisions based on the service. The general liability cap is the fees paid during the preceding twelve months, with exceptions including indemnification obligations, gross misconduct and applicable legal duties. Trial Features carry separate warranty and indemnity exclusions and cannot be used in production. These terms allocate platform infringement risk more specifically than a generic disclaimer, while leaving errors in an accepted redline and resulting legal decisions with the customer.
The service agreement includes an indemnity for third party claims involving patents, copyright or trade secrets infringed by the service, subject to stated exclusions and control of the defense. Available remedies include replacement, modification, a license or termination with unused fees returned. General liability is capped at fees paid in the preceding twelve months and excludes data inaccuracies and several categories of loss. AI answers are expressly described as potentially incomplete or wrong, with verification assigned to the customer. There is no separate output accuracy warranty or AI insurance promise. Availability remedies have separate claim deadlines and exclude beta features.
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.
ReviewPro runs as a Microsoft Word add in applying tracked redlines in the document, and as a Google Docs add in whose marketplace listing documents exactly what it does: reads the current document to extract contract text, creates a redlined copy in Drive, transmits content to LegalSifter's servers and stores nothing locally, with the Google permission scopes listed. The product page states connection to existing apps and CLM software without naming them beyond the company's own Contract Logix.
The Word plugin uploads an agreement for playbook review, displays matched clauses and proposed fixes, inserts approved language as tracked changes and records review decisions between rounds. The MCP connection exposes eight read only tools for contract text, metadata, parties, playbooks, clauses and account information to external clients such as Claude and Cursor. Public instructions specify API key or OAuth authentication, administrator consent, filters, returned fields and request limits. Separate APIs can generate contracts from templates and support webhooks. DocuSign and Adobe Sign support execution, while the Ultimate plan's SharePoint connection is described as backup only rather than general document synchronization.
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.
ReviewPro operates on AWS with multiple availability zones, encrypted storage and customer separation enforced at the record level. OpenAI and Anthropic appear in the model processor register with United States locations. The security description covers resilience, identity and tenant controls, but does not name an available application hosting region or a customer residency selector. A model provider's listed country is not a complete account of where every processing step takes place. Contract Logix belongs to the same company but is a separate platform, so its Azure hosting arrangement does not establish ReviewPro's architecture or a deployment option for this review service.
Core hosting, compute and Bedrock inference use AWS in Singapore by default, with Malaysia for specified Malaysian customers. Structured data in MongoDB Atlas remains in Singapore for all customers. The supplier table separately identifies United States processing for document conversion, OCR, Cerebras inference and fallback Anthropic or OpenAI services, plus Langfuse monitoring in Germany and Cloudflare's global edge. Those routes make regional hosting different from exclusive regional processing. The SLA also recognizes fully managed private deployments, without a standard public price for them. Singapore and Malaysia have separate service entry points, and the published provider map identifies functions as well as locations.
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.
LegalSifter states that ReviewPro's security controls undergo independent SOC 2 Type II auditing. Its security material describes AES 256 encryption, TLS 1.2 or later, and AWS key management using FIPS 140 2 Level 3 validated hardware. Staff background checks, security training, monitoring and identity controls accompany the attestation claim. The certification description does not identify an audit coverage period, named assessor or freely accessible report with a scope statement. Encryption standards and a cloud provider's validated hardware support the operating controls but are separate from the scope of LegalSifter's own independent audit.
Pactly identifies ISO 27001 certification in its product, pricing and trust materials and offers its certificate, security whitepaper and penetration test results on request. The public trust FAQ describes Amazon's certified data centers when explaining ISO coverage, so infrastructure attestations need to be distinguished from Pactly's own claim. No openly supplied certificate names its current auditor, validity period and exact company scope. SOC, PCI and FISMA references in the infrastructure section concern AWS rather than a separate Pactly audit. Security practices include vulnerability scans, access logging, staff training and incident response, without resolving that certification scope question.
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 current processor register names OpenAI and Anthropic as large language model and API suppliers for ReviewPro, both in the United States. The security explanation discusses OpenAI's business terms, while the service agreement requires third party AI components not to train on customer content and to follow stated retention controls. LegalSifter separately reserves the right to develop and improve its own models from anonymized customer material. Exact model versions, a mapping of review tasks to each provider and a commitment to notify customers of every model substitution are not specified. Earlier marketplace descriptions of provider choices do not fully describe this current supplier list.
Pactly names AWS Bedrock for core inference, Cerebras for tasks requiring low latency, and Anthropic and OpenAI as fallback providers when Bedrock is unavailable. The supplier register identifies processing locations and also lists Langfuse for AI monitoring. Customers can subscribe to at least thirty days' written notice before a new subprocessor is engaged and raise an objection during that period. Exact production model families and versions are not supplied for each feature, nor is there a promise to notify every model version change within an existing provider. External MCP clients bring their own model relationship in addition to Pactly's built in AI.
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.
ReviewPro offers annual volume subscriptions with unlimited seats or annual seat subscriptions with unlimited interactive contract reviews. Volume plans cost $2,750 for 50 reviews, $7,500 for 150, $18,000 for 400 and $40,000 for 1,000. Seat pricing starts at $6,000 a year for one user; larger minimum seat commitments reduce the rate per user. Standard implementation is included at no extra charge. Custom playbook architecture and ongoing custom maintenance are separately scoped optional services. Named seat subscriptions are limited to internal contracts, while legal client work requires express permission under a consumption subscription. The plan choice therefore changes both the charging unit and permitted use.
Standalone Projects starts at $69 a month for one user, fifty documents and 250 monthly runs, or $690 annually with 3,000 runs available immediately. Larger packages, additional documents and extra runs have published charges. The wider CLM starts at $99 per user monthly on an annual plan; Growth is $139 with five users minimum and Ultimate $179 with ten. Their monthly AI review allowances are ten, fifty and one hundred respectively. Growth and Ultimate include Projects under fair use without a numerical allowance. Enterprise, migration and some implementation services require a quote. Projects has a fourteen day trial, while the CLM trial lasts thirty days.
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.
ReviewPro supports legal departments and business teams handling recurring commercial agreements against approved positions. Standard playbooks cover common forms, and custom architecture lets a legal team encode its own preferred and fallback language. Industry offerings include healthcare, insurance, manufacturing, technology, higher education, staffing and law firms. A firm's plan matters because named seat subscriptions cover only its internal contracts, not an unlimited external client review service. Client work requires express authorization under a consumption subscription. The terms also restrict protected health information to an executed BAA and eligible features. The full set of supported jurisdictions and excluded agreement types is not defined.
Pactly primarily serves corporate legal departments, including solo counsel and small teams across Southeast Asia and other Asia Pacific markets. Larger organizations can configure approval routes, business intake and administrator controls. Supported examples include NDAs, services, procurement, leases, employment and software licenses; Projects extends analysis to loan agreements, insurance and related portfolios. Sales, HR, finance and procurement can participate without turning the product into a consumer legal advice service. The company explicitly describes most customers as internal legal departments rather than firms. No measured language coverage or comprehensive jurisdiction matrix defines where AI interpretation is most reliable.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
The ReviewPro terms grant LegalSifter a perpetual right to use anonymized customer content to train, tune and improve its own models and services. They prohibit using that content to train third party AI components. The security FAQ describes training as an agreement choice, but the standard agreement itself supplies the permission. This is a contractual right to reuse content, not evidence that any particular customer's contracts have already trained a model.
The agreement permits analysis of service information involving customer data during the subscription for improvement and development. It also allows anonymized customer data to enter aggregate datasets used for lawful business purposes during and after the term, with safeguards against reidentification. Marketing separately promises that contracts never train AI models. The published agreement does not repeat that prohibition or exclude model improvement from its permission.
This records the contractual scope, not a claim that Pactly actually feeds every raw agreement into a shared training process.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Contracts are permanently deleted within 30 days after the subscription ends. Third party model handling is subject to separate retention restrictions, while the terms reserve continuing rights over anonymized training material and derived improvements. Neither the termination deadline nor processor handling establishes an ordinary lifetime for the customer's prompt and output history in ReviewPro. A configurable in service retention period or a zero history setting is not specified in the current security position.
Contract data remains retrievable for sixty days after termination. The standard terms then provide deletion on written request, excluding anonymized data already combined into aggregate datasets; online plans may delete after the same access window. Assist attachments expire after seven days, but a complete schedule for normal chat history, backups and provider copies is absent. The upcoming standalone Word generation description gives a thirty day file expiry, which should not be treated as the lifetime of all current AI outputs or contracts saved to the repository.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
ReviewPro isolates customer records and supports role and feature based access inside the application. Its single sign on connection delegates authentication to the organization's identity provider. Those controls protect a tenant and govern which functions a user can access. The current security explanation does not describe internal client matter walls or a retrieval connector that inherits per user permissions from a legal document management system.
Pactly uses its own groups and roles rather than inheriting a document management system's matter walls. Sensitive groups hide contracts even from nonmember administrators, but an authorized person can deliberately share a contract outside the group. Projects creates another boundary: every project member sees all present and future project documents, even when the normal repository link is unavailable. Administrators can see all projects.
This is a described access model with important widening rules, not a promise that an original contract restriction automatically follows every AI analysis surface.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
The agreement requires notice before legally compelled disclosure unless the law prohibits it, allowing the customer to seek protection and participate in the response. Confidential information includes customer contract content, and the parties intend disclosure through the service not to waive privilege or work product protection. This is a protection for legal demands, separate from the promise to notify confirmed security or model integrity incidents. A government request transparency report is not specified.
The service agreement incorporates Pactly's law enforcement request policy for compelled disclosure of customer data. That policy requires evaluation of governmental requests and notification to the customer where legally permitted, allowing an opportunity to seek protective measures. It applies to hosted and fully managed deployments, while excluding self hosted or customer managed solutions. Foreign authorities are directed through applicable legal and diplomatic channels.
No report of request volumes or outcomes accompanies this commitment, and the general privacy notice's legal disclosure permissions do not replace the more specific customer data policy.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
ReviewPro interprets a customer's contract against standard or custom playbooks containing legal positions and editing instructions. The July 2026 study identifies attorney approved edits as the reference for its NDA benchmark and varies the detail in those playbooks. These are concrete sources for reviewing an agreement. The product does not identify a licensed primary law collection or a complete account of the foundational training material behind every model it uses.
The analysis context is the customer's agreements, playbooks, approved clauses and related files. Projects reads each row's main contract and supporting amendments or schedules; Word review uses configured positions and fallback language. These are customer supplied materials rather than a catalog of primary law or licensed legal commentary. Pactly does not name an external research corpus, describe the source rights behind general model knowledge or supply an update process for legislation and case law. The public subprocessor list identifies processing suppliers, not a legal content licensing arrangement.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
ReviewPro connects review issues to contract language and the selected playbook, with redlines and explanations available in Word or Google Docs. Its accuracy study concerns issue detection and the fidelity of edits to an attorney approved position. A method for checking subsequent judicial treatment, a named licensed citator or a warning that an authority has ceased to be reliable is not part of the stated contract review workflow.
A source passage in Projects establishes where a contract value came from, and playbook review identifies the agreement language relevant to a configured rule. Neither function determines whether a case remains good law or legislation has changed. No licensed citator, subsequent history service or independent treatment signal is described. The legal team maintains its own clause positions and decides whether they remain appropriate.
Contract source highlighting and a verified cell marker therefore support review of supplied material without establishing the continuing validity of an external legal proposition.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
The review process flags issues and proposes edits against a selected playbook. A person remains responsible for vetting that playbook and checking the returned changes, and Trial Features cannot be used in production. The study measures missed issues and incorrect actions rather than a per answer confidence display. A defined abstention response when the playbook provides insufficient support for a conclusion is not described.
Playbook review includes an Uncertain result when a clause cannot be conclusively assessed, directing a person to decide. Each position also defines what happens when no relevant clause is found: compliant, not compliant or uncertain, according to the customer's chosen rule. Projects treats placeholders such as an unfilled name as not found and explains common interpretation failures. These are described negative and uncertainty states rather than a general guarantee of refusal. A wrong configuration of the absent clause rule can still produce a misleading result.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database has no tool entry naming LegalSifter or ReviewPro as of October 15, 2026. ReviewPro's stated task is to identify contract issues and generate playbook guided redlines rather than prepare a court brief. That use context is separate from the database result. Neither the absence of a named court entry nor a contract benchmark establishes that every proposed legal edit is correct.
Damien Charlotin's AI Hallucination Cases database contained no entry naming Pactly on October 16, 2026. The database concerns reported court decisions involving fabricated AI material and does not capture every private error in contract analysis. Pactly principally supports corporate agreements rather than preparation of court authorities, which limits what that incident record can say about its usual work. Its terms independently warn that AI answers may be incomplete or incorrect. No named court incident is therefore a limited reporting observation, not a validation of model accuracy.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
LegalSifter says it is not a law firm and does not provide legal advice. Its terms require customer verification, encourage legal counsel and distinguish internal seat subscriptions from authorized services for legal clients. Those are concrete responsibilities and scope limits. A named bar ethics opinion or jurisdiction specific professional rule governing the use of ReviewPro is not identified in these product and contractual instructions.
Pactly explains that it is not a law firm and requires people to verify AI answers against source text. Its review guidance describes accepting tracked edits, recording deviations and resolving uncertain results. These are practical controls for legal work, but the materials do not map them to a named professional ethics opinion, bar rule or regulator's jurisdiction specific AI guidance. References to Singapore privacy law and a data protection officer address data regulation rather than a lawyer's professional obligations when serving a client.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
LegalSifter compares the time and cost of automated review with conventional review, including a field account of a complex contract review falling from about 90 minutes to five. Firms may provide client services only under an expressly authorized consumption subscription. The subscription charge does not establish what a lawyer should bill a client. A client invoice disclosure method or a matter time record designed to allocate AI assisted work is not described.
The principal buyer is a company's own legal department, with sales, procurement and HR using forms and approvals around that team's contracts. The Virtuos case measures internal NDA turnaround, and the product's savings claims concern corporate workloads and staffing capacity. Those examples do not involve a lawyer billing an external client for AI assisted work. Published subscription and run charges describe Pactly's software fees, without a client invoice method, pass through rule or accounting of billable legal time. Law firm fee treatment is not part of the described workflow.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The processor list identifies OpenAI and Anthropic and their United States locations, while the agreement covers confidentiality, training permissions, incident response and restrictions on sensitive data. A law firm can use those details in responding to a client's AI requirements. They do not form a ready made client consent pack, and the default own model training permission remains relevant even though third party model training is prohibited.
A public provider register identifies data categories, functions and regions, including core Bedrock inference, fallback Anthropic and OpenAI services, and AI monitoring. Customers can subscribe to change notices and object before a new supplier is engaged. The trust page offers security reports and a certificate on request, while service terms and the law enforcement policy provide additional diligence material. No dedicated client consent pack or outside counsel AI disclosure form is supplied. Counsel would still need to distinguish the contractual improvement permissions from the marketing training promise.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
ReviewPro returns tracked edits and explanatory comments in the working agreement, preserving part of the reviewer's interaction with proposed changes. Its versioned repository and playbook management add context about contract work. An export combining the model version, all retrieved material and human verification for each generated passage is not specified. The editing record is therefore useful context for review but is not a complete court AI disclosure certificate.
Projects can export values, reasoning and source references to Excel, and produce a PDF preserving the table's visual labels. Human corrections and verifications record who acted and when inside the application, but the help guide expressly says the Excel export omits that sign off marker. Word review retains tracked edits and written justifications for deviations, while account activity is available through logs. These records preserve parts of the process without a combined export of model version, exact prompts, source context and human approval for a court filing.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- Good Law Verification
- Bar Guidance Alignment
Which one fits
Choose LegalSifter if
- Reviewers work in both Word and Google Docs.
- Unlimited seats with a defined annual review volume fit the team.
- You want standard setup included and optional custom playbook services.
Choose Pactly if
- The first requirement is a small portfolio analysis subscription.
- Word review should feed the same system's approvals and signatures.
- Analysis cells need retained originals and protected human corrections.
In summary
LegalSifter
LegalSifter ReviewPro applies organizational positions in Word and Google Docs and includes an assistant, playbook builder, repository and intake ticketing. Customers can choose annual contract volume or named seat subscriptions.
Pactly
Pactly combines Word playbook review with approvals and signature workflows. Its separately priced Projects table supports repeated questions across contracts, quoted support and human corrections protected during reruns.
Questions buyers ask
Does LegalSifter ReviewPro only provide a Word add in?
No. The subscription also includes Google Docs access, a contract assistant, playbook management, a repository and intake ticketing. Managed redlining and other services are separate offerings. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
What is the difference between annual reviews and Pactly runs?
LegalSifter's smallest consumption subscription is $2,750 annually for 50 reviews with unlimited seats. Pactly Projects counts a run across a contract's selected question columns and also limits stored documents; the units are not equivalent. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
What implementation work is included with LegalSifter?
Standard implementation and onboarding are included with ReviewPro. Custom playbook architecture is a separately scoped service. Pactly identifies additional setup work without a universal implementation price. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How should a team compare their portfolio controls?
For maintaining a table of reviewed answers, AI Legal Index highlights Pactly's result verification and protection of corrected values. LegalSifter's repository and intake ticketing serve a broader contract work queue alongside its redlining tools.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
ReviewPro volume subscriptions and Pactly Projects runs measure different work; custom playbook services add separately agreed costs.