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 06 — TR-06
Provider Skills
Taskrabbit's treatment of provider capability data: categories, declared skills, tools, category expectations and how capability is represented to customers and used to constrain candidacy.
Executive Finding
Structured, provider-declared categories and skill areas operate as a hard constraint on which Taskers may be presented, aligning closely with the patent's skills element — but skills, qualifications and experience are treated here as three separate concepts, and only skills is strongly evidenced.
Observed Workflow
- Provider Registration
- Category Selection
- Skill & Tool Declaration
- Category Expectations Accepted
- Activation
- Capability Record Constrains Candidacy
Patent Question
Does Taskrabbit's publicly documented treatment of Tasker skills correspond to the provider capability input of the patent architecture — and can skill be treated as equivalent to qualification or experience?
Patent Architecture Sequence
- Provider Skill / Qualification / Experience
- Capability Confirmation
- Provider Suitability
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
- Service provider records maintained within the network include skills information used, with other provider data, to identify a subset of suitable providers.
Specification / Embodiment Disclosure
- The specification describes provider records comprising skills, qualifications and experience as distinct attributes of a provider profile.
- Embodiments contemplate capability data being weighted alongside historical performance when providers are assessed for a task.
Potential Future Patent Evolution
Potential Future Patent Development — Subject to Patent Attorney Review.
- Machine-verified capability, capability inferred from completed-task evidence, and capability modelled at sub-task rather than category level.
Taskrabbit Position
- Taskers select the service categories and skill areas they wish to work in during registration; those selections determine the tasks they may be offered.
- Category material sets out expectations including required tools and the nature of the work, which the Tasker accepts on entering the category.
- Skills and specialities are surfaced on the public profile alongside completed-task counts, so capability is both a filter and a customer-facing signal.
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
- Skills: strong alignment. Structured, category-level capability data is held and used as a filtering input — the exact functional role the architecture assigns it.
- Qualifications: partial only. Verification exists as an activation gate; there is no public evidence of a machine-readable credential record used as a task-level constraint.
- Experience: partial only. Completed-task counts and ratings are displayed, but no public source establishes their use as a capability constraint rather than a reputation signal.
Difference / Gap
- Capability is self-declared rather than assessed, so the record describes what a provider elects to do, not what they have been verified as able to do.
- Category granularity is coarser than the task-level requirement matching the architecture contemplates.
Where Public Evidence Is Incomplete
- Whether any internal capability scoring supplements the declared category set is not publicly disclosed.
- Whether tool possession is recorded as structured data or only as a category expectation is not established.
Patent \u2194 Taskrabbit Mapping
| Patent element | Taskrabbit position | Status |
|---|---|---|
| Provider skill | Tasker declared skills and categories | Strong Observed Correspondence |
| Provider qualification | Category-dependent licensing certifications only | Category-Dependent Evidence |
| Provider experience | Skills & Experience profile section | Partial Correspondence |
Investigation Checklist
- Does Taskrabbit store skills as structured categories?Partial
- Are skills used to determine search eligibility?Answered
- Are skill-specific performance metrics maintained?Partial
- Are skills used when computing provider recommendations?Evidence Required
- Are skills applied within Partner API scheduling?Evidence Required
Important Distinction
- A declared Taskrabbit skill is not automatically mapped to the patent's qualification element.
- A declared Taskrabbit skill is not automatically mapped to the patent's experience element.
- Each concept is assessed separately in this review; see Page 07 / 24 (TR-07).
Search Significance
- Taskrabbit's own guidance states that adding skills can increase a Tasker's visibility.
- Its 2026 Tasker update describes the Skills & Experience section as helping clients find the right match and improving discoverability.
- Capability data therefore operates as an eligibility and visibility variable, not merely as profile decoration.
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.
- Qualification-class records used as matching constraints, and capability inference from completed-task evidence, are not publicly established.
Evidence Confidence
Provider onboarding documentation and public provider profiles both evidence structured, category-level capability data that determines the work a Tasker may be offered.
Strategic Interpretation
- Capability data is the constraint that makes automated selection possible at all; its structure sets the ceiling on matching precision.
- Treating skills, qualifications and experience as one concept overstates alignment — separating them is what makes this analysis defensible under challenge.
Page Conclusion
One Of The Stronger Correspondences
Provider skill is one of the stronger publicly observable functional correspondences with the patent architecture. Qualification and experience are assessed separately and are more limited.