PPuntSign

Agreement lifecycle

A clear path from document preparation to final evidence.

The workflow separates what the sender controls, what each recipient needs to do, and what PuntSign generates when the agreement completes.

Agreement lifecycle from sender preparation through recipient action to final evidence

For the sender

Build and launch the envelope.

01

Upload the source PDF

Start from the document your team already uses. PuntSign stores the original privately and registers its document metadata and hash.

02

Add the people involved

Add signers, approvers, and copy recipients with the email addresses and roles needed for the agreement.

03

Choose the route

Use parallel routing when recipients can act together, or sequential routing when later recipients must wait for an earlier order to complete.

04

Place the required fields

Drag signature, initials, name, date, text, and checkbox fields onto the PDF and assign them to the relevant recipients.

05

Review and send

Confirm the envelope setup, then send invitations to the active recipients. Scheduled reminders support agreements that remain open.

For the recipient

Keep the task focused on the agreement.

01

Open the secure invitation

The recipient follows an agreement-specific email link and exchanges that access token for a time-limited signing session.

02

Review the agreement

The signing page presents the PDF, organization branding, recipient role, and fields assigned to that person.

03

Accept electronic-signature consent

Before submitting required fields, the recipient confirms the electronic-signature consent shown in the signing flow.

04

Complete the assigned action

A signer fills fields and signs, an approver approves or declines, and copy recipients receive the agreement without a signing task.

05

Advance the route

In sequential workflows, completion of the current order activates the next routing order until all required recipients are finished.

At completion

The final document and its evidence are produced together.

When all required recipients are complete, the finalization workflow loads the original PDF and submitted values, stamps the completed document, calculates its SHA-256 hash, generates a separate audit certificate, and stores both outputs privately.

  • The original PDF remains separate from the completed output.
  • The completed PDF receives its own SHA-256 value.
  • Completion downloads use expiring secure access.

Ready to build your first agreement workflow?

Create a workspace, upload a PDF, define recipients and routing, then move the envelope through the same lifecycle described above.