Is an electronic signature legally valid?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and in most states under UETA; ensure intent, consent, attribution, and retention. Certain documents like wills, court orders, and some statutory notices remain excluded from electronic execution.

What constitutes a valid e-signature?

A valid e-signature shows (1) signer intent, (2) consent to transact electronically, (3) attributable identity, and (4) reproducible record retention. Consumer-facing agreements may also require ESIGN consumer disclosures under 15 U.S.C. §7001(c).

Do I need notarization or witnesses?

Most Project Plan Charters do not require notarization or witnesses. If the charter attaches or amends notarized legal instruments, notarization may be required. Remote online notarization is permitted in most states with identity proofing and recording requirements; verify state notary rules before use.

How can errors be corrected after signing?

Do not alter the signed document itself. Execute a signed amendment or corrective addendum that references the original baseline and signature dates to preserve the audit trail and maintain legal clarity.

When is HIPAA relevant to a charter?

If the charter contains or references protected health information, HIPAA applies. Use a business associate agreement for vendors, implement access controls, and retain records for six years per 45 CFR §164.530(j).

What if the eSignature platform fails?

Retain a documented fallback process: pause routing, notify signers, and offer alternative authenticated signing (in-person, RON, or reissue). Preserve transaction logs and correspondence to support continuity and auditability.

Project Plan Charter

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

PROJECT PLAN CHARTER

This Project Plan Charter (the "Charter") is entered into as of by and between Client Name: and Contractor Name: .

WHEREAS

WHEREAS, Client desires to engage Contractor to perform the work described in this Charter for the project titled (the "Project"), subject to the terms and conditions set forth herein; and

WHEREAS, Contractor represents that it has the experience, qualifications and personnel to perform the Project in accordance with the schedule, deliverables and standards described in this Charter; and

WHEREAS, the parties agree to define the scope, governance, payment and termination provisions for the Project in this Charter to create a binding framework for project execution.

SCOPE OF WORK

Contractor shall perform the following services and deliverables in accordance with the terms of this Charter. The services shall be performed with reasonable skill, care and professional standards customary in the industry.

Detailed Scope of Work Key Deliverables and Acceptance Criteria

PROJECT MANAGEMENT

Project Manager (Client) Project Manager (Contractor) Primary Contact Information

PAYMENT TERMS

The Client shall pay Contractor for performance of the Project in accordance with the amounts, schedule and invoicing procedures set forth below. All amounts are stated in the parties' agreed currency and exclude taxes unless otherwise stated.

Total Contract Amount Payment Schedule and Milestones Invoice Terms

Invoices shall reference the applicable milestone or deliverable and be submitted to the Client's billing contact. Client shall pay undisputed amounts within the number of days specified above from receipt of a proper invoice. Disputes to invoiced amounts must be raised in writing within fourteen (14) days of receipt.

Late Payment Fee

Late payments shall bear interest at the rate specified above, calculated monthly from the invoice due date until paid in full. Interest shall be in addition to any other remedies available to Contractor under this Charter or at law.

TERM AND TERMINATION

This Charter commences on the Start Date and continues until the End Date, unless earlier terminated in accordance with this section.

Start Date: End Date:

Notice Period for Termination Without Cause

Either party may terminate this Charter for material breach by the other party if such breach remains uncured for thirty (30) days following written notice specifying the nature of the breach. Upon termination, Client shall pay Contractor for work performed and reasonable, documented costs incurred through the effective date of termination and for any deliverables accepted by Client prior to termination.

CONFIDENTIALITY

For purposes of this Charter, "Confidential Information" means non-public, proprietary or business information designated as confidential or which a reasonable person would understand to be confidential given the nature of the information and the circumstances of disclosure. Confidential Information includes, without limitation, trade secrets, technical data, business plans, customer lists and pricing.

Each party agrees to: (a) hold Confidential Information of the other party in strict confidence using at least the same degree of care it uses to protect its own confidential information (but not less than reasonable care); (b) use Confidential Information only for performance of obligations under this Charter; and (c) not disclose Confidential Information to third parties except to those employees, contractors or advisors who need access to perform this Charter and who are bound by confidentiality obligations no less protective than those contained herein.

The obligations in this section do not apply to information that is: (i) known to the receiving party prior to disclosure without obligation of confidentiality; (ii) publicly available through no fault of the receiving party; (iii) rightfully received from a third party without breach of an obligation of confidentiality; or (iv) independently developed by the receiving party without use of the disclosing party's Confidential Information. A party may disclose Confidential Information if compelled by law, provided the disclosing party is given prompt written notice and, if possible, an opportunity to seek protective relief.

GOVERNING LAW

This Charter shall be governed by and construed in accordance with the laws of the jurisdiction of , without regard to its conflicts of law principles.

ENTIRE AGREEMENT

This Charter, together with any attachments, exhibits and mutually executed change orders, constitutes the entire agreement between the parties with respect to the Project and supersedes all prior and contemporaneous agreements, proposals, representations and understandings, whether written or oral. No amendment to this Charter will be effective unless in writing and signed by authorized representatives of both parties.

MISCELLANEOUS

Assignment: Neither party may assign its rights or delegate its obligations under this Charter without the prior written consent of the other party, except that Contractor may assign to an affiliate or in connection with a sale of substantially all of its assets.

Notices (Client Address) Notices (Contractor Address)

Change Orders: Any changes to the scope, schedule or price must be documented in a written change order, describing the change, impact on schedule and cost, and signed by authorized representatives of both parties prior to implementation.

Client Name:

By:

Date:

Contractor Name:

By:

Date:

What the Project Plan Charter Is

A Project Plan Charter is a concise governing document that authorizes a project, defines high-level objectives, scope, and measurable success criteria, and identifies key stakeholders and resources. It records project sponsor approval, initial risks, assumptions, and constraints, and establishes the project's timeline, budget envelope, and major milestones. The charter functions as the formal initiation record that aligns sponsors, managers, and delivery teams on objectives and authority to execute. Use it to prevent scope confusion, enable decision-making, and provide a baseline for project governance throughout the lifecycle.

Why a Charter Matters for Project Initiation

A clear Project Plan Charter provides formal authorization, reduces ambiguity about objectives and scope, and clarifies decision rights, funding limits, and stakeholder expectations. It supports risk identification, prioritization, and alignment across teams so work can proceed with defined authority and measurable goals.

Core Elements to Include

Primary Project Plan Charter elements align scope, roles, resources, milestones, risks, and acceptance criteria into a single, authoritative reference for project initiation.

Project Overview

Summarize purpose, objectives, deliverables, and high-level scope. Include measurable success criteria and any exclusions to prevent later scope disputes; this section frames the project's strategic value and expected outcomes.

Scope and Deliverables

List included workstreams and major deliverables with explicit exclusions. Tie deliverables to acceptance criteria, dependencies, and baseline assumptions so scope changes require formal change control and sponsor approval.

Stakeholders & Roles

Identify project sponsor, owner, steering committee, project manager, and primary team leads. Define decision authority, approvals required, and communication responsibilities to reduce ambiguity and accelerate escalation.

Milestones & Schedule

Provide high-level milestone dates, key phase gates, and dependencies. Note constraints that affect scheduling and include contingency allowances for critical path activities to manage expectations.

Budget & Resources

Document authorized budget envelope, major cost categories, and allocated resources. Include funding source, procurement constraints, and any resource assumptions impacting delivery or timeline.

Risks & Assumptions

Record initial risk register entries, top risks, mitigation approaches, and project assumptions. State known constraints and dependencies so stakeholders understand uncertainty and acceptance thresholds at project start.

Stepwise Procedure to Complete and Approve

Follow these steps to complete and approve the Project Plan Charter, from draft through sponsor sign-off and baseline publication.

01

Draft Charter: Assemble overview, scope, and stakeholders.
02

Review: Circulate to stakeholders for comments.
03

Approve: Sponsor signs and authorizes execution.
04

Publish: Issue baseline and start tracking.

How to Configure the Online Workflow

Configure online settings to match organizational process, authentication needs, and automated routing before sending the charter for signature.

Configurable Field Name and Setting	Configuration guidance and default values
Authentication Method and Strength Requirement	Email, SMS, or SAML SSO
Signer Identity Verification Settings and Options	Guest links, SMS code, or KBA
Field Types and Conditional Logic	Signature, initials, date, conditional required fields
Automated Email Notifications and Reminder Schedule	Set cadence and escalation recipients
Record Retention and Export Settings	Set PDF/A export and storage location

Platform and Technical Requirements

Ensure the eSignature platform supports required authentication, document formats, and integrations for efficient charter processing.

Formats: PDF, DOCX, and fillable forms
Integrations: Salesforce, NetSuite, Google Workspace
Authentication options: Email, SMS, SSO, or KBA

Typical Routing and Submission Flow

Typical routing describes where to send the charter, required reviewers, and final archival destination after sign-off.

Upload Document: Attach final charter PDF to workflow.
Assign Reviewers: Add stakeholder emails and roles.
Collect Signatures: Route for electronic signatures in order.
Archive Copy: Export signed PDF and audit trail.

Who Typically Prepares and Signs the Charter

Organizations of various sizes use a Project Plan Charter to formalize project starts and align leadership, delivery teams, and external partners.

Project Managers create, maintain, and track the charter baseline during execution and changes.
Sponsors authorize funding, approve initial scope, and resolve escalated schedule or budget decisions.
PMO and Governance use the charter as a control baseline for portfolio oversight and compliance reporting.

The charter centralizes authority and expectations, reducing rework and supporting consistent governance across projects.

Key Signatory Roles and Responsibilities

Sponsor — Executive

The sponsor provides strategic direction, authorizes the charter, and approves the budget and major scope changes. They are responsible for resolving escalated decisions, ensuring funding continuity, and validating that project outcomes align with organizational goals.

