Signature requests

Ready means content-complete, comment-clean, version-pinned, and internally approved when your process requires it. Placeholders, “TBD pricing,” and unresolved legal threads are signs you are early.

If Design Studio letterheads or stamps are part of the pack, confirm the correct brand assets are in place before signature. A signed letter on yesterday’s letterhead is an avoidable re-sign.

Export may be part of your filing practice, but the signature flow should reference the agreed document state. Do not invent a parallel “sign this other PDF” path that drifts from Document Studio.

For external counterparties, communicate clearly what they are signing and by when. Status tracking helps chase outstanding signatures without losing the thread in email.

While signatures are outstanding, treat the document as locked for substance. If a material change is required, stop the request, revise, re-approve, and send again. Partial signatures on obsolete text are worse than a short delay.

When complete, store the signed copy in the organisation library with naming and access practices your ops team can sustain. Future amendments should start from that artifact plus a new drafted version.

Audit questions often combine “who approved” and “who signed.” Keep approval workflow records and signature status together conceptually even if they are different steps. The platform AI audit trail remains separate — it tracks tokens for AI calls, not wet-ink meaning.

Role design still applies: editors prepare; owners and admins manage organisation settings and spending; viewers may need read access to the signed file without edit rights on working drafts.

Watermarked share links are for provisional review. Signatures are for execution. Do not use a watermarked draft as a substitute for a signature packet, and do not skip soft review when the counterparty still needs to comment.

Approvals are internal; signatures are often multi-party. A document can be fully approved internally and still awaiting an external signer. Status should make that distinction obvious to the deal owner.

CasperWasp’s marketplace pitch is consolidation: documents, design, and collaboration under one subscription. Signature requests extend that consolidation so you are not exporting to a completely disconnected tool by default — while still respecting that legal standards vary.

AI writing tools may have helped draft the agreement earlier. By signature time, humans own the text. There is no pre-run token estimate for signing because signing is not an AI generation step.