
Form 135-R
Use the 135 R 2006 template to simplify high-volume document management.
Form 135-R overview
Form 135-R is a document that can be prepared, routed, signed, and retained electronically when its underlying transaction permits electronic execution. In signNow, the sender uploads the form, reviews auto-detected fillable fields, assigns signer roles, and sends it for completion. Signers review the assigned information and apply an electronic signature, while signNow records timestamps and document activity in an audit trail. The completed form and its evidence should be retained under the legal or organizational rule governing the underlying record.
Legal standing for business use
Form 135-R may be used as an electronic business record when the signer demonstrates intent, consents to electronic records, can be identified, and the completed record remains reproducible. ESIGN and applicable state law support electronic transactions, but wills, court orders, and family-law decrees remain excluded.

Who benefits from Form 135-R
Form 135-R fits workflows that require completed information, signer intent, and a retrievable electronic record across distributed teams.
Independent consultants use Form 135-R to collect signed client documents remotely, preserve the completed file, and avoid manually tracking separate email attachments. Healthcare practices use Form 135-R for authorized administrative paperwork, pairing signer verification with access controls when documents contain protected health information. Enterprise operations teams use Form 135-R with templates, delegated sending, and audit trails to standardize repeat transactions across departments and locations.
These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.
Key features for Form 135-R
signNow organizes the Form 135-R workflow from field preparation through signing and retrieval, while keeping the document and transaction evidence connected.
Field preparation
Upload Form 135-R, identify its fillable areas, and prepare assigned fields without rebuilding the document manually. Review detected fields before sending to prevent omissions.
Signer routing
Send Form 135-R to named recipients by email or provide a controlled signing link. Each signer can review the assigned fields before applying an electronic signature.
Audit trail
Capture timestamps, signer actions, and document history as the transaction progresses. The resulting audit trail helps connect the completed Form 135-R with its signing events.
Reusable templates
Use templates for repeat Form 135-R transactions so field placement, signer roles, and routing remain consistent across departments and recurring workflows.
Mobile access
Access Form 135-R from desktop or mobile workflows when authorized users need to prepare, review, or sign outside a fixed office environment.
Record retrieval
Store the completed document with its audit trail and completion evidence. Controlled retrieval supports internal review and applicable recordkeeping obligations.
- 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.
How to complete Form 135-R
Use this sequence to prepare Form 135-R in signNow, route it to the right signer, and retain the completed record with its transaction history.
Upload:
Upload the Form 135-R source file. Check fields:
Review auto-detected fields and correct assignments. Send:
Add each signer and send the document. Archive:
Review the signed file and audit trail.
Recommended Form 135-R workflow setup
Configure Form 135-R around signer identity, electronic intent, audit evidence, and the retention rule governing the underlying transaction.
| Setting | Recommendation |
|---|---|
| Authentication method | Email verification with SMS OTP |
| Signature type | Typed or drawn electronic signature |
| Audit trail | Capture timestamps, IP, and actions |
| Document retention | Apply the underlying record rule |
| Encryption | TLS 1.2 or TLS 1.3 in transit |
Find and fill out the correct usar form 135 r stayarmyreservecom stayarmyreserve army
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 |
|---|---|---|
| *2006 USAR 135-R [2006-01-01] 2006 | 4.8 Satisfied (4502 Votes) |
What the Form 135-R audit trail records
The audit trail documents signing evidence separately from field setup, helping reviewers inspect who acted, when actions occurred, and how the completed Form 135-R was preserved.
Authenticate:
Timestamp:
Hash record:
Seal:
Log activity:
Export:
Security for Form 135-R records
Transport encryption:
Stored data:
SOC 2 Type II:
ISO 27001:
HIPAA controls:
ESIGN and UETA:
Platform requirements for Form 135-R
Form 135-R can be prepared in a supported browser on Windows or macOS, while mobile access uses iOS or Android browsers. signNow protects data in transit with TLS 1.2 or TLS 1.3.
Desktop browsers Chrome, Firefox, Safari, and Edge on Windows or macOS. Mobile browsers Safari on iOS and Chrome on Android. Connection security TLS 1.2 or TLS 1.3 protects browser connections.
Organizations should manage browser updates, device access, and user permissions before sending Form 135-R. Teams using Salesforce, Microsoft 365, or an API should also confirm administrator provisioning, authentication policies, and storage controls for the completed record and its audit trail.
Retention periods for Form 135-R records
Form 135-R does not create one universal retention period. Keep the completed record according to the underlying transaction and the controlling federal or state rule.
Three years — tax records
Six years — substantial understatement
Six years — HIPAA records
Three years — FLSA payroll
Five years — OSHA injury records
Form 135-R troubleshooting
These answers address field detection, signer authentication, electronic consent, regulated information, plan selection, and record retention for Form 135-R workflows.
Confirm the uploaded file opens correctly, then review signNow’s detected fields before sending. Correct missing or misplaced fields manually, assign every field to the intended signer, and save the template only after comparing it with the source Form 135-R.
The Business plan includes templates and audit trails, while Business Premium adds bulk send. If one Form 135-R must be delivered repeatedly with different signer data, confirm that the selected plan supports the required sending pattern before deployment.
Use email verification or stronger authentication when the transaction requires more signer assurance. Business Premium includes request payments and kiosk mode; Enterprise adds advanced signer authentication. Select the control required by your organization and the underlying Form 135-R workflow.
For consumer-facing electronic records, provide the disclosure required by 15 U.S.C. §7001(c), demonstrate access to the electronic format, and explain withdrawal procedures. signNow can preserve the signing record, but the business remains responsible for obtaining legally required consent.
HIPAA applies only when the Form 135-R workflow handles protected health information for a covered entity or business associate. signNow identifies HIPAA compliance as requiring a BAA; execute the BAA and configure access controls before handling PHI.
Export the completed Form 135-R together with its audit trail and completion evidence. Store both under the retention rule for the underlying record, such as IRC §6501(a) for applicable tax records, rather than applying one universal period.
Key performance indicators that demonstrate SignNow's proven track record.
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.