What if I miss the deadline?

Timely submission is typically required. Missing the deadline can result in denial or dismissal. Contact the issuing office immediately to request an extension only if the RFE permits it; retain proof of all communications.

Can electronic signatures be used?

Electronic signatures are legally valid under ESIGN and UETA when intent, consent, attribution, and retention requirements are met. If the issuer requires notarization or a wet signature, follow that instruction instead.

Are scanned copies acceptable?

Scanned copies are commonly accepted unless the RFE explicitly requires originals, certified copies, or notarized documents. Verify the format requirements listed in the RFE before submitting scanned materials.

How should I label submitted files?

Use clear filenames that include the case number and RFE item number. Include a numbered table of contents inside the packet so reviewers can match each file to the requested item.

What proof of delivery is sufficient?

Keep tracked shipment receipts, portal upload confirmations, or stamped delivery acknowledgements. These records demonstrate submission date and method and can be critical if timeliness is questioned.

Who can sign an affidavit?

Anyone with direct knowledge may sign, but affidavits often require notarization and a statement of identity and relation to the facts. Follow the issuer's instructions about witness or notarization requirements.

Electronic Signature
Templates
Miscellaneous
Request for Evidence Form

Request for Evidence Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

REQUEST FOR EVIDENCE FORM

Requesting Party Name: Respondent Name:

Authorized Representative

Requesting Party Address

Contact Email

Contact Phone

Case / File Number: Date of Request:

WHEREAS

WHEREAS, Requesting Party Name: seeks documents, information and other evidence reasonably necessary for the review, investigation, or enforcement of the matters identified in Case / File Number: ; and

WHEREAS, Respondent Name: may possess documentary, electronic or physical evidence responsive to this Request for Evidence and is legally obligated to produce the same in accordance with the terms set forth herein.

EVIDENCE REQUESTED

The Respondent is requested to produce the following categories of evidence. Check all that apply and provide the requested detail below.

Documents and correspondence
Contracts and agreements
Financial records and statements
Photographs / Video evidence
Electronic data / emails / metadata
Other (describe)

Detailed Description of Evidence Requested Attachments / Specific Documents to be Produced

Response Required By: Method of Delivery:

Failure to comply with this Request for Evidence by the Response Required By date may result in administrative remedies, court action, or other enforcement measures permitted by law. If any responsive material is withheld on grounds of privilege, produce a privilege log identifying the basis for withholding.

SCOPE OF WORK

Scope of Work

PAYMENT TERMS

Total Fee Amount: $

Payment Schedule / Invoicing

Late Payment Fee: . All fees are due within the period set forth in the invoice. Nonpayment constitutes a breach and entitles the requesting party to suspend services or seek legal remedies.

TERM AND TERMINATION

Commencement Date: Termination Date/End Date:

Either party may terminate this Request for Evidence by providing written notice to the other party not less than days prior to the effective date of termination. Termination does not relieve the parties of obligations accrued prior to termination, including payment for services rendered and production of materials requested prior to the date of termination.

CONFIDENTIALITY

All materials produced in response to this Request for Evidence shall be treated as confidential to the extent permitted by applicable law. Such materials shall be used solely for the purposes of the investigation, review or proceeding identified herein and shall not be disclosed to third parties except as required by law or with the prior written consent of the producing party.

Acknowledgement of Confidentiality: I certify that I will treat produced materials as confidential and in accordance with the terms above.

GOVERNING LAW

This Request for Evidence and any dispute arising hereunder shall be governed by and construed in accordance with the laws of the State of without regard to choice of law principles.

ENTIRE AGREEMENT

This Request for Evidence constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous communications, representations, understandings and agreements, whether oral or written, relating to such subject matter. Any amendment or waiver must be in writing and executed by authorized representatives of both parties.

By signing below, the parties acknowledge receipt of this Request for Evidence, confirm that the information provided in this form is true and correct to the best of their knowledge, and agree to comply with the obligations set forth herein.

Requesting Party — Printed Name:

By:

Date:

Respondent — Printed Name:

By:

Date:

