715 USA Form 186Pretrial Diversion Agreementjm

Use a 715 USA Form 186Pretrial Diversion AgreementJM template to make your document workflow more streamlined.

What this pretrial diversion agreement does

The 715 USA Form 186Pretrial Diversion Agreementjm is a document used to record the parties’ agreed terms for a pretrial diversion arrangement, but the supplied materials do not identify its issuing agency, jurisdiction, fields, or filing deadline. Do not assume that electronic signing alone completes a court requirement. Upload the exact form, verify every field against the responsible court or prosecutor’s instructions, obtain required consent, and preserve the signed copy with its audit trail. ESIGN and applicable state electronic-transaction law may support the signature record, subject to statutory exclusions and local procedure.

Who handles this diversion agreement

The responsible attorney, prosecutor, participant, or court-services team should verify the applicable jurisdiction before signing.

A defense attorney can prepare the named agreement, route it to the required participant, and retain execution evidence for the client file.
A prosecutor’s office can use a controlled template to collect signatures while confirming local court, witness, and filing requirements independently.
A court-services administrator can track completed agreements, preserve audit trails, and restrict access without treating signNow as the issuing authority.

Complete this agreement in signNow

Use the exact court- or agency-provided agreement, verify its fields, and preserve execution evidence after all required parties sign.

Upload agreement:
Upload the exact agreement PDF.
Check fields:
Review detected fields and add missing signature, date, or initials fields.
Assign roles:
Assign each field to the correct participant.
Send for signing:
Send the agreement and monitor completion status.
Store evidence:
Download the completed agreement and audit trail.

Authenticate signer:

Records the signer’s email, access method, and authentication event.

Capture timestamp:

Captures signing time with the applicable transaction timezone.

Hash document:

Associates document content with a recorded integrity value.

Seal document:

Locks completed content against undetected post-signing changes.

Log actions:

Logs field completion, signature actions, and participant events.

Export trail:

Allows authorized users to retrieve or export completion evidence.

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.

Platform requirements for this agreement

Complete the 715 USA Form 186Pretrial Diversion Agreementjm in Chrome, Firefox, Safari, or Edge on Windows 10, macOS 12, iOS 16, or Android 11.

Supported browsers Chrome, Firefox, Safari, and Edge
Operating systems Windows 10, macOS 12, iOS 16, Android 11
Supported devices Desktop, iPhone, iPad, and Android devices

For managed legal workflows, confirm browser updates, device access, and organizational retention policies before sending. signNow Business provides templates, mobile apps, and audit trails; stronger authentication, integrations, or regulated controls may require higher plans or configuration.

Security controls for this agreement

Transport encryption:

TLS 1.2/1.3 in transit

Stored data encryption:

AES-256 at rest

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Electronic signatures:

ESIGN and UETA compliant

Health information:

HIPAA compliant with BAA

Integrations for agreement workflows

Connect agreement data with Salesforce, NetSuite, Microsoft 365, Google Drive, Box, or Procore to reduce rekeying and preserve organized records.

Privacy risks when sharing this agreement

Personal identifiers copied into the agreement may be visible to every recipient; limit fields and verify recipients before sending.
Missing electronic-consent evidence can weaken the record; provide required disclosures and retain the signer’s consent history.
Incorrect role permissions can expose a completed agreement; restrict template, sending, and download access to authorized personnel.
A public signing link can circulate beyond the intended participant; use controlled recipients or added authentication for sensitive agreements.

Retention periods for related records

The agreement has no single universal retention period; select the record class and governing authority that actually applies.

At least 3 years: federal tax records

Apply the governing state or contractual retention rule.

3 years after hire or 1 year after termination

Retain required employment records under the cited immigration regulation.

6 years from creation or last effective date

Retain covered health records under the HIPAA privacy rule.

6 years for broker-dealer records

Preserve broker-dealer books and records under SEC Rule 17a-4.

3 years for basic payroll records

Retain payroll records under the Fair Labor Standards Act.

State rules affecting this agreement

Notary requirement

May require notarization

Wills and codicils

Excluded from ESIGN

Family law decrees

Excluded from ESIGN

Real-estate deeds

State recording may fail

Record-keeping practices for this agreement

Retain the completed agreement according to its legal context, preserve its audit evidence, and control access throughout the retention period.

Apply the governing retention period

Keep the completed agreement and its audit trail together in a controlled repository. If the record contains protected health information, retain it for six years from creation or the last effective date under 45 CFR §164.530(j). Apply any longer state or contractual period.

Export the audit trail promptly

Export the signed PDF and completion evidence after every completed transaction. Preserve the file name, signer sequence, timestamps, and delivery record so the agreement can be reproduced during a dispute or internal review.

Limit access to agreement records

Restrict access to authorized legal, compliance, and case-management personnel. Use role-based permissions and avoid sending agreement copies through unsecured personal email or shared public links.

Maintain secure archival controls

Test that stored files open correctly and remain associated with their audit evidence. Document deletion approvals, legal holds, and any state-specific retention rule before removing a completed agreement.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

Troubleshooting this agreement workflow

Use these answers to resolve field, signing, audit-trail, plan, and retention questions before distributing the completed agreement.

Upload the agreement as a supported PDF, then review signNow’s detected fields before sending. If fields are missing, add signature, date, initials, or text fields manually and confirm each participant’s role.

The signNow Business plan includes legally binding eSignatures, templates, audit trails, and mobile apps at $8 per user per month when billed annually. Higher tiers add bulk sending, kiosk mode, or advanced authentication.

ESIGN and UETA generally recognize electronic signatures when intent, consent, attribution, and record retention are established. For consumer-facing records, 15 U.S.C. §7001(c) also requires required electronic-record disclosures and access procedures.

Use signNow’s audit trail to preserve signer identity, timestamps, actions, and completion evidence. The audit trail supports evidence of execution, but it does not replace a state-required notary, witness, filing, or court procedure.

Business Premium includes bulk send and costs $15 per user per month when billed annually. For one agreement, Business can provide templates, audit trails, and mobile signing without the bulk-send feature.

The agreement itself does not establish a universal retention period. Apply the rule governing its underlying matter; HIPAA-covered records require six years under 45 CFR §164.530(j), while state requirements may be longer.

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.