Skip to content

Agreements signed in the portal, not in an inbox

Write each agreement once as a template with fields that fill in from the project. Attach it to a task, the client signs it in your portal, you countersign, and both sides keep the signed PDF.

Write it once, with fields that fill themselves in

A template holds the title, the contract text and whether your team must countersign. Smart fields pull in the client, company, project and dates when you send it.

  • Each task gets its own copy, so editing the template never changes a contract you already sent
  • Smart fields are fixed when the first client signs, so every signer sees the same text
  • Duplicate a template to start the next one, archive it when you retire it

Always clear where a contract stands

Your team sees each status on the task. Clients see who signed and when, and whether you still need to countersign.

  1. Sent01

    On a task and waiting for the client.

  2. Viewed02

    The client opened it in the portal. Your team is told the first time.

  3. Signed03

    The client signed. Without a countersign, it is fully executed.

  4. Countersigned04

    Both sides have signed. The text is locked and the PDF is ready.

  5. Voided—

    Cancelled, with an optional reason. Signature records are kept.

  • Edit before it is executed

    Change the text while it waits for signatures. If someone already signed, saving clears their signature and they sign the new version.

  • Locked once both sides sign

    A fully executed contract cannot be edited, voided or removed from its task. The signed PDF includes the text, signatures and signing details.

  • The PDF comes to you

    Emails about a fully executed contract carry the signed PDF, and both sides can download it at any time.

What your client sees

The contract appears on a task in their portal. They read it, type their full legal name or draw a signature, agree to sign electronically, and click Sign.

  • After signing they see who signed and when
  • If you still need to countersign, the task says so, and they are told when you have
  • Once both sides have signed, the task shows Contract fully executed and a Download PDF button

Works with workflows

Contract signed fires once the contract is fully signed: after your countersign when the template asks for one.

All triggers and actions

Welcome after signing

The signed agreement starts the project: a welcome email with next steps, the questionnaire opens and the project lead hears about it.

Contract signedService agreement
  1. 1Send email to the client
  2. 2Set task status: Kickoff questionnaire to Active
  3. 3Notify team member: Maya Ortiz

Still unsigned

If the agreement task has been waiting for three days, the client gets a friendly reminder.

Task status elapsed3 days in Active
  1. 1Send email to the client

Questions

Who on my team can send, countersign or void a contract?

Workspace Owners and Admins. Members can follow the project’s tasks, but cannot send, countersign or void a contract.

What does Upclient record when a client signs?

The time, IP address and browser, and a fingerprint of the exact text that was signed. You can see these in the audit details for each signature.

If I update a template, do contracts I already sent change?

No. Adding a template to a task makes that project’s own copy. Later changes to the template only affect contracts you send afterwards.

Do I always have to countersign?

Only when the template has Require countersign turned on. Otherwise the contract is fully executed as soon as the client signs.

What if I sent the wrong contract?

Void it, optionally with a reason, then add the right template to the task. The client sees that the first one was voided.

More of Upclient

All features

Put your agreement on a task

Paste your current contract into a template and add the smart fields.