CUSTOM PHP WEBSITE: SUPPORT AND HANDOVER WORKSHEET
Turing Websites | 1 November 2026
https://turingwebsites.com/services/custom-php-website-support

Use this worksheet to describe an existing website and organise an authorised
handover. Record account ownership and access availability, not passwords,
tokens, keys, customer records or raw server logs.

1. YOUR WEBSITE AND THE TASK
Public URL:
Task: repair / update / maintenance / developer handover / other:
What a customer or team member needs to do:
What happens today:
When it last worked, if there is a fault:
Business deadline, if relevant:
What you know about the application or framework:

2. ACCOUNT OWNERSHIP AND AVAILABLE ACCESS
For each item, name the business owner and whether access is available.
Arrange credentials separately through a secure channel.
Domain registrar:
DNS provider:
Hosting account:
Code repository and the deployed release:
Database:
Uploaded files or object storage:
Email provider:
Payment provider or connected services:
Who can authorise the work?
What the previous developer has handed over:
What is still missing:

3. TECHNICAL INVENTORY FOR YOUR DEVELOPER
PHP runtime serving web requests:
PHP runtime used by scheduled/command-line work:
Framework, extensions and dependency versions:
Composer files and installed package requirements, where used:
Database engine and relevant connections:
Deployment method and application configuration location:
Scheduled jobs, queues and webhook destinations:
Provider notices or current compatibility constraints:

A command-line PHP version can differ from the runtime serving the website.
On a controlled test copy, Composer's check-platform-reqs command can check
installed package platform requirements. It does not prove that customer
journeys work or that a different serving runtime meets those requirements.

4. RECOVERABLE COPY AND CHANGE ARRANGEMENT
Backup owner, private location and last verified time:
Code, database, uploads and configuration included:
Test environment available:
Customer emails, payments and production webhooks isolated from testing:
New records to preserve during release or database recovery:
Supported target runtime and dependency work needed:
Repair or maintenance scope:

5. ACCEPTANCE AND HANDOVER RECORD
For each relevant action, record environment, time, expected result and outcome.
Website page and application health:
Customer sign-in and permissions:
Enquiry -> inbox or saved record:
Booking or order -> expected record and confirmation:
Upload -> stored item and correct access:
Supported test-mode payment -> expected payment and order result:
Scheduled job -> expected execution and result:
Connected service -> expected record without duplicates:

Deployment instructions stored with the authorised code:
Backup and runtime maintenance responsibility:
Checks to repeat after future changes:
Outstanding work or unverified assumptions:
One-off task completed or agreed ongoing support scope:

GET HELP
https://turingwebsites.com/contact?enquiry=custom-php-support#enquiry

PRIMARY REFERENCES
https://www.php.net/supported-versions.php
https://getcomposer.org/doc/03-cli.md#check-platform-reqs