Scope of Services
Precisely list covered environments, supported modules, excluded items, and any assumptions about third-party dependencies and customer responsibilities.
A clear Production Support Agreement aligns expectations, reduces downtime risk, and creates measurable remedies for failures. It protects both parties by defining accountability, preserving evidence for disputes, and ensuring security and regulatory obligations are assigned and monitored.
Properly executed agreements help operations, procurement, and legal teams coordinate support handoffs and limit exposure from outages, data incidents, or miscommunications.
Precisely list covered environments, supported modules, excluded items, and any assumptions about third-party dependencies and customer responsibilities.
Define severity tiers, response and resolution targets, measurement windows, and how uptime is calculated for availability guarantees.
Specify contact points, escalation chain, notification methods, on-call schedules, and required status reporting cadence during incidents.
Describe approval workflows, maintenance windows, rollback procedures, and testing or staging requirements before production changes.
Assign responsibilities for logging, access control, encryption, incident response, and any required regulatory controls such as HIPAA safeguards.
Cover fees, billing cadence, service credits, termination rights, indemnities, limits of liability, and intellectual property treatment.
| Field | Configuration |
|---|---|
| Authentication Method | Email link + SMS OTP or enterprise SSO for higher assurance |
| Required Fields | Make Effective Date, Parties, Signatures, and SLA table mandatory |
| Signing Order | Use sequential signing when counterparty review is required |
| Audit Trail | Enable full activity logging, timestamps, and IP capture |
Retain the completed agreement in a searchable repository and ensure automated distribution to legal, IT, finance, and security teams to enable compliance and faster incident response.
Priority 1: 1 hour; Priority 2: 4 business hours; Priority 3: 24 hours
P1: 8 hours; P2: 48 hours; P3: 7 business days
Provider delivers SLA report within 5 business days of month-end
Planned maintenance requires 72 hours advance notice
Either party must give 60–90 days written notice before renewal
Agreement signed and countersigned; effective date begins SLA obligations.
Provider completes access, runbook handoff, and knowledge transfer within agreed days.
Monitoring and alerting active and tested; incident playbooks validated.
First SLA performance review and adjustment meeting scheduled shortly after first reporting period.
| 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 (Business Premium) | Yes (paid tiers) | Yes (paid tiers) | Yes (paid tiers) | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Optica aligned support responsibilities across internal teams and vendors to reduce ambiguity during incidents.
A small property management firm used a standardized agreement to outsource monitoring and incident response.
Typically approves technical scope and signs on behalf of the customer; responsible for confirming environment inventory, access provisioning, and change control obligations with the provider.
An executive or delegated contract manager signs for the provider; responsible for operational delivery, escalation points, and ensuring staff comply with the agreement.