Care for the working website. Give its dependencies an owner.

Onboarding establishes the platform, hosting, domain, relevant licences, connected services and the people controlling them. Record known faults and missing access before ordinary care begins. The supported tasks might include approved text and media changes, suitable component updates, proportionate troubleshooting and checks of important visitor and editor journeys. The written arrangement states what is included and what requires a separate estimate.

The operating plan should explain how requests are approved, scheduled and checked. A planned update needs an appropriate recovery point and a review proportionate to the change. A request involving a new provider, additional feature or inherited technical problem may need investigation before a reliable implementation proposal is possible. Coverage, urgency and response expectations are agreed for the actual need.

Renewal work adds a commercial and account boundary. The business decides which dependency it wants to retain and who is authorised to approve payment or account changes. A support team can document an approaching date and help organise an approved action, but a reminder alone does not establish that the owner has renewed the service. Charges and third-party decisions remain explicit in the agreement.

Imagine a paid website dependency approaching its renewal date. Notices reach a previous account holder, while the current owner can see the public website but cannot confirm the account position. There may be enough time to resolve the ownership question, or an unavailable account may require a provider-specific process. This is a hypothetical care-planning example, not a Seattle incident or a claim of completed account recovery.

Identify the dependency, the account owner of record, the nominated business approver and the person able to perform the authorised renewal. Establish the relevant date and current status from an appropriate source. If access is incomplete, record that limitation and agree who will address it. Avoid treating a working homepage as evidence about a licence or billing state.

The business then decides whether to renew, replace or retire the dependency and approves the corresponding work. Record the observed account result and repeat the selected public journey checks afterward where relevant. If the action remains unresolved, the care report should say what is outstanding and who owns the next step. It should not mark the task complete because a warning was forwarded.

Share the website, known platform information and the tasks your team relies on. Identify who controls domain, hosting, paid components and connected services, with any existing renewal notices or access uncertainty described through an agreed secure process. Ordinary enquiry messages should contain context rather than passwords or customer records. Explain which routine updates you expect to request and who can approve them.

For Seattle work, agree request and review arrangements using America/Los_Angeles and Asia/Kolkata, with dated invitations showing the relevant local times. Any support hours, escalation contacts, provider costs and response targets belong in the actual agreement.