Parties
Full legal names and entity types for each party, including contact details and a primary representative authorized to sign.
A precise No PE Agreement reduces ambiguity about who bears design and code-compliance responsibility, supports permitting conversations, and documents the parties’ intent for liability allocation under contract and local building codes.
Common users include property owners, general contractors, subcontractors, architects, and permitting agents who need to confirm whether PE involvement is required for a specific submission or minor scope of work.
An individual or entity owning the site who confirms awareness of the scope and agrees that no PE-stamped documents will be provided for the specific work. This party should understand the implications for inspections and liability and ensure the agreement matches permit requirements.
A licensed contractor, project manager, or authorized agent who attests the described work does not require a professional engineer and accepts operational responsibility for complying with applicable building codes and permit conditions.
Full legal names and entity types for each party, including contact details and a primary representative authorized to sign.
A precise description of work, locations, plans, and conditions for which PE services are explicitly not required.
A statement that each signer has the authority to bind their organization, including job title or role.
Statements that the scope complies with applicable codes or a declaration that the party assumes risk if the authority later requires PE involvement.
Choice of law clause naming the state whose rules will govern interpretation and enforcement of the agreement.
Dated signature lines for each party, with printed name and title; include witness or notary lines if required locally.
Choose a platform that supports standard file types, common integrations, and audit trails required for legal records.
| Field | Configuration |
|---|---|
| Signature Order | Set sequential or parallel signing to control who signs first. |
| Required Fields | Make name, effective date, and scope required before sending. |
| Authentication Level | Select email link, SMS code, or KBA depending on risk. |
| Retention Policy | Automatically store signed PDFs and audit trails in chosen cloud folder. |
Set the MM/DD/YYYY start to establish when obligations begin.
Specify a date by which all parties must sign to preserve permit timelines.
Submit documents before local permit application cutoffs to avoid rejection.
Keep signed originals per retention rules in case of later reviews.
Identify any period during which a party may revoke consent, if applicable.
| Criteria | No PE Agreement | Engineering Contract |
|---|---|---|
| Purpose | document lack of pe | retain pe services |
| Design responsibility | contractor/owner | licensed engineer |
| PE stamp required | no for stated scope | yes for stamped deliverables |
| Typical risk allocation | owner/contractor assume risk | engineer retains professional liability |
The owner documented nonstructural interior upgrades to avoid submitting stamped plans
A contractor used a No PE Agreement to state that specific grading adjustments did not require engineering plans
| 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 (Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes (BAA) | Yes (BAA) | No | No |