Establishing secure connection…Loading editor…Preparing document…

Pre-Application Meeting Request

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

PRE-APPLICATION MEETING REQUEST AND CONSULTING AGREEMENT

Applicant Name:   Primary Contact:

Applicant Address:

Agency Name:   Agency Contact:

Date Submitted:

WHEREAS

WHEREAS, Applicant seeks an initial pre-application consultation regarding the proposed project identified as Project Name: located at Site Address: for the purpose of obtaining preliminary guidance on land use, permits and procedural requirements.

WHEREAS, Agency agrees to schedule and conduct a pre-application meeting to review the materials submitted by Applicant and provide preliminary comments, identification of applicable regulations, and guidance as set forth in this Agreement.

WHEREAS, the parties desire to set forth the scope, payment terms, confidentiality and other administrative provisions governing the pre-application meeting and related preparatory services.

Scope of Work

Description of Services to be Provided (scope must include specific items Applicant requests review of; e.g., site plan, traffic, utilities, zoning interpretation):

Meeting Request Details

Site Plan    Technical Reports (traffic, geotech)    Architectural Sketches    Photographs / Aerials

In-person    Virtual meeting    Telephone conference

  Preferred Time:

  Preferred Time:

  Preferred Time:

Payment Terms

Meeting Fee Amount:

Late Payment Fee: . Applicant agrees to pay reasonable costs of collection, including attorney fees, for overdue amounts.

Term and Termination

Effective Date:   Termination Date:

Either party may terminate this Agreement for convenience upon written notice to the other party delivered no fewer than days prior to the effective termination date. Termination shall not relieve Applicant of obligations to pay for services performed and costs incurred through the effective date of termination.

Confidentiality

Confidential Information means non-public information disclosed by one party to the other related to the Project and identified at the time of disclosure as confidential. The receiving party shall hold all Confidential Information in strict confidence and shall not disclose such information to third parties except to its employees, consultants or contractors who have a need to know and are bound by confidentiality obligations at least as protective as those contained herein. Confidential Information does not include information that is (i) publicly available through no fault of the receiving party, (ii) rightfully received from a third party without obligation of confidentiality, or (iii) independently developed by the receiving party without use of the disclosing party’s Confidential Information.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state indicated below, without regard to conflict of laws principles. Governing State:

Entire Agreement

This Agreement, together with any attachments, exhibits and the submitted meeting materials expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations and understandings, whether oral or written. Any amendment or modification of this Agreement must be in writing and signed by both parties.

Acknowledgment

By submitting this Pre-Application Meeting Request, Applicant certifies that the information provided is true and accurate to the best of Applicant’s knowledge and agrees to abide by the payment and meeting procedures set forth herein. Applicant acknowledges that any comments provided by Agency at a pre-application meeting are advisory only and do not constitute a final determination of permits or approvals.

Applicant:

By:

Date:

Agency Representative:

By:

Date:

Enter text✕

What the Pre-Application Meeting Request Is and When it’s Used

A Pre-Application Meeting Request is a formal written request submitted to a permitting or planning authority to schedule a preliminary meeting prior to filing a full application. The request explains the proposed project, identifies key contacts, and asks for guidance on submission requirements, applicable codes, and expected review timelines. Agencies use this meeting to flag major issues, clarify submittal checklists, and advise on studies or permits that will be required. Preparing a clear request reduces back-and-forth, uncovers jurisdictional requirements early, and helps applicants scope work, costs, and timelines before committing to full application fees and studies.

Why a Clear Request Matters for Project Planning

Submitting a concise Pre-Application Meeting Request helps secure targeted agency feedback, narrows the scope of required studies, and can reduce unexpected delays during formal review. Early engagement often identifies applicable regulations, permit routes, and potential design constraints so teams can budget and schedule more accurately.

Why a Clear Request Matters for Project Planning

Who Typically Submits a Pre-Application Meeting Request

Developers, property owners, architects, civil engineers, land-use consultants, and municipal planning staff commonly participate in pre-application meetings.

  • Developers and owners: Clarify feasibility, permitting sequence, and expected conditions of approval before investing in studies or construction documents.
  • Design professionals: Seek code interpretations, identify required technical studies, and confirm submission format and plan sheet expectations.
  • Public agency staff: Use the request to triage proposals, assign internal reviewers, and prepare preliminary comments for the meeting.

Clear identification of the submitting party and their authority to speak for the project speeds scheduling and ensures the right reviewers attend.

Core Sections to Include in a Professional Request

A well-structured Pre-Application Meeting Request contains six core components that help reviewers assess the proposal quickly and prepare useful feedback for the meeting.

Project Summary

Brief description of the proposal, proposed uses, size, and key metrics so reviewers can understand scale and potential impacts.

Site Location

Parcel ID, address, assessor’s parcel number, and map coordinates to ensure staff pull accurate site records and zoning information.

Proposed Scope

Detailed list of proposed improvements (units, square footage, access points) and any anticipated grading, tree removal, or land disturbance.

Requested Input

Specific questions for reviewers (e.g., parking requirements, stormwater triggers, affordable housing obligations) to frame the meeting agenda.

Attachments

Preliminary site plan, vicinity map, concept elevations, and technical memos that help staff evaluate the application at a glance.

Contact and Availability

Primary contact name, role, phone, email, and requested meeting windows to expedite scheduling with the agency.

Essential Data Fields to Provide

