Parties
Full legal names and entity types for each contracting party, including d/b/a lines where applicable and a line for signatory title or capacity to establish who is bound.
Using a consistent RD TYSK format reduces ambiguity about parties, dates, and obligations, supports enforceability under 15 U.S.C. §7001 (ESIGN), and helps meet state UETA or ESRA formalities for electronic execution when applicable.
The RD TYSK is commonly used across transactional, administrative, and compliance workflows where a clear signed record is required.
Use the form when parties need an auditable, portable record of agreement terms that can be stored and reproduced for regulatory or business purposes.
An officer or manager with delegated authority should sign on behalf of an entity. Confirm corporate resolution, articles, or operating agreement before execution to ensure capacity and avoid later challenge based on lack of authority.
A natural person signs with government-name identification. For executors, trustees, or attorneys-in-fact, attach proof of appointment (letters testamentary, trust certification, or power of attorney) to validate signing authority.
Full legal names and entity types for each contracting party, including d/b/a lines where applicable and a line for signatory title or capacity to establish who is bound.
Short factual background explaining purpose and context of the agreement; keep recitals factual and avoid creating standalone obligations.
Clear, numbered clauses describing obligations, deadlines, deliverables, payment terms, and liability limits to reduce later disputes over scope.
Conspicuously state monetary amounts, services exchanged, or other consideration; avoid vague phrases like 'reasonable value' where possible.
Specify the governing state and venue for disputes; choice-of-law affects interpretation and enforceability, especially for consumer-facing contracts.
Signature lines with printed name, title, date, witness/notary fields, and electronic signature metadata placeholders for audit trails and notarization when required.
| Field | Configuration |
|---|---|
| Authentication | Email link | SMS code | KBA where available |
| Signing Order | Sequential or parallel as transaction requires |
| Reminders | Automatic reminders at 3 and 7 days |
| Retention Settings | Automatic export to secure storage after execution |
Ensure the chosen platform supports required file formats, authentication methods, and audit trails before sending RD TYSK electronically.
Verify platform-level compliance (ESIGN/UETA support, HIPAA BAA if required) and ensure signed copies plus audit logs are exported to your records system.
| Criteria | Electronic Signature | Digital Signature |
|---|---|---|
| Definition | any electronic act | pki-based cryptographic signature |
| Legal Acceptance | esign/ueta accept | accepted, stronger proof |
| Non-Repudiation | audit trail dependent | certificate-based non-repudiation |
| Typical Use | general contracts | high-assurance regulated records |
| 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 | Trial available | Trial available | Trial available | Trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |