Download signNow app
4.7 / 5 rating on

D R L 113 Applicable Where The Adoption Petition Was Form

Use a D R L 113 Applicable Where The Adoption Petition Was template to make your document workflow more streamlined.

What this adoption petition form does

D R L 113 Applicable Where The Adoption Petition Was Form is a court filing used in an adoption matter to present required information about the child, petitioners, and requested legal relief. Its exact fields, filing method, signature requirements, and supporting documents depend on the issuing court and state law. Before using an electronic workflow, confirm whether the court accepts electronic signatures and whether notarization, verified statements, consent documents, or in-person filing are required. signNow can organize the source PDF, place fields, route designated signers, and preserve an audit trail, but it does not replace court rules or legal review.

Who uses this adoption petition form

Family-law counsel

Family-law counsel coordinates petitioner information, required acknowledgments, supporting declarations, and court-specific signature steps while preserving a controlled case record.

Adoption agencies

Adoption agencies and authorized case teams route designated supporting documents, confirm participant identity, and separate sensitive child information from unnecessary recipients.

Who works with this petition form

  • Family-law attorneys use the petition PDF to coordinate petitioner information, required acknowledgments, and supporting signatures while checking the receiving court’s filing and notarization rules. A controlled workflow helps separate drafts from the final record and preserves signer activity for the case file while counsel remains responsible for legal sufficiency and submission requirements.
  • Adoption agencies and authorized case teams may use signNow to collect designated acknowledgments or supporting forms from multiple participants. They should confirm that each signer has authority, that sensitive child and family information is access-controlled, and that the court accepts the resulting signature method before relying on the completed petition package.

How to process the petition

Use this sequence to prepare the D R L 113 petition while keeping court acceptance and record integrity separate from platform mechanics.

  • Upload form: Upload the D R L 113 petition PDF to signNow.
  • Check fields: Review detected fields against the court copy.
  • Send securely: Route only authorized signers and required recipients.
  • Store evidence: Preserve the completed file and audit trail.
be ready to get more
Get legally-binding signatures now!
  • 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 the petition audit trail works

The audit trail documents who interacted with the adoption petition, when each event occurred, and how authorized users can preserve the resulting evidence.

01

Signer authentication:

Records the signer’s email or configured authentication event.
02

Timestamp capture:

Captures the signing event’s date and time.
03

Document identity:

Associates the completed petition file with its audit record.
04

Tamper evidence:

Preserves actions in a tamper-evident history.
05

Action history:

Records delivery, viewing, signing, and completion events.
06

Audit export:

Allows authorized users to retrieve or export evidence.

Recommended petition workflow setup

Configure the D R L 113 workflow around court acceptance, signer identity, restricted case access, and preservation of the completed record.

SettingRecommendation
Authentication methodRecipient-specific email with SMS verification
Signature typeCourt-approved electronic signature
Audit trail and retentionExport completion evidence to the case file
EncryptionTLS 1.2/1.3 and AES-256
User provisioningRole-based access for authorized case staff

Security controls for petition records

Transport encryption:

TLS 1.2/1.3 in transit

Stored encryption:

AES-256 at rest

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Healthcare safeguards:

HIPAA compliance with BAA

Privacy compliance:

GDPR compliant data controls

Privacy pitfalls in adoption filings

  • Child names, addresses, medical details, and family history can be exposed when petition files or signing links are sent to unintended recipients.
  • A signer may complete the petition without the electronic-consent disclosure required for a qualifying consumer transaction under 15 U.S.C. §7001(c).
  • Shared accounts or broad folder permissions can allow unauthorized case-team members to view adoption records and audit evidence.
  • A signNow completion record may be mistaken for court acceptance when the court requires notarization, wet ink, or an approved filing portal.

Check legal formalities before signing

Notarization required

May require notarization

Court acceptance

Filing may be rejected

Family-law filing

Excluded from ESIGN exceptions

Real-estate deed

Separate recording rules apply

Wills excluded

Probate formalities still govern

Legal standing and filing limits

ESIGN, 15 U.S.C. chapter 96, and UETA generally recognize electronic signatures when intent, consent, attribution, and record retention are established. However, federal exceptions include court orders and official court filings, as well as family-law decrees such as adoption matters. Confirm the receiving court’s rules before relying on an electronic petition.

Why teams look for DocuSign alternatives

Best practices for this petition

A reliable petition workflow starts with court-rule verification, precise field placement, restricted access, and a documented final-record process.

Verify every field against the court form

Compare the uploaded PDF with the court-issued D R L 113 form before placing fields. Verify every petitioner name, child reference, date, attachment, and signature location. Do not assume automatic field detection identifies legally required fields or distinguishes a filing copy from a working draft.

Confirm the receiving court’s rules first

Confirm the court’s electronic-filing, signature, notarization, and service instructions before routing the petition. Adoption and other family-law filings are among ESIGN’s listed exceptions, so a completed electronic document may still require an approved portal, wet-ink execution, or in-person submission.

Limit exposure of family information

Restrict access to the case team and intended signers, then use recipient-specific delivery and stronger authentication when appropriate. Keep child names, medical details, addresses, and consent information out of unnecessary messages or shared links.

Archive the final record carefully

Export the completed petition and audit trail into the matter’s authorized record system, then apply the court and state retention schedule. Do not use HIPAA’s six-year rule unless the record is actually subject to HIPAA 45 CFR §164.530(j).

Troubleshooting this petition workflow

Resolve signing, access, and filing questions by separating signNow workflow behavior from the adoption court’s independent requirements.

If the receiving court requires a wet-ink signature, notarization, or an approved court portal, a signNow completion record does not satisfy that separate rule. Confirm the court’s instructions before sending the petition. ESIGN and UETA do not override statutory exceptions or court-specific filing procedures.

The Business plan includes legally binding eSignatures, audit trails, templates, and mobile apps at $8/user/month when billed annually. If the petition workflow requires bulk send, Business Premium is listed at $15/user/month annually and adds bulk send.

Adoption records may contain sensitive child and family information. Use role-based access, limit recipients, and confirm applicable state privacy rules. HIPAA compliance is available with a BAA when protected health information is involved; adoption status alone does not establish HIPAA coverage.

A signing link can simplify delivery, but anyone who obtains the link may attempt access unless additional controls are configured. Use recipient-specific delivery or stronger authentication when identity, consent, or court evidence requires it.

If fields are misplaced after upload, review every page against the source petition before sending. Auto-detection can accelerate field placement, but the sender remains responsible for petitioner names, dates, attachments, and required signature locations.

For consumer-facing electronic records, ESIGN requires disclosure of the right to receive paper, access to the electronic format, and procedures for withdrawing consent under 15 U.S.C. §7001(c). Apply those requirements when the transaction qualifies as consumer-facing.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

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.