Lean Patent Operations: Jidoka, Automation, and AI in Patent-Prosecution Workflows

Executive Summary

Patent prosecution is legal knowledge work, but it is also repeatable process work: new application filings, formalities, assignments, IDS submissions, Office communication processing, allowance, issuance, maintenance fees, foreign filing, and portfolio reporting all depend on accurate information, timely handoffs, reliable controls, and appropriate professional supervision. This white paper argues that patent operations can be improved by applying Lean Six Sigma, jidoka, traditional automation, and artificial intelligence as an integrated operating model. Lean reduces waste and delay; Six Sigma reduces defects and variation; traditional automation performs stable, rules-based tasks consistently; and AI can assist with unstructured information, comparison, classification, and drafting. Jidoka supplies the critical quality principle: when a process detects missing, conflicting, unauthorized, unreliable, or out-of-scope information, the workflow should stop, contain the issue, make the abnormality visible, route it to the appropriate owner, and preserve a record for correction and governance. The objective is not simply to make paralegals work faster or to replace judgment with technology; it is to create workflows in which the right work is performed by the right person, at the right time, using authoritative information, with fewer defects, fewer unnecessary handoffs, and stronger controls. In a mature patent operation, technology does not displace legal responsibility; it removes friction around professional judgment while strengthening verification, confidentiality, traceability, supervision, and accountability.

I.               Introduction

Patent prosecution is knowledge work, but it is also process work. Before a patent application is filed, a patent paralegal may collect inventor and applicant information, confirm filing instructions, coordinate signatures, assemble documents, obtain fee authorization, update a docketing system, submit the filing, verify the electronic filing receipt, report the filing to the client, and reconcile the official filing receipt when it issues. Comparable transactions recur throughout prosecution, allowance, issuance, assignment recordation, foreign filing, maintenance-fee administration, and portfolio reporting.

Each of these transactions has a triggering event, defined inputs, participants, decision points, governing rules, handoffs, outputs, and completion criteria. Patent-paralegal operations are therefore particularly suitable for Lean Six Sigma. Six Sigma treats work as a process whose inputs and outputs can be defined, measured, analyzed, improved, and controlled, while the DMAIC methodology—Define, Measure, Analyze, Improve, and Control—provides a structured approach for improving an existing process that does not consistently satisfy performance requirements or customer expectations. (Am. Soc’y for Quality, What Is Six Sigma? (last visited June 23, 2026); Am. Soc’y for Quality, DMAIC Process: Define, Measure, Analyze, Improve, Control (last visited June 23, 2026)).

Lean and Six Sigma provide complementary perspectives. Lean focuses on flow, lead time, and the removal of activity that does not create value or satisfy a legitimate legal, regulatory, quality, or business requirement. Six Sigma focuses on reducing defects and controlling process variation. Jidoka adds a third and especially important dimension: quality should be built into the process so that an abnormal condition is detected, contained, and resolved before the defect travels downstream.

Toyota identifies jidoka as one of the two pillars of the Toyota Production System and describes it as “automation with a human touch.” Under jidoka, equipment or an operator stops work when an abnormality is detected so that defective output does not continue through the process. The purpose is not merely to inspect quality at the end. It is to make abnormalities visible and prevent their recurrence. (Toyota Motor Corp., Toyota Production System (last visited June 23, 2026); Lean Enter. Inst., Jidoka (last visited June 23, 2026)).

Applied to patent operations, jidoka means that a filing process should not silently continue when critical information is missing, conflicting, unauthorized, or unreliable. The process should identify the abnormality, prevent it from contaminating downstream work, notify the appropriate person, and create a record from which the underlying cause can be corrected. Traditional automation and artificial intelligence can support this model, but only when they are designed to expose defects rather than accelerate them.

The objective is not simply to make patent paralegals work faster. The objective is to create a reliable operating system in which the appropriate work is performed by the appropriate person, at the appropriate time, using authoritative information, with the minimum necessary number of handoffs and corrections. Efficiency is the result of quality and flow, not a substitute for them.

II.            Patent-Paralegal Work as a Transactional Process

A process converts inputs into outputs for a customer. In patent operations, the customer may be the inventor, applicant, patent owner, supervising practitioner, in-house intellectual-property department, foreign associate, the United States Patent and Trademark Office, or a downstream team that cannot begin its work until the preceding transaction is complete.

Consider a new-application filing. The transaction may be triggered by client authorization to file. Its inputs may include a specification, claims, drawings, inventor information, applicant information, priority data, entity-status information, filing instructions, and fee authorization. Its output is not merely a collection of uploaded documents. The required output is an accurately filed application supported by a complete and traceable record, verified submission and payment receipts, correctly docketed follow-up obligations, and an appropriate report to the client.

This distinction is critical because process improvement requires an operational definition of completion. A filing should not ordinarily be treated as complete simply because someone selected a submission button. Depending on the organization’s approved procedure, completion may require confirmation that the correct documents were transmitted, the required fees were accepted, the application number was captured accurately, the docket was updated, the filing record was stored in the document-management system, and the submission receipt was reconciled against the approved filing package.

Patent operations may be understood as an end-to-end value stream beginning with invention intake and continuing through prefiling preparation, filing, prosecution, allowance, issuance, post-grant administration, and portfolio reporting. Within that value stream are recurring transactions involving application data sheets, inventor declarations, assignments, powers of attorney, Information Disclosure Statements, Office communications, prosecution-response filings, issue-fee payments, continuation decisions, assignment recordations, maintenance fees, foreign-filing instructions, and client reports.

Characterizing these activities as processes does not diminish their legal significance. Nor does it suggest that substantive legal judgment may be transferred to a non-practitioner or delegated to software. The USPTO Rules of Professional Conduct require appropriate supervision of non-practitioner assistants and prohibit practitioners from assisting in the unauthorized practice of law. (37 C.F.R. §§ 11.503, 11.505 (2025)). Lean Six Sigma should therefore improve the manner in which authorized work is performed while preserving the distinction between operational execution and legal judgment.

III.         Defining Quality and Value in Patent Operations

A Lean Six Sigma project begins by defining quality from the customer’s perspective and translating that concept into measurable requirements. In patent-paralegal work, critical-to-quality requirements commonly include deadline accuracy, correct matter and application identifiers, accurate inventor and applicant data, correct priority and benefit information, complete filing packages, approved document versions, proper signatures and authorizations, accurate entity-status and fee information, successful transmission and payment, timely receipt reconciliation, confidentiality, data security, and an auditable record of the transaction.

Broad aspirations such as “file accurately” or “report promptly” are not sufficiently precise. A useful operational definition might require that each filed bibliographic field match the approved system of record, every required document appear in the electronic submission receipt, each signature comply with the applicable procedure, every resulting deadline be independently verified, and the filing report be issued within a specified period after confirmation of submission.

It is also important to distinguish among value-adding work, business-required work, and pure waste. Value-adding work directly contributes to the result required by the client. Business-required work may not visibly transform the work product but is necessary for legal compliance, quality assurance, information security, or risk management. Pure waste consumes resources without creating client value or satisfying a legitimate requirement.

This distinction prevents an overly simplistic application of Lean principles. A second review of a high-risk priority claim may be a necessary control. Four duplicative reviews of the same low-risk field, performed because responsibilities are unclear, may constitute overprocessing. The proper question is not whether a step consumes time. The proper question is whether the step addresses a defined requirement or risk in an effective manner.

IV.         Recognizing Waste in Patent-Paralegal Work

The traditional Lean wastes are readily observable in patent operations. Defects include inaccurate inventor names, incorrect application numbers, missing priority information, unsigned documents, wrong fee selections, and erroneous docket entries. Overproduction occurs when reports, forms, or document sets are created before they are needed or without a defined downstream user. Waiting occurs when work remains idle for client instructions, inventor signatures, attorney review, fee authorization, foreign-associate confirmation, or missing bibliographic data.

