Parties
Full legal names and business entity types for each contracting party; include DBA names and registered addresses to avoid identity confusion.
A properly completed PCV6 reduces ambiguity about deliverables, clarifies payment milestones, and documents risk allocation; it also supports compliance where electronic records are used under ESIGN (15 U.S.C. ch. 96) or state UETA rules.
The form is most often completed by operational and contract teams tasked with executing service arrangements.
Multiple stakeholders — operations, finance, legal — should review the completed PCV6 before signatures to avoid downstream disputes.
Responsible for completing scope, schedule, and acceptance criteria. Ensures operational feasibility and confirms resource availability before signing; coordinates with finance for invoicing details.
Reviews liability, indemnity, and termination clauses. Confirms that choice of law and dispute resolution language align with organizational policy and regulatory obligations.
Full legal names and business entity types for each contracting party; include DBA names and registered addresses to avoid identity confusion.
Precise description of services, deliverables, acceptance criteria, and any excluded items to reduce disputes over expectations.
Start and end dates, renewal mechanics, early-termination rights, and notice periods for nonrenewal or breach events.
Fees, invoicing schedule, payment method, late fees, and any milestone-based billing tied to deliverable acceptance.
Nondisclosure obligations, permitted disclosures, and data handling expectations, including any special security requirements.
Limits on damages, indemnification scope, insurance requirements, and any carve-outs for intellectual property claims.
| Field | Configuration | Authentication | Email + SMS code or stronger |
|---|---|
| Template Name | PCV6 Standard Services Template |
| Auto-Remind | Reminders at 3 and 7 days after sending |
| Conditional Fields | Show payment fields only for paid engagements |
| Integration | Push signed copy to CRM and document storage |
Choose a signing platform that supports required authentication and audit logs for regulatory needs.
Day 0: Intake and template selection.
1–3 business days depending on complexity.
2–5 business days for finance and legal review.
2–10 business days depending on negotiation.
Typically complete within 1 business day after final approval.
Capture request details and supporting files promptly.
Populate template and verify key terms and pricing.
Legal and finance approval before signature circulation.
Signatures obtained, certificate of completion recorded, and document stored.
| Document Type | Typical Use | Binding Scope |
|---|---|---|
| Business Services PCV6 | project services | detailed, single-project terms |
| Statement of Work | specific deliverables | sows sit under an msa |
| Master Services Agreement | framework terms | governs multiple sows |
| Purchase Order | commodity procurement | short, purchase-focused |
| 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 | Yes, 7-day trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes (Business Premium) | Varies | Varies | Varies | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Tim Martin used PCV6 for property services to replace paper workflows and speed approvals
John Butler adapted PCV6 with privacy addenda to protect patient-related information