SIGNDOK

Sign your contracts without leaving NexDok.

From a Word document, send the current version to up to 20 signers, in order. While it’s being signed, the document is locked. The signed PDF comes back as a new version of the same document.

UP TO 20 SIGNERS1→NIn orderEXTExternals need no accountPAdESRFC 3161 timestampvNSigned (vN)
WHO SIGNS

Internal and external signers, one after another.

Each signer gets a link by email when it’s their turn. Externals need no account: they draw their signature on the SignDok portal, in English or Spanish.

1Ana Ruiz● Signed
CFO · internal
Signed
2Carlos Méndez● Pending
Legal representative · external
Gets the link
DOCService Agreement 2026● Locked
.docx · v2
Document locked
PORSignDok portal● No account
EN / ES
Draw your signature
PDFSigned PDF● PAdES-B-T
RFC 3161 timestamp
One signature per signer
v3Signed (v3)● New version
Same document
Ready to publish
While signing: new versions, publishing, archiving and approvals are blocked.
When it’s done: the signed PDF is saved as “Signed (vN)” on the same document.
HOW SIGNING WORKS

From a .docx to a signed version, without leaving NexDok.

1 · SENDThe current version

From the document page, “Request signatures” with 1 to 20 signers in order.

2 · LOCKThe document

No one can change it while signing is in progress.

3 · SIGNIn order

Each signer gets their link in turn and draws their signature.

4 · RETURNAs a version

The PAdES-signed PDF comes back as “Signed (vN)”.

If someone rejects: the request closes with their reason, shown on the document page.
TRY IT — SAMPLE WORKSPACE

Send a contract for signature. Follow every step.

“Grupo Andino Legal” · Service Agreement 2026 · 2 signers.

About .docxv2
Request signatures · Ana Ruiz (CFO) → Carlos Méndez
IN PROGRESS

0 / 2 signed · Expires in 30 days

DOCUMENT LOCKED

New versions, publishing, archiving, and approvals are blocked.

Reminder every 48 h

Sample data. Requires a plan with electronic signatures.

EVIDENCE IN THE PDF

A signature you can check in any PDF reader.

01PAdES-B-T

One incremental signature per signer.

02Timestamp

RFC 3161 on every signature.

03SignDok log

Created, sent, viewed, signed, rejected and completed.

04Operations console

So an admin can see and resolve every request.

Defaults

What every request applies.

ItemValueWhereNote
Signers1 to 20Per requestIn order
Expiry30 daysPer request
Reminderevery 48 hAutomaticRenews the link
Input format.docxFrom NexDokComes out as PDF
HONEST BY DESIGN

What SignDok does today.

In order only

There’s no parallel signing.

Drawn signature

No typed or uploaded signatures.

One platform certificate

The PAdES signature uses SignDok’s certificate.

CSV exports

For compliance, from the console.

OPERATIONS CONSOLE

Everything happening with your signatures, in one place.

Admins see every request’s status, spot what needs attention and act: sync, retry, remind or cancel.

OverviewAll RequestsNeeds AttentionHistoryCompliance & Export
SignDok OperationsLast 30 days
SUBMITTED12requests
COMPLETED9signed
EXPIRING1< 3 days
Sync nowSend reminderCancel request
Export: All Requests · Completed Signers · Admin Actions · Errors & Retries (CSV)
THE CONTRACT, SIGNED

The signed version, on the same document.

When it’s done, the document page shows the new signed version, ready to publish.

v3 · SIGNED (v3)

Signed PDF imported from SignDok

2 / 2 SIGNED

Ana Ruiz · Carlos Méndez

PAdES-B-T with an RFC 3161 timestamp
A plan with signing

Professional or Enterprise.

A Word document

The current version as a .docx, in draft.

To send

Editor role or higher.

Setup

An admin connects SignDok in Settings.

Which contract are you signing this week?

We’ll show you SignDok on one of your documents.

Contact us