Website Reliability Package Terms and Service Boundaries
Clear expectations for monitoring, alerting, investigation, reporting, after-hours response, remediation, access, and package fit.
These terms explain how the Website Reliability packages are intended to work before any client-specific agreement is written. A final service agreement may define additional details for the specific site, access, business risk, and response expectations.
Short Version
Reliability packages include monitoring, automated alerting, investigation during standard response hours, and scheduled reporting.
Packages do not include guaranteed after-hours human response unless a separate written arrangement says otherwise.
Remediation, maintenance, hosting changes, DNS changes, WordPress updates, backup work, and emergency fixes are separate from monitoring unless explicitly included in writing.
The service is built for important business sites, not simple non-critical sites that only need basic uptime notifications.
Included Package Scope
The monthly reliability packages are managed monitoring and review services. They are designed to detect problems earlier, organize technical signals, and create a clearer path for investigation.
- Monitoring setup and configuration for the agreed package level
- Automated alerting for configured checks and thresholds
- Investigation during the standard response hours defined for the client service agreement
- Scheduled reporting appropriate to the package level
- Internal notes, client-facing summaries, and recommendations when issues need follow-up
Standard Response Hours
Standard response hours are the times when human review and investigation are expected to happen under the normal package.
- Standard response hours are defined in the client service agreement
- Automated monitoring may run continuously even when human response is not available
- Response means review or investigation begins; it is not a guaranteed resolution time
- Actual resolution may depend on hosting providers, DNS providers, registrars, Cloudflare, plugin vendors, client approvals, or access availability
After-Hours Definition
After-hours means any time outside the standard response hours defined for the client service agreement.
- Unless a separate written agreement says otherwise, nights, early mornings, weekends, holidays, and unavailable periods are treated as after-hours
- No standard package includes guaranteed after-hours human response
- After-hours response, phone escalation, overnight incident handling, emergency remediation, and guaranteed response outside standard response hours require a separate written arrangement
- Separate after-hours arrangements may require separate pricing, escalation rules, response expectations, and notification paths
Monitoring Versus Remediation
Monitoring identifies signals and supports investigation. It does not automatically include the labor, permissions, provider coordination, or risk of fixing every issue found.
- Remediation work is billed separately unless a written agreement includes it
- WordPress core, plugin, and theme update oversight requires explicit scope and access
- Hosting fixes, DNS changes, Cloudflare changes, backup restoration, malware cleanup, and code changes are not included by default
- Detected issues may become separate recommendations, quoted work, or add-on tasks
Access And Client Responsibilities
Coverage depends on the access and information available for the specific site.
- The client is responsible for providing accurate site, hosting, DNS, registrar, Cloudflare, WordPress, email, and business-contact information when needed
- Some checks or integrations may be conditional if the platform, provider, plugin, account, or permissions do not support them
- Client-owned services, licenses, hosting accounts, domains, and third-party tools remain the client responsibility unless a written agreement says otherwise
- Missing, revoked, expired, or restricted access can limit monitoring, investigation, reporting, and remediation options
Alerts, Incidents, And Reporting
The service is intended to create useful visibility rather than raw alert noise.
- Alerts may be grouped, deduplicated, prioritized, or reviewed before being escalated
- Not every alert means there is a confirmed client-facing outage or business-impacting problem
- Reports summarize configured monitoring data, incidents, notable trends, and recommendations
- Report frequency and depth depend on the selected package and any written add-ons
Package Fit
The reliability packages are for sites where quiet technical problems have real business cost.
- A simple, non-critical brochure site may be better served by a low-cost self-serve uptime tool
- A site that needs a redesign, rebuild, hosting move, cleanup, or security remediation may need project work before monitoring adds enough value
- Package scope can be adjusted only after the site, risk level, access, and desired response model are reviewed
- Main Street Web Developer may decline package coverage when the fit, access, risk, or expectations are not workable
Need a different operating model?
Critical sites can have custom terms for after-hours response, phone escalation, emergency remediation, multi-site coverage, or a deeper reporting cadence. Those expectations should be priced and documented separately before relying on them.