01
Localized
Templates per market
Germany gets German clauses. India gets Indian clauses. Automatic.
For legal, compliance, and program leads
Signed AoR paper locked to the classification behind it
Your German contractor passes classification on Wednesday. By Thursday, Gruv issues a localized agreement referencing that exact result, sends it for signature via DocuSign, and stores the signed PDF with a content hash. If the classification changes later, the paper is flagged stale.
Localized templates per countryLocked to classification result and rule versionSigned PDF stored with content hashStale paper flagged on law change or reclass
Three parties, one record
Signed AoR paper sits between your company, Gruv, and the contractor.
The agreement is bound to the assessment that justified it. Each party reads the same record, so reclassification or law updates never leave one side working from stale paper.
Engagement owner
Your company
- Defines engagement scope and contract intent
- Approves localized templates per market
- Reads agreement state on the engagement record
- Owns final activation decision
Issuing party
Gruv (AoR)
- Issues localized agreements tied to the assessment
- Captures signature and validates provider PDFs
- Stores immutable signed artifacts
- Refreshes paper after reclassification or law update
Counterparty
Contractor
- Signs the localized agreement once
- Receives a copy bound to the engagement
- Sees status updates as paper refreshes
- Acknowledges the latest assessment basis
Operating tokens
What signed paper on Gruv looks like
02
Locked
To the assessment
Rule version, jurisdiction, and classification result stamped on the paper.
03
Immutable
Storage with hash
Signed PDF and event log retrievable for audits in one call.
04
Stale-aware
Refresh on drift
Reclassification or law change marks paper stale. Payouts hold until a new one is signed.
What signed paper carries
Six properties on every signed agreement
The agreement is more than a PDF. It is the record other teams read to confirm the engagement still has valid paper.
Localized templates
Germany gets German-law clauses. Brazil gets Brazilian disclosures. Templates are managed per supported country with jurisdiction-specific overlays.
Locked to the classification
Every agreement records the assessment ID, rule version, and result it was generated against. Reclassification marks the paper stale automatically.
Signature via DocuSign
Gruv sends paper for signature, validates the returned PDF, and captures the signed artifact bound to the engagement.
Immutable storage with content hash
Signed PDFs are stored with a content hash and versioned metadata. Retrievable in one call for audits.
Stale paper signals
Reclassification, law updates, and overlay changes mark paper stale. Payouts hold until a refreshed agreement is signed.
One-click audit pack
Export the agreement, the classification it was tied to, and the signature event. Your auditor stops asking for screenshots.
How it works
How signed paper moves from generated to stored
Four steps. Reclassification triggers a refresh before the next gate passes.
gruv.app › agreements › draft
agreementseng_3f4adraft
DraftLocalized agreement drafted
Engagement
Coral Talent Co. · Worker
aor_3f4a · jurisdiction US-CA
ContractorCA overlay
Template assembled5 / 5
Engagement type · Independent contractor
Scope of services · 2026-Q2 SOW
Compensation · $8,500 / month
Tax basis · 1099-NEC · CA
Term · 12 months · auto-recheck
Anatomy of a signed agreement
Eight retrievable properties on every signed engagement. The artifact is the agreement. The metadata is what makes it defensible in an audit.
Signed PDF + content hash
Immutable artifact with content hash. Retrievable in one API call.
Classification lock
Rule version (v2024.3), jurisdiction overlay, and classification result stamped on the paper.
Signer + timestamp
Signature event with signer IP and UTC timestamp pinned to the engagement.
Localized template
Country template (Germany, India, Brazil) plus jurisdiction overlay snapshot.
Effective term
Term length and recheck cadence. Expiry queues a refresh automatically.
Compensation snapshot
Rate, tax basis, and SOW reference frozen at sign-time.
Reviewer + clearance note
Compliance reviewer name and clearance note pinned to the record.
Audit pack ready
PDF, CSV, and provider references export in one click.
Legal & compliance scenario
Compliance lead
Last quarter an auditor asked why we engaged a contractor in Brazil. We pulled the signed agreement, the classification it referenced, and the engagement record in one export. No DocuSign hunting. No spreadsheet archaeology.
Scenario: Head of contractor compliance - Multi-region software platform
After agreements
Translate signed paper into payout hold controls
Paper is signed and stored. Now every payout run reads AoR state before release. Holds, reason codes, and override paths all reference the same engagement record.
Frequently Asked Questions
What ties an agreement to the classification?+
Every issued agreement records the assessment ID, rule version (e.g. v2024.3), jurisdiction overlay, and classification result. If any of those change, Gruv marks the paper stale and requires a fresh signature.
How does signature capture work with DocuSign?+
Gruv sends the agreement via DocuSign, captures the signed PDF with signer IP and UTC timestamp, validates the artifact, and stores the immutable copy on the engagement record.
What happens to old paper after reclassification?+
It stays attached for audit history, but readiness flips to stale. Payouts hold until a fresh agreement is generated, sent, and signed.
Are templates localized for each country?+
Yes. Germany gets German-law clauses. India gets Indian disclosures. Brazil gets Brazilian requirements. Templates are managed per supported country with jurisdiction-specific overlays.
How do we retrieve signed artifacts for an audit?+
Pull the signed PDF, the classification it was locked to, and the signature event metadata in one export from the engagement record. No DocuSign hunting required.
Ready to scope your AoR agreements?
Bring your launch countries (US, UK, Germany, India, Brazil), DocuSign account, and existing agreement templates. Gruv scopes the localized paper and refresh logic your team needs before the first contractor signs.
Many teams start with a narrow launch in weeks.