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 21 — TR-21
Patent Architecture Beyond Publicly Established Taskrabbit Functionality
This section is deliberately not titled as a list of company deficiencies. It records two distinct things: architecture described by the application that has not been established from Taskrabbit's public material, and functions where the public record is simply incomplete. The two must not be conflated.
An Important Distinction
The application describes a function that no public Taskrabbit material addresses in any form. This indicates architectural reach, not an assertion about the company's internal systems.
Related company behaviour is observable but the mechanism is undisclosed. The position is unresolved and should be treated as a question for diligence, not as a finding.
Four-Column Classification
A
Public Evidence Identified
- Historical performance
- Replacement provider after cancellation
B
Partial Evidence
- Provider ranking / recommendation
- Price estimation as computational processing
- AI-mediated service discovery
C
Not Publicly Established
- AI task duration
- Multi-job daily schedule construction
- Geographic task clustering
- Travel-aware scheduling
- Traffic-aware scheduling
- Weather-aware scheduling
- Historical performance directly altering future schedules
- Fully autonomous schedule recovery (C / D)
D
Future Patent Development
- Multi-agent orchestration
- Fully autonomous schedule recovery (C / D)
- Credential governance within suitability
Language rule: no public evidence is never converted into a statement that Taskrabbit does not have the functionality.
Architecture Beyond Publicly Established Functionality
Multi-Task & Route Optimisation
Full analysis →Patent architecture: A task schedule is generated for a provider consistent with availability, location and the assigned duration.
Public position: Providers accept engagements individually and manage their own travel between them; guidance addresses allowing time between tasks rather than the platform doing so.
Architectural reach: Geographic clustering, travel-time calculation, traffic-aware scheduling, provider-day optimisation and multi-customer schedule construction are all areas where the architecture extends beyond publicly established functionality.
Where Public Evidence Is Incomplete
Task Duration Intelligence
Full analysis →The architecture assigns the duration; the observable product appears to receive it from the parties.
Diligence Questions Arising
- How is the duration presented to the customer at booking derived, and does that derivation draw on historical completion data?
- Is provider ordering within the presented shortlist model-driven, and which signals are weighted?
- Does any internal system construct or sequence a provider's day, and does it account for travel between engagements?
- Is any completion-probability or suitability prediction applied before providers are presented?
- Which publicly announced AI initiatives operate on scheduling rather than on discovery and support?
- Does the retail integration channel originate tasks through a documented programmatic interface?
Technical alignment is an analytical assessment of publicly observable functionality and does not constitute a legal conclusion regarding infringement.