Sending and Signing

Sending

Send the agreement from its screen; the status moves to Sent and the client receives a secure link. The link is protected - before viewing, the client clicks Send Code and a 6-digit access code goes to the contract’s primary contact email (shown to them masked, so the address itself is never exposed). Public agreement pages only expose what’s needed to review and sign.

What the client does

The link opens a branded welcome screen explaining what a Payment Agreement is, then walks them through it:

Make the welcome screen yours

The illustration on this start page is the default Sawfish artwork until you upload a brand image - do that under Settings → Organisation → Branding and every agreement you send opens on your own image.

1. Reviews their organisation details, then the agreement - the project, invoices covered, payment terms, and schedule.
2. Adds a payment method as part of signing - credit card, PayTo, or bank details, depending on what you’ve enabled.
   • PayTo agreements are validated with the client’s bank before signing completes, so an active agreement always has a working payment method behind it.
3. Accepts the terms - the terms you set on the agreement, plus the Sawfish platform terms (linked from the same screen). Their acceptance is recorded with the signature.
4. Signs - drawing or typing their signature.

“To action” tags guide the client through the page, DocuSign-style - every field or step still waiting on them is flagged, so nothing gets missed on longer agreements.

When they finish, the agreement becomes Active, you’re notified, and both sides can access the signed document.

While you wait

• The agreement shows as Sent with its expiry counting down - if the client doesn’t sign in time, it lapses and can be re-sent.
• Resend agreement summary emails the link again.
• Client View shows you exactly what they’re looking at if they call with questions.

After signing

• View signed document - the executed agreement, with who signed and when.
• The payment schedule starts running - see Managing active agreements.