Nonutilized talent appears when experienced paralegals spend substantial portions of their day copying information between systems, renaming files, or monitoring routine automated functions. It also appears when attorneys perform repetitive clerical work that could be completed through properly supervised standard work. Transportation is the unnecessary movement of information among email, spreadsheets, docketing software, document-management systems, client portals, and local folders. Inventory appears as accumulated unsigned declarations, unreconciled filing receipts, unprocessed correspondence, aging docket tasks, or matters awaiting instructions.

Motion includes searching across several systems for the controlling instruction, correct document version, or approved client requirement. Overprocessing includes repeated data entry, unnecessary reformatting, duplicative status reports, and review layers that are not connected to a defined failure mode.

These wastes are usually symptoms of process design rather than individual performance. Incomplete intake standards, fragmented technology, unclear ownership, inconsistent client requirements, and historical controls that were added without reconsidering the end-to-end workflow commonly create the conditions in which waste flourishes. A sound Lean Six Sigma initiative focuses on correcting the system rather than blaming the people who must operate within it.

V.            Jidoka: Building Quality into the Patent Process

Jidoka is particularly well suited to patent-paralegal operations because patent work combines high transaction volume with low tolerance for certain defects. In manufacturing, jidoka permits a machine or operator to stop production when an abnormal condition occurs. In a legal-service environment, the corresponding principle is that work should not pass to the next stage when a defined critical condition has not been satisfied.

A patent-operation jidoka system has four practical elements. First, the process must be capable of detecting an abnormality. Second, ordinary processing must stop or be contained so that the abnormality does not propagate. Third, the process must make the condition visible and route it to a person with the authority and knowledge to resolve it. Fourth, the organization must examine the cause and implement an appropriate countermeasure so that the same problem is less likely to recur.

Detection may be automated or human. A rules engine may detect that the inventor name on a declaration does not match the approved matter record. A document-assembly system may determine that required priority data is missing. An AI extraction tool may return a confidence score below an approved threshold. A paralegal may observe that client instructions conflict with the application data sheet or that the selected filing fee does not appear consistent with the recorded entity status.

The stop function should be proportionate to risk. A hard stop may be appropriate where the detected condition concerns the identity of the applicant, inventorship data, a priority claim, filing authorization, a required signature, entity status, or an imminent deadline. A lower-risk discrepancy may generate a warning that permits work to continue only after acknowledgement and documented resolution. The system should distinguish between a true stop condition and an informational alert; otherwise, excessive warnings will create alert fatigue and users will learn to bypass controls reflexively.

The legal-operations equivalent of an andon signal is a visible exception notification. Instead of allowing a discrepancy to remain buried in an email thread, the system should place the matter in an exception queue, identify the reason for the stop, assign an owner, record the time of escalation, and display the remaining time before the applicable internal or external deadline. The purpose is to make the abnormal condition impossible to ignore.

Jidoka also requires that employees have the authority to stop the process. A paralegal who identifies a material discrepancy should not be expected to choose between filing questionable information and being criticized for delaying the workflow. Management and supervising practitioners must establish that pausing ordinary processing and escalating a defined risk is an expected quality-control action.

In patent practice, however, “stop the process” cannot mean passively allowing a statutory, regulatory, or client deadline to expire. The stop must trigger a time-bounded escalation and an approved deadline-protection procedure. The ordinary workflow may be suspended, but protective action must remain available under the direction of the responsible practitioner. A well-designed jidoka control therefore identifies not only when work must stop, but also who must be notified, how quickly that person must respond, what contingency path is authorized, and how the decision will be documented.

Jidoka differs from end-of-process inspection. An organization that relies exclusively on a final checklist may discover a defect after considerable downstream work has already been performed. By contrast, a jidoka control seeks to identify the problem at its source. If an applicant name is inconsistent at intake, the process should not allow the inconsistency to populate an application data sheet, declaration, assignment, docketing record, client report, and foreign-filing instruction before someone notices it.

Jidoka also complements mistake-proofing, or poka-yoke. A mistake-proofing control may prevent an invalid date format or require completion of a mandatory field. A jidoka control addresses the broader situation in which an abnormal condition is detected and the process must be stopped, contained, and escalated. The strongest workflows use both. They prevent predictable errors where possible and stop the process when an error or exception cannot be prevented automatically.

Finally, jidoka supports the separation of human and machine work. Humans should not spend their time continuously watching software perform a routine task. The system should execute the task, monitor defined conditions, and call for human attention only when an exception arises. This principle is especially important when AI is introduced. A professional should not be required to reread every field merely because an unreliable AI system produced it; the organization should validate the tool, establish confidence and exception thresholds, and focus human review on the portions of the output that present material risk.

VI.         Applying DMAIC to Patent-Paralegal Work

Define

The Define phase begins with a sufficiently bounded problem. “Improve patent prosecution” is too broad. “Reduce lead time and rework in preparing and filing new U.S. nonprovisional applications” is more suitable.

The project charter should identify the business problem, the beginning and end of the process, the customer, the process owner, the project sponsor, participating personnel, expected benefits, exclusions, and risks that may not be compromised. A project addressing filing formalities should not quietly expand into claim drafting, inventorship determinations, or prosecution strategy.

A SIPOC analysis can identify the suppliers, inputs, high-level process, outputs, and customers. A RACI analysis can clarify who is responsible, accountable, consulted, and informed at each material stage. These tools are particularly valuable when attorneys, paralegals, docketing personnel, administrative staff, inventors, clients, foreign associates, and technology vendors share portions of the same workflow.

A suitable problem statement might explain that the new-application filing process experiences incomplete intake packages, repeated data entry, inconsistent review practices, late discovery of exceptions, and avoidable deadline escalation. The objective would be to reduce total lead time and improve first-pass completeness without weakening signature, confidentiality, deadline, or practitioner-review controls.

The Define phase should also identify the conditions that will activate jidoka. The project team should determine which abnormalities require an immediate stop, which require a warning, who owns each exception, and what escalation time is appropriate.

Measure

The current process should be mapped as it actually operates rather than as the procedure manual assumes it operates. A swimlane or value-stream map should show every material action, system, handoff, approval, waiting period, correction loop, and control point. Value-stream mapping is intended to expose the flow of work and information so that a future state can be designed with less delay, backflow, and waste. (Am. Soc’y for Quality, Six Sigma Tools: DMAIC, Lean & Other Techniques (last visited June 23, 2026)).

Useful measures include total lead time, active touch time, waiting time, number of handoffs, number of systems accessed, number of manual data entries, first-pass yield, rework rate, defects per transaction, deadline compliance, backlog age, filing-receipt reconciliation time, and the percentage of matters requiring escalation.

Jidoka events should also be measured. The organization should record the number and type of stops, the process stage at which each abnormality was detected, the time required to resolve it, the frequency of overrides, the number of false-positive alerts, and whether the same condition has recurred. A high number of stops is not necessarily evidence that jidoka is failing. It may initially demonstrate that the process is finally making previously hidden defects visible.

Every measure requires an operational definition. The team must determine when the process begins and ends, what constitutes rework, what qualifies as a defect, and how delays caused by incomplete client instructions will be classified. Without consistent definitions, the data will reflect the observers’ opinions rather than the process’s actual performance.

Analyze

The Analyze phase seeks causes rather than symptoms. A Pareto analysis may show that most filing rework arises from a small number of categories, such as inconsistent inventor information, missing priority data, late signature collection, or discrepancies between the docketing system and the application data sheet.

