Can the document be signed electronically?

Yes. Electronic signatures are legally valid in interstate and intrastate commerce under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met.

When is notarization required?

Notarization is required for recordable instruments and in jurisdictions for deeds and some easements; check local rules—certain states also require witnesses for deeds or POAs.

What authentication level should be used?

Match authentication strength to risk: email-only for low-risk approvals, SMS or KBA for higher assurance, and RON when notarization must occur remotely under state RON rules.

Are eSigned PDFs admissible in court?

Yes. Electronic records and signatures are admissible under ESIGN/UETA when the signature is attributable and the record can be reproduced, subject to specific evidentiary rules.

How to handle a missing attachment after signing?

If a required attachment was omitted, issue an amendment or supplement signed by authorized parties and attach the missing document with clear reference to the original execution.

Does electronic signing meet HIPAA or tax requirements?

Electronic execution can meet HIPAA and tax rules if the platform supports required controls; for HIPAA a BAA may be required and tax record retention follows IRC and IRS guidance.

Project Storm Works

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

PROJECT STORM WORKS - GENERAL BUSINESS AGREEMENT

This General Business Agreement ("Agreement") is entered into by and between:

Party A (Client) — Legal Entity / Individual Client Address Party B (Contractor) — Legal Entity / Individual Contractor Address

Effective Date: . The parties agree as follows.

WHEREAS

WHEREAS, Client has initiated a business project known as "Project Storm Works" involving design, implementation, and management of specified deliverables and services to mitigate storm-related impacts and improve operational resilience; and

WHEREAS, Contractor represents that it possesses the expertise, personnel, equipment, and licenses required to perform the services set forth in this Agreement and desires to provide such services to Client under the terms and conditions set forth herein; and

WHEREAS, the parties desire to set forth their respective rights and obligations with respect to the scope, schedule, compensation, confidences, and termination of the services to be provided in connection with Project Storm Works.

1. SCOPE OF WORK

Contractor shall perform the services and deliver the deliverables described below in accordance with the specifications, schedule, and acceptance criteria stated herein. The scope shall include design, procurement oversight, installation supervision, testing, and close-out documentation for Project Storm Works.

Detailed Scope of Work and Deliverables

2. PAYMENT TERMS

Client shall pay Contractor for full and timely performance under this Agreement in accordance with the fees and schedule below. All payments shall be made in United States dollars unless otherwise agreed in writing.

Total Contract Amount Payment Schedule / Milestones

Late Payment: Amounts not paid within days of invoice due date shall accrue interest at a rate of (or the maximum rate permitted by law). Client shall also be responsible for reasonable collection costs and any taxes assessed on payments.

3. TERM AND TERMINATION

Term: This Agreement commences on Start Date: and continues until End Date: , unless earlier terminated in accordance with this Section.

Either party may terminate this Agreement for convenience upon providing days' prior written notice to the other party. Either party may terminate for material breach if the breaching party fails to cure the breach within days following written notice of the breach. Termination shall not relieve Client of its obligation to pay for work performed and documented through the effective termination date.

4. CONFIDENTIALITY

For the purposes of this Agreement, "Confidential Information" means non-public information disclosed by one party to the other, whether oral, written, electronic or other form, that is identified as confidential or that a reasonable person would understand to be confidential under the circumstances. Confidential Information does not include information that is (a) already lawfully known to the recipient without obligation of confidentiality, (b) becomes publicly available through no fault of the recipient, (c) is rightfully received from a third party without restriction, or (d) is independently developed by the recipient without reference to the discloser's Confidential Information.

Each party shall (i) use Confidential Information only for purposes of performing its obligations under this Agreement, (ii) restrict disclosure to those employees, agents, or subcontractors who have a need to know and are bound by confidentiality obligations at least as protective as those set forth herein, and (iii) exercise at least the same degree of care to protect Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care. A permitted disclosure pursuant to law or court order shall be made only after providing prompt written notice to the disclosing party to allow the disclosing party to seek protective relief.

5. INDEPENDENT CONTRACTOR; INSURANCE; INDEMNITY

Contractor is an independent contractor and not an employee, partner, or agent of Client. Contractor is solely responsible for all taxes, withholdings, benefits, and other obligations related to its personnel. Contractor shall maintain insurance of types and limits customary for the services provided and shall provide evidence of insurance upon request.

Each party shall indemnify, defend, and hold harmless the other party from and against third-party claims arising out of the indemnifying party's breach of this Agreement, willful misconduct, or negligent performance, subject to applicable law and any limitations set forth in this Agreement.

6. GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to its conflict of laws principles. The parties shall attempt in good faith to resolve disputes by negotiation. If the parties cannot resolve a dispute within 30 days, the dispute may be submitted to mediation or other non-binding alternate dispute resolution prior to initiation of litigation, at the election of the party seeking relief.

7. ENTIRE AGREEMENT; AMENDMENT

This Agreement, including all exhibits, attachments, and incorporated statements of work, constitutes the entire agreement and understanding of the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, representations, and understandings, whether written or oral. No amendment or waiver of any provision shall be effective unless in writing and signed by authorized representatives of both parties.

8. MISCELLANEOUS PROVISIONS

Severability: If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Notices: All notices required under this Agreement shall be in writing and delivered to the addresses provided above or to such other address as a party may designate by written notice.

Additional Provisions or Special Instructions

Client Printed Name:

By:

Date:

Contractor Printed Name:

By:

Date:

What Project Storm Works Is and where it fits

Project Storm Works is a standardized project document used to define storm-related construction or remediation tasks, scope, schedules, budgets, and approval workflows. It typically combines technical specifications, site information, regulatory permits, and roles/responsibilities into a single actionable package that contractors, engineers, and public agencies use to manage stormwater, drainage, or storm-restoration work. The form supports attachments for drawings, permits, and test reports, and is often routed for signature, notarization, and record retention by project stakeholders and regulatory bodies.

Why a clear Project Storm Works document matters

A complete Project Storm Works document reduces scope ambiguity, aligns stakeholders on responsibilities, and documents regulatory compliance that affects permits and inspections.

Who typically prepares or signs Project Storm Works

The document is used by public agencies, contractors, design professionals, and project owners to record scope and approvals before work begins.

Municipalities and regulators — Issue permits, confirm standards, verify inspection schedules and compliance.
General contractors — Accept scope, commit schedule and resources, and track subcontractor responsibilities.
Design engineers and inspectors — Certify designs, approve testing, and attest to conformance with specifications.

Multiple parties sign or approve at distinct milestones; use the signature order defined in the workflow to preserve clear attribution.

Core parts of a professional Project Storm Works package

A professional package organizes contract terms, technical plans, regulatory documents, approvals, cost estimates, and acceptance criteria so all parties can act consistently and preserve an audit trail.

Project ID

Unique identifier and location details used to match permits, drawings, and inspection logs across systems and reports.

Scope Summary

Concise description of work, deliverables, exclusions, and referenced technical standards to avoid interpretation disputes.

Schedule

Milestones, mobilization dates, inspection windows, and completion targets tied to liquidated damages or milestone payments.

Budget

Line-item estimate, approved change order procedure, and who is authorized to approve cost adjustments.

Regulatory Attachments

Permits, approvals, testing protocols, and inspection criteria required by local, state, or federal agencies.

Signatures

Designated signer roles, signature blocks, and any notarization or witness requirements to validate the agreement.

Essential information fields to include

Project Name: Official project title

Site Address: Street, city, state, ZIP

Parties: Owner, contractor, engineer

Effective Date: MM/DD/YYYY

Budget Total: Approved contract value

Approval Status: Signed / Pending / Rejected

Step-by-step: completing and executing Project Storm Works

Follow a consistent order to reduce review cycles: populate data, attach permits, route for approvals, then execute signatures in role order.

01

Prepare: Populate fields and attach required documents.
02

Review: Internal and regulatory review for compliance.
03

Approve: Authorized parties sign in designated order.
04

Archive: Save executed copies and retain audit trail.

Digital workflow settings to configure for online completion

Configure routing, signer order, authentication, and retention settings before sending to reduce rework and ensure compliance.

Field	Configuration
Signer Order	Define sequential or parallel signing
Authentication	Use email, SMS code, or KBA as required
Attachment Required	Mark permits and drawings as mandatory uploads
Retention Settings	Set archive period and access controls

Where to send, file, or submit the completed document

Use a single, auditable route to submit the executed Project Storm Works to the owner, regulator, and contractor to maintain a consistent record.

Owner Copy: Deliver signed PDF to owner or asset manager.
Regulatory Filing: File permits with the issuing agency per local instructions.
Contractor Records: Store executed version with project control documents.
Inspector Archive: Provide inspector copy before scheduled inspections.

How to share and sign Project Storm Works electronically

