Authority
Define who may approve EDC systems and delegate signing or data-capture authority, including thresholds for escalation and board-level approvals when required.
A clear memorandum reduces operational ambiguity by documenting authority, workflows, and data handling rules; it helps meet regulatory and internal audit expectations and supports defensible recordkeeping for electronic records and signatures under ESIGN and UETA.
Teams across legal, compliance, IT, and operations commonly prepare or reference this memorandum when implementing or changing EDC processes.
The document supports cross-functional alignment and is used as a reference during audits, vendor onboarding, and incident investigations.
As the technology owner, the CIO typically certifies technical controls, encryption standards, and system access policies; their approval confirms that the EDC implementation meets enterprise IT and security requirements.
The General Counsel or head of legal reviews legal risks, ensures ESIGN/UETA compliance, and approves required consumer disclosures and retention schedules to align the memorandum with applicable statutes and contracts.
| Field | Configuration |
|---|---|
| Authentication | Email link or SMS code; enable stronger methods for high-risk records |
| Reminders | Set automatic reminders at 3 and 7 days to reduce turnaround time |
| Conditional Fields | Show or hide sections based on party type to simplify signer experience |
| Audit Trail | Capture IP, timestamp, and actions for each signer for legal evidence |
Define who may approve EDC systems and delegate signing or data-capture authority, including thresholds for escalation and board-level approvals when required.
List systems, data categories, and business processes covered by the memorandum, and note any excluded systems or limited-use platforms.
Describe encryption in transit and at rest, access control, logging, and incident response measures to protect captured data.
Specify retention periods, archival locations, and secure deletion procedures consistent with regulatory obligations and business needs.
Provide step-by-step procedures for data capture, error correction, exception handling, and routine audits to ensure consistent execution.
Detail acceptable e-signature methods, signer authentication levels, audit trail requirements, and evidence to preserve for legal defensibility.
Determine and record the MM/DD/YYYY effective date to start obligations and retention clocks.
Schedule an annual compliance review to validate controls and update the memorandum as needed.
Allow typical sign-back windows of 7–14 days; shorter windows may be needed for operational changes.
Retention periods typically begin on the effective date or record creation date, whichever the memorandum specifies.
Preserve audit logs and completed copies for the full retention period to satisfy review or legal requests.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no credit card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year limit | Varies by plan | Varies by plan | Varies by plan |
Confirm platform compatibility with your systems and required security controls before enabling e-signatures and e-submissions.