Delivery, hosting and support.
Ownership and support are part of the scope. We agree who does what, which costs recur and what happens when something needs attention.
Synthetic planning sample / Version 1.0
CMS migration and redirect plan
/departments/public-works/trash/services/waste/forms/permit.pdf/services/permitsReconcile all agreed records and resolve failed priority journeys before launch.
Managed hosting with named responsibilities.
WordPress delivery can use WP Engine managed hosting. Drupal, Next.js, React and custom API services are scoped to an appropriate managed platform. The hosting schedule names the account owner, platform and plan, region, access controls, monitoring, backups, recovery responsibilities and recurring costs.
WP Engine publishes information about its SOC 2 Type II and ISO 27001 platform controls. The selected service’s audit scope, reporting period, location and contractual commitments are checked during procurement. Provider evidence and application acceptance are recorded separately.
Review WP Engine’s published security information ↗
A named hosting platform is an architecture option. Provider agreements, coverage, report access and buyer-specific security acceptance are confirmed for the engagement.
Published care proposal targets.
Managed care proposals can include the following service levels. A signed service schedule activates the selected coverage after the hosting provider, escalation path and named support roles are confirmed.
- Availability
- 99.95% monthly availability target, with the monitoring source, exclusions and service-credit rules recorded in the signed schedule.
- Critical incidents
- A proposed 15-minute human acknowledgement with contracted 24/7 critical coverage; a four-hour restoration target. Acknowledgement and restoration are measured separately.
- Major and routine requests
- Proposed acknowledgement within one business hour for major degradation and one business day for routine requests. The schedule defines business hours and the client time zone.
- Incident updates
- Proposed notification within 30 minutes of a confirmed critical incident, followed by at least hourly updates while the incident remains active.
- Recovery
- A proposed four-hour recovery-time objective and 24-hour recovery-point objective. Backup retention, separate recovery location, restore tests and communications fallback are specified for the system.
- Planned maintenance
- A proposed 72-hour notice for ordinary maintenance. Maintenance windows, emergency changes, patch approval and availability exclusions are agreed before coverage begins.
Severity definitions, fees, service credits, measurement, exclusions, escalation contacts and recovery tests are included in the written schedule. These proposal targets do not establish active round-the-clock coverage for an uncontracted system.
Video delivery belongs in the operating plan.
Video hosting, storage, encoding, delivery bandwidth and access controls are scoped alongside the website. The plan identifies the media host or CDN, ownership, retention, captions, transcripts, descriptive alternatives, player controls and mobile performance. Higher-volume or restricted streaming has its own service and security requirements.
The portfolio on this site includes nine hosted, captured-screen walkthroughs with intentional playback, pause controls, static posters, text alternatives and GIF downloads. The film collection also provides caption and description options; its formal human media acceptance remains documented in the accessibility assessment.
A fixed price with an understandable operating cost.
The proposal separates the fixed implementation scope, optional care, hosting and third-party services. It identifies recurring charges, change-control rules, ownership and handover. A multi-year cost view can be prepared for the buyer’s term; scope and price are agreed in writing.
Delivery is organized around named responsibilities: product and content, design and accessibility, engineering, language review, security and hosting, testing and operational handover. The engagement identifies the people and subcontractors assigned to those roles and their availability.
Responsibility matrix for scoping
This matrix connects each contracted workstream to a named owner. The signed service schedule records coverage and the proposal targets selected for the engagement.
- Repository and editable source
- The agreement identifies source deliverables, intellectual-property rights, third-party licenses and the repository/account owner.
- Hosting and deployment
- Name the environment owner, billing party, access model and release authority before setup. Third-party fees are identified separately.
- Backups and recovery
- Agree which data is backed up, retention, restore responsibilities and evidence from a restore test.
- Monitoring and incident response
- Specify what is monitored, who receives alerts, the escalation path and supported coverage windows.
- Security maintenance
- Identify patch responsibility, access review, update cadence and the customer controls that apply. Specialized controls require qualified personnel and acceptance criteria.
- Training and handover
- Deliver the agreed runbook and training. Ask the receiving operator to demonstrate the tasks needed to operate the system.
Before the transition is accepted
- Confirm the repository, account and data owners.
- Record software, model, content and third-party license rights.
- Test the agreed deployment, backup and restore procedures.
- Deliver documentation and train the receiving operators.
- Record acceptance, unresolved items and any support period.