PatentNode — Workbench preview

PatentNode ran the full pipeline on this OA

Each stage runs on a purpose-built model; ★ is your review gate — nothing drafts until you confirm.

Parse OA & spec
Fetch references
Evaluate rejection
Structured analysis
Practitioner review★ your review
Draft amendment & argument
Automated checks
Analysis report

Voice picker

Choose the technical area and register for how you'd want the drafts written. The argument below updates live for software × concise and business_method × formal — try toggling.

Practice areaRegisterVoice: software_concise

Active voice: Software / CIIs · [Concise] Direct · minimum prose

Office Action — examiner's text

The rejection as the examiner wrote it. The analysis and drafts cite back into these passages — open a reference chip to jump here.

Rejection summary

Claims 1–20 are rejected under 35 U.S.C. § 103 as unpatentable over Agarwal in view of Masson. The examiner finds Agarwal teaches the claimed loan-processing/chat-interface features and relies on Masson to supply limitations such as mapping AUS results to system conditions and other lending-system integrations, and concludes it would have been obvious to combine these teachings.

Cited examiner passages

Claims 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Agarwal (U.S. Patent Application Publication No. US 2023/0105825 A1) in view of Masson (U.S. Patent Application Publication No. US 2023/0186385 A1).
Agarwal teaches a method for managing a loan origination process comprising, by a chat manager, in response to receiving a message from a user conversation, extracting borrower details and loan conditions and displaying a system-generated response to the user.
It would have been obvious to one of ordinary skill in the art before the effective filing of the claimed invention to have modified Agarwal with the features of Masson's system because Masson's system, by capturing industry knowledge in lending strategies, reduces performance limitations that conventional systems exhibit.

Structured Analysis

Four sections per rejection, structured for partner-level skim-and-correct. In the live workbench every field is editable; drafts fire only after you confirm.

Why this layer: The drafters treat your validated Structured Analysis as ground truth. Catch a missed gap here and every downstream argument and amendment is anchored on it; let a wobble through and the drafts amplify it. The fastest place to apply judgment.

Overall confidence: 76%

Overall reasoning

Reference mechanism

Masson (US 2023/0186385 A1)

Technical problem: Capturing industry knowledge in pre-developed lending strategies to optimize revenue
Technical means: A repository of automated lending strategies developed and finalized based on historical performance testing and optional manual changes (Masson ¶ 16)
Technical effect: Codifies institutional lending knowledge into reusable strategy modules; reduces strategy-development team load
Difference from the claims: Masson's task library is STATIC — strategies are finalized in advance. It is not a dynamic generator that iteratively updates in response to current loan status or AUS findings. The examiner's mapping of Masson's 'task library' to the claim's dynamic-generation requirement relies on the shared word 'library,' not on structural or functional equivalence.

Claim mapping

Claim 1
using a task library to generate tasks according to the current loan status including AUS findings
Identified gap: No disclosure in Masson of dynamic task generation responsive to AUS findings or current loan status. The static-vs-dynamic distinction is dispositive.
Claim 1
mapping Automated Underwriting System (AUS) results to system conditions
Identified gap: The AUS-to-system-conditions mapping is absent from both references; the examiner provides no cited passage on this point.

Amendment risk

Written descriptionLow

ClarityMedium

New matterLow

Drafted response

Amendment and argument language produced from the validated Structured Analysis above. In the live workbench you edit either side and submit when ready.

Posture choice: Argue + amend paired. Argument hits the dispositive doctrinal gap (Masson static vs claimed dynamic); amendment narrows claim 1 to the limitation Masson can't reach, so the §103 vulnerability is removed even if the argument loses. Use argument-only on the cleanest first responses; amendment-only when you'd rather narrow than litigate. Both = belt and suspenders.

Amendment to claim 1

1. (Currently amended) A method for managing a loan origination process, the method comprising: by a chat manager, in response to receiving a message from a user conversation, extracting borrower details and loan conditions; using a task library to generate tasks according to the current loan status including AUS findings, wherein the task library is dynamically updated based on the current loan status and the AUS findings; and displaying a system-generated response to the user that directs subsequent steps in the loan process, wherein the AUS findings are mapped to system conditions to update the task library.

Rationale

Traversal of the §103 rejection over Agarwal in view of Masson

Try a voice:

When to pick: Surgical traversal. Minimizes prosecution-history estoppel and earns examiner attention by hitting only the dispositive gap. Strongest on first responses where the rejection is structurally weak.

Masson does not supply the dynamic task-library limitation recited in claim 1. Masson ¶ 16 describes a static list of pre-defined lending strategies, finalized in advance based on historical performance and optional manual changes — not a task library that dynamically generates tasks from current loan status and AUS findings. The architectural gap is dispositive: Masson's strategies are inputs to a pre-baked repository; the claims require generation responsive to live status. The Examiner has cited no Masson passage to bridge that gap.

The Examiner's motivation rationale — that Masson's system 'is unable to capture industry knowledge' and requires 'several teams' to produce a higher-quality strategy — addresses a generic strategy-quality concern, not a technical reason to restructure Masson's static architecture into a status-responsive task generator. This is conclusory under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007), which requires articulated reasoning with rational underpinning.

Withdrawal of the §103 rejection of claims 1–5 is respectfully requested.

Reference precedent

Similar OAs retrieved from the public USPTO corpus by the in-house embedding model. Surfaced so the draft sits in the context of how this rejection family has historically played out.

App 17/812,xxxSimilarity 89%
Static-vs-dynamic distinction on a 'task library' / 'strategy library' combination rejection
Same rebuttal posture: examiner mapped a static repository to a claimed dynamic generator by shared terminology; argued the structural and functional difference under KSR.
Rejection withdrawn after first response
App 16/954,xxxSimilarity 82%
Generative-AI / LLM claims — hindsight on 'shared word' motivation
Argued that the examiner relied on the word 'library' shared between Masson and the claim, without any reasoning why the cited system would adopt the claimed architecture.
Allowance after RCE + first response
App 16/441,xxxSimilarity 74%
AUS / dynamic-status feedback loop missing from cited combination
PTAB agreed that combining a chat interface with a static strategy list did not teach a dynamic task generator responsive to underwriting feedback.
Final rejection appealed → reversed at PTAB

Automated checks

Inline guards that run on every draft before you see it. Catches the structural defects that would otherwise reach the client letter.

§112(d) claim-breadth check
checking…
Cite-clean check
checking…
Statute-mismatch check
checking…
Spec-support trace
checking…

Analysis report preview

The bilingual analysis report, ready to send. Full DOCX and PDF rendering happens after submission; this is the executive-summary snippet.

Allowance likelihood: highillustrative

English (US)

Executive summary

The §103 rejection over Agarwal in view of Masson rests on Masson's 'task library' supplying the dynamic, status-responsive task-generation limitation of claim 1. Masson ¶ 16 actually discloses a STATIC repository of pre-developed lending strategies — not a dynamic generator. The examiner's mapping relies on the shared word 'library' and reads the claim language back into the reference. We recommend a one-paragraph narrowing amendment to claim 1 specifying dynamic task-library updating from current loan status and AUS findings, supported by spec ¶¶ [0059], [0062], [0067], [0069]. Estimated likelihood of allowance after first response: high.

Recommended strategy: amend + argue (paired response)
Amendment risk: low (spec ¶¶ [0059], [0062], [0067], [0069] support the dynamic-update behavior)
Lead authority: KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007)
Estimated practitioner hours saved on the full OA response: ~8 (end-to-end, vs. handling it unaided)

繁體中文 (TW)

結論摘要

本件 §103 核駁援引 Agarwal 與 Masson 之結合，主張 Masson 提供請求項 1 所述之「動態且具狀態回應性之任務生成」（dynamic, status-responsive task generation）。然而 Masson ¶ 16 所揭示者實為「靜態策略清單」（static strategy list），即預先建構並依績效調整之策略集合，並非依當前貸款狀態動態生成任務之機制。審查官之映射依賴於請求項與 Masson 共享之「library」一詞，並將請求項語言反推回引證文獻，屬事後諸葛重建（hindsight）。建議於請求項 1 加入一段限縮性修正，敘明任務庫依當前貸款狀態（含 AUS findings）動態更新，並以說明書 ¶¶ [0059]、[0062]、[0067]、[0069] 提供書面揭示支持。預期首次答辯後即可獲准之機率：高。

建議策略：修正＋答辯雙軌應對
修正風險：低（說明書 ¶¶ [0059]、[0062]、[0067]、[0069] 支持動態更新行為）
主要援引判例：KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007)
預估節省從業人員工時（整份 OA 答辯）：約 8 小時（相較於人工從頭處理）

≈ 8 practitioner-hours saved on the full OA responseillustrativeDOCX · PDF · plain text

Allowance likelihood and hours saved are illustrative figures on this sample — not a computed result for a live case.

Sample workbench — edit it live