Five Whys analysis and cause-and-effect diagrams can test why those conditions occur. The immediate explanation for a late declaration may be that the inventor did not sign promptly. The underlying causes may be that the signature request was initiated too late, the inventor’s contact information was not validated at intake, no aging alert existed, or no one owned escalation of an unanswered request.

Failure modes and effects analysis is especially useful in patent operations because it examines how a process may fail, the effects of that failure, the likelihood of occurrence, and the strength of existing detection controls. Potential failure modes include an incorrect priority claim, inconsistent inventor names, an outdated document version, a missing signature, an erroneous fee selection, an omitted filing document, or a failure to reconcile an official filing receipt.

Jidoka data can sharpen the analysis. If a system repeatedly stops because applicant information is incomplete, the root cause may not be the validation rule. The real problem may be an inadequate intake form or an unclear responsibility for obtaining ownership information. Disabling the alert would hide the symptom rather than improve the process.

The team should also distinguish common-cause variation from special-cause variation. Repeated incomplete intake, routine duplicate entry, and inconsistent naming conventions are systemic conditions. A platform outage, unexpected client emergency, or unusual legal issue may be a special cause. The former requires process redesign; the latter requires a contingency procedure.

Improve

Improvement should follow a deliberate sequence. The organization should first eliminate unnecessary activity, simplify the remaining workflow, standardize the process, mistake-proof foreseeable failure points, and then introduce automation.

Standardization may include structured intake forms, minimum-entry criteria, authoritative data fields, controlled templates, uniform naming conventions, standard work instructions, defined escalation paths, and risk-based review requirements. Client-specific requirements should be maintained in a governed repository rather than in individual memory or scattered email messages.

Jidoka controls should be embedded at the point where each critical defect can first be detected. The system might block package generation when approved inventor information is absent, prevent task closure until the filing receipt has been reconciled, route a low-confidence AI extraction to manual verification, or stop submission when the filing package differs from the approved package.

Review should be proportionate to risk. Low-risk structured data may be validated through deterministic rules. A patent paralegal may verify operational completeness and resolve routine discrepancies. Defined high-risk information may require an independent secondary review. Questions involving inventorship, ownership, priority entitlement, disclosure obligations, legal sufficiency, or prosecution strategy should be escalated to the responsible practitioner.

A successful improvement does not merely make the normal transaction faster. It also makes exceptions easier to identify and resolve. The future-state process should therefore contain an explicit exception path rather than forcing unusual matters through a routine workflow that was not designed for them.

Control

An improved process will regress unless ownership, monitoring, and change control are established. The control plan should identify each critical requirement, its metric, the process owner, the review frequency, the acceptable range, the escalation threshold, and the corrective action required when performance falls outside that range.

Control mechanisms may include dashboards, aging reports, transaction audits, exception queues, automated reconciliation reports, template version control, access reviews, training records, and periodic sampling of automated or AI-assisted work. Jidoka overrides should be logged and reviewed. A hard stop that can be bypassed without explanation is not a meaningful control.

The organization should also monitor whether controls themselves are functioning properly. Excessive false positives, unresolved exception queues, repeated manual overrides, and long stop-resolution times may indicate that a control is poorly calibrated or that the underlying process remains unstable.

Change control should be triggered when USPTO rules or forms change, fee schedules are revised, a client modifies its outside-counsel requirements, a docketing platform is updated, an automation rule is changed, or an AI model or vendor changes. The process owner should determine whether the modification affects existing validations, thresholds, training materials, or escalation procedures.

VII.       Traditional Automation as the Operational Foundation

Traditional automation is generally the best tool for stable, structured, rules-based activity. It is well suited to populating forms from an approved matter record, generating filing checklists, routing incoming correspondence, initiating signature workflows, validating application numbers and date formats, creating docket tasks, generating standard reports, retrieving receipts, and initiating post-filing or post-allowance workflows.