Project Manager — Lead

The project manager drafts and maintains the charter, coordinates stakeholder reviews, manages baseline changes through formal change control, tracks milestones and risks, and ensures deliverables meet acceptance criteria. They act as primary point of contact for execution and reporting.

Essential Information to Include

Project Title: Short, unique project name used

Effective Date: MM/DD/YYYY formatted start date

Project Sponsor: Full legal name and title

Authorized Budget: Approved USD total with contingency noted

Scope Summary: High-level inclusions and exclusions

Signatures: Printed name, title, date

Common Preparation Mistakes to Avoid

Vague scope language leads to scope creep, disagreement about deliverables, and frequent uncontrolled change requests that delay schedule and increase costs.
Missing or inconsistent signatory authority causes rejection during approval and may require re-execution after legal review, delaying project start.
Undocumented assumptions about resource availability or dependencies produce scheduling conflicts and unrealistic milestone dates once execution begins.
Incomplete risk entries or absent mitigation plans prevent proactive issue handling and force reactive, often costly, firefighting.

Practical Risks and Consequences

Delayed Start: Cost overruns likely.

Scope Creep: Increases schedule and budget.

Compliance Gaps: Regulatory exposure for regulated projects.

Contractual Disputes: Vendor disagreements and claims.

Resource Conflicts: Double-booked personnel.

Approval Rework: Redraft and re-signature required.

How Teams Use Charters in Practice

Practical examples show how a Project Plan Charter streamlines initiation across sectors from construction to software delivery.

Construction Project

A regional contractor uses a charter to align owner, contractor, and design teams before mobilization, clarifying scope and schedule expectations.

Reduces change orders during early phases.
By documenting milestones, payment terms, and acceptance criteria, the charter enabled faster procurement, reduced disputes, and provided clear basis for progress billing, improving cashflow predictability and contract compliance across multiple subcontractors.

IT Implementation

An enterprise IT team issues a charter for SaaS migration to define data migration scope, security requirements, and cutover windows.

Prevents scope drift during build phases.
Including stakeholder roles, acceptance tests, and rollback criteria in the charter reduced post-launch issues, accelerated executive approvals, and provided a documented rollback plan to minimize downtime and regulatory exposure for customer data.

Typical Timing and Deadlines

Key dates for a Project Plan Charter include drafting deadlines, review cycles, sponsor approval, baseline date, and archival actions.

Draft Completion Deadline:

Set a target date for working draft circulation.

Stakeholder Review Cycle:

Define review window, typically 5–10 business days.

Sponsor Approval Date:

Specify when sponsor must sign to avoid project delay.

Baseline Publication Date:

Record formal baseline issue date for tracking.

Archival and Retention Start:

Note when retention timelines begin after baseline.

Key Milestones from Initiation to Baseline

Milestone sequence from charter initiation through baseline publication and procurement readiness helps teams track approvals and execution readiness.

01

Initiation and Drafting

Prepare draft with objectives, scope, and stakeholders.

02

Stakeholder Review

Collect feedback and resolve discrepancies before approval.

03

Sponsor Approval

Formal sign-off authorizes budget and scope.

04

Baseline Release

Publish baseline and begin schedule and budget tracking.

Comparing eSignature Pricing and Core Features

Comparing common eSignature plans shows pricing and key feature differences relevant when choosing a platform for charter signing workflows.

	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	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 by vendor and plan	Varies by vendor and plan	Varies by vendor and plan

Frequently Asked Questions and Troubleshooting

Answers to common questions about completing, electronically signing, and storing a Project Plan Charter, with notes on legal and technical requirements.

Need help? Contact support

Is an electronic signature legally valid?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and in most states under UETA; ensure intent, consent, attribution, and retention. Certain documents like wills, court orders, and some statutory notices remain excluded from electronic execution.
What constitutes a valid e-signature?
A valid e-signature shows (1) signer intent, (2) consent to transact electronically, (3) attributable identity, and (4) reproducible record retention. Consumer-facing agreements may also require ESIGN consumer disclosures under 15 U.S.C. §7001(c).
Do I need notarization or witnesses?
Most Project Plan Charters do not require notarization or witnesses. If the charter attaches or amends notarized legal instruments, notarization may be required. Remote online notarization is permitted in most states with identity proofing and recording requirements; verify state notary rules before use.
How can errors be corrected after signing?
Do not alter the signed document itself. Execute a signed amendment or corrective addendum that references the original baseline and signature dates to preserve the audit trail and maintain legal clarity.
When is HIPAA relevant to a charter?
If the charter contains or references protected health information, HIPAA applies. Use a business associate agreement for vendors, implement access controls, and retain records for six years per 45 CFR §164.530(j).
What if the eSignature platform fails?
Retain a documented fallback process: pause routing, notify signers, and offer alternative authenticated signing (in-person, RON, or reissue). Preserve transaction logs and correspondence to support continuity and auditability.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now