Establishing secure connection…Loading editor…Preparing document…

Project Submittal Form

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

PROJECT SUBMITTAL FORM

Parties

Recitals

WHEREAS Submitter is engaged in the business of providing professional services, materials and deliverables related to projects described herein and possesses the experience and personnel necessary to perform the obligations set forth in this form; and

WHEREAS Recipient requires the services and deliverables described below and desires to receive the project submittal for evaluation, approval and potential engagement under terms set forth in this document; and

WHEREAS the parties intend that this Project Submittal Form set forth the scope, payment terms, schedule and other material terms for the proposed project and shall constitute the foundation for any subsequent agreement to proceed;

Project Details

Submission Date:

Scope of Work

Provide a concise but complete description of the work, deliverables, performance standards and any milestones. This scope shall govern the work to be performed unless modified in a written change order signed by both parties.

Payment Terms

The following payment provisions apply to the proposed project submittal. Invoices will reference the project number and supporting documentation for amounts billed.

Invoices not disputed in good faith within ten (10) calendar days of receipt shall be deemed accepted. Disputed amounts shall be documented in writing with supporting evidence and will not relieve the obligation to timely pay undisputed amounts.

Term and Termination

This submittal is effective as of the Start Date below and shall remain in effect until the End Date below unless earlier terminated in accordance with this section.

Start Date:

End Date:

Either party may terminate for cause if the other party fails to cure a material breach within the notice period above. Upon termination, Recipient shall pay Submitter for work performed and documented through the effective date of termination, subject to any applicable offsets for unperformed work or defective deliverables.

Confidentiality

All information identified as confidential by one party and disclosed to the other in connection with this submittal shall be treated as confidential. Recipient and Submitter shall use such information only for evaluation and performance of the project and shall not disclose it to third parties except as required by law or with prior written consent.

By checking this box, the signing party acknowledges and agrees to be bound by the confidentiality obligations stated above.

Governing Law

This Project Submittal Form and any agreement arising from it shall be governed by and construed in accordance with the laws of the jurisdiction specified below, without regard to conflict of law principles.

Entire Agreement

This Project Submittal Form, together with any attachments, exhibits, and any subsequently executed written change orders, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and communications, whether written or oral. Any modifications must be in writing and signed by both parties.

Representations and Certifications

Each party represents that it has the authority to enter into this Project Submittal Form and that the individual signing below is authorized to bind that party. Submitter certifies that all information in this submittal is true, complete and accurate to the best of its knowledge.

Certification: By checking this box, the signing party certifies the accuracy of the information provided and acknowledges that false statements may give rise to remedies available at law or in equity.

Submitter:

By:

Date:

Recipient:

By:

Date:

Enter text✕

What the Project Submittal Form Is and when it’s used

A Project Submittal Form is a standardized document used to propose, describe, and request approval for discrete work items, materials, or deliverables within a project. Typical uses include construction material approvals, design deliverables, vendor proposals, and procurement requests. The form collects project identifiers, scope descriptions, schedule milestones, cost estimates, attachments (spec sheets, drawings), and designated approvers. In the United States, electronic versions of this form are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided the signature and record-retention requirements are met.

Why a clear Project Submittal Form matters

A properly completed Project Submittal Form centralizes required information, reduces back-and-forth questions, and creates an auditable trail for approvals and change control. It clarifies expectations for scope, timing, and cost while preserving a reproducible record for compliance and future reference.

Why a clear Project Submittal Form matters

Who typically completes and reviews this form

Project managers, contractors, architects, engineers, procurement staff, and vendor representatives commonly fill out or review submittal forms depending on the project stage and organizational role.

  • Project Managers: Prepare submittals, track approval status, and coordinate revisions across stakeholders.
  • Contractors / Subcontractors: Provide product data, shop drawings, and schedule impacts tied to procurement.
  • Design Professionals: Review technical compliance, approve materials, and attach specification references.

Use role-based routing so each stakeholder receives only the fields and attachments they must review or sign, improving turnaround and reducing review errors.

Essential sections to include on a professional submittal

A complete Project Submittal Form balances identification, technical detail, schedule, cost, attachments, and clear approval fields so reviewers can act without follow-up.

Project ID

Unique identifier and project name for cross-referencing drawings, contracts, and change orders; include client and internal job numbers.

