Skip to content
Dastawez
Menu

E-signature features: send, sign, track, and seal

Dastawez covers every step of getting a PDF signed electronically in Pakistan, from upload to a sealed copy in everyone's inbox. This page lists each e-signature feature available today, from document templates and bulk send to branded signing and the audit trail.

Anything that is not ready yet is kept apart, under "Coming soon", at the end.

Sending

A signature request is one PDF, the people who need to act on it, and the fields they fill in.

  • Upload a PDF of up to 25 MB and 100 pages, or join up to 20 PDFs into one document within the same limits.
  • Add up to 20 recipients to a request. Each one is a signer, an approver who approves without signing, or copy-only, someone who receives the sealed copy.
  • Choose a signing order: one after another, in the order you set, or all at once.
  • Write a message that every recipient sees, and set an expiry date. Unless you change it, a request expires 30 days after you send it.
  • Drafts save automatically while you work, so a closed tab loses nothing. Before sending, a review step shows the document, every recipient, and every field together.

Fields

Fields are the places on the pages where each recipient signs or writes. You draw them on the document and choose who fills each one.

  • Signature, drawn with a finger or mouse, typed, or uploaded as a picture.
  • Initials, made once by the signer and then used on every page that asks for them.
  • Date, filled in automatically with the day of signing, in Pakistan time.
  • Text, with an optional CNIC number check: Dastawez checks that the number has 13 digits and shows it as 12345-1234567-1.
  • Checkbox, with your own wording, such as "I agree to the terms on page 3".
  • Company stamp, an uploaded picture of the organization's stamp.

Text typed in Urdu is stamped into the sealed PDF in Nastaliq script, alongside English.

Document templates

A template saves the work of preparing a document you send again and again. It keeps:

  • the document itself;
  • roles for future recipients, such as "Candidate" and "HR manager", with their order, whether each must enter a one-time code, and an optional default person;
  • every field, already in place;
  • a deadline, counted in days from sending.

To use it, choose the template, fill in the people for this request, and send. You can also turn a request you have already prepared into a template with "Save as template".

Bulk send documents from a spreadsheet

Bulk send creates one signature request for each row of a CSV or Excel file, up to 500 rows at a time. It starts from a template, so every request has the same document and fields.

  1. Download the sample file for the template. It already has a column for each role.
  2. Fill in one row for each request, with each person's name and email address.
  3. Upload it. Dastawez checks every row first and lists any problem by row and column.
  4. Nothing is sent until every row passes. Then you confirm, and the requests go out.

Tracking and reminders

The dashboard shows what is waiting on others, what is waiting on you, what expires within the next few days, and what was completed recently, with your five newest requests underneath.

  • Search and filter every request.
  • Up to 3 automatic reminders, every 1 to 3 days, as you choose. You can also remind someone yourself while a request is waiting, at most once an hour for each recipient.
  • The sender is emailed as each person signs.
  • Cancel a request at any time before it completes.
  • On completion, the sealed PDF is emailed to the sender and to every recipient. A file too large to attach arrives as a download link, which works for 30 days.

Signer identity and consent

  • One-time email codes. For any recipient, you can require a 6-digit code sent to their email address. It is valid for 10 minutes and allows 5 attempts.
  • Explicit consent. Before signing, each person reads how signing works and agrees to sign electronically. The wording names the signing method, and its version is recorded.
  • Declining. A signer who will not sign can decline and give a reason. The request stops, and you are told.

Audit trail and evidence

  • Every step is recorded with its time, IP address, and device, in an append-only audit trail where each entry is chained to the one before by its hash.
  • When everyone has finished, Dastawez digitally seals the PDF with a trusted timestamp, so any later change is detectable.
  • A completion certificate page is added inside the sealed PDF. It lists the participants, their roles and times, the consent wording version, the SHA-256 fingerprints of the original and of the signed version, and a QR code.
  • The QR code opens the document's public verification page, where anyone can check a copy. The file is checked inside their browser and never uploaded.

Branded signing pages and emails

Add your organization's logo, as a PNG, JPEG, or WebP file, and one brand colour. They appear on the signing page, in the emails Dastawez sends for you, and across your team's dashboard. Dastawez checks that text stays readable on the colour you choose.

Organizations and teams

  • One workspace per organization. Invite colleagues by email; an invitation stays open for 7 days.
  • Three roles: owner, admin, and member. Owners and admins manage members, branding, API keys, and webhooks.
  • Each organization's documents, templates, keys, and webhooks are kept separate from every other organization's.

Credits

  • One credit pays for one completed signature request.
  • A credit is reserved when you send, used only when the request completes, and returned if it is declined, cancelled, or expires.
  • Your first document is free, and test mode is always free.
  • Owners and admins see usage and the full credit history in Settings.

API and real-time webhooks

Everything above is also available through the Dastawez REST API, which the dashboard itself uses. Real-time webhooks tell your system as each of these events happens:

signature_request.sent
Sent when a request goes out to its recipients.
recipient.viewed
Sent when a recipient opens their signing link.
recipient.signed
Sent when a signer finishes signing.
recipient.approved
Sent when an approver approves.
recipient.declined
Sent when a recipient declines, which ends the request.
signature_request.completed
Sent when everyone has finished and the sealed PDF is ready.
signature_request.cancelled
Sent when the sender cancels the request.
signature_request.expired
Sent when the deadline passes before everyone has finished.

The e-signature API page covers keys, test mode, retries, and rate limits.

Coming soon

  • Coming soon

    WhatsApp delivery and verification codes

    Signing links and one-time codes sent over WhatsApp, as well as by email.

  • Coming soon

    SMS delivery and verification codes

    Signing links and one-time codes sent by text message.

  • Coming soon

    Embedded signing

    For API customers, signing inside your own app or website, without leaving it.

Send your first document free

Upload a PDF, add the people who need to sign, and send it. Your first completed document costs nothing.