Docusign records every action on an envelope and issues a Certificate of Completion for it. That certificate is only as meaningful as the account behind it — who was allowed to send, from which template, with what identity check applied. This page is about designing that account before the first envelope goes out.
A Docusign eSignature implementation is the configuration of the account itself: how it divides into groups, which permission profiles exist and what each may do, what signers see, which templates are sanctioned, how each signer's identity is established, and how long completed envelopes are retained. It is the layer underneath every integration and every workflow — and because it is invisible when it is right, it is routinely skipped.
What Docusign provides and what we do. Docusign provides the signing infrastructure, the authentication methods, the template engine and the Certificate of Completion that records every action taken on an envelope. Our work is deciding how those are configured for your organisation, your document types and your regulatory position, and building it so it survives staff changes.
Electronic signatures are recognised under frameworks including the US ESIGN Act and UETA and the EU's eIDAS regulation, and Docusign holds certifications including SOC 2 Type 2 and ISO 27001. Regulated processes have additional requirements — Docusign offers modules aimed at FDA 21 CFR Part 11 obligations for life sciences, for example. None of that is automatic. The platform makes the right configuration possible; it does not choose it for you, and a Certificate of Completion documents whatever actually happened, including a sender using a template they should not have had access to.
So the design questions are ordinary governance questions. Which documents require an identity check stronger than an email link? Who is allowed to send a master agreement as opposed to an NDA? What happens to a completed envelope when the retention period expires? We answer them per document type and configure accordingly.
Docusign supports a range of authentication methods. Applying the strongest one everywhere adds friction and cost that signers will route around; applying the weakest one everywhere leaves high-value agreements resting on access to an email account. The decision belongs per document type.
| Method | What it establishes | Typically used for |
|---|---|---|
| Email link | Control of the email address the envelope was sent to. The default, and the baseline recorded on the certificate. | Internal approvals, low-value routine documents, agreements with an existing known counterparty. |
| Access code | Possession of a code shared with the signer through a separate channel by the sender. | Documents where the sender already has a trusted side channel — a phone call, an account portal. |
| SMS or phone | Control of a specific phone number as a second factor alongside the email. | Consumer agreements, higher-value commercial documents, anything where email compromise is a live concern. |
| Knowledge-based | Ability to answer questions generated from public and commercial data records about the signer. | Processes that require a recognised identity-proofing step, commonly in US financial and property transactions. |
| ID Verification | Validity of a government-issued document, with biometric checks against the person presenting it. | Regulated onboarding, high-value or fraud-exposed agreements, remote transactions with an unknown party. |
Docusign continues to develop this area — biometric ID verification now includes liveness checks intended to defeat presentation attacks such as a photograph of a photograph. Because these capabilities move, the method selected for each document type is worth revisiting annually rather than treating as settled, and the licensing attached to the stronger methods is worth confirming at the same time.
Every account we review has more templates than anyone expects and fewer owners than it needs. Template sprawl is not a tidiness problem — it is how outdated legal language keeps leaving the building.
Templates organised by agreement type and business unit, shared to groups rather than individuals, with naming that tells a sender which one to use without asking. Personal templates are the mechanism by which sprawl happens, so their use is a deliberate decision.
Every template has an owner who is accountable for its content and a review date. Without those two attributes nobody can safely retire anything, which is precisely why accounts accumulate templates that nobody will delete and nobody will vouch for.
Where fields are positioned by anchor text rather than by coordinates, a document that reflows because legal added a paragraph still tags correctly. Coordinate-placed fields are the reason a template silently breaks the month after someone edits the wording.
Where several agreements share a cover sheet or a standard schedule, composing an envelope from multiple templates beats maintaining six near-identical documents that will drift apart within a year.
Where a signer starts the process, Docusign offers two routes. Web Forms collect structured, mobile-responsive input and pre-fill the agreement from it; PowerForms expose a template through a link with URL prefill. They suit different jobs and we pick per use case rather than per preference.
Envelope custom fields are the difference between an account you can report on and one you cannot. Stamping agreement type, business unit and source record at send time is trivial then, and impossible to reconstruct later.
An eSignature account that works for thirty users and one that works for a thousand differ in exactly one respect: whether user management, template control and policy are handled by process or by hand. The items opposite are what we configure so the account does not require a full-time person to stay correct.
Where you would rather not staff that role internally at all, our support and managed services practice runs it.
Users authenticate through your identity provider, and joiners, movers and leavers flow through automated provisioning rather than a manual admin task. This is also the control that ensures a departing employee loses sending rights on their last day rather than at the next licence review.
Profiles built around what roles actually do — send only, send and void, manage shared templates, administer. Granting broad rights because it is quicker at rollout is the single most common finding in the account reviews we run.
Policy acknowledgements, annual renewals and similar one-to-many sends run through bulk send against a recipient list, rather than as hundreds of individual envelopes assembled by hand over a week.
Set per agreement type rather than globally. An NDA that expires after fourteen days is good hygiene; an enterprise agreement that expires mid-negotiation because it inherited the same setting is an avoidable incident.
How long completed envelopes and their documents remain in the account, what is exported to the system of record, and what happens at the end of the period. Decided with legal, configured once, and documented so the next administrator inherits the reasoning.
Accounts drift quietly. Permissions granted for one project stay granted, templates outlive the people who made them, and the identity settings chosen in year one apply to documents nobody imagined then.
A structured account review takes a few days and produces a prioritised list: what is a risk, what is friction, and what is simply untidy. Bring us the account and we will tell you which is which.
