The executive by the lake

Electronic document signing in EPK

Today, signing often means carrying a laptop and token or returning to the office for paper. With EPK, an assistant prepares the documents and signature positions. The executive reviews, selects and—when a remote signing service is connected—signs from a phone. Individually or in bulk. Done.

For executives, statutory representatives and other people receiving documents for signature from several processes and systems.

How to leave the laptop and token behind
Crayon story of the solution: The executive stays by the lake. The documents get signed.

From start to finish

The assistant prepares. The executive decides and signs — even away from the office.

  1. Document in the signature book

    A business system or authorised colleague sends the document straight to the signature book.

  2. Signature positions prepared

    The assistant sets the order and signature positions so the executive does not have to find them.

  3. One queue to handle

    The signatory opens one queue, reads the documents and selects those ready to sign.

  4. Sign from anywhere

    Selected documents can be signed together or individually, at a desk or away from it.

  5. Result returned automatically

    Signed files return to their source without saving attachments or searching email threads.

When signing lives in email

Download. Open the PDF. Read. Find the field. Sign. Save. Find the right email. Reattach.

Every document creates another file and another opportunity to use the wrong version or reply to the wrong thread.

EPK

Review. Select. Sign.

Documents wait in one signature inbox with signature positions ready. Results return automatically. With a suitable signing service, you can also sign from mobile.

Who is involved

Who is responsible for what.

Case worker or source system

Sends the correct document version, metadata and signature request to EPK.

Executive assistant

Checks the material, sets the order and prepares visible signature positions — digital sticky tabs.

Executive or other signatory

Reviews one queue, selects documents and signs individually or in bulk without downloading or reattaching files.

EPK and signing service

EPK controls the task and responsibility; WSCS performs the configured signature and returns the result.

What happens when something goes wrong

A document is not ready to sign

The signatory can exclude, reject or return one document with a comment. The system does not sign a different version or position from the one prepared. Signature level, certificate and timestamp follow the process configuration.

The result

The signed document, status, time and audit trail return automatically to the source process. The signatory is done without saving attachments, finding the right email or manually sending a file back.

Product and integrations

The solution connects to the systems you already use.

Forms, roles and rules follow the way your team works. Every integration keeps the source of truth and error ownership clear.

Explore the product: Workflows, documents and people
Software602 SecuSignCESNET eIDASSEFIRA OBELISK Remote Signature

Signing without a token at your desk

Sign with a local certificate or a remote service.

EPK remains the shared document queue. The signing method follows who signs, where they sign and the legal level the document requires.

DERS Web Signer

Try the PDF workflow. We deliver integration through the API.

The public demo is only a preview and may change or become unavailable without notice; it is not a guaranteed test environment or part of an SLA. API access and integration work are paid services. Google Drive and Gmail have a ready integration. Microsoft 365 remains experimental and is not part of the standard delivery.

Concise answers

Frequently asked questions

Who is this solution for?

For executives, statutory representatives and other people receiving documents for signature from several processes and systems.

What happens when the input is incomplete or incorrect?

A document is not ready to sign. The signatory can exclude, reject or return one document with a comment. The system does not sign a different version or position from the one prepared. Signature level, certificate and timestamp follow the process configuration.

What is the outcome of the workflow?

The signed document, status, time and audit trail return automatically to the source process. The signatory is done without saving attachments, finding the right email or manually sending a file back.

Next step

Facing a similar situation?

Tell us how the work runs today and where it gets stuck. We will reply with a concrete next step, not a generic presentation.

Describe my situation