These functions may be performed through database rules, document-assembly systems, application programming interfaces, robotic process automation, macros, scripts, electronic-signature platforms, and workflow engines. When properly designed, deterministic automation is relatively easy to test, reproduce, explain, and audit.

Jidoka changes the design question from “Can this step be automated?” to “Can this step be automated while detecting and containing abnormal conditions?” A form generator that rapidly populates an incorrect applicant name is not an improvement. A workflow that automatically files a document despite conflicting instructions is not efficient. It merely produces defects at greater speed.

Accordingly, an automated process should have defined entry criteria, validation rules, exception handling, and an authoritative source of data. It should know when it cannot safely continue. This is the difference between automation that blindly executes and autonomation that incorporates human intelligence and quality control.

VIII.    AI as an Augmentation Layer

AI is most useful where conventional automation encounters unstructured or linguistically variable information. In patent-paralegal workflows, AI may assist in classifying incoming correspondence, extracting candidate bibliographic data, summarizing an Office communication for routing purposes, comparing inventor and applicant information across documents, identifying inconsistencies, extracting prior-art citation data, detecting possible duplicate references, searching internal procedures, drafting routine status communications, or forecasting workload.

These uses should be treated as proposals or analytical assistance rather than authoritative determinations. The preferred operating model is that AI extracts, classifies, compares, or drafts; deterministic rules validate what can be validated; the paralegal verifies the operational result; the practitioner decides or approves matters requiring legal judgment; and the system records the final action.

Jidoka is essential because AI systems can generate fluent output even when the output is incomplete, unsupported, or incorrect. An AI-assisted process should stop or route the transaction when the model cannot identify an authoritative source, when its confidence falls below an approved threshold, when extracted data conflicts with the system of record, when required information is absent, or when the requested task falls outside the approved use case.

The system’s output should also be traceable. A discrepancy report should identify the document and text from which a proposed field was extracted. A summary should permit the reviewer to return to the underlying source. A deadline cue should never become a controlling docket entry solely because an AI model inferred it from a document.

The USPTO has stated that existing duties continue to apply when AI tools are used in practice before the Office. A person presenting a paper must perform an inquiry reasonable under the circumstances, review and verify the filing, and remain responsible for its contents; simply relying on an AI tool is not a reasonable inquiry. (Guidance on Use of Artificial Intelligence-Based Tools in Practice Before the United States Patent and Trademark Office, 89 Fed. Reg. 25,609, 25,614–15 (Apr. 11, 2024)).

The same guidance explains that AI may assist with an IDS but that a natural person must personally sign the submission, review the listed information, and satisfy the applicable certification obligations. The duty of disclosure cannot be transferred to a computer system. (Id. at 25,615–16).

AI likewise should not determine inventorship. The Federal Circuit has held that only natural persons may be named as inventors, and the USPTO’s revised guidance states that the ordinary inventorship standard applies regardless of whether AI assisted the inventive process. (Thaler v. Vidal, 43 F.4th 1207, 1211–13 (Fed. Cir. 2022); Revised Inventorship Guidance for AI-Assisted Inventions, 90 Fed. Reg. 54,636, 54,636–38 (Nov. 28, 2025)).

The appropriate use of AI is therefore augmentation, not abdication. AI can reduce the effort required to locate, compare, classify, and prepare information. It cannot assume the professional accountability attached to legal judgments, certifications, signatures, or representations to the USPTO.

IX.         A Worked Example: Improving a New Nonprovisional Filing

Consider a current-state filing process in which client instructions arrive by email, inventor data is maintained in a spreadsheet, applicant information is stored in a docketing system, the application data sheet is prepared manually, signatures are requested late, and client-specific requirements are located in individual email folders.

The process may contain only a few hours of active work but require several days of elapsed time because of waiting, searching, repeated entry, correction, and approval. Management may initially assume that the solution is to require the paralegal to work faster. A Lean Six Sigma analysis would instead ask why the information is incomplete, why it is entered repeatedly, why exceptions are discovered late, and why the review process is not aligned with risk.

