Peak Sign / For IT service providers
The change request is approved.But which version?
SOW, maintenance contract, three change requests by e-mail. In the end nobody knows for sure which state applies. In Peak Sign every contract has revisions with a word-level comparison. When you send, the version is frozen, and the signature lands on exactly that version.
One answer changes the follow-up
Pick a sample rating.
Local draft · no product activationTry the sample rule. Nothing is sent.
02 / The next question
What changed compared with the previous version, and who has to confirm it?
Renewal shows up in the deadlines of the next 12 months.
Explainer · fictional Nordwind IT GmbH · not the product interface
Check the rule yourself
How clear is your status?
Pick a value. At 0 to 6 the question about the change appears, from 7 up you go straight to sending. Nothing is uploaded or sent.
Local rule demo · Please use neutral sample details only.
Pick a rating to see the next step.
The answer sets the direction.
- Rating
- —
- Seguimiento
- Waiting for a rating
No example picked yet.
From draft to the binding version
Compare first. Then get it signed.
The sample rule: if a change request's state seems unclear at 0 to 6, you clarify the change first. From 7 up the version can go out.
- 01Versión
Upload the change request.
SOWSigned, version frozen.
PDF, DOCX, TXT or pasted text. Peak Sign detects parties, terms and obligations with the source paragraph.
Upload → new revision - 02Compare
Make the change visible.
0–6Seguimiento7–10FinishRevision against revision, or draft against standard, word by word. You see what the client is really approving.
Comparison → marked differences - 03Record
Sign exactly this version.
MaintenanceRenewal shows up in the deadlines of the next 12 months.
When you send, the version is frozen with a hash. The executed PDF carries a signature sheet and an audit trail.
Sample artifact → executed PDF
The next proof is the product
Upload your next change request.
In Peak Sign the SOW, maintenance and changes sit in one place with revisions, comparison and deadlines. Follow-up tasks after signing land in Peak Work.
Start with Peak SignPeak Sign / Your next step
Every change has a version.
Check both paths in the example. Then upload the change request whose status is unclear right now.
See the IT example
Clear which version counts.
Renewal shows up in the deadlines of the next 12 months.
Frequently asked questions
Which IT contracts fit Peak Sign?
Maintenance and support contracts, project orders, data processing agreements and acceptances that can be closed with a simple electronic signature.
Can the client comment on single clauses?
Not yet. The client can request a change; redlines and clause-level comments are not available.
Is there an API or webhooks?
No, a public API and webhooks for Peak Sign are planned and not available today.