Peak Sign · Guide
Requesting a digital signature.
From contract to signature.
A practical guide in three stages: prepare the contract, send the request, follow the response and secure the evidence. This is how it works in Peak Sign.
Which change do you want to check?
Upload the contract as a PDF, DOCX or TXT, or use a built-in template: mutual NDA, services or freelancer contract. Peak Sign recognises parties, signers and terms and shows under “Ready to send” what is still missing.
Prepare, send,
prove.
- 01Preparation
- 02Sending
- 03Response & evidence
A real story starts with its release.
What do you need before you send the request?
A finished contract, the right signers and a short message. Peak Sign checks whether anything is missing, suggests an order and, after sending, records who has signed and why someone has not signed yet.
This pattern shows the structure. It doesn't tell a real customer case yet.
The path to change
A signature request in three stages.
Preparing the contract
Upload the contract as a PDF, DOCX or TXT, or use a built-in template: mutual NDA, services or freelancer contract. Peak Sign recognises parties, signers and terms and shows under “Ready to send” what is still missing.
A contract with no open checksEvidence format · not filled in yetThe starting point.
In the original.Original excerptInsert the released passage here.
A / ObservationWhich concrete friction is visible in this source?Example · Ready to send Sending the request
Check the suggested order: steps one after another, parallel within a step. Write a personal message that arrives by email in your name. When you send, the version is frozen.
Every signer has their personal linkEvidence format · not filled in yetOne step.
Traceable.BeforeOriginal processSource evidence requiredChangeConcrete interventionProduct view and date requiredExample · Order and message Following the response and securing evidence
The status is shown in plain language. Reminders go out after three days unopened or four days opened, at most three, never during an open change request. After countersigning, you have the executed PDF with signature page and audit trail.
Signed contract with evidenceEvidence format · not filled in yetThe result.
With a yardstick.- Observation
- Not evidenced yet
- Period
- Open
- Source & release
- Pending
Without released data this statement stays open.
Example · Executed PDF
What can be evidenced
What you have at the end.
The evidence is still pending
There are deliberately no metrics such as turnaround times here. Peak Sign shows the status of your own contracts, not made-up averages.
The sculpture does not depict a customer.
One perspective.
With name and release.
Beyond the single case
What you do right away next time.
Check first, then send
Once “Ready to send” reports nothing more, signers and details are complete. You can still correct things: change an email, renew a link or withdraw the request.
Key ideaFewer questions after sending
Know the limits
Bulk sending and identity verification by SMS or ID are planned and not yet available. The signature is a simple electronic signature with evidence.
Key ideaClear expectations of the workflow
What this article is based on.
Practical guide with a made-up sample contract. The features described exist in Peak Sign today. Bulk sending, identity verification, AES and QES are planned and not yet available. Not legal advice.
- Editorial demo
Editorial example with made-up sample data. Only features Peak Sign has today are described; everything else is marked as planned or example.
Your first request.
Upload a contract or start with the sample contract and send the request to yourself.
Frequently asked questions
Does the recipient need an account?
No. Signers open a personal link and sign in the browser.
Can I set an order?
Yes. You set who signs first and who signs next.
What happens after the last signature?
The agreement is completed. You can create follow-ups as tasks in Peak Work.




