To Be Sent

Use a To Be Sent 2020 template to make your document workflow more streamlined.

What To Be Sent is and how it works

To Be Sent is a document that can be prepared, completed, and signed electronically when its underlying transaction permits electronic execution. In signNow, upload the source file, review automatically detected fillable areas or place fields manually, assign recipients, and send the signing request. Each signer reviews the document and applies the assigned fields, while signNow records the signing events in an audit trail. The completed file and related evidence can then be retained according to the applicable business, legal, or regulatory policy.

Business teams

Use To Be Sent for contracts, NDAs, HR forms, invoices, or consent records when multiple parties must complete defined fields and sign electronically.

Service organizations

Use To Be Sent for client, patient, employee, vendor, or customer paperwork when access controls and an auditable completion record matter.

How To Be Sent works in signNow

To Be Sent moves from document preparation to signer completion through a controlled sequence that preserves the final file and its signing evidence.

Upload document: Upload To Be Sent to signNow.
Prepare fields: Detect or place fillable fields.
Set recipients: Add recipients and signing order.
Complete record: Collect signatures and retain evidence.

Quick steps to complete To Be Sent

Prepare To Be Sent in signNow by checking the document, assigning fields, sending the request, and preserving the completed record.

Upload:
Upload the To Be Sent file.
Check fields:
Review detected or placed fields.
Add signers:
Add signers and signing order.
Complete:
Send, sign, and store the record.

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.

Authenticate signer:

Confirm signer identity through configured authentication.

Capture timestamp:

Record the exact signing event time.

Hash document:

Associate document content with a hash.

Seal record:

Seal completed records against later changes.

Record actions:

Preserve signer actions and document history.

Export trail:

Retrieve or export the completed audit trail.

Signer authentication for To Be Sent

PKI:

Public-key infrastructure support

X.509 certificates:

Certificate-based document identity

Two-factor authentication:

Two-step signer verification

SMS OTP:

One-time passcodes by text

ID verification:

Additional identity checks available

Signer evidence:

Audit trail supports attribution

Find and fill out the correct to be sent

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

Versions	Form popularity	Fillable & printable
Health Partners 18534 2020	4.8 Satisfied (1915 Votes)
Health Partners 18534 2019	4.8 Satisfied (172 Votes)

Mobile options for To Be Sent

To Be Sent can be prepared or signed through signNow mobile apps for iOS and Android. Browser-based access remains available through supported desktop environments, while camera capture can turn a paper copy into a digital document for preparation.

Mobile apps iOS and Android apps available
Offline signing Offline signing supports disconnected work
Camera capture Camera capture scans paper documents

Offline signing can help when connectivity is unavailable, but completed records should be synchronized and reviewed after reconnection. Organizations handling regulated information should configure authentication, access permissions, retention, and audit-trail procedures before distributing To Be Sent from managed mobile devices.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Typed or drawn electronic signature
Audit trail	Enable completion history and export
Document retention	Follow the governing record policy
Encryption	TLS in transit and AES-256 at rest

Best practices for To Be Sent

A controlled preparation process helps prevent field errors, unauthorized access, incomplete consent, and weak evidence after To Be Sent is completed.

Verify the source before preparing fields

Upload the final To Be Sent source, then compare the rendered document with the original. Confirm that page order, text, attachments, and required fields are complete before adding recipients or sending invitations.

Assign every field to the correct signer

Use distinct signer roles and place fields beside the information each recipient must provide. A deliberate field map reduces misplaced signatures, missing dates, and later requests to correct To Be Sent.

Match authentication to document sensitivity

Choose email authentication or stronger options according to the information contained in To Be Sent. For consumer transactions, address electronic-record disclosure and consent requirements under 15 U.S.C. §7001(c).

Preserve the signed record and audit trail

Retain the completed To Be Sent record with its audit trail, access controls, and applicable organizational retention policy. If the document supports a regulated process, confirm the governing rule before deletion.

Prepare the document

Upload the correct To Be Sent source and verify every required field.

Deliver to signers

Add signer details and send the configured signing request.

Complete signer review

Signers review, complete, and authenticate To Be Sent.

Archive the record

Download or retain the completed document and audit trail.

Check exclusions before signing

Notarization

May require notarization under applicable state law.

Wills

Excluded from ESIGN and UETA.

Court orders

Court filings may require official submission.

Family law

Family-law decrees remain excluded.

Real-estate deeds

Deed validity depends on state acknowledgment rules.

Troubleshooting To Be Sent

Use these checks to resolve field, invitation, authentication, consent, and legal-scope questions before completing To Be Sent.

Upload the source document again after confirming it opens normally and contains the intended To Be Sent pages. In signNow, place fields manually when automatic detection does not identify the document’s fillable areas. Review every field before sending.

Check that each signer has the correct email address and that the signing order matches the intended To Be Sent process. Resend only after confirming the recipient list, permissions, and document version in signNow.

Use signNow’s audit trail to review timestamps, signer actions, and document history. Under ESIGN and UETA, enforceability depends on intent, consent, attribution, and retaining a reproducible electronic record, not merely an image of a signature.

Business includes legally binding eSignatures, templates, and audit trails. Business Premium adds bulk send, kiosk mode, and quick invite links. Select a plan according to the number of recipients and the workflow requirements for To Be Sent.

For consumer-facing transactions, provide the ESIGN disclosure, explain the right to receive paper records, confirm electronic access, and provide withdrawal procedures under 15 U.S.C. §7001(c). Obtain appropriate consent before sending To Be Sent electronically.

An electronic signature does not replace every legally required formality. Wills, court orders, family-law decrees, and certain notices are excluded under ESIGN; state law may also require notarization or other treatment for the specific document.

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.