Project Addendum Report
What the Project Addendum Report Is and when it matters
Why a clear Project Addendum Report protects the project
A concise addendum reduces disputes, clarifies deliverables, and creates a documented approval trail that supports invoicing and change-order tracking while helping teams comply with contract terms and internal controls.
Who typically prepares and reviews project addenda
Typical owners and reviewers span project management, contracting, and legal teams and vary by industry and project scale.
- Project Manager — Prepares the factual change summary and attaches impact analysis for schedule and resources.
- Contract Administrator — Reviews contract language, identifies change-order clauses, and tracks approvals and budget authority.
- General Counsel / Legal — Assesses legal risk, revises governing terms, and signs where authority requires legal approval.
Collaboration among these roles ensures technical accuracy, contractual compliance, and that the document is enforceable and auditable.
Key penalties and legal risks of an incorrect addendum
Common preparation errors to avoid
- Vague change descriptions that omit measurable deliverables or acceptance criteria, causing disagreements at implementation and billing stages.
- Failing to link the addendum to the original contract clause or reference number, which complicates auditability and legal interpretation.
- Not documenting cost breakouts or who bears escalation, leaving finance teams unable to process invoices correctly.
- Skipping signer authority checks so the signatory lacks delegated power and the modification is later challenged.
Step-by-step: complete a Project Addendum Report
-
01Identify reference: Enter original contract ID and effective date.
-
02Describe change: Summarize scope, deliverables, and acceptance criteria.
-
03Quantify impact: Record cost, schedule, and resource changes numerically.
-
04Obtain approvals: Collect authorized signatures and record signer roles.
How the addendum flows through approval and recordkeeping
-
Draft: Author prepares addendum and attaches supporting documents.
-
Legal review: Legal verifies terms and checks for conflicts.
-
Approvals: Budget and contracting signatories approve changes.
-
Archive: Store executed addendum with original contract record.
Recommended digital workflow settings for e-submission
| Field | Configuration |
|---|---|
| Template | Create reusable addendum template with locked original contract field. |
| Signer order | Set sequential routing by role (PM → Finance → Legal). |
| Authentication | Use email + SMS code or advanced auth where required. |
| Retention policy | Attach retention tag and exportable audit report. |
Digital delivery and format considerations
Choose a platform that supports PDF and DOCX, audit trails, and integrations with your document repository.
- File formats: PDF and DOCX preferred for archival and edit history.
- Integrations: Connect with NetSuite, Salesforce, Google Workspace, or Box.
- Authentication: Support email, SMS, and optional KBA or SSO.
Ensure exportable signed PDFs include an embedded audit trail and are retained in your records system for legal defensibility.
Timing and typical deadlines for issuing addenda
Immediate notice:
Issue an addendum as soon as material change is identified, typically within 48–72 hours.
Approval window:
Require approvals within 7–14 business days to avoid schedule drift.
Cost reconciliation:
Submit cost adjustments for billing within 30 calendar days.
Dispute notice:
Provide written dispute notices per contract timelines, often 14–30 days.
Archive timing:
Store executed addendum immediately upon final signature.
Milestones from change identification to archival
1. Change identified
Document issue, impacted deliverables, and notify stakeholders immediately.
2. Draft addendum
Prepare addendum with impact analysis and attach supporting exhibits.
3. Sign and approve
Collect required signatures in the established signer order.
4. Archive and distribute
Save executed document and circulate to relevant teams for implementation.
eSignature vendor comparison for handling Project Addendum Reports
| 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 | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Frequently asked questions about Project Addendum Reports
-
Can a Project Addendum be e-signed?
Yes. Electronic signatures are legally valid under the federal ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are satisfied.
-
What makes an addendum enforceable?
An enforceable addendum identifies the original agreement, clearly states modifications, shows authorized signatories, and includes dates; missing approvals or unclear scope increase enforceability risk.
-
Do I need notarization or witnesses?
Most addenda do not require notarization, but state or contract-specific rules may require it for certain instrument types; verify local law or contract clauses before notarizing.
-
How do I correct errors after signing?
Execute a corrective addendum or amendment signed by the same authorized parties; avoid manual alterations to executed copies as they may be challenged.
-
Who may sign the addendum?
Only persons with delegated authority under the contract or corporate resolution should sign; list signer name, title, and delegation source in the addendum.
-
How long must I keep the addendum?
Retain executed addenda per business retention policies and legal requirements—minimum 3 years for tax records, 6 years for HIPAA where applicable; consult counsel for industry-specific rules.