Scope
Narrowly define project-management activities, deliverables, excluded services, and interfaces with third-party vendors to avoid ambiguity during execution.
A clear Project Management Addition allocates responsibility, reduces disputes, and documents scope and billing for project oversight, improving chances that deliverables meet expectations.
Typical users complete the Project Management Addition to formalize delivery responsibilities and payment terms tied to project oversight.
Use this addendum with the underlying services or construction agreement so signatures and effective dates align with the master contract.
Name and title of the client-side approver; must have authority to approve scope, accept deliverables, and approve change orders per the base contract.
Project manager or authorized signatory for the provider; responsible for executing work, submitting reports, and coordinating resources under the addendum.
Narrowly define project-management activities, deliverables, excluded services, and interfaces with third-party vendors to avoid ambiguity during execution.
List milestones, target dates, acceptance windows, and any phased delivery approach so timeline obligations are enforceable and measurable.
Assign tasks, deliverable owners, and points of contact for approvals, testing, and closeout to prevent gaps in accountability.
Specify report types, frequency, required content (status, risks, budget), and delivery method to standardize communication.
Define how scope changes are proposed, estimated, approved, and billed, including required documentation and response timelines.
State fees for PM services, invoicing schedule, acceptance-based payments, and consequences for late payment or dispute.
| Field | Configuration |
|---|---|
| Signer Order | Sequential or parallel routing as contract requires |
| Authentication | Email link or SMS code; consider KBA for high-risk deals |
| Required Fields | Signatures, dates, initials on each change-item |
| Retention | Automatic archival and copy distribution after completion |
Choose a signing platform that supports secure e-signing, audit trails, and the integrations your teams use.
Ensure the chosen configuration logs an auditable chain of custody and stores completed copies according to retention policy.
| 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 | Available (Business Premium) | Available | Available | Available | Limited |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes (BAA) | Yes (BAA) | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Specify days for formal acceptance testing and corrective action after delivery
Define invoice due date and net payment terms to avoid late-payment disputes
State maximum response time for change-order estimates and approvals
Include required notice periods for dispute escalation and termination
Date when retention clock begins (typically effective date or completion date)
Initiate project, confirm scope, and distribute contact list and schedule.
Regular status checkpoints for progress, risks, and corrective actions.
Formal review window where deliverables are validated against acceptance criteria.
Final acceptance, deliverable transfer, and archival of project records.
A SaaS implementation firm added a PM addendum to define weekly sprints and acceptance criteria.
A general contractor attached a PM addendum to clarify superintendent responsibilities and reporting cadence.