Can a Pre-Application be electronically signed?

Yes. Electronic signatures are legally enforceable in interstate commerce under the ESIGN Act (15 U.S.C. ch. 96) and in most states under UETA (1999). Ensure the signing process captures intent, consent, attribution, and retention to meet the four-part ESIGN test.

When is notarization required?

Notarization depends on program rules and state law. If a jurisdiction or program requires notarized signatures, follow that requirement; remote online notarization is available in most states subject to state-specific rules.

What supporting documents should be attached?

Attach the items listed on the form’s checklist such as government ID, proof of address, financial statements, or project plans. Missing attachments commonly lead to completeness rejections.

How do I correct a submitted pre-application?

If edits are allowed, the platform may permit revisions before review; otherwise, submit an amendment or contact the intake reviewer. Retain both versions for audit purposes and document the reason for the change.

How long will my pre-application be retained?

Retention varies by program and content. Follow federal minimums where applicable (e.g., IRS three years, HIPAA six years) and extend retention per program rules or legal holds.

Is signNow suitable for handling PHI in Pre-Applications?

signNow supports HIPAA compliance and will execute a Business Associate Agreement when required. Ensure workflows and access controls are configured to limit PHI exposure and follow 45 CFR §164.530(j) retention rules.

Pre-Application Form

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

Pre-Application Form and Pre-Engagement Agreement

Whereas

WHEREAS, Applicant seeks preliminary consideration of the proposed business project described in this Pre-Application Form for potential services by the Company; and

WHEREAS, Company has the capacity to review, advise, and potentially provide professional services related to the proposed project subject to the terms and conditions set forth below; and

WHEREAS, the parties desire to record certain preliminary project information and agree certain terms governing evaluation, confidentiality, and potential engagement prior to execution of any definitive engagement agreement.

Applicant Information

Applicant Name Contact Person Email Phone Mailing Address Entity Type (check all that apply)

Individual Corporation LLC Partnership Other

Business Information

Business Name Tax ID / EIN Years In Operation

Project Details / Scope of Work

Project Title Scope of Work

Proposed Start Date: Proposed Completion Date:

Estimated Budget

Payment Terms (Preliminary)

Total Estimated Fee:

Proposed Payment Schedule

Late payment charge: on all overdue balances until paid in full.

Term and Termination

Agreement Term: This pre-engagement evaluation shall commence on and shall terminate on unless earlier terminated in accordance with this section.

Either party may terminate this pre-engagement evaluation upon written notice to the other party delivered not less than days prior to the intended termination date. Termination shall not affect payment obligations incurred prior to the effective date of termination.

Confidentiality

The parties acknowledge that during preliminary discussions and evaluation each may disclose Confidential Information. "Confidential Information" means non-public business, technical, financial, or proprietary information disclosed in any form. Each receiving party shall: (a) hold Confidential Information in strict confidence; (b) use Confidential Information solely to evaluate or perform the proposed engagement; and (c) restrict disclosure to employees, agents, or advisors who have a need to know and are bound by confidentiality obligations no less protective than those herein. Confidential Information shall not include information which is or becomes publicly known through no breach by the receiving party or which is rightfully received from a third party free of restriction.

Governing Law and Dispute Resolution

This Pre-Application Form and any dispute arising out of or related to it shall be governed by the laws of the state of without regard to conflict of law principles. The parties agree to attempt to resolve disputes through good faith negotiation prior to initiating litigation.

Entire Agreement

This document, together with any attachments explicitly incorporated by reference, constitutes the entire understanding between the parties with respect to the subject matter herein and supersedes all prior written or oral agreements or understandings relating to the same. Any amendment must be in writing and signed by authorized representatives of both parties.

Certifications and Authorizations

By signing below, Applicant certifies that the information provided in this Pre-Application Form is true, complete and accurate to the best of Applicant's knowledge, and authorizes Company to perform reasonable due diligence, including verification of business and credit information as necessary for evaluation. Applicant further acknowledges that completion of this Pre-Application Form does not obligate Company to enter into any further agreement unless and until a definitive engagement agreement is executed.

I certify the information provided is true and correct. I authorize reasonable due diligence and background checks. I have read and accept the terms contained in this Pre-Application Form and Pre-Engagement Agreement.

Applicant:

By:

Date:

Company:

By:

Date:

What a Pre-Application Form Is and when it’s used

