DocuSign
Category: E-signature — electronic document signing Status: Active. Will be replaced by Workday CLM (Contract Lifecycle Management) via Evisort partnership in Q2-Q3 2027. Estimated cost: ~$25K/year
What it is
DocuSign is how MR gets documents signed electronically. Offer letters, employment agreements, policy acknowledgments — anything that needs a signature goes through DocuSign.
What MR uses it for
- Offer letter signatures — when a candidate accepts, the offer letter is sent via DocuSign
- Document execution — employment agreements, policy updates, compliance acknowledgments
- Personnel file component — signed documents are pulled into the employee's personnel file (manually)
Who uses it
- TA (Talent Acquisition) team — sends offer letters
- HR operations — manages other document signatures
- All employees — sign documents as needed
CMPRSSN access
Blocked. Kyle pinged Shlanda on July 6 about getting DocuSign API access. Still waiting.
Known pain points
- Manual pull into personnel files. When a document is signed, someone has to manually download it and file it in the right Google Drive folder. There's no automatic routing.
- ~5,700 files need auditing and sorting. There's a backlog of DocuSign documents that need to be organized. This is one of the "small builds" in the $6K/month pod support line — the DocuSign audit and ongoing sorting.
- No integration with other People systems. DocuSign operates as a standalone tool. Signed documents don't automatically update Paylocity or trigger downstream workflows.
What's relevant to your role
DocuSign is part of the "small-build lane" in the consolidated proposal — the $6K/month pod support line covers the DocuSign audit (~5,700 files to sort) plus ongoing document sorting automation. This isn't your primary scope (which is the People Systems seat), but it falls under the broader team work you'll support. Getting API access unblocked is a dependency for automating the document routing.
Developer tools
| REST API | Yes — one of the most mature developer ecosystems on this list. Developer center: developers.docusign.com. Full eSignature REST API reference: developers.docusign.com/docs/esign-rest-api/reference/. Also available as a Postman collection. |
| SDKs | Official SDKs for C#, Java, PHP, Node.js, Python, and Obj-C. The Quickstart generates personalized starter code in 8 languages. |
| Sandbox | Yes — free developer sandbox account at signup. Completely separate from production. Supports testing all API features including webhooks. |
| Webhooks | Yes — DocuSign Connect is the webhook/notification service. Supports account-level webhooks and per-envelope webhooks (via eventNotification in API requests). Events include: envelope sent, delivered, completed, declined, voided. |
| Authentication | OAuth 2.0 (Authorization Code Grant, Implicit Grant, and JWT Grant flows). Integration keys managed through the developer portal. |
| Rate limits | Exist but vary by plan and endpoint. API returns standard rate limit headers. |
| Current integration approach at MR | Manual. Signed documents are downloaded and filed in Google Drive by hand. No automated routing. Once API access is unblocked, this is one of the more straightforward systems to automate given how strong the developer tooling is. |
Replacement timeline
Workday's Contract Lifecycle Management module (powered by Evisort, an AI contract intelligence tool) will replace DocuSign when Workday goes live in Q2-Q3 2027. Until then, DocuSign stays.