Scope Summary

Concise description of the item or work being submitted, including quantity, performance criteria, and any deviations from contract requirements.

Attachments

List and attach spec sheets, cut sheets, shop drawings, calculations, and photos required for technical review and recordkeeping.

Schedule

Proposed delivery, installation, or milestone dates and any impact on critical-path activities or phased approvals.

Cost Details

Estimated cost, unit pricing, change-order implications, and whether the line is billable or budget-impacting.

Approvals

Role-based signature and date fields for reviewer disposition (approve, approve with comments, reject) and space for reviewer notes.

Security and compliance checkpoints

Encryption: TLS 1.2/1.3 in transit
Data at rest: AES-256 encrypted storage
Audit trail: Timestamped signing events
Access controls: Role-based permissions
Regulatory coverage: ESIGN and UETA compliance
HIPAA option: BAA available when required

Step-by-step: filling and submitting the form

Follow a consistent sequence to prepare a submittal, attach evidence, and route for approval so reviewers can make decisions quickly.

  • 01
    Prepare the data: Collect spec sheets, drawings, and cost backup before you start.
  • 02
    Complete required fields: Enter identifiers, scope, dates, and cost using formats above.
  • 03
    Attach supporting docs: Upload PDFs, images, and spreadsheets referenced in the scope.
  • 04
    Route and monitor: Send to approvers and track status until final disposition.

How e-submittal workflows typically operate

Electronic workflows streamline submittal routing, reviewer authentication, and archival while keeping a tamper-evident audit trail.

  • Upload document: Sender uploads the form and attachments to the platform.
  • Place fields: Add signatures, initials, dates, and conditional inputs as needed.
  • Send to reviewers: Route by role or send a signing link to recipients.
  • Complete & archive: Collect signatures, capture audit trail, and store final copy.

Typical digital workflow settings for submittals

Configure field validation, routing order, and notifications to match your review process and reduce manual follow-up.

Field Configuration
Required fields Mark IDs, dates, and signature blocks as mandatory
Validation Use date and numeric formats; enforce MM/DD/YYYY
Routing Set sequential or parallel reviewers per role
Notifications Email and SMS reminders for pending approvals

Digital delivery and platform considerations

When moving submittals online, confirm file formats, integrations, and authentication levels to match internal controls and external reviewer needs.

  • Integrations: CRM, ERP, and cloud storage connections
  • File formats: PDF, DOCX, and Excel supported
  • Authentication: Email, SMS, or stronger MFA options

Pick a platform that supports your required authentication strength, preserves an audit trail, and integrates with systems like Salesforce, NetSuite, Microsoft 365, or Procore to avoid duplicate data entry and keep project records synchronized.

Typical timelines and expected processing windows

Set clear deadlines on the form to manage expectations. Typical review and processing timeframes vary by complexity and organization.

Submission lead time:

Submit at least 7 business days before scheduled work

Initial review period:

Allow 3–5 business days for technical review

Approval turnaround:

Final approval commonly within 5–10 business days

Revision window:

Request clarifications within 5 business days of review

Project start date:

Schedule start only after written approval

Common mistakes that delay approvals

  • Incomplete attachments: Omitting required spec sheets or drawings forces reviewers to request more information and restarts the review clock.
  • Incorrect identifiers: Using inconsistent project numbers or names causes misfiling and can decouple approvals from contracts or purchase orders.
  • Vague scope descriptions: Non-specific language about performance or dimensions results in conditional approvals or outright rejections.
  • Unauthorized signers: Signatures from individuals without delegated authority may be rejected and require re-execution under the correct signatory.

Risks and consequences of incorrect submittals

Delayed approval: Work stoppage risk
Cost overrun: Changed scope increases spend
Contract breach: Noncompliance with specs
Regulatory exposure: Potential permit violations
Tax or billing errors: Incorrect invoicing implications
Invalid signature: May require re-execution

eSignature pricing and feature snapshot for submittal workflows

Compare per-user pricing, trial availability, bulk-send capability, audit trail presence, HIPAA readiness, and envelope limits to match volume and compliance needs.

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) Varies by vendor Varies by vendor Varies by vendor Varies by vendor
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

Frequently asked questions about Project Submittal Forms

Answers to common questions on signing, attachments, processing times, and corrections when working with project submittals.


Need help? Contact support

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