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 16 — TR-16
Multi-Task & Route Optimisation
Whether multiple engagements are composed into an optimised provider day — clustering, travel time, traffic awareness, multi-customer schedule construction — as distinct from booking one provider for one customer.
Executive Finding
No public source establishes that Taskrabbit constructs an optimised provider day, clusters tasks geographically, calculates travel time or performs route optimisation; this is recorded as no sufficient public evidence identified and is a major differentiation area.
Observed Workflow
- Independent Bookings
- Provider Accepts Individually
- Provider Manages Own Travel
- No Evidenced Platform Sequencing
Patent Question
Does Taskrabbit publicly construct an optimised multi-task provider day incorporating travel, distance or routing?
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
- A task schedule is generated for a provider consistent with availability, location and the assigned duration.
Specification / Embodiment Disclosure
- The specification contemplates schedules accounting for geographic and time constraints across the tasks assigned to a provider.
Potential Future Patent Evolution
Potential Future Patent Development — Subject to Patent Attorney Review.
- Traffic-aware and weather-aware sequencing, dynamic clustering across customers and continuous re-optimisation of a provider's day.
Taskrabbit Position
- Providers accept engagements individually and manage their own travel between them; guidance addresses allowing time between tasks rather than the platform doing so.
- No public material describes the platform grouping nearby tasks, computing travel time between engagements or offering windows selected for route efficiency.
- Availability is expressed by the provider in blocks, which is consistent with self-managed rather than system-composed days.
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
- Single-engagement scheduling is well evidenced; multi-engagement composition is a materially different computational problem and is not evidenced at all.
- The underlying data — location, duration expectation, availability — exists, so the absence is one of disclosed function rather than of raw inputs.
- Nothing here supports a conclusion that the capability does not exist privately; only that no public evidence of it was identified.
Difference / Gap
- Booking one provider for one customer does not require sequencing, travel modelling or optimisation; the architecture contemplates schedule construction under those constraints.
Where Public Evidence Is Incomplete
- Whether internal tooling sequences provider days or suggests adjacent work is not publicly established.
- Whether retail-originated assembly volume is batched geographically behind the scenes is not disclosed.
Patent \u2194 Taskrabbit Mapping
| Patent element | Taskrabbit position | Status |
|---|---|---|
| Individual bookings | Established | Strong Observed Correspondence |
| Provider calendar | Established | Strong Observed Correspondence |
| Multiple daily availability blocks | Established | Strong Observed Correspondence |
| Algorithmically optimised multi-job daily schedule | No sufficient public evidence identified | Not Publicly Established |
| Travel-aware scheduling | No sufficient public evidence identified | Not Publicly Established |
| Route optimisation | No sufficient public evidence identified | Not Publicly Established |
Investigation Checklist
- Multiple jobs per Tasker day?Partial
- Optimised sequence of tasks?Evidence Required
- Travel time between jobs?Evidence Required
- Distance between jobs?Evidence Required
- Route calculation?Evidence Required
- Traffic data?Evidence Required
- Geographic task clustering?Evidence Required
- Schedule buffers?Evidence Required
- Delay propagation handling?Evidence Required
- Automatic schedule reconstruction?Evidence Required
Language Rule
- This review does not state that Taskrabbit lacks route optimisation.
- It states: no sufficient public evidence has presently been identified establishing that Taskrabbit constructs an optimised multi-task provider schedule incorporating inter-task travel or route optimisation.
Patent-Position Significance
- Marketplace architecture: customer books provider.
- Orchestration architecture: system constructs an economically and operationally viable provider work schedule.
- The distinction between the two may become commercially important as service platforms automate.
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.
- 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.
Evidence Confidence
Provider guidance addresses travel and back-to-back work as a matter for the provider's own judgement. No located source describes platform-side sequencing, clustering, travel-time computation or route optimisation.
Strategic Interpretation
- This is the most significant differentiation area identified in the Taskrabbit review.
- It is also the direction utilisation economics push every marketplace toward, which is what makes architectural coverage here commercially material.