Scope
Describe the tasks performed, specifications met, measurable results, and reference to the original statement of work or contract. Be specific about exclusions and any deviations from the original scope.
A Service Completion Document clarifies deliverables, documents client acceptance, and establishes the date when obligations conclude. It reduces billing disputes, supports warranty and lien decisions, and creates an auditable record admissible under ESIGN and UETA when executed electronically.
Typical users include service providers, clients, project managers, accounts payable staff, and legal teams who need formal confirmation of completed work.
Use the document to support invoicing, dispute resolution, regulatory audits, and long-term recordkeeping, and to evidence warranty start dates and lien waivers.
Describe the tasks performed, specifications met, measurable results, and reference to the original statement of work or contract. Be specific about exclusions and any deviations from the original scope.
Record the actual date when work was finished, using MM/DD/YYYY format. This date triggers warranty periods, payment deadlines, and statutory timelines such as lien notice windows where applicable.
List all tangible and intangible deliverables delivered to the client, including versions, serial numbers, and acceptance criteria. Attach delivery receipts, test results, or digital handover records.
Document client acceptance language, any conditional approvals, outstanding punchlist items, and criteria for final acceptance. Note whether acceptance is explicit, implied, or subject to inspection.
Include final invoice amounts, retainage withheld, payment terms, change order references, any credits or deductions agreed at completion, and the date payment is due.
Provide printed names, titles, company names, signature lines, and dates for all authorized signatories. Specify who has authority to sign and whether electronic signatures are acceptable.
| Workflow Configuration and Routing Field | Define steps, recipient order, authentication, and notifications in the workflow. |
|---|---|
| Default Sender Role (Project Manager) | Project manager initiates and monitors routing status. |
| Signing Order and Required Roles | Specify sequential or parallel signing and role responsibilities. |
| Authentication Method and Security Level | Choose email link, SMS code, KBA, or enterprise SSO as needed. |
| Notifications, Reminders, and Escalation Rules | Set automatic reminders and escalation to alternate approvers after configured intervals. |
For electronic completion and signatures, confirm platform capabilities, authentication, integration, and supported file formats before routing the document.
Specify due date per contract and any retainage release conditions.
Completion date often begins lien notice period; verify state law.
Use the documented acceptance date to calculate warranty start.
Retain copies for IRS recordkeeping and match invoices to tax year.
Start retention at completion; follow federal and industry retention rules.
Work completed per contract; record completion date and deliverables.
Client inspects deliverables and reports acceptance or exceptions.
Provider remedies punchlist items within agreed timeframe.
Both parties sign completion document and archive final copies.
| 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 vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| 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 plan | Varies by plan | Varies by plan |