PHP Website Maintenance Contract: Scope, Response Time & Spare Parts

The trickiest part of a maintenance contract isn't price—it's defining what counts as maintenance versus a new requirement.

Insights:PHP Website Maintenance Contract: Scope, Response Time & Spare Parts

Clause 1: Scope Boundaries

Suggested inclusions:

  • Bug fixes for existing features.
  • Security updates for dependencies and plugins.
  • Regular backups and inspections.
  • Limited copy and image replacements (with a monthly cap).

Suggested exclusions:

  • New features and pages.
  • Full redesigns.
  • Third-party service procurement costs.
  • Data recovery caused by client errors.

The excluded items must clearly state the pricing method (per man-day or per project).

Clause 2: Response Timeframes

分级 recommendation:

Level Scenario Response SLA
High Site completely inaccessible Within 2 hours
Medium Core functionality malfunction Within 8 hours
Low Styling and copy issues Within 2 business days

Note the distinction between "response" and "fix": most contracts only commit to response timeframes, while fix timelines are negotiated based on issue complexity.

Clause 3: Spare Parts and Consumables

  • Who bears server and hosting costs.
  • Certificate costs and renewal responsibility.
  • Third-party service fees (SMS, CDN, analytics).
  • Backup storage costs.

It is recommended to list these in a table appended to the contract.

Other Essential Items

  • Maintenance cycle (monthly/quarterly).
  • Deliverables (inspection reports, change logs).
  • Data ownership and confidentiality clauses.
  • Handover process upon contract termination (code, accounts, documentation).
  • Common Pitfalls

    • Only stating "provides maintenance" without defining scope.
    • Response time left as "as soon as possible."
    • Third-party cost responsibilities are undefined.
    • No agreed handover terms, causing delays when changing providers.

    Pricing Considerations

    • Website scale and page count.
    • Functional complexity (membership, orders, payments).
    • Frequency of past issues.
    • Required response times.

    Scope

    This article outlines a clause framework and does not constitute legal advice. We recommend having legal counsel review the final contract against local regulations.

    Related Reading: