Prosecution Insights
Last updated: November 20, 2026
Application No. 19/308,787

DELEGATION OF TASKS IN AN ENTERPRISE ENVIRONMENT

Non-Final OA §101
Filed
Aug 25, 2025
Priority
Nov 18, 2022 — continuation of 12/400,159
Examiner
WAESCO, JOSEPH M
Art Unit
3625
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
ADP Inc.
OA Round
1 (Non-Final)
46%
Grant Probability
Moderate
1-2
OA Rounds
2y 0m
Est. Remaining
89%
With Interview

Examiner Intelligence

Grants 46% of resolved cases
46%
Career Allowance Rate
222 granted / 478 resolved
-5.6% vs TC avg
Strong +42% interview lift
Without
With
+42.4%
Interview Lift
resolved cases with interview
Typical timeline
3y 3m
Avg Prosecution
38 currently pending
Career history
544
Total Applications
across all art units

Statute-Specific Performance

§101
48.4%
+8.4% vs TC avg
§103
34.5%
-5.5% vs TC avg
§102
2.8%
-37.2% vs TC avg
§112
13.3%
-26.7% vs TC avg
Black line = Tech Center average estimate • Based on career data from 478 resolved cases

Office Action

§101
DETAILED ACTION Claims 1-20 are pending. Claims 1-20 are considered in this Office action. Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Information Disclosure Statement The information disclosure statement (IDS) submitted on 2/2/2026 has been acknowledged. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. The initialed and dated copy of Applicant’s IDS form 1449 is attached to the instant Office action. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the claims at issue are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a nonstatutory double patenting ground provided the reference application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The USPTO internet Web site contains terminal disclaimer forms which may be used. Please visit http://www.uspto.gov/forms/. The filing date of the application will determine what form should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to http://www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp. Claims 1, 14, and 19 of the current application (Hereby known as ‘787) is rejected on the grounds of nonstatutory double patenting as being unpatentable over claim 1 of U.S. Patent No. 12,400,159 (Hereby known as ‘159). Although the claims at issue are not identical, they are not patentably distinct from each other because: Regarding Claims 1, 14, and 19, Claims 1,14, and 19 of the current application (‘787) recite substantially similar steps of '159 – Claim 1. Claims 1, 14, and 19 of ‘787 recites the steps of: identify that a delegating user associated with an enterprise service is out-of-office or unavailable during a first time period; automatically create, responsive to the identification, a delegation that (i) identifies one or more delegate users and (ii) specifies temporal restrictions that include the first time period; detect a task, associated with a request from a first device, that is actionable by the delegating user within the enterprise service; add the task to a task queue of each of: the delegating user and the one or more delegate users; notify the one or more delegate users that the task requires action; authenticate a second device of a first delegate user of the one or more delegate users; obtain, from the first delegate user, an approval of the task; and remove, responsive to the approval, the task from the task queue of each of the delegating user and the one or more delegate users. Whereas Claim 1 of ‘159 states: receive, from a first device remote from the computing device, via a network using a secure communication channel, a first request to approve a task associated with a first account identifier; determine, based on an account profile for the first account identifier, that the first account identifier is associated with a second account identifier; retrieve, from a database, data associated with the second account identifier, the data structure including one or more tasks linked with the second account identifier; append, responsive to retrieval of the data, the task to the data such that the task is included in the one or more tasks; cause a second device, associated with the second account identifier, to generate a first graphical user interface that includes a first notification of the task; receive, from the second device, first information that includes (1) a device signature associated with the second device and (2) an authentication token of the second account identifier; authenticate the second device in response to receipt of the first information; cause, responsive to authentication of the second device, the second device to generate a second graphical user interface that includes a second notification with a second request for approval of the task; control, responsive to receipt of the approval of the task, execution of an application stored on the second device to cause the second device to perform one or more actions associated with implementation of the task; and truncate, responsive to performance of the one or more actions, the data to remove the task from the one or more tasks. These are obvious variants of each other as both recite substantially the same limitations. Further, elimination of an element or its functions is deemed to be obvious in light of prior art teachings of at least the recited element or its functions (see In re Karlson, 136 USPQ 184, 186; 311 F2d 581 (CCPA 1963)), thereby rendering the elimination of any elements recited in the claims of the related patent (that are not recited in the instant claims) obvious. Thus, Claims 1, 14, and 19 of the current application is an obvious variant of claim 1 in ‘159. Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Alice – Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Claims 1, 14, and 19 recite the limitations for identify that a delegating user associated with an enterprise service is out-of-office or unavailable during a first time period (Receiving and Analyzing the Received Information, an Observation and Evaluation, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity),automatically create, responsive to the identification, a delegation that (i) identifies one or more delegate users and (ii) specifies temporal restrictions that include the first time period (Analyzing the Information, an Evaluation, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), detect a task, associated with a request from a first device, that is actionable by the delegating user within the enterprise service (Analyzing the Information, an Evaluation, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), add the task to a task queue of each of: the delegating user and the one or more delegate users (Analyzing the Information, an Evaluation, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), notify the one or more delegate users that the task requires action; authenticate a second device of a first delegate user of the one or more delegate users (Analyzing the Information, an Evaluation, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), obtain, from the first delegate user, an approval of the task (Receiving and Transmitting the Analyzed Information, an Observation and Judgment, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), and remove, responsive to the approval, the task from the task queue of each of the delegating user and the one or more delegate users (Transmitting the Analyzed Information, a Judgment, a Mental Process; Managing Human Behavior, i.e. managing tasks; a Certain Method of Organizing Human Activity), which under their broadest reasonable interpretation, covers performance of the limitation in the mind for the purposes of managing tasks, which is Organizing Human Behavior, but for the recitation of generic computer components. That is, other than reciting a system, one or more processors, memory, and computer-readable medium, nothing in the claim elements preclude the step from practically being performed or read into the mind for the purposes of Managing Human Activity. If a claim limitation, under its broadest reasonable interpretation, covers performance of the limitation in the mind but for the recitation of generic computer components, then it falls within the “Mental Processes” grouping of abstract ideas, an observation, evaluation, and judgment. Further, as described above, the claims recite limitations for Managing Human Activity/Behavior, a “Certain Method of Organizing Human Activity”. Accordingly, the claim recites an abstract idea. This judicial exception is not integrated into a practical application. In particular, the claim recites the above stated additional elements to perform the abstract limitations as above. The system, one or more processors, memory, and computer-readable medium are recited at a high-level of generality (i.e., as a generic software/module performing a generic computer function of storing, retrieving, sending, and processing data) such that they amount to no more than mere instructions to apply the exception using generic computer components. Even if taken as an additional element, the receiving and transmitting steps above are at best insignificant extra-solution activity as these are receiving, storing, and transmitting data as per the MPEP 2106.05(d). Accordingly, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. The claim is directed to an abstract idea. The claim does not include additional elements that are sufficient to amount to significantly more than the judicial exception, when considered both individually and as an ordered combination. As discussed above with respect to integration of the abstract idea into a practical application, the additional element being used to perform the abstract limitations stated above amount to no more than mere instructions to apply the exception using generic computer components. Mere instructions to apply an exception using generic computer components cannot provide an inventive concept. The claim is not patent eligible. Applicant’s Specification states: “[0030] The client device 206 is representative of one or more client devices 206 that may be coupled to the network 215. The client device 206 may be representative of a client device used by the user and/or a corresponding client devices 206 used by project users. The client device 206 can include any computer system. Examples of computer systems can include a desktop computer, a laptop computer, personal digital assistants, cellular telephones, smartphones, set-top boxes, music players, web pads, tablet computer systems, game consoles, electronic book readers, or other devices with like capability. ” Which shows that these steps can be performed on any generic computing device with a processor and memory, which can be used to perform the abstract limitations, such as a laptop, phone, desktop, etc., and from this interpretation, one would reasonably deduce the aforementioned steps are all functions that can be done on generic components, and thus application of an abstract idea on a generic computer, as per the Alice decision and not requiring further analysis under Berkheimer, but for edification the Applicant’s specification has been used as above satisfying any such requirement. This is “Applying It” by utilizing current technologies. For the receiving and transmitting steps that were provisionally considered extra-solution activity in Step 2A above, if they were to be considered additional elements, they have been re-evaluated in Step 2B and determined to be well-understood, routine, conventional, activity in the field. The background does not provide any indication that the additional elements, such as the system, medium, processor, etc., nor the receiving and transmitting steps as above, are anything other than a generic, and the MPEP Section 2106.05(d) indicates that mere collection or receipt, storing, or transmission of data is a well‐understood, routine, and conventional function when it is claimed in a merely generic manner (as it is here). For these reasons, there is no inventive concept. The claim is not patent eligible. Claims 2-6, 9-13, 15-18, and 20 contain the identified abstract ideas, further narrowing them, with the additional elements of a user interface and application which are highly generalized when considered as part of a practical application or under prong 2 of the Alice analysis of the MPEP, thus not integrated into a practical application, nor are they significantly more for the same reasons and rationale as above. After considering all claim elements, both individually and in combination, Examiner has determined that the claims are directed to the above abstract ideas and do not amount to significantly more. Therefore, the claims and dependent claims are rejected under 35 U.S.C. 101 as being directed to non-statutory subject matter. See Alice Corporation Pty. Ltd. v. CLS Bank International, No. 13–298. Examiner notes Claim 7 would be eligible if not for depending on Claim 1. Allowable Subject Matter Claims 1-20 have overcome the prior art and would be allowable if amended to overcome the 35 USC 101 rejections. The closest prior art of record is Pakanathi (U.S. Publication No. 2016/029,2601), Babeanu (U.S. Publication No. 2009/006,4280) and Fowler (U.S. Publication No. 2018/012,9995). Pakanathi, a system and method for delegation of tasks to other personnel in an ERP application, teaches to identify a task associated with a first user, the task associated with a request related to a subject user, determine that the first user is associated with an indication to delegate the task to at least one other user, generate a first notification for the at least one other user to act on the indication to delegate the task, authenticate one of the at least one other user in response to the notification, to obtain a grant or a denial of the request related to the subject user in response to the notification from the one of the at least one user, generate a user interface for the first user to define the temporal data associated with the task, which allows the user to select the at least one user to whom the task is delegated during the time period, to generate a user interface for the one of the at least one other user indicating that the request is a delegated request, to define a delegation of the task by identifying an action associated with the task, obtain a selection of a user or a user group to whom the action is delegated, and associate the delegation of the task with first user, but it does not explicitly state that the receiving user can accept or deny, nor does it teach the appending and truncating of the task data based on the approvals. Babeanu, a framework for delegating roles in human resources ERP systems, teaches users accepting and denying delegations where the selecting user interface device is used to notify the user and approve or reject the delegation and to generate a second notification comprising the approval or denial of the request, the second notification being transmitted to the subject user, but it does not explicitly stat the control of an application on the second device nor does it teach the truncation of data from tasks or removing of tasks. Fowler, a system and method for efficiency enhancements in task management application, teaches assigning of tasks to work groups of several employees and when an employee assumes a task, the other employees are notified, assigned tasks to roles and employees, use of a calendar service along with authentication of user, but it does not explicitly stat the control of an application on the second device nor does it teach the truncation of data from tasks or removing of tasks. None of the above prior art explicitly teaches teach this r it does not explicitly stat the control of an application on the second device with the truncation of data from tasks or removing of tasks, use of authentication tokens, along with the other limitations, and these are the reasons which adequately reflect the Examiner's opinion as to why Claims 1-20 are allowable over the prior art of record. Conclusion The prior art made of record is considered pertinent to applicant's disclosure. US 20240086859 A1 GILLAM; Michael SYSTEM AND METHOD FOR OPTIMIZED RESOURCE ALLOCATION AND SCHEDULING US 20180129995 A1 Fowler; Chad et al. EFFICIENCY ENHANCEMENTS IN TASK MANAGEMENT APPLICATIONS US 20160292601 A1 Pakanathi; Sriram DELEGATION OF TASKS TO OTHER PERSONNEL IN AN ERP APPLICATION US 20090064280 A1 Babeanu; Razvan Alexandre et al. FRAMEWORK FOR DELEGATING ROLES IN HUMAN RESOURCES ERP SYSTEMS US 20230090862 A1 Cupersmith; Michelle et al. GAMING SERVICE AUTOMATION SYSTEM WITH GRAPHICAL USER INTERFACE US 20200410133 A1 Barday; Kabir A. et al. DATA PROCESSING SYSTEMS FOR FULFILLING DATA SUBJECT ACCESS REQUESTS AND RELATED METHODS US 20200394595 A1 Fowler; Chad et al. EFFICIENCY ENHANCEMENTS IN TASK MANAGEMENT APPLICATIONS US 20190259038 A1 Papa; Steven Paul et al. Computer-guided Corporate Governance with Document Generation and Execution US 20190213528 A1 GUPTA; Rahul et al. DIGITAL ASSISTANT TASK MANAGEMENT US 20180075413 A1 Culver; Andrew et al. COLLABORATION TOOL US 20160155135 A1 Papa; Steven Paul et al. Computer-guided Corporate Governance with Document Generation and Execution US 20150269854 A1 Maharaj; Ashok Doraisamy et al. Computer Implemented Network Enabled Learning Aid and a System for Measuring a Learner's Progress US 20150220649 A1 Papa; Steven Paul et al. Computer-guided Corporate Governance with Document Generation and Execution Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOSEPH M WAESCO whose telephone number is (571)272-9913. The examiner can normally be reached on 8 AM - 5 PM M-F. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, BETH BOSWELL can be reached on (571) 272-6737. The fax phone number for the organization where this application or proceeding is assigned is 571-273-1348. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /JOSEPH M WAESCO/Primary Examiner, Art Unit 3625B 11/5/2026
Read full office action