Choose a platform that supports PDF/DOCX import, audit trails, and the authentication level required by your authorities.

Supported Formats: PDF, DOCX, XLSX
Integrations: Salesforce, NetSuite, Microsoft 365
Authentication: Email, SMS, KBA options

Common timelines and milestone deadlines to track

Track regulatory and contractual timelines explicitly; missed dates commonly trigger fines, inspection delays, or change orders.

Permit Approval Window:

Submit permits early; agency review times vary by jurisdiction and workload.

Mobilization Date:

Date when on-site work may begin per contract schedule.

Inspection Notice:

Provide required notice periods prior to regulatory inspections.

Completion Date:

Final acceptance and punchlist deadline for project closeout.

Warranty Start:

Date warranty obligations begin after acceptance.

Key project stages from planning to closeout

Organize the project into sequential stages so approvals, payments, and inspections follow a predictable flow.

01

Planning and Design

Prepare drawings, specs, and cost estimates before permitting.

02

Permitting and Approvals

Obtain required permits and regulatory sign-offs before mobilization.

03

Construction and Testing

Execute work, perform tests, and complete inspections.

04

Closeout and Warranty

Resolve punchlist items and document warranty start.

Common mistakes to avoid when preparing Project Storm Works

Incomplete attachment lists cause permit rejections and require resubmission that delays mobilization by weeks.
Using ambiguous scope language increases change order disputes and can delay payment processing.
Missing authorized signer information often forces an administrative amendment and a second signature cycle.
Failing to set mandatory attachments in the workflow allows submissions without required permits or tests.

Key risks and consequences of errors

Permit Rejection: Project delay

Contract Breach: Liquidated damages

Inspection Failure: Remediation costs

Incorrect Signatures: Invalid execution

Record Loss: Compliance exposure

Unauthorized Work: Fines or stop-work orders

Comparison: eSignature options for executing Project Storm Works

Common capability comparisons for document execution; signNow appears first per vendor ordering conventions and supports a range of compliance 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	Yes, 7-day trial	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
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Real-world examples of Project Storm Works in use

These condensed examples show how organizations use an executed project package to streamline approvals and documentation.

Optica Ventures (COO)

Optica standardized storm repair packages to reduce back-and-forth with contractors and regulators.

The team used a consistent attachment set for permits and tests.
As a result, permit review cycles shortened and the city inspector accepted projects more quickly, reducing idle crew time and improving payment timing without changing technical standards.

Martin Properties (Founder)

A small owner used digital execution to manage multiple seasonal storm projects remotely.

They required signed site acceptance before release of final payment.
This allowed project managers to complete closeout remotely, maintain a clear audit trail, and reduce field rework linked to missing approvals.

Practical tips for accurate, efficient completion

Adopt consistent conventions for names, dates, attachments, and signer authority to reduce administrative cycles and disputes.

Standardize Names and IDs

Use a consistent project naming convention and include legal entity names exactly as registered to prevent payment and title issues.

Require Mandatory Attachments

Mark permit numbers, drawings, and test reports as required fields in the workflow so submissions are not accepted incomplete.

Define Signer Roles

Specify who can sign for each party and include position titles and contact information to avoid unauthorized signatures.

Preserve Audit Trails

Choose formats and platforms that capture timestamps, IP addresses, and version history to simplify disputes and regulatory reviews.

Frequently asked questions about completing and signing Project Storm Works

Answers cover execution, validity of electronic signatures, and common platform or filing issues encountered during project workflows.

Need help? Contact support

Can the document be signed electronically?
Yes. Electronic signatures are legally valid in interstate and intrastate commerce under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met.
When is notarization required?
Notarization is required for recordable instruments and in jurisdictions for deeds and some easements; check local rules—certain states also require witnesses for deeds or POAs.
What authentication level should be used?
Match authentication strength to risk: email-only for low-risk approvals, SMS or KBA for higher assurance, and RON when notarization must occur remotely under state RON rules.
Are eSigned PDFs admissible in court?
Yes. Electronic records and signatures are admissible under ESIGN/UETA when the signature is attributable and the record can be reproduced, subject to specific evidentiary rules.
How to handle a missing attachment after signing?
If a required attachment was omitted, issue an amendment or supplement signed by authorized parties and attach the missing document with clear reference to the original execution.
Does electronic signing meet HIPAA or tax requirements?
Electronic execution can meet HIPAA and tax rules if the platform supports required controls; for HIPAA a BAA may be required and tax record retention follows IRC and IRS guidance.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now