Can an ECD be signed electronically?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are legally enforceable for most commercial transactions. Verify exceptions where a recording, notarization, or specific statutory formality is required.

When is notarization needed?

Notarization is generally not required for internal ECDs. Notary or witness requirements may apply if the change amends a recorded instrument or modifies real property interests; consult state recording rules or counsel in those instances.

What signer authentication is recommended?

Use at least email plus a second factor for critical approvals. For higher-assurance needs consider identity proofing or advanced signer authentication in line with your compliance policies and audit requirements.

How long should you retain signed ECDs?

Retain ECDs for the active contract term plus a minimum of three years; extend retention for tax- or health-related matters per IRS guidance (IRC §6501(a)) and HIPAA (45 CFR §164.530(j)).

What supporting documents belong with an ECD?

Include revised drawings, updated BOMs, test reports, supplier acknowledgements, cost impact summaries, and training records so implementation and verification are auditable.

How to correct errors after signing?

If a signed ECD contains errors, issue a new ECD or formal amendment that references and supersedes the prior document. Retain both documents for audit trail integrity and document the reason for the correction.

Electronic Signature
Templates
Miscellaneous
Engineering Change Document

Engineering Change Document

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

ENGINEERING CHANGE DOCUMENT

Client Name: Supplier Name:

WHEREAS

WHEREAS, Client Name: (the "Client") and Supplier Name: (the "Supplier") have an existing agreement governing the supply, manufacture and engineering of products and services; and

WHEREAS, the parties desire to document and authorize a discrete engineering change to one or more items covered by their agreement, including scope, cost, schedule and implementation responsibilities, as set forth in this Engineering Change Document (the "ECD");

WHEREAS, the parties intend for the terms of this ECD to supplement and, where inconsistent, to modify the applicable provisions of the underlying agreement only to the extent expressly stated below.

Change Request Identification

ECD Number Request Date Originator

Scope of Work

Change Description

Affected Item(s) / Part Numbers Proposed Technical Change

Reasons for Change

Impact Analysis

Cost Impact (Total Change Cost) Schedule Impact Quality / Risk Assessment Affected Documents / Drawings

Implementation Plan

Proposed Effective Date Implementation Owner

Payment Terms

Total Change Cost:

Payment Schedule Late Payment Fee

Term and Termination

Term Start Date: Term End Date (if applicable):

Either party may terminate this ECD for material breach of its terms that remains uncured after written notice of: . Termination will be without prejudice to rights or liabilities accrued prior to termination.

Confidentiality

The parties acknowledge that the engineering change may include Confidential Information. Each party will treat information disclosed in connection with this ECD as confidential and will not disclose it to third parties except as necessary to perform this ECD or as required by law. Confidentiality obligations survive termination of this ECD for a period of: .

Change includes Confidential Information that is subject to the confidentiality provisions above.

Approvals and Routing

Originator Approval Engineering Approval Customer / Receiving Approval

Governing Law

This ECD is governed by and construed in accordance with the laws of the State of , without regard to its conflicts of law principles.

Entire Agreement

This ECD, together with the underlying agreement between the parties and any documents expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter of this ECD and supersedes all prior negotiations, proposals and representations, whether written or oral, relating thereto. Any amendment to this ECD must be in writing and signed by authorized representatives of both parties.

Execution

By signing below, each party represents and warrants that it has the authority to enter into this ECD and that the persons signing on its behalf are authorized to do so.

Client Printed Name:

By:

Date:

Supplier Printed Name:

By:

Date:

What an Engineering Change Document is and when it’s used

An Engineering Change Document (ECD) is a formal record that describes, authorizes, and tracks changes to a product design, bill of materials, manufacturing process, or specification. It captures the rationale, technical details, affected assemblies, change classification, impacted documents, risk assessment, required approvals, and implementation steps. Typical signatories include the originating engineer, change control board, quality assurance, procurement, and manufacturing leadership; the document usually records effective date, schedule, and rollback criteria.

Why using a formal ECD improves outcomes

An ECD provides formal authorization, documents technical and commercial impacts, and preserves an audit trail for regulatory and quality reviews. It reduces implementation errors, aligns stakeholders, and supports supplier communications and contract compliance throughout the lifecycle.

Who prepares and approves Engineering Change Documents

ECDs are created and reviewed by cross-functional teams to ensure technical accuracy and business alignment.

Design engineers — prepare technical change details and justifications, including drawings and BOM revisions.
Change control board — reviews classification, risk, and approval sequencing; includes QA and manufacturing representatives.
Procurement and suppliers — verify part availability, lead times, and update purchase orders or supplier instructions.

Final approval and distribution ensure traceability, supplier notification, and coordinated implementation across affected departments.

Core sections a professional ECD should include

A complete Engineering Change Document includes technical specs, impact analysis, approvals, and implementation instructions to manage risk and ensure traceability.

Change ID

Assign a unique identifier and version. Record the originating department, reference drawings and BOM versions, and include cross-references to related change requests to maintain traceability across systems.

Description

Provide a clear, concise description of the change, technical drawings, affected components, tolerances, and justification. Include before-and-after state and any substitute parts with part numbers.

Impact Analysis

Document product, process, cost, schedule, regulatory, and safety impacts. Quantify affected units, estimate rework, and identify tests required to validate the change prior to production release.

Approvals

List required approvers by role, include signature blocks, dates, and any conditional approvals from quality, safety, procurement, and the change control board.

Implementation Plan

Define tasks, responsible owners, effective date, affected work orders, production hold/backout steps, and supplier notifications with timelines and acceptance criteria.

Attachments

Append revised drawings, test plans, supplier acknowledgements, updated BOMs, cost estimates, and training materials necessary to implement and verify the change.

Step-by-step: preparing, approving, and implementing an ECD

Follow this sequence to prepare, approve, and implement an ECD while maintaining records for audit and supplier communication.

01

Draft: Record change details and attach supporting drawings.
02

Analyze: Complete impact analysis and tests required.
03

Approve: Route to required approvers in defined order.
04

Implement: Notify suppliers, update BOMs, and release changes.

Configure your online ECD workflow for reliable routing

Set up automated routing, conditional approvals, and attachments in your e-document platform to reduce manual handoffs and speed implementation.

Field	Configuration
Routing Logic	Sequential or parallel approvals
Conditional Fields	Show fields based on change classification
Attachments	Require PDFs for drawings, test reports
Notifications	Email and in-app alerts on status changes

Where to file the signed ECD and who to notify

File the signed ECD in the engineering document control system and notify procurement, manufacturing, suppliers, and quality teams to coordinate implementation.

Record System: Save final PDF to PLM or document control repository.
Procurement: Send supplier notification and request acknowledgement.
Manufacturing: Update work orders and production schedules.
Quality: Archive ECD for audit and validation records.

Digital signing, authentication, and integration checklist

Configure signing methods, signer authentication, and system integrations before initiating e-signature workflows to reduce rework.

Authentication: Email, SMS, or two-factor
Integrations: PLM, ERP, and cloud storage
Formats: PDF/A recommended with audit trail

Typical timelines and processing expectations for ECDs

Timelines vary by change severity; document expected lead times and review windows to align stakeholders and suppliers.

Minor change review window:

3–10 business days for assessment and approvals.

Major engineering change timeline:

4–12 weeks including testing and supplier lead times.

Supplier acknowledgement deadline:

Typically 5–15 business days after notification.

Production hold period:

Immediate hold until verification or rollback criteria met.

Document posting and release:

Post signed ECD and notify teams within 24–48 hours.

Milestone sequence from request through verification

Track numbered milestones from initiation through verification to provide a clear schedule for approvals and implementation checkpoints.

01

Initiation

Originator submits ECD with preliminary analysis.

02

Impact review

Cross-functional review identifies technical and commercial impacts.

03

Approval and scheduling

Authorized approvers set effective date and release plan.

04

Verification and close

Post-implementation tests confirm success before formal close.

Common mistakes to avoid

Incomplete impact analysis leads to unanticipated production delays, rework, and increased costs when supplier or manufacturing constraints are overlooked.
Mismatched part numbers or omitted revision levels cause incorrect assemblies to be built and complicate corrective actions and warranty claims.
Routing to incorrect approvers or missing signature levels delays implementation and may invalidate the ECD during audits.
Failing to notify suppliers promptly results in lead-time slips, obsolete inventory, and potential contractual disputes and costs.

Potential consequences of an incorrect or incomplete ECD

Production Errors: Manufacturing defects and recalls.

Cost Overruns: Unexpected rework and scrap costs.

Regulatory Risk: Noncompliance for regulated products.

Contract Liability: Supplier disputes; breach of contract.

Audit Findings: Failed quality audits or corrective actions.

Schedule Delays: Missed delivery dates and penalties.

E-signature vendor comparison for executing ECDs

Compare common plan features and starting prices for e-signature providers; signNow is listed first per vendor ordering conventions.

	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	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Real-world examples of Engineering Change Document workflows

These examples show how ECDs are used in different operational contexts to control risk and document change execution.

Manufacturing example

A component redesign request documents the defect and proposed fix, quantifies affected lots, and specifies test verification

Cross-functional review confirmed supplier lead times
After approvals the ECD updated the BOM, notified suppliers, and scheduled validation runs before full production release to prevent field failures and preserve traceability.

Construction example

A specification change affects embedded materials and schedule, so the ECD recorded cost impacts and revised drawings

Procurement confirmed alternate supplier availability
The signed ECD drove contract amendments, updated site work orders, and provided an auditable record for owner approvals and payment adjustments.

Security and compliance considerations for ECDs stored and signed electronically

Encryption in transit: TLS 1.2/1.3

Encryption at rest: AES-256

Compliance standards: SOC 2 Type II; ISO 27001

Healthcare support: HIPAA compliant (BAA required)

FDA-ready: 21 CFR Part 11 support available

Accessibility: WCAG 2.0 Level AA

Frequently asked questions about using an Engineering Change Document

Answers address common execution issues, digital signing concerns, and retention or legal validity questions for ECDs.

Need help? Contact support

Can an ECD be signed electronically?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are legally enforceable for most commercial transactions. Verify exceptions where a recording, notarization, or specific statutory formality is required.
When is notarization needed?
Notarization is generally not required for internal ECDs. Notary or witness requirements may apply if the change amends a recorded instrument or modifies real property interests; consult state recording rules or counsel in those instances.
What signer authentication is recommended?
Use at least email plus a second factor for critical approvals. For higher-assurance needs consider identity proofing or advanced signer authentication in line with your compliance policies and audit requirements.
How long should you retain signed ECDs?
Retain ECDs for the active contract term plus a minimum of three years; extend retention for tax- or health-related matters per IRS guidance (IRC §6501(a)) and HIPAA (45 CFR §164.530(j)).
What supporting documents belong with an ECD?
Include revised drawings, updated BOMs, test reports, supplier acknowledgements, cost impact summaries, and training records so implementation and verification are auditable.
How to correct errors after signing?
If a signed ECD contains errors, issue a new ECD or formal amendment that references and supersedes the prior document. Retain both documents for audit trail integrity and document the reason for the correction.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now