Faith Forge LabsWebsite Maintenance
4 MIN READ

How to explain the website work you need

A broken form, a content update, and a hosting move need different preparation. Start with the change you want and the details you already know.

The brief is particularly useful when several people, providers or stages are involved. For a single initial concern, the first-request guide may be sufficient.

Name the immediate objective

State the outcome in terms of the website's responsibility. Examples include restoring an enquiry path, publishing a coordinated location change, establishing a maintenance routine or moving hosting before a provider deadline.

Separate immediate work from later ideas. A broken form and a future redesign can appear in the same planning document, but they shouldn’t become one undifferentiated project. The decision to restore the form can proceed on a different scope from the decision to rebuild the site.

Describe the present arrangement

Record the platform, hosting, domain, email and relevant external services to the extent known. Identify account owners and current maintainers without including credentials. Note missing access, undocumented customizations and any other supplier actively changing the site.

List known faults and recent changes. This establishes the starting condition for the work. If a new care arrangement excludes an existing issue, that exclusion should be visible with a next decision rather than silently treated as resolved.

Match the evidence to the kind of request

Request Useful starting evidence Acceptance should address
Repair Reproduction steps, time, expected result and observed failure Original task, related dependencies and remaining uncertainty
Content update Approved facts, affected pages/files and effective date Consistency, presentation, links and business approval
Ongoing care Components, important tasks, current gaps and owners Agreed activities, records, findings and response boundaries
Hosting move Providers, application requirements, data and connected services Transfer, continuing activity, final-host checks and old-service retirement

The table doesn’t replace a technical assessment. It helps avoid asking for the wrong deliverable, such as treating a successful file copy as proof that a migration is complete.

Identify the people who can decide

Name the content approver, technical contact, budget owner and person accepting the result. One person may fill several roles. If the usual contact is unavailable, establish who can make an important decision.

Provider involvement should be explicit. A maintainer may identify a host-controlled issue but lack authority to change the account or approve a new charge. Decide who contacts the provider, shares the necessary evidence and records the outcome.

Define the protected behavior

List the tasks and information that must remain intact. These may include enquiries, downloads, login, stored records, publishing or a connected business service. Focus on representative responsibilities rather than a vague requirement that “everything works.”

For a content change, include the meaning of the information and its related destinations. For a software change, include the operations the component supports. For a migration or restore, include how new activity is handled while the work is underway.

Establish testing and recovery boundaries

Identify the private test arrangement and any differences from production that limit the evidence. A copied application may need live notifications and integrations disabled or redirected before it can be exercised safely. The test plan should say which behavior will be simulated and which can be verified directly.

Record the recovery method and who authorizes it. Restoring a database can affect records created after the snapshot; reverting code may not reverse a data migration. The business must understand the consequences of the chosen path.

State coverage and commercial boundaries

Clarify included activities, provider costs, additional-work approval and communication expectations. If recurring support is requested, describe review and response responsibilities explicitly. Monitoring doesn’t by itself create repair coverage, and a general enquiry doesn’t establish an emergency service.

Timing should reflect the real deadline, access and dependencies. Uncertain provider actions should be recorded as uncertainties, not converted into a fixed promise without evidence.

Finish with the next decision

A brief can be complete enough to authorize an assessment even when the repair isn’t yet defined. State what that assessment will produce and who will decide whether to proceed. This creates a useful boundary around discovery.

Read planning a care transition or discuss the website and requested outcome.