Envelope

An envelope is the package you send out for signature: one or more documents, the list of recipients, where each person signs, and the rules for how the signing happens. If you have ever wondered what an envelope is in DocuSign or other e-signature apps, it is simply the digital equivalent of putting papers in an envelope, addressing it and posting it.

Inside a typical envelope you will find the files themselves, signature and date fields placed on the pages, recipient details, an optional signing order, a message to signers, and settings such as reminders or an expiry date. The envelope moves through statuses like draft, sent, viewed, completed or declined, and every change is written to the audit trail.

A property manager renewing a tenancy might send one envelope containing the renewal agreement and an updated house rules sheet. Two tenants sign, then the manager countersigns. Everything travels together, completes together and produces one certificate of completion, rather than three separate emails with three separate histories to chase.

A common source of confusion is pricing. Many vendors bill per envelope, so people assume an envelope equals one document. It usually does not: one envelope can hold several documents and several signers. The reverse mistake also happens, where people send each page as its own request and lose the connection between them. It is also worth knowing that envelope is an industry term, not a legal concept. The ESIGN Act and UETA say nothing about envelopes.

Some tools use other words for the same idea, such as request, packet, transaction or document. The name matters less than whether the related files, signers and records stay grouped together. A useful test is to ask what you would need to show a court or an auditor later: the documents, the people, and the sequence of events. A well-built envelope keeps all three in one place and produces a single audit trail rather than scattered fragments.

Our take: the envelope metaphor is useful but gets overcomplicated. Most people just want to send a PDF, choose who signs, and get it back with a clear record. If a tool needs a training course to explain its envelope settings, something has gone wrong.

In eSignSimple you upload a PDF, add signers, optionally set a signing order and reminders, and send. Signers need no account. Reusable templates help with documents you send often, and every completed request comes with an audit trail, a certificate of completion and a SHA-256 hash you can check on /verify. Bulk send and API-created requests are on our roadmap.