Prepare a Google Doc carefully before requesting signatures. Google’s eSignature workflow creates a signing PDF, so check the source wording, signer assignments, and eligibility before initiating a request.
Check feature access and the document
Consult the current official eligibility list for the account and organization. Some Workspace plans require administrator enablement; do not assume every free personal account has the same feature.
Finalize the text through the appropriate review process. The eSignature interface provides a signing workflow, not advice that a document meets every legal or organizational requirement.
Assign the correct fields
- Open Tools > eSignature in the Google Doc.
- Review the signer list and placeholder labels.
- Add the required signature, initials, name, date, or text fields.
- Check which signer each field belongs to.
Signer labels are placeholders at this stage. Verify the actual email addresses when preparing the request rather than assuming the labels themselves determine delivery. The documented limits include ten signers and 200 fields per document; check a complex request against those limits.
Review before sending
Inspect the complete document, recipient addresses, optional message, reminder choices, and audit-trail language. Sending a request is an external action and should follow the document owner’s authorization.
After a request is created, Google locks the signing PDF against changes while the source Google Doc remains editable. Editing the source later does not silently rewrite that pending signing copy. Keep those versions distinct and verify the actual request status. A field placed on the page is not evidence that the request was sent, signed, or completed.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.