Non Law Enforcement Referral Form

Use a Non Law Enforcement Referral template to make your document workflow more streamlined.

What this referral form does

The Non Law Enforcement Referral Form records a referral to an authorized recipient without presenting it as a law-enforcement request. It can identify the referring party, the person or matter being referred, relevant circumstances, consent or disclosure limits, and requested follow-up. With signNow, a sender uploads the form, checks detected fillable fields, assigns recipients, and sends it for review and signature. The completed PDF and audit trail preserve the signing sequence, timestamps, and recipient actions for later recordkeeping.

Public agencies

Public agencies and nonprofit service providers can use a referral workflow to collect identifying information, consent, contact details, and supporting records from authorized individuals. Access controls and disclosure procedures should match the sensitivity of the referral and any applicable state or federal privacy requirements.

Service providers

Community organizations and regulated providers can route referrals to designated reviewers, capture signatures, and preserve the completed record. A documented approval path helps distinguish the referring person, receiving organization, and any staff member authorized to review the information.

How the referral workflow works

Complete the Non Law Enforcement Referral Form by preparing its fields, identifying authorized signers, and preserving the signed record with supporting evidence.

Upload form: Upload the blank referral PDF to signNow.
Check fields: Auto-detect fields, then verify each placement.
Assign signers: Add authorized recipients and signing order.
Complete record: Send, sign, and store the completed referral.

Setting	Recommendation
Authentication method	Email link with SMS OTP
Signature type	Typed or drawn electronic signature
Audit trail	Enable completion certificate and action log
Document retention	Apply category-specific written policy
Encryption	TLS 1.2 or 1.3 and AES-256

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 signing

Use signNow through Chrome, Firefox, Safari, or Edge on Windows 10, macOS 12, iOS 16, or Android 12. The signNow mobile app supports completing and signing the referral form from iOS and Android devices.

Browsers Chrome, Firefox, Safari, and Edge
Operating systems Windows 10, macOS 12, iOS 16
Mobile app Android 12 and signNow mobile app

Organizations handling sensitive referral information should manage supported devices, restrict downloads, and confirm that recipients can access the completed PDF. Enterprise deployments may also require API access, SSO provisioning, managed mobile devices, and retention controls aligned with internal policy.

Security controls for referral documents

Data in transit:

TLS 1.2 and 1.3

Data at rest:

AES-256 protects stored documents

Operational controls:

SOC 2 Type II certification

Information security:

ISO 27001 certification

Health information:

HIPAA compliance requires a BAA

Electronic signatures:

ESIGN and UETA compliant

Quick steps to complete the referral

Use this sequence to prepare, route, sign, and preserve the Non Law Enforcement Referral Form in signNow.

Prepare form:
Upload the referral PDF.
Check fields:
Verify detected fields and labels.
Set recipients:
Add recipients and signing order.
Send form:
Send the referral for signature.
Archive evidence:
Download the signed record and audit trail.

Authenticate signer:

Record the authentication event.

Timestamp action:

Capture the exact signing time.

Track activity:

Log recipient activity and IP data.

Hash document:

Preserve the signed document hash.

Seal record:

Seal the completed record against changes.

Export evidence:

Retrieve the audit trail with the PDF.

Privacy pitfalls in referral workflows

Personal details in a referral may be visible to unintended recipients when copies are forwarded, downloaded, or stored outside approved systems.
Missing consent language can make it difficult to demonstrate that the referred person authorized disclosure of specific information.
Unrestricted templates or shared accounts can expose referral data to staff without a defined need to access it.
Sending a completed referral to the wrong address can disclose sensitive allegations, contact details, or supporting documentation.

Retention periods for referral records

Keep the completed referral and related evidence according to the record category, applicable authority, and your organization’s documented retention policy.

Six years for HIPAA records

HIPAA 45 CFR 164.530(j) requires covered entities to retain required policies, procedures, and documentation for six years.

Three years for tax records

IRC §6501(a) generally allows three years from filing for federal tax records connected to referral-related payments.

Three years after hire or termination

8 CFR §274a.2(b)(2)(i)(A) requires Form I-9 records for three years after hire or one year after termination, whichever is later.

Three years for payroll records

29 CFR §516.5 requires covered payroll records for three years when referral work includes FLSA-covered employees.

Five years for injury records

29 CFR §1904.33 requires OSHA injury records for five years following the year of record creation.

Best practices for referral records

Accurate field review, controlled access, category-based retention, and complete evidence export reduce disclosure and recordkeeping problems for this referral form.

Verify referral details before sending

Review the completed referral before signature, confirming the referred person, recipient organization, disclosure limits, and every required field. Export the signed PDF and audit trail together so the record preserves both the form contents and evidence of who acted, when, and in what sequence.

Restrict access to authorized reviewers

Limit access to staff assigned to intake, review, or follow-up. Use named recipient accounts instead of shared credentials, confirm email addresses independently, and remove unnecessary access after the referral is completed or reassigned.

Map retention to the record category

Select retention by record category rather than applying one period to every referral. HIPAA documentation generally requires six years under 45 CFR §164.530(j), while other records may follow IRS, employment, payroll, or state rules.

Archive the complete evidence package

Store the signed referral, completion certificate, and audit trail in an approved repository. Use signNow integrations such as Google Drive, Box, or Egnyte only when permissions and retention settings match the organization’s records policy.

Troubleshooting referral form signing

Resolve field, recipient, consent, security, and plan-limit questions before distributing the completed referral.

Upload the original PDF again and inspect every detected field before sending. signNow templates can standardize recurring referral forms, while the Business plan includes templates and audit trails at $8/user/month with annual billing. Confirm that required fields are assigned to the correct recipient.

Use signNow’s recipient settings to assign each field to the referring person, reviewer, or approving organization. Send the form again only after checking signing order and recipient email addresses. The Business Premium plan adds bulk send when multiple individualized referrals require distribution.

A signed referral can generally use an electronic signature when the signer intends to sign, consents to electronic records, can be identified, and the record can be retained and reproduced. ESIGN, 15 U.S.C. ch. 96, and applicable state UETA law provide the governing framework.

Consumer-facing electronic records may require an ESIGN disclosure explaining paper-record rights, electronic access, and withdrawal procedures under 15 U.S.C. §7001(c). Obtain any required consent before sending the referral, especially when the recipient is a consumer or patient.

Use role-based access, recipient authentication, and a documented retention policy before storing the completed referral. signNow supports TLS 1.2 and 1.3, AES-256, SOC 2 Type II, and ISO 27001; HIPAA workflows require a business associate agreement.

The Business plan includes 100 signature invites per user annually, with overage fees; it does not provide unlimited subscription invites. Business Premium adds bulk send, while Site License pricing is $1.50 per signature invite for usage-based deployments.

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.