Who signs, and in what order

Each document sent for signature has a signer list. You can add a second signer from the customer's company and a Velaro countersigner. Open the contract, find the Signers panel, and add signers with Add company signer or Add Velaro signer.

Choose how the order works:

• Sequential: the next signer gets an email only after the previous signer finishes. Signers with the same order number sign at the same time.
• Parallel: everyone gets the email at once.

The Velaro countersigner always signs after the customer side is complete. You can change the signer list until the first person signs.

Reassignment

Turn on Allow signers to ask for reassignment when the person you sent the document to may need to pass it to a colleague. The signer asks from their signing page and gives a new name, email and optional reason. The request appears in the Signers panel with Approve and Deny. When you approve, the new person gets their own signing link and the old link stops working.

Reminders

Set Remind every N days, up to M reminders per document. Only the current signer is reminded. If you do not set a schedule, the standard schedule applies.

Completion certificate and final PDF

When the last person signs, Velaro builds a final PDF that includes a completion certificate: each signer's name, email, time signed, IP address, the electronic-signature consent they agreed to, and the SHA-256 fingerprint of the original file. Use Download signed PDF in the Signers panel. The panel also shows the original and final SHA-256 values.

Verify a signed document

Go to Billing > Verify signed document (or use the Verify box on any contract), choose the PDF, and select Verify.

• Match: the file is identical to the original or final document Velaro stored. It shows the contract it belongs to.
• No match: the file is not one Velaro stored, or it was changed, even by a single byte, after signing.

A matching SHA-256 proves the file is unchanged since signing. It does not prove who signed it. Who signed is shown by the completion certificate (email, time, IP and consent).

You can also compute the fingerprint yourself: sha256sum signed.pdf on Linux or Git Bash, or Get-FileHash signed.pdf -Algorithm SHA256 in PowerShell, and compare it to the Final SHA-256 shown on the contract.