Different support needs, different scopes
These fictional examples show how website care can start with a concrete responsibility. They illustrate planning decisions and don’t describe completed Faith Forge Labs projects.
An enquiry disappears after submission
An equipment-hire business receives a customer's call about an unanswered request. The page displayed confirmation, but staff can’t find the message. The investigation must distinguish browser submission, application handling and delivery to the intended team.
A repair scope would collect the time and non-sensitive reproduction steps, inspect the relevant evidence and agree a controlled test. Acceptance would confirm the intended receiving path and useful failure feedback. Repeatedly submitting real customer details or changing several email settings at once would make the situation harder to assess.
A collection point changes address
A food producer moves its local collection counter. The contact page is updated, but an order-information page and printable collection sheet still show the old location. The request is a coordinated content correction, not a redesign.
The business would approve the address, effective date and visitor instructions. The implementation would review related pages, links and documents in context, including the handling of old download links. A named approver would confirm the final visitor journey before publication.
The only administrator leaves
A community association has a website with a functioning public programme, but provider notices go to a departing volunteer. The next committee knows the content system password yet can’t identify who controls domain renewal or backup access.
The first scope would map providers, business ownership and recovery contacts through authorized channels. Missing access becomes a documented action. A continuing care plan would follow the review rather than assume that logging into the editor establishes control of the whole site.
A hosting move overlaps with new submissions
A venue wants to leave its current host before renewal. Its enquiry records continue changing while a copy is prepared on the destination. A successful rehearsal doesn’t settle how those later records will reach the final site.
The migration plan would define the transfer window, treatment of new activity, connected email and scheduled work, verification and a retirement point for the old service. The business must understand any interruption or reconciliation required before approving the switch.
Explore the service directory or use the brief guide to describe your own situation.
