Engagement-scoped result
Result, coverage status, jurisdiction path, confidence, and rule version are written to the worker-client engagement, not the worker globally.
For compliance, legal, and ops leaders
Classification readiness, recorded against the engagement.
Run contractor assessments against the worker and client context, record result with confidence and rule version, and stop unsupported or employee outcomes from reaching activation.
Engagement-scopedVersioned rule setsMaker-checker reviewReclassification triggers
Eligible
Contractor, UK design retainer
Independent worker, multiple clients, project-scoped scope, fixed milestones.
CoverageActive
ConfidenceHigh
ReviewerAuto-pass
Review
Dependent, full-time growth lead
Single client, fixed schedule, integrated reporting line, control indicators present.
CoverageHold
ConfidenceMedium
ReviewerMaker-checker
Two engagements, two outcomes. The same questionnaire answered differently produces different coverage, different paper, and different downstream payout posture. AoR keeps that distinction visible.
The classification gate
Decide whether the work fits a contractor model before anything else moves.
Misclassified workers create the most expensive cleanup in any contractor program. AoR runs the assessment against the worker and client context, records the result with confidence and rule version, and routes ambiguous cases through a real review path rather than a one-line admin override.
- Engagement-scoped result, confidence, and rule version on the record.
- Employee, unsupported, and indeterminate outcomes follow stop or review paths.
- Reclassification can mark signed paper stale and trigger a refresh.
What Gruv records
Six properties on every classification, every time.
Every assessment is more than a yes or no. The downstream gates need confidence, version, jurisdiction, and reason codes to act with consistency.
Reason codes on every outcome
Employee, unsupported, indeterminate, and dependent-contractor outcomes carry reason codes the next team can act on.
Maker-checker review queue
Manual cases route to a review queue with a second approver, recorded decision, and audit trail attached to the assessment.
Versioned rule sets
Rule version is captured on every assessment so historical decisions can be re-read without ambiguity.
Reclassification triggers
Expiry, law update, payout concentration, and assessment updates can mark a result stale and request a recheck.
Visible to downstream gates
Documents, agreements, payout holds, and monitoring all read the same classification truth on the engagement.
Four steps from input to bound result.
Each step is observable. The result is the same record every other AoR gate reads.
01
Capture engagement context
Pull worker country, client entity, jurisdiction overlay, and engagement type into the assessment input.
02
Run the assessment
Apply the current rule set, record result, confidence, and coverage status, and write the outcome to the engagement.
03
Route ambiguous cases
Send manual, dependent-contractor, and indeterminate outcomes through the review queue with a second approver.
04
Bind to downstream gates
Documents, paper, payout holds, and monitoring read the saved result instead of recomputing on the fly.
Assessment
ENG-9824 / Aria Patel
- Worker country
- United Kingdom
- Engagement
- Design retainer
- Jurisdiction overlay
- UK launch v1
- Result
- Contractor, eligible
- Confidence
- High
- Rule version
- v2025.04
- Reviewer
- Auto-pass
- Expires
- 31 Mar 2027
Bound to engagement ENG-9824
Auditable record
The assessment is the record. Not a screenshot, not a thread.
Compliance audits ask for the result, the data behind it, and the reason it was accepted. AoR keeps each of those bound to the engagement so you can answer that question quickly when someone asks.
- Result and reason codes attached to the engagement record.
- Rule version retained for historical comparison.
- Reviewer identity stored for manual outcomes.
- Recheck history visible without rebuilding from logs.
Where classification readiness earns its keep.
Programs reach for AoR classification when the cost of a wrong call shows up in legal exposure, payout reversals, or audit findings.
Global contractor programs
Get one assessment surface for every contractor engagement so finance, legal, and ops are looking at the same record.
Marketplace worker activation
Tie marketplace worker activation to a passing classification so unsupported regions and roles never reach payout setup.
Compliance-led migrations
Re-run assessments on existing populations after a labor-law change and see who needs fresh paper or reclassification.
Audit-ready vendor records
Keep result, confidence, rule version, and reviewer identity attached for follow-up support and audit response.
After classification
Pass the result into onboarding without losing context.
Classification is the start, not the finish. The next gate collects required documents, registrations, screening, and tax readiness against the same engagement record.
Frequently Asked Questions
How does the classification assessment know which path to run?+
Assessments take the worker country, client context, jurisdiction overlay, and engagement details into account. The selected rule set version is recorded on the result so the same engagement assessed in a future quarter can be compared cleanly.
What happens to manual or indeterminate cases?+
Indeterminate, dependent-contractor, and manual outcomes are routed to a maker-checker review queue rather than approved by a single admin. The decision and reviewer identity stay attached to the engagement record.
Does a passing assessment commit the engagement?+
No. A passing classification is the first gate. The engagement still has to clear documents, signed paper, payout setup, screening, and tax readiness before activation.
When does an existing assessment go stale?+
On expiry, on labor-law update, on payout concentration threshold change, and when the underlying assessment is updated. Monitoring records the trigger so the right teams know what to revalidate.
Can we override a classification result?+
Override requests move through a support case with a second approver. The approval, rejection, and reasoning are recorded against the assessment instead of being lost to a chat thread.
Does Gruv guarantee a contractor outcome?+
No. Employee, unsupported, and blocked outcomes follow stop paths. Gruv records the outcome and reason codes for follow-up, but the underlying labor reality drives the result.
Ready to map a classification rollout?
Bring your contractor cohort, launch countries, jurisdiction overlays, and reviewer owners. Gruv can scope the assessments and reason codes your team needs before activation.