Prepare Project Agreements and Collect Signatures

Project Agreements turn a published business template into an exact, versioned document with named signers. A required Agreement can block Project activation until the current version is fully signed and its immutable PDF is stored.

Plan availability

An owner must make Agreements available in Projects → Workflow Settings. The Project must then enable Agreements and, if needed, the Agreement activation gate.

Permission required

Preparing, sending, revising or voiding requires Manage Project Agreements. Business countersignature requires Sign Project Agreements. Client signers need an active explicit stakeholder record with Agreement signing access.

Prepare access and the document

Add client stakeholders in People → Client Stakeholders & Access before assigning signatures. You can add the main Project customer once. If that person already has a matching Customer Account, no new invitation is needed; otherwise Yepsta creates a one-time invitation link that is shown once and expires after 48 hours.

Send an Agreement for signature

1. Open Documents → Agreements and create an Agreement from an active published template.
2. Enter the title and optional expiry date.
3. Select one or more required signers and any view-only recipients.
4. Confirm whether the template requires a business countersignature.
5. Preview the exact generated content and recipient list.
6. Send the Agreement. Yepsta freezes the version and notifies eligible recipients.

The Agreement moves through Sent, Viewed, Partially Signed and Signed as the required people act. A client signer enters their name and records explicit consent while authenticated to the matching Customer Account. They can also decline and provide a reason.

Countersign and complete

If required, an authorised business user countersigns the frozen version. When all required signatures are present, Yepsta generates the private signed PDF and checksum. That stored final document—not a status badge alone—satisfies a required Agreement start gate.

Important information

Signatures always belong to one exact frozen version. A sent version cannot be edited in place, and a signed Agreement cannot be rewritten.

Revise or void safely

To revise a sent Agreement, provide a meaningful revision reason and create a new version. The previous version remains preserved. To stop an Agreement, void it with a reason; recipients are notified and it no longer satisfies a required current Agreement gate.

If a client declines, review their reason, decide whether to revise, then send the new version deliberately. An informal email acceptance does not replace signature completion.

Warning

Do not upload a signed file as a general Project document and assume the Agreement gate is complete. Use the Agreement workflow so signers, consent, versions and the final PDF are connected.

Manage templates

Create and publish Agreement templates in Projects → Workflow Settings. A template can define content and whether business countersignature is required. Existing sent Agreements keep their frozen content when the template changes.

Tip

If a signer cannot act, verify the stakeholder is active, their invitation matches their verified email or phone, and Sign Agreements is enabled for that stakeholder.

Related guides

• Manage intake forms
• Set up client stakeholders and access
• Clear activation gates
• Find signed Agreements in Documents

Last reviewed: 1 September 2026