A future-state process could begin with a structured intake form containing minimum-entry criteria. Approved information would populate a governed matter record. Traditional automation would generate the application data sheet, declarations, assignment documents, and filing checklist from that record. An AI tool could compare the application documents, intake data, filing forms, and docketing record and produce a source-linked discrepancy report.

Jidoka controls would prevent the routine workflow from proceeding when critical abnormalities are detected. A mismatch in inventor names could stop declaration generation. Missing priority data could block final package approval. An inconsistency between entity status and the selected fee could route the matter to an exception queue. A low-confidence AI extraction could require manual verification. A missing signature or unresolved filing authorization could prevent submission.

The paralegal would resolve routine operational discrepancies and escalate legal questions to the responsible practitioner. If a stop occurred close to a filing deadline, the system would invoke a time-bound escalation and approved contingency path. After submission, automation would capture the receipt and compare it with the approved filing package. The process would not close until the submission had been reconciled, the docket had been updated, and the client report had been issued.

Performance could then be evaluated through lead time, first-pass yield, rework rate, manual data entries, exception frequency, stop-resolution time, deadline compliance, and receipt-reconciliation time. The organization should also examine whether the process reduced emergency work and released experienced paralegal capacity for higher-value activities.

X.            Professional Responsibility and Governance

Process improvement does not change professional obligations. USPTO practitioners remain responsible for competent and diligent representation and for appropriately supervising non-practitioner assistants. (37 C.F.R. §§ 11.101, 11.103, 11.503 (2025)).

The signature and certification requirements are particularly important. Presenting a paper to the USPTO may constitute a certification that factual contentions have evidentiary support, legal contentions are warranted, and an inquiry reasonable under the circumstances has been performed. (37 C.F.R. § 11.18(b) (2025)). AI output does not independently satisfy that obligation. The USPTO has further stated that an AI system cannot sign correspondence, cannot obtain a USPTO.gov account, and cannot insert a person’s signature on that person’s behalf. (Guidance on Use of Artificial Intelligence-Based Tools in Practice Before the United States Patent and Trademark Office, 89 Fed. Reg. at 25,616–17).

Confidentiality must also be designed into the process. Practitioners must make reasonable efforts to prevent unauthorized access to or disclosure of information relating to a representation. (37 C.F.R. § 11.106(a), (d) (2025)). An AI service may retain submitted information, use it for further model training, process it through third parties, or transmit it through servers outside the United States. In patent matters, such information may include unpublished inventions and sensitive technical data. The USPTO has cautioned that AI use may therefore implicate confidentiality, national-security, export-control, secrecy-order, and foreign-filing-license considerations. (Guidance on Use of Artificial Intelligence-Based Tools in Practice Before the United States Patent and Trademark Office, 89 Fed. Reg. at 25,612–13, 25,617).

ABA Formal Opinion 512 similarly addresses competence, confidentiality, communication, supervision, and reasonable fees in connection with generative AI. It explains that lawyers should understand the capabilities and limitations of the tools they use, apply an appropriate degree of independent verification, establish clear policies, train lawyers and nonlawyers, and evaluate vendor security and data practices. (ABA Comm. on Ethics & Pro. Resp., Formal Op. 512, at 2–12 (2024)).

Governance should therefore specify approved tools, authorized users, permissible data, prohibited uses, verification requirements, retention rules, access controls, incident-reporting procedures, and manual fallback processes. Vendor diligence should address security architecture, data location, retention, secondary use, model training, breach notification, subcontractors, and contractual remedies.

The National Institute of Standards and Technology’s AI Risk Management Framework provides a useful structure. Its four functions—Govern, Map, Measure, and Manage—encourage organizations to establish accountability, understand the context and possible harms of a use case, evaluate performance and risk, and implement continuing controls throughout the system’s lifecycle. (Elham Tabassi, Nat’l Inst. of Standards & Tech., NIST AI 100-1, Artificial Intelligence Risk Management Framework (AI RMF 1.0) 20–32 (2023)).

