1CES Application Form Designate Third Party, Release Information Form Des V 1

Use a 1CES Application Form Designate Third Party, Release Information Form DES V 1 pdf template to make your document workflow more streamlined.

What this third-party release does

This form records a person’s authorization for a named third party to receive specified information. In practice, the signer identifies the designated recipient, describes the information or records covered, and confirms the release terms before signing. With signNow, the document can be uploaded, its fillable fields reviewed, and signature fields assigned before delivery. The completed release can then be stored with an audit trail showing signing activity. Electronic enforceability depends on intent, consent, attribution, and record retention under ESIGN and applicable state law.

Business users for this release

This form is most useful when a person or organization must authorize another party to obtain defined information.

Solo practitioners use the release to authorize a specific accountant, attorney, caregiver, or family representative to receive information without repeatedly requesting permission for each disclosure.
Healthcare practices use the form to document a patient’s designated recipient, limit disclosures to the stated scope, and preserve signed authorization records for internal review.
Enterprise compliance teams use shared templates, controlled access, and audit trails to manage recurring third-party information releases across departments and locations.

Field preparation

Upload the release and review automatically detected fields before assigning signer responsibilities, reducing manual preparation while keeping the designated recipient and authorization scope visible for review.

Signer delivery

Send the release by email or configured signing link, allowing the named signer to review the authorization terms before applying an electronic signature.

Audit trail

Capture timestamps, signer actions, and document history so the completed release has supporting evidence for internal review and later retrieval.

Signer identity

Use SMS OTP or other configured authentication controls to strengthen signer attribution without changing the recipient or information scope written in the release.

Secure storage

Store completed releases in an organized workflow with controlled access, supporting retention and retrieval requirements for personal or protected information.

Named integrations

Connect release workflows with Google Drive, Box, Salesforce, or Microsoft 365 when the organization needs controlled document routing and record access.

How the release workflow works

The signNow workflow converts this release into a controlled signing sequence while preserving the authorization scope and completion evidence.

Upload form: Upload the designated third-party release document.
Prepare fields: Review detected fields and add missing authorization fields.
Request signature: Send the release to the required signer.
Archive record: Store the completed release with its audit trail.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Typed or drawn electronic signature
Audit trail	Capture timestamps, IP address, and actions
Document retention	Follow the applicable state or industry rule
Encryption	TLS 1.2/1.3 and AES-256 protection

Platform requirements for signing

Complete the 1CES Application Form Designate Third Party, Release Information Form Des V 1 through Chrome, Firefox, Safari, or Edge on Windows 10, Windows 11, or macOS. signNow also provides mobile apps for iOS and Android, allowing signers to review and complete the release from supported mobile devices.

Supported browsers Chrome, Firefox, Safari, and Edge
Operating systems Windows 10, Windows 11, macOS, iOS, Android
Mobile access signNow mobile apps for iOS and Android

Organizations handling sensitive releases should manage supported browsers, mobile applications, and device permissions centrally. For regulated workflows, evaluate signNow authentication, API access, SSO provisioning, certificate requirements, and long-term validation separately; the platform environment does not replace the organization’s legal retention or disclosure obligations.

Security for signed releases

Transport encryption:

TLS 1.2/1.3 protects data in transit

Stored encryption:

AES-256 protects stored release records

Security certification:

SOC 2 Type II report available on request

Security management:

ISO 27001 certification supports information security

Electronic signatures:

ESIGN and UETA compliance supports electronic signing

Healthcare disclosures:

HIPAA compliance requires a BAA

Authenticate signer:

Record the signer’s email or configured authentication event.

Capture timestamp:

Capture the exact time of each signing action.

Hash document:

Create a document hash for integrity checking.

Seal record:

Seal the completed release against later alteration.

Build history:

Attach signer actions and access details.

Export evidence:

Retrieve or export the completed audit trail.

Record-keeping practices for releases

Retention and access controls should match the information disclosed, the recipient, and the governing U.S. rule.

Set the retention period first

Define a written retention rule before sending the release, based on the information involved and applicable state or industry requirements. For HIPAA-covered records, retain required documentation for six years from creation or its last effective date under 45 CFR §164.530(j).

Export the complete evidence package

Export the completed release and audit trail together after every signing event. Preserve the final PDF, completion evidence, signer identity details, and authorization scope in a controlled repository with access limited to authorized personnel.

Restrict the disclosure scope

Limit the form to the information and recipient actually authorized by the signer. Review the designated party, disclosure scope, expiration language, and revocation process before sending, because overbroad wording can create disclosure disputes.

Protect archived release records

Use role-based access and encryption for stored releases containing personal or health information. Review permissions periodically, document any revocation, and preserve the original completed record instead of editing the signed file.

Privacy and disclosure pitfalls

Including unrestricted language can authorize disclosures beyond the signer’s intended information scope.
Omitting the designated recipient’s identity can make the authorization difficult to apply or verify.
Sending the completed release through uncontrolled email can expose personal information and weaken access governance.
Failing to capture electronic-record consent can create uncertainty about the signer’s agreement to transact electronically.

State rules and excluded documents

State notary rules

Notarization may be required

Wills excluded

Release may be rejected

Family decrees excluded

Court filing rules apply

Deed requirements

Recording may be refused

Legal standing and evidence

A signed release can support a U.S. business transaction when the signer shows intent, consents to electronic records, can be identified, and the record remains reproducible under ESIGN and applicable UETA or New York ESRA rules. Wills, codicils, testamentary trusts, court orders, and family-law decrees remain statutory exclusions.

Why teams look for DocuSign alternatives

Troubleshooting this release form

These answers address field detection, electronic signing, authentication, protected information, and preservation of the completed release.

Upload the original PDF again and review signNow’s detected fields. Auto-detection may require correction when labels, checkboxes, or signature areas are scanned images. Confirm the designated recipient and authorization scope manually before sending the release.

The Business plan provides legally binding eSignatures, templates, audit trails, and mobile apps at $8 per user per month when billed annually. Bulk sending is listed for Business Premium at $15 per user per month annually.

SignNow supports ESIGN and UETA requirements, but enforceability still depends on intent, electronic consent, attribution, and record retention. For consumer-facing disclosures, review the electronic-record requirements in 15 U.S.C. §7001(c).

A HIPAA-covered workflow requires a business associate agreement and appropriate safeguards. SignNow identifies HIPAA compliance as requiring a BAA; the organization remains responsible for authorization scope and six-year documentation retention under 45 CFR §164.530(j).

Use signNow’s signer authentication options, including SMS OTP where configured, and verify the recipient before disclosure. Authentication supports attribution but does not expand the information or recipient scope written in the release.

Export the completed document and audit trail after signing, then store them together under the organization’s retention policy. Do not alter the signed PDF; preserve the original record and restrict access to authorized personnel.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.