Naar de inhoud springen

Peak Sign / Client approval workflows

The client has a question.And the contract stalls.

Instead of e-mail ping-pong, the recipient requests a change directly in Peak Sign. Reminders pause while the request is open. An owner or admin approves protected clauses before sending, and the Change Studio suggests edits with before and after.

One answer changes the follow-up

Pick a sample rating.

Local draft · no product activation
Try approvals

Try the sample rule. Nothing is sent.

02 / The next question

0–6 Follow-up

Which change is the client asking for, and does it need internal approval?

New revision, frozen again, sent again.

Explainer · fictional Beispiel GmbH · not the product interface

Check the rule yourself

How clear is what the client wants?

Pick a value. At 0 to 6 the question about change and approval appears, from 7 up you go straight to signing. Nothing is sent.

Local rule demo · Please use neutral sample details only.

Peak Sign / Question pathRULE DEMO
With your current contract, how clear is it what the client still wants changed?
0 · Completely open10 · All settled

Pick a rating to see the next step.

The rule in actionLocal preview

The answer sets the direction.

Rating
—
Follow-up
Waiting for a rating

No example picked yet.

From question to signature

Settle first. Then sign.

The sample rule: if it's open at 0 to 6 what the client wants, you settle the change first. From 7 up the version can go for signature.

  1. 01Request

    The client requests a change.

    Client

    Requests a change to the payment term.

    On the recipient page they can request a change, decline or download the PDF. Reminders pause meanwhile.

    Recipient page → change request
  2. 02Approval

    Approve internally.

    0–6Follow-up7–10Finish

    The Change Studio suggests edits; nothing is applied without a click. An owner or admin confirms protected clauses.

    Suggestion → approval before sending
  3. 03Signature

    Send the new version.

    Afterwards

    New revision, frozen again, sent again.

    The new revision is frozen and signed. The activity history shows every step.

    Sample artifact → history

The next proof is the product

Try it with your next contract.

In Peak Sign client change requests, internal approval of protected clauses and revisions come together on one contract.

Start with Peak Sign

Peak Sign / Your next step

Every question has a place.

Check both paths in the example. Then send the contract with an open question right now.

Try approvals
Local working example

Approved, then signed.

New revision, frozen again, sent again.

Frequently asked questions

Who approves protected clauses?

Owners and admins of your workspace. This internal approval is available today.

Can the client request changes?

Yes, client change requests are available. Clause-level redlines are not.

Are there multi-stage approvals on the client side?

No, multi-stage client approvals and rules by discount or value are not available yet.