Skip to content

DocsProtect and sign

Preparing contracts for signature

Check contracts for what is unfinished, review it, and get flattened, signed execution copies.

All topics

Prepare contracts for signature checks one or more contracts for what still looks unfinished, waits for you to review, and then creates an execution copy of each. Open Playbooks at the top of your library and choose Prepare contracts for signature, or use Prepare for signature… in a document’s menu in the library or in the editor’s File menu.

What it finds

  • Placeholders in brackets or braces, such as [Client name] or {{date}}
  • Blank lines of four or more underscores
  • TBD, TBC and TBA
  • Form fields left empty
  • Signature fields nobody has signed

Select a finding to see it on the page. To fix one, edit the contract and start a new run. Scanned pages are checked once they have been through OCR.

The execution copy

When you approve, Seben creates a new document for each contract:

  • its form fields are drawn into the page, so the values can’t be changed (signature fields stay, so the other party can still sign);
  • every page is marked “Execution copy”;
  • and, for workspaces Aqili has set up for signing, it is certificate-signed with your workspace’s key as a PAdES signature.

Each copy is checked before it is created: the page count, that no form fields are left, the mark, and that the signature verifies and is PAdES. Your original is not changed. Only a person signed in to Seben can approve. The agent and connected AI clients can start a run but not approve it.

If your workspace isn’t set up for signing, the preview says so, and you can run the playbook without signing. A contract that is already signed is left out, because drawing its fields into the page would invalidate those signatures; use File → Digitally sign to add a signature to it instead.

Something missing or wrong on this page? Write to support@seben.io.