A Pre-Application Form is a preliminary application used to collect structured information before a full application, permit, loan, or grant submission. It standardizes basic applicant data, project or service descriptions, and required attachments so reviewers can screen eligibility and completeness before inviting a full filing. Pre-Application Forms reduce intake friction, ensure consistent records, and create an audit trail that supports later review, verification, or underwriting decisions across public- and private-sector workflows.

Why use a Pre-Application Form and its legal standing

Pre-Application Forms speed initial eligibility checks, lower full-application errors, and preserve a timestamped record of intent. Electronically collected pre-applications are legally recognized in the United States under the ESIGN Act (15 U.S.C. ch. 96) and UETA (1999) when they meet intent, consent, attribution, and retention requirements.

Organizations and roles that commonly complete Pre-Application Forms

Designing the form with these user groups in mind reduces back-and-forth, speeds screening, and improves data consistency.

Real estate brokers and property managers conducting tenant screening and rental pre-qualification.
Lenders and loan officers collecting borrower basics before full underwriting begins.
Grant administrators and permitting agencies gathering eligibility details before inviting full proposals.

Typical signers and submitters

Applicant — Primary

The individual or entity requesting pre-qualification who must provide identity, contact, and project details. The applicant is responsible for attesting accuracy and providing supporting documents; mismatches with official IDs can trigger verification steps or rejection.

Reviewer — Intake

A loan officer, grant manager, or intake clerk who checks completeness and eligibility. Reviewers flag missing items, request full applications, or route to underwriting; their notes and timestamps form part of the record retained for compliance.

Essential parts of a professional Pre-Application Form

A well-structured Pre-Application Form groups identity, project, and compliance elements so reviewers can quickly assess eligibility and route next steps.

Applicant Details

Full legal name, entity type, TIN or SSN where required, and primary contact details to match identity verification records and backup-withholding rules.

Project Summary

Short description of the proposed activity, requested amount or permit type, location, and anticipated start date to determine jurisdictional applicability and prioritization.

Supporting Attachments

Checklists for required documents (ID, financials, site plans). Clearly mark allowed file types and maximum sizes to prevent upload failures.

Declarations & Consents

Statements attesting to truthfulness, data-sharing permissions, and consent to electronic records where required by consumer-facing statutes.

Signature Block

Fields to capture signer name, signature, and date; indicate whether e-signature, in-person signature, or notarization is required.

Routing Metadata

Internal fields for reviewer assignment, priority, and status that drive automated notifications and next-step workflows.

Step-by-step: completing and submitting a Pre-Application Form

Follow this sequence to prepare, validate, and submit a Pre-Application Form so it moves quickly through intake and review.

01

Gather Documents: Collect IDs, financials, and attachments required by the checklist.
02

Complete Form: Enter fields precisely and upload supporting documents in allowed formats.
03

Review for Accuracy: Double-check names, dates, and dollar amounts before signing.
04

Submit and Receive Acknowledgement: Submit electronically and retain the confirmation or timestamp for your records.

Typical online workflow settings for Pre-Application intake

These configuration items support consistent routing, authentication, and document handling in a digital intake system.

Field	Configuration
Notifications	Email and optional SMS alerts
Authentication	Email link by default; SMS code optional
Conditional Fields	Enable to show additional questions by answer
Attachments	Require PDF or JPG; max file size enforced

Digital distribution and technical compatibility

Ensure the intake platform you select can export signed records and audit trails to your archive or case management system.

Supported Formats: PDF | DOCX | HTML | XLSX
Integrations: Salesforce, Microsoft 365, NetSuite, Google Workspace
Authentication Options: Email link, SMS code, KBA, or SSO

How a Pre-Application moves from intake to decision

A repeatable routing pattern accelerates review: capture, authenticate, route, and retain a signed record with audit data.

Capture: Applicant completes form and uploads required files.
Authenticate: Platform confirms identity via email, SMS, or stronger methods.
Route: System forwards to intake reviewer or assignment queue.
Record: Signed copy and audit trail are stored for compliance.

Common timelines and expected processing windows

Timelines vary by program and jurisdiction; use these typical windows as planning benchmarks and check program-specific deadlines.

Application Window:

Open and close dates set by program; check each solicitation.

Acknowledgement:

Immediate automated receipt upon successful submission.

Initial Review:

Usually completed within 7–30 business days depending on volume.

