Skip to main content
Gruv.ai logo

Localized AoR agreements

Carry eligible classification into a signable agreement

Prepare the agreement for the engagement, open its current PDF, and send it through DocuSign. Signed means the completed agreement and certificate have returned to the record.

Plan signingSee the example

ENG-846 · AoR agreement

Maya Chen contractor agreement

Awaiting signature
Classification context
Eligible assessment linked
Agreement
Localized document prepared
Current PDF
Draft available to open
Signature delivery
DocuSign envelope sent
Counterparty signature pending

Completion will add the executed PDF and certificate.

ENG-846 · Worked agreement

A draft becomes signed when the executed packet returns

The agreement record connects the classification used at creation to the current PDF, DocuSign envelope and signed documents.

  1. 01

    Prepare

    Use the eligible engagement context

    The localized agreement links to the engagement and snapshots its latest classification assessment and jurisdiction context.

  2. 02

    Render

    Create the draft PDF

    The generated document becomes the current PDF that the customer can open before sending.

  3. 03

    Send

    Create the DocuSign envelope

    The signing provider receives the verified draft PDF and sends the envelope to the counterparty.

  4. 04

    Complete

    Store the executed packet

    The completion event returns the executed PDF and certificate before the agreement records Signed.

Draft document

Current PDF

Generated from the engagement context and terms, stored with a version number and content hash, and verified before provider send.

Completed packet

Signed packet

  • Combined executed agreement
  • Completion certificate
  • Signer and completion context

Illustrative record. This example assumes the agreement and DocuSign path are enabled for the program. Confirm the available path with Gruv.

Customer agreement view

Keep the current state beside the latest PDF

The engagement page shows the linked agreement and its current state. The customer can open the latest PDF and request DocuSign delivery from a Draft agreement. The state changes only after the workflow completes provider delivery.

The record keeps versioned PDF files. The customer list and engagement view expose the latest version rather than a version comparison workspace.

Agreement

Current document for ENG-846

Maya Chen contractor agreement

Localized AoR template · Updated after signing

Signed

Latest PDF · Executed agreement

Current customer-facing document

What opens here?

The current PDF link opens the latest stored document. Earlier PDF versions are not presented as a comparison view.

Before agreement readiness clears

See what still needs attention

The next step depends on what is missing. A generated draft, a sent envelope and a current signed agreement each mean something different to readiness.

Draft document

The PDF is not ready

The agreement remains Draft until the workflow has a PDF and DocuSign delivery succeeds.

Can the agreement be sent anyway?

No. The workflow must create and verify the draft PDF before it calls DocuSign. Recheck the agreement state and PDF availability before treating the request as sent.

Signature state

Sent is still awaiting signature

Sent and viewed states show progress through DocuSign, but the talent onboarding step remains blocked until the agreement is Signed.

What confirms completion?

The DocuSign completion event returns the executed PDF and completion certificate. Gruv stores both files and records the signed PDF version before the agreement reaches Signed.

Current classification

A newer assessment changes the check

Agreement readiness requires the signed agreement to reference the engagement’s latest classification assessment.

Does the older agreement relink itself?

No. A newer assessment makes the older signed agreement fail the current agreement check. Review the current agreement requirement with Gruv before relying on that record.

Separate payout check

See what an unsigned current agreement changes

Payout readiness evaluates the agreement separately. Agreement signing does not itself execute or release a payment.

Continue to payout holds

AoR agreement questions

When can an AoR agreement be prepared?+
The customer engagement view enables agreement preparation after the loaded assessment is eligible. When a readiness snapshot is available, its classification gate must also be ready. The legally binding AoR agreement links to the engagement and snapshots its latest classification assessment.
What happens if the draft PDF is not ready?+
The workflow must create the draft PDF before DocuSign delivery can succeed. A send request is asynchronous, so the agreement can remain Draft while PDF generation or provider delivery is still running.
How does the agreement become signed?+
DocuSign owns the signature step. When Gruv receives the completion event, it downloads and stores the combined executed agreement and completion certificate, records the signed PDF version, and moves the workflow to Signed.
What if classification changes after signing?+
Agreement readiness compares the signed agreement with the engagement’s latest classification assessment. If a newer assessment exists, the older agreement no longer satisfies the current agreement check. Review the current agreement requirement with Gruv before relying on that record.
Do clause changes follow the same path?+
A supported clause override follows a specific counsel review before PDF generation or sending. Approval keeps the override, while rejection removes it.

Plan the agreement path

Plan the signing path

Review enabled countries, agreement requirements, the signing path and the documents kept after completion for your contractor program.

Plan signingSee payout holds