U.S. Patent Position Review — 19/476,586
DATA COMMUNICATIONS NETWORK AND METHOD FOR PROVIDING TASK SCHEDULES TO SERVICE PROVIDERS
Published international application: PCT/AU2024/050370 / WO2024216337A1
Section 15 — TR-15
Rescheduling & Schedule Management
How confirmed engagements are amended, cancelled or recovered after booking, and how much of that process is system-determined rather than human-agreed.
Executive Finding
Post-booking change at Taskrabbit is publicly described as a negotiated process between customer and Tasker, with no evidence of automated schedule reconstruction or substitute-provider assignment.
Observed Workflow
- Confirmed Project
- Change Requested
- Customer / Tasker Agreement
- Rescheduled or Cancelled
- Calendar Updated
Patent Question
How is a booked schedule managed after booking, and how far is that from autonomous schedule recovery?
Patent Position
United States Patent Application No. 19/476,586 — "DATA COMMUNICATIONS NETWORK AND METHOD FOR PROVIDING TASK SCHEDULES TO SERVICE PROVIDERS"
Claimed Patent Element
- The generated task schedule is transmitted to the provider; the claimed elements are directed to generation and transmission rather than to post-booking recovery.
Specification / Embodiment Disclosure
- The specification contemplates schedules being amended and updated schedules being provided as availability or task circumstances change.
Potential Future Patent Evolution
Potential Future Patent Development — Subject to Patent Attorney Review.
- Automated rescheduling, substitute-provider selection on cancellation and schedule reconstruction that preserves the rest of a provider's day.
Taskrabbit Position
- A confirmed appointment can be rescheduled or cancelled in the application, with rescheduling described as agreed between the customer and the Tasker.
- Cancellation policies apply within stated windows and the project record reflects the current status.
- Released time returns to the provider's availability, but no public source describes the platform proposing a replacement provider or a new window automatically.
Public Evidence
Each record below opens the full source entry — extract, publication and access dates, direct URL and archived URL where available — without leaving this analysis.
Technical Alignment
- The system maintains schedule state and reflects changes, which corresponds to the maintenance aspect of the architecture.
- The determination of the new arrangement, however, rests with the parties rather than with the system.
- Recovery from disruption is therefore human-mediated on the public evidence.
Difference / Gap
- No system-generated replacement schedule is evidenced; the architecture contemplates updated schedules being produced and transmitted.
- Cancellation is treated as a commercial and policy event rather than as a scheduling event requiring reconstruction.
Where Public Evidence Is Incomplete
- Whether internal tooling proposes alternatives to support agents or providers is not publicly established.
- Whether high-volume partner channels have any automated recovery path is not disclosed.
Patent \u2194 Taskrabbit Mapping
| Patent element | Taskrabbit position | Status |
|---|---|---|
| Schedule amendment | Customer and Tasker agree a new date/time, then confirm the reschedule in the platform | Partial Correspondence |
| Replacement provider identification | On Tasker cancellation, Taskrabbit can offer a new Tasker; the customer may accept or browse alternatives | Partial Correspondence |
| Autonomous schedule reconstruction | Not established from public material | Not Publicly Established |
Important Finding
- The standard rescheduling workflow involves human agreement before the revised schedule is confirmed.
- This review therefore does not describe Taskrabbit rescheduling as autonomous.
Strategic Importance
- Cancellation handling is more sophisticated than simply cancelling a transaction, because the system supports a recovery journey.
- It remains different from an architecture that detects disruption, identifies a replacement, reoptimises the schedule, accounts for travel, secures customer approval automatically and reconstructs the remaining provider schedule.
Patent Evolution Opportunity — Autonomous Schedule Recovery
- Cancellation / delay → impact analysis → replacement provider identification → availability assessment → travel assessment → schedule reconstruction → customer approval → updated schedule.
- Potential Patent Evolution — Attorney Review Required.
Patent Architecture Beyond Publicly Observed Functionality
The following matters are contemplated by the patent architecture and have not been established from Taskrabbit's public material. Absence of public evidence is not evidence that the functionality is absent from the company's internal technology stack.
- Automated rescheduling, substitute-provider selection and schedule reconstruction after disruption are labelled Potential Future Patent Development — Subject to Patent Attorney Review where they extend past existing disclosure.
Evidence Confidence
Rescheduling and cancellation behaviour is described directly in customer help documentation, including the reliance on agreement between the parties.
Strategic Interpretation
- Disruption recovery is where scheduling systems create the most operational value, and it is presently the least automated part of the observable workflow.
- It is also the clearest bridge between the existing architecture and the evolution section of this portal.