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 13 — TR-13
Pricing & Estimation
Taskrabbit's estimation stack — eligibility, address validation, estimated price, window-dependent pricing and provider rates — and its relationship to duration intelligence.
Executive Finding
Taskrabbit publicly evidences address validation, service eligibility and price estimation by appointment window, but price estimation is not equivalent to estimation of the time required to complete a task and is not treated as such anywhere in this review.
Observed Workflow
- Address Validation
- Service Eligibility
- Tasker Rate
- Estimated Price
- Price by Window
- Final Hourly Billing
Patent Question
Does Taskrabbit's computational estimation architecture bear on the patent's AI-duration element, or is it a distinct function?
Patent Architecture Sequence
- Task Information
- AI Processing
- Recommended Task Duration
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 assigned amount of time required to complete a task is used in generating the schedule; no claimed element is directed to price determination.
Specification / Embodiment Disclosure
- The specification is concerned with scheduling determinations rather than with commercial pricing, though duration and cost are related in practice.
Potential Future Patent Evolution
Potential Future Patent Development — Subject to Patent Attorney Review.
- Pricing derived from predicted duration and route cost, so that commercial and scheduling intelligence share one model.
Taskrabbit Position
- Partner integration material describes obtaining an estimate for a service at a validated address before availability is retrieved.
- Estimated price is presented before booking and may vary with the appointment window chosen.
- The final amount reflects the Tasker's hourly rate applied to the time actually worked.
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 estimation stack demonstrates system-side computation at the point of capture, which shows the technical capability to compute against a validated task and address.
- Window-dependent pricing indicates that time is already a variable in the commercial model.
- None of this establishes a duration determination, and the review does not treat it as doing so.
Difference / Gap
- Price estimation answers what it will cost; duration estimation answers how long it will take. Only the latter is an element of the architecture.
- A currency figure derived from a rate and an assumed number of hours does not evidence a system-determined assumption about those hours.
Where Public Evidence Is Incomplete
- Whether the estimate is computed from an internal duration assumption, and whether that assumption is category-fixed or derived, is not disclosed.
- The full parameter set of the partner estimate step is not openly published.
Patent \u2194 Taskrabbit Mapping
| Patent element | Taskrabbit position | Status |
|---|---|---|
| Computational processing of task and location input | Estimate API accepts service and postal code / address, returns eligibility and estimated price | Partial Correspondence |
| Recommended task duration output | Availability API returns date/time windows with estimated prices | Not Publicly Established |
Strategic Question
- Could Taskrabbit's underlying pricing logic depend in part upon expected service duration?
- That question is commercially interesting, but the answer cannot be inferred from price output alone.
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.
- Duration-derived pricing, and pricing that accounts for travel and sequencing cost, are not publicly established.
Evidence Confidence
Pricing behaviour and hourly billing are directly evidenced in help documentation; the partner estimate step is described in integration material rather than in an openly published API reference.
Strategic Interpretation
- Distinguishing price from duration protects the review from the most obvious challenge a technical reviewer would raise.
- It also sharpens the differentiation argument: the commercial layer is mature while the scheduling-intelligence layer beneath it is not publicly evidenced.
Page Conclusion
Estimation Observed — Duration Not Established
There is an observable concept of computational estimation within Taskrabbit. Price estimation should not be characterised as satisfaction of the patent's AI-duration element without additional evidence.