Invitation to Full Application:

Issued only to applicants meeting screening criteria.

Appeal or Clarification:

Time-limited windows for responding to reviewer requests.

Key procedural milestones during pre-application processing

Track these sequential stages from receipt through final determination; each stage has distinct responsibilities and expected timing.

01

Submission Received

System logs timestamp and issues confirmation to the applicant.

02

Completeness Check

Reviewer verifies required fields and attachments; incomplete submissions flagged.

03

Eligibility Screening

Program-specific criteria applied to determine advancement.

04

Decision / Invite

Eligible applicants receive invitation for full application or next steps.

Common mistakes that delay pre-application processing

Using a nickname or business DBA instead of the legal entity name causes verification delays and identity mismatches.
Uploading unreadable scans or wrong file types trips manual processing and prolongs intake time substantially.
Leaving conditional fields blank when they are required by earlier answers leads to automatic rejection for incompleteness.
Failing to consent to electronic records when required for consumer-facing programs forces manual paper handling and processing delays.

Consequences of incorrect or incomplete Pre-Application Forms

Rejection: Application may be rejected

Delays: Processing timeline extended

Financial Risk: Loss of priority or funding

Legal Exposure: Potential false-statement liabilities

Data Breach: Privacy fines if PHI exposed

Audit Findings: Recordkeeping violations cited

Security and compliance controls to protect Pre-Application data

Encryption: TLS 1.2/1.3; AES-256 at rest

Audit Trail: Signed PDF with timestamp and IP log

HIPAA Support: BAA available for covered entities

Authentication: Email link, SMS code, or stronger

Standards: SOC 2 Type II; ISO 27001

Retention Controls: Configurable retention and export

eSignature vendor comparison for handling Pre-Application Forms

A concise price and capability snapshot for common eSignature vendors. signNow is listed first per comparison formatting rules.

	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
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Real-world Pre-Application examples

These condensed examples show how organizations use pre-application intake to improve throughput and recordkeeping.

Optica Ventures

Optica used a short pre-application to screen tenants quickly

Reduced full-application volume by 40%
The result was fewer incomplete submissions and faster decision cycles, improving occupancy timelines and applicant communication.

Xerox NetSuite Operations

Xerox integrated intake with ERP for consistent data capture

Automated routing to the correct reviewer
This reduced manual entry errors and improved traceability between intake and contract execution.

Practical tips for accurate, efficient pre-application intake

Adopt these practices to minimize errors, speed review, and maintain compliance when collecting pre-application data.

Standardize Field Labels

Use consistent labels and required-field indicators so applicants know what to provide and reviewers can automate validation rules.

Use Conditional Logic

Show only relevant questions to reduce applicant burden and reduce incomplete or irrelevant responses.

Require Validation

Validate TINs, ZIP codes, and date formats client-side to prevent common transcription errors.

Keep an Audit Trail

Store signed PDFs, timestamps, and activity logs to support later verification or audit requests.

Frequently asked questions about Pre-Application Forms

Answers to common questions about electronic collection, signatures, notarization, correction, and compliance.

Need help? Contact support

Can a Pre-Application be electronically signed?
Yes. Electronic signatures are legally enforceable in interstate commerce under the ESIGN Act (15 U.S.C. ch. 96) and in most states under UETA (1999). Ensure the signing process captures intent, consent, attribution, and retention to meet the four-part ESIGN test.
When is notarization required?
Notarization depends on program rules and state law. If a jurisdiction or program requires notarized signatures, follow that requirement; remote online notarization is available in most states subject to state-specific rules.
What supporting documents should be attached?
Attach the items listed on the form’s checklist such as government ID, proof of address, financial statements, or project plans. Missing attachments commonly lead to completeness rejections.
How do I correct a submitted pre-application?
If edits are allowed, the platform may permit revisions before review; otherwise, submit an amendment or contact the intake reviewer. Retain both versions for audit purposes and document the reason for the change.
How long will my pre-application be retained?
Retention varies by program and content. Follow federal minimums where applicable (e.g., IRS three years, HIPAA six years) and extend retention per program rules or legal holds.
Is signNow suitable for handling PHI in Pre-Applications?
signNow supports HIPAA compliance and will execute a Business Associate Agreement when required. Ensure workflows and access controls are configured to limit PHI exposure and follow 45 CFR §164.530(j) retention rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now