What a Request for Evidence Form Is and When it Appears

A Request for Evidence Form (RFE) is a formal notice from an adjudicating agency or organization asking for additional documentation or clarification to support an application, claim, or filing. RFEs appear in many contexts — immigration, insurance claims, licensing, and regulatory reviews — and specify the exact items requested, the reason for the request, and a deadline for submission. The notice typically identifies the issuing office, cites the relevant application or case number, and explains acceptable formats and delivery methods for the requested evidence.

Why a Clear, Complete Request for Evidence Matters

A precise Request for Evidence reduces processing delays, lowers the risk of denial or audit, and creates a clear record of what evidence was sought and when. Clear RFEs limit follow-up questions and help recipients respond accurately and on time.

Who Typically Issues or Responds to an RFE

Organizations and individuals across legal, regulatory, and administrative functions issue and respond to RFEs; the roles differ by industry and case type.

Government adjudicators and case officers who need supporting documentation to complete application reviews.
Applicants, claimants, or their legal representatives who must collect and submit the requested evidence.
Records or compliance teams responsible for verifying, assembling, and certifying documents for submission.

Identifying the right issuer and the proper recipient contact reduces rejections and ensures evidence is routed to the correct review queue.

Common Roles Involved

Immigration Attorney

Counsel reviews the RFE, advises the client on which supporting documents meet agency standards, and prepares a concise response packet that maps each piece of evidence to the RFE items and the controlling statute or regulation.

Claims Adjuster

An adjuster evaluates whether submitted materials satisfy the insurer's factual and policy thresholds, documents chain-of-custody for evidence, and documents any outstanding items required to resolve the claim without litigation.

Security and Compliance Considerations

Data Encryption: TLS 1.2/1.3 in transit, AES-256 at rest

Audit Trail: Timestamped actions and signer metadata

Regulatory Compliance: ESIGN and UETA conformity

Healthcare Privacy: HIPAA support with BAA available

Certification: SOC 2 Type II and ISO 27001

Accessibility: WCAG 2.0 Level AA support

Risks of an Incomplete or Late Response

Application Denial: May result in outright denial

Processing Delay: Adds weeks or months to review

Financial Penalties: Fines or fee forfeiture possible

Loss of Benefits: Eligibility or coverage may terminate

Audit Trigger: May prompt broader compliance reviews

Evidence Rejection: Wrong formats can be deemed unacceptable

Common Preparation Pitfalls to Avoid

Submitting documents without labeling how each item corresponds to specific RFE requests, which forces reviewers to infer relevance and increases rejection risk.
Missing the issuer's deadline or misunderstanding time calculations (mail date versus receipt date) leading to late-filed responses and possible denials.
Providing photocopies or unsigned affidavits when originals, notarized copies, or certified documents were explicitly required in the RFE.
Failing to include required identifiers such as application number, beneficiary name, or case ID on each page of submitted evidence.

Step-by-step: How to Prepare an Effective Response

Follow a structured sequence to gather, verify, and deliver requested evidence so the response is complete, traceable, and timely.

01

Review Notice: Read the RFE carefully and list each requested item.
02

Map Evidence: Match documents to RFE line items and annotate sources.
03

Verify Originals: Obtain notarizations or certified copies if required.
04

Assemble Packet: Order items, include index, and attach cover letter.

Where and How to Submit Your Response

Routes differ by issuer; use the RFE's instructions to choose the correct mailing address, online upload portal, or email address for evidence submission.

Physical Mail: Send to the address on the RFE; use tracked delivery.
Online Portal: Upload via the issuer's secure case portal when available.
Email Submission: Only if the RFE explicitly permits email delivery.
In-Person Dropoff: Deliver to the office specified on the notice.

Essential Elements of a Professional Request for Evidence Response

A well-constructed response packet organizes materials so reviewers can easily verify compliance with each requested item and the regulatory standard cited in the RFE.

Cover Letter

A concise letter stating the case number, issuer, and a numbered index that maps each submitted document directly to the RFE items and the statutory or regulatory reference.

Case Identifiers