The NIST framework and jidoka are mutually reinforcing. Governance determines who may stop an AI-assisted process and who owns the exception. Mapping identifies the abnormalities that matter. Measurement determines whether the detection and stop controls are effective. Management determines whether the tool should continue operating, be modified, be restricted, or be withdrawn.

Billing practices must also reflect actual efficiency. When services are billed hourly, a lawyer may charge for the time actually spent using and reviewing AI-assisted work but may not bill time that was not expended. Any separate charge for technology must be reasonable and consistent with the engagement terms. (ABA Comm. on Ethics & Pro. Resp., Formal Op. 512, at 11–14 (2024)).

XI.         Measuring What Matters

A patent-operations improvement should be evaluated through a balanced set of measures rather than a single productivity target. Quality measures may include first-pass yield, defects per transaction, correction frequency, receipt-reconciliation accuracy, and escaped defects. Delivery measures may include total lead time, queue time, deadline compliance, and backlog age. Capacity measures may include touch time, number of manual entries, number of handoffs, and time redirected to higher-skill work.

Jidoka measures should include the frequency of stop events, the stage at which abnormalities are detected, the time required to resolve them, override frequency, recurrence, and false-positive rates. AI-specific measures may include extraction accuracy, unsupported-output frequency, exception-routing accuracy, and the percentage of material outputs receiving the required human verification.

People measures are equally important. Overtime, workload balance, training completion, employee confidence, and the number of improvement suggestions can reveal whether the future-state process is sustainable. A process that appears faster only because employees absorb more stress or perform unrecorded corrective work is not genuinely improved.

Management should avoid measuring only the number of matters processed per person. A productivity measure that ignores quality, risk, workload, and client service can reward the concealment of problems and discourage employees from using stop-the-process authority. Jidoka requires the opposite culture: abnormalities should be surfaced promptly and treated as opportunities to improve the system.

XII.       A Practical Implementation Sequence

Implementation should begin with one high-volume, reasonably stable process that presents visible delay, rework, or risk. The organization should establish a baseline, simplify the process, create standard work, define critical abnormalities, implement appropriate mistake-proofing and jidoka controls, automate deterministic steps, and then pilot AI on limited and reviewable uses.

The pilot should include actual users, realistic transaction volumes, known exception types, measurable acceptance criteria, and a rollback procedure. It should test not only whether the routine case works, but whether the system detects and appropriately handles missing information, conflicting data, low-confidence output, system outages, unauthorized access attempts, and deadline-sensitive exceptions.

Scaling should occur only after the organization demonstrates that the process improves quality and flow without weakening professional controls. A technology deployment should not be called successful merely because it reduces average touch time. It must also preserve or improve accuracy, confidentiality, traceability, exception handling, and human accountability.

XIII.    Conclusion

Patent-paralegal efficiency is not achieved by asking capable people to work faster within a fragmented and unstable process. It is achieved by designing the process so that complete information arrives at the appropriate time, work moves without unnecessary delay, foreseeable errors are prevented, abnormalities are made visible, and each participant understands both the participant’s responsibilities and the limits of the participant’s authority.

Lean removes unnecessary activity and delay. Six Sigma reduces defects and variation. Traditional automation performs stable, rules-based transactions consistently. AI assists with unstructured information, comparison, classification, and drafting. Jidoka ensures that neither humans nor technology silently pass defective work to the next stage.

The governing principle is therefore not automation for its own sake. It is automation with human intelligence, defined controls, and the ability to stop when the process is no longer operating as intended. In a well-designed patent operation, technology removes friction surrounding professional judgment while attorneys and paralegals remain accountable for the verification, supervision, confidentiality, and legal decisions that sound patent practice requires.