Applicant Name: Full legal name of the person or entity submitting the request.
Authorized Contact: Name, title, phone and email for scheduling and follow-up.
Project Address: Street address, city, state, ZIP and parcel or assessor number.
Project Description: Short summary of intended use and scope.
Requested Meeting Type: Initial review, neighborhood meeting, technical review, or completeness check.
Preferred Dates: Two to three available date ranges and preferred duration.

Step-by-Step: Submitting a Request

Follow these sequential steps to prepare and submit a complete Pre-Application Meeting Request to a municipal or agency intake point.

  • 01
    Prepare Summary: Draft a concise project description and list key questions.
  • 02
    Gather Attachments: Assemble site plan, vicinity map, and preliminary exhibits.
  • 03
    Complete Form: Enter all required fields and preferred meeting windows.
  • 04
    Submit to Agency: Send via the agency’s intake portal, email, or eSubmission method noted by staff.

Where the Request Goes and What Happens Next

Understand the routing so you know who reviews the request and what to expect before the meeting.

  • Intake and Triage: Staff confirm receipt and assign to the planning reviewer or department.
  • Reviewer Assignment: Technical reviewers (planning, engineering, stormwater) are scheduled to attend.
  • Pre-Meeting Review: Reviewers examine attachments and prepare preliminary comments.
  • Scheduled Meeting: Agency and applicant meet to discuss issues, next steps, and submittal checklist.

How to Configure an Online Submission Workflow

Set up fields and routing in an eSubmission system to ensure consistent intake and automated notification.

Field Configuration
Applicant Name Required; single-line text
Parcel / APN Required; numeric or alphanumeric
Attachments PDF upload; max file size per agency
Meeting Preference Dropdown: Concept / Technical / Neighborhood

Digital Submission and eSignature Requirements

Confirm the agency’s accepted formats and required authentication for e-submissions and signed forms.

  • File Formats: Accept PDF and DOCX; PDF/A preferred for long-term retention.
  • Authentication: Email plus SMS code or agency portal account for identity verification.
  • Integration: Platforms often integrate with Google Drive, Box, or permitting systems.

Using the correct formats and an accepted eSignature provider prevents intake rejection and keeps the review on schedule.

Typical Timelines and Agency Processing Expectations

Processing timeframes vary by jurisdiction and project complexity. Use these common benchmarks to set internal schedules and expectations.

Acknowledgement:

1–5 business days for intake confirmation.

Reviewer Assignment:

5–14 business days to assign reviewers for standard projects.

Pre-Meeting Comments:

1–3 weeks for written preliminary comments from staff.

Scheduling Window:

Meetings scheduled within 2–6 weeks depending on staff availability.

Follow-up Actions:

Expect written meeting notes within 5–10 business days after the meeting.

Key Milestones from Request to Formal Application

Track these numbered milestones to manage coordination between design team and agency reviewers.

01

Submit Request

Applicant files the request with required attachments.

02

Agency Intake

Staff confirm form completeness and assign reviewers.

03

Pre-Application Meeting

Stakeholders meet to discuss issues and next steps.

04

Formal Application Preparation

Applicant revises plans based on meeting feedback before official submittal.

Common Mistakes That Slow or Prevent Scheduling

  • Incomplete contact details or no authorized representative listed, which delays scheduling and reviewer assignment.
  • Missing or unlabeled attachments (site plan, legal description) that prevent staff from assessing applicable codes.
  • Vague project descriptions that do not state use, size, or anticipated impacts, producing non-actionable comments.
  • Ignoring agency-specified submission format or eSignature requirements, leading to intake rejection or resubmission.

Risks of an Inadequate or Incorrect Request

Scheduling Delays: Loss of preferred meeting dates
Incomplete Feedback: Missed issues requiring costly redesign later
Application Rejection: Formal submittal may be rejected for missing items
Increased Costs: Additional studies or rework required
Regulatory Risk: Noncompliance triggers permit conditions
Public Opposition: Poorly scoped meetings can provoke neighborhood concerns

Illustrative Use Cases from Practice

Real-world examples show how pre-application meetings clarified requirements and avoided rework.

Local Mixed-Use Redevelopment

Developer sought zoning flexibility and parking relief

  • City staff identified stormwater triggers
  • Result: applicant added stormwater study early and avoided a second design review round, saving months and reducing consultant costs.

Small Medical Clinic Expansion

Clinic requested utility and access guidance

  • Reviewers flagged ADA routing and patient flow requirements
  • Result: design team adjusted entry location before final drawings, preventing costly change orders during construction.

Practical Tips for a Faster, More Useful Meeting

Adopt these practices to improve the quality of agency feedback and reduce the risk of miscommunication.

Be Concise and Specific
Frame two to four targeted questions for reviewers rather than broad requests; specific queries yield actionable answers and focused staff preparation.
Label Attachments Clearly
Use consistent file names and include a one-page cover memo summarizing key metrics so reviewers can quickly locate critical information.
Confirm Reviewers Needed
Ask the agency which disciplines will attend (e.g., planning, engineering, fire) so technical leads can be present and all issues are addressed.
Follow Up in Writing
After the meeting, send a concise summary of agreed next steps and any timelines to create a clear administrative record.

eSignature Pricing Context for Delivering and Signing Requests

Common eSignature providers offer different pricing and features. signNow is listed first for comparison; choose a plan that supports your document volume and required features.

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, no card No No Yes, limited Yes, limited
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions and Troubleshooting

Answers to common questions about preparing, submitting, and following up on Pre-Application Meeting Requests.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users