WebCareShelf.Sample report ↗

A FREE RESOURCE FOR WEBSITE BUILDERS

A clearer website handoff.

Before you hand over a site or finish a change, leave a record of what you checked. This checklist helps you separate an observation from an assumption. Use it with your existing tools; buying SiteWatch Local is optional.

Download the text checklist Read the checklist

By WebCareShelf · 17 October 2026 · No email address or signup required. You may use and adapt the checklist for your work and clients without attribution. Your browser’s Print command also produces a clean copy.

What this covers: a practical handoff record, HTTP responses, TLS certificate expiry and repeatable snapshots. It is not a security audit or proof of continuous uptime. Functional checks such as forms and checkout still need their own verification.

  1. Agree on the scope

    • List the exact public HTTPS URLs you are authorized to check. Include important pages, rather than assuming the home page represents the whole site.
    • Record which domain and environment you are checking: production, staging or another authorized target.
    • Write down what is outside the check, including login, forms, payments and third-party services.

  2. Capture a baseline before the change

    • Save the capture time, URL and HTTP response. Note any redirects and their final destinations.
    • Record the TLS certificate expiry and whether normal certificate verification succeeds.
    • Keep the original result in its own folder. A screenshot or report is a record of that moment, rather than a guarantee about the next visitor.

  3. Repeat the same check afterwards

    • Check the same original URLs after the deployment or DNS change, and record another timestamp.
    • Investigate a changed status, unexpected redirect or certificate warning before marking the work complete.
    • Preserve both captures. State what improved, deteriorated or remained unchanged only when both observations are known.

  4. Keep unknowns visible

    • If a request times out or cannot resolve, record it as unknown and investigate the URL, DNS, network and certificate.
    • Compare with an ordinary browser when a server blocks an automated request. A blocked client is not by itself proof that the website is down.
    • Do not turn off certificate verification just to obtain a successful result. Record the problem and fix its cause.

  5. Check the actual customer journey separately

    • Open the important pages in desktop and mobile layouts and check navigation and readable content.
    • Verify forms, authentication and any checkout flow using the appropriate authorized test environment. An HTTP200 response does not prove those functions work.
    • Agree who will monitor the site after handoff if ongoing monitoring is required. A manual snapshot does not provide scheduled checks or alerts.

  6. Leave a useful handoff note

    • Include the URLs, before/after timestamps, results, known limitations and unresolved items.
    • Tell the recipient which observations need investigation and who owns each next action.
    • Remove passwords, tokens and unnecessary personal information before sharing reports. Share only with authorized recipients.

A simple record you can copy

Website / environment:
Authorized URLs:
Before capture (UTC):
After capture (UTC):
HTTP / redirect changes:
TLS expiry / verification:
Unknown observations:
Functional checks performed separately:
Unresolved items and next owner:
Saved report locations: