Localized templates
Templates are managed per supported country with overlays for jurisdiction-specific clauses and required disclosures.
For legal, compliance, and program leads
Signed AoR paper, tied to the assessment behind it.
Issue localized agreements that freeze the classification state, capture signature, validate provider PDFs, and keep signed artifacts attached to the engagement record.
Localized templatesTied to the assessmentImmutable signed artifactsStale paper signals
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
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 know whether the engagement still has valid paper.
Tied to the assessment
Every agreement records the assessment, rule version, and result it was generated against. Stale assessments mark the paper stale.
Signature capture
AoR sends paper for signature, validates provider PDFs, and captures the signed artifact bound to the engagement.
Immutable storage
Signed artifacts are stored with versioned metadata and remain attached for audit retrieval and follow-up.
Stale paper signals
Reclassification, law updates, and overlay changes can mark paper stale. Readiness blocks until a refresh is signed.
Audit retrieval
Exports can package the agreement, the assessment, and the signature event for audit response without rebuilding context.
Anatomy of a signed agreement
Eight properties an auditor can pull at any time.
The artifact is the agreement. The metadata is what makes it defensible. Every property is recorded against the engagement record so the next conversation does not start from scratch.
- Tied to the assessment that justified the agreement.
- Stale paper detection on reclassification or rule change.
- Signature events captured with timestamps.
- Audit-ready exports retrievable from the engagement record.
Agreement
AGR-44829
- Agreement template
- UK contractor v3.2
- Assessment ID
- ENG-9824 / 2026-Q2
- Rule version
- v2025.04
- Jurisdiction overlay
- UK launch v1
- Generated on
- 08 May 2026
- Signed on
- 09 May 2026
- Provider
- AoR signing flow
- Artifact
- PDF + event log
Artifact stored against engagement ENG-9824
Four steps from generated paper to signed artifact.
Each step is observable. Reclassification triggers a refresh before the next gate can pass.
01
Generate localized paper
AoR pulls the right template and overlays based on launch country and the engagement assessment result.
02
Send for signature
The contractor receives the agreement, reviews, and signs through the supported provider workflow.
03
Validate and store
Provider PDFs are validated and the signed artifact is stored bound to the engagement record.
04
Refresh on stale paper
Reclassification or rule change marks paper stale. AoR requires a fresh signed artifact before the next gate can pass.
After agreements
Translate signed paper into payout hold controls.
Once paper is signed and bound, payouts can read AoR state before disbursement. Holds, reason codes, and exception paths all reference the same engagement record.
Frequently Asked Questions
What ties an agreement to the assessment?+
Every issued agreement records the assessment ID, rule version, jurisdiction overlay, and result it was generated against. If any of those change, AoR can mark the paper stale and require a refresh.
How does signature capture work?+
AoR sends the agreement to the contractor for signature, captures the signed artifact, validates provider PDFs, and stores the immutable copy bound to the engagement.
What happens to old signed paper after reclassification?+
It stays attached to the engagement for audit, but agreement readiness flips to stale. The next gate cannot pass until a fresh agreement is generated, sent, and signed.
Are templates localized per launch country?+
Yes. Templates are managed per supported country with overlays for jurisdiction-specific clauses. The page should reflect supported countries rather than implying universal coverage.
Can we use our own paper?+
AoR works with localized templates that have been reviewed for the supported coverage. Custom paper is scoped during rollout when underwriting and legal review are part of the launch program.
How are signed artifacts retrieved?+
Signed artifacts are queryable from the engagement record. Audit-ready exports include the artifact, the assessment it was tied to, and the signature event metadata.
Ready to scope signed AoR agreements?
Bring your launch countries, agreement templates, signing provider, and storage requirements. Gruv can scope the localized paper and refresh logic your team needs before activation.