Prominently include application ID, petition number, beneficiary name, and page headers on every document so reviewers can associate pages with the correct record.

Requested Evidence

Produce the exact documents requested — originals, certified copies, or notarized affidavits — and avoid submitting extraneous or irrelevant materials that obscure key evidence.

Document Index

A numbered table of contents showing document title, page range, and which RFE item it addresses, enabling rapid verification during review.

Declaration or Cover Affidavit

Signed statement from the preparer or witness explaining document provenance, translations, and the chain of custody if required by the issuer.

Delivery Proof

Include tracked shipment receipts, portal upload confirmation, or signed delivery acknowledgements to document the submission date and method.

Configuring a Digital Workflow for RFE Responses

Set up a repeatable digital workflow to collect, verify, and deliver evidence while preserving an audit trail and access controls.

Field	Configuration
Signer Authentication	Email OTP or SMS code verification
Attachment Handling	Allow PDF, DOCX uploads; set max size
Conditional Fields	Show fields only when relevant answers selected
Retention Policy	Auto-archive signed packets for compliance

Digital Submission: Platform Capabilities to Look For

Choose a platform that preserves evidentiary integrity, creates a robust audit trail, and supports required document formats.

File Formats: PDF and DOCX support
Integrations: Connectors for Google Drive and NetSuite
Authentication: SMS, email, or advanced KBA

Ensure the solution meets legal and privacy requirements for your industry and retains records in compliance with applicable statutes and internal policy.

Typical Timing Expectations and Deadlines

Respond precisely by the deadline stated on the RFE and follow delivery instructions; timelines and consequences vary by issuing agency and case type.

Agency Deadline:

Use the exact date on the RFE as your response cutoff.

Delivery Proof Deadline:

Document the submission date with tracking or portal receipts.

Late Submission Risk:

Late responses can be rejected or considered untimely.

Request Extensions:

Only seek extensions if the issuer provides an option.

Internal SLA:

Set an internal 7–14 day buffer before the official deadline.

eSignature Vendor Comparison for Submitting Evidence Packets

Comparing practical cost and compliance features can help organizations pick a solution that supports secure evidence collection and preserves audit trails.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Practical Response Examples

Two concise scenarios illustrate how an organized packet simplifies review and reduces back-and-forth with the issuing office.

Immigration Case Response

A petitioner receives an RFE requesting birth certificates and translations

Documents were certified and translated
The response included a numbered index mapping each certificate and translation to the RFE items, plus tracked delivery confirmation and a signed cover affidavit explaining chain of custody.

Insurance Claim Supplement

An insurer asks for proof of repair invoices and photos

Claimant collected itemized invoices
The response packet contained an evidence index, notarized repair affidavits, high-resolution photos labeled by date, and portal upload receipts showing time-stamped submission.

Frequently Asked Questions and Troubleshooting

Answers to common questions help avoid avoidable errors and clarify acceptable formats, authentication, and timing considerations for RFE responses.

Need help? Contact support

What if I miss the deadline?
Timely submission is typically required. Missing the deadline can result in denial or dismissal. Contact the issuing office immediately to request an extension only if the RFE permits it; retain proof of all communications.
Can electronic signatures be used?
Electronic signatures are legally valid under ESIGN and UETA when intent, consent, attribution, and retention requirements are met. If the issuer requires notarization or a wet signature, follow that instruction instead.
Are scanned copies acceptable?
Scanned copies are commonly accepted unless the RFE explicitly requires originals, certified copies, or notarized documents. Verify the format requirements listed in the RFE before submitting scanned materials.
How should I label submitted files?
Use clear filenames that include the case number and RFE item number. Include a numbered table of contents inside the packet so reviewers can match each file to the requested item.
What proof of delivery is sufficient?
Keep tracked shipment receipts, portal upload confirmations, or stamped delivery acknowledgements. These records demonstrate submission date and method and can be critical if timeliness is questioned.
Who can sign an affidavit?
Anyone with direct knowledge may sign, but affidavits often require notarization and a statement of identity and relation to the facts. Follow the issuer's instructions about witness or notarization requirements.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now