Prosecution Timeline

Aug 25, 2025
Application Filed
Nov 10, 2026
Non-Final Rejection mailed — §101 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12770160
SYSTEMS AND METHODS FOR PREDICTING CONSUMER SPENDING BEHAVIOR BASED ON HISTORICAL TRANSACTION ACTIVITY PROGRESSIONS
2y 5m to grant Granted Oct 20, 2026
Patent 12749089
SYSTEMS AND METHODS FOR ATTRIBUTING ELECTRONIC PURCHASE EVENTS TO PREVIOUS ONLINE AND OFFLINE ACTIVITY OF THE PURCHASER
2y 9m to grant Granted Sep 29, 2026
Patent 12725103
AUTOMATED TASK PLANNING SYSTEM AND METHOD USING HEURISTIC EVALUATION VALUE CALCULATED BASED ON CAUSAL ACTION NETWORK
2y 7m to grant Granted Sep 01, 2026
Patent 12718171
SYSTEMS AND METHODS FOR QUANTIFYING NETWORK GROWTH USING ARTIFICIAL INTELLIGENCE AND MACHINE LEARNING MODELS
2y 4m to grant Granted Aug 25, 2026
Patent 12709971
DEVICES, SYSTEMS, AND METHODS FOR GENERATING DRILLING REPORTS
2y 1m to grant Granted Aug 18, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
46%
Grant Probability
89%
With Interview (+42.4%)
3y 3m (~2y 0m remaining)
Median Time to Grant
Low
PTA Risk
Based on 478 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month