"Can you update the services page?" is a reasonable way to start a conversation. It leaves the writer or developer needing more information before they can make the edit. A website change request template helps you supply that information once, without turning a small correction into a long project brief. Begin with the page address and the result you want.
Replace a Vague Request With an Editable One
Imagine the business has stopped offering a weekend appointment. The useful request identifies the wording, its location and the places the change should also reach. Here's an example you can adapt:
Page: [exact URL]. Section: appointment information. Current wording: [paste the sentence]. Replace with: [approved sentence]. Reason: the weekend option is no longer available. Please also check the booking link and any shared notice that mentions it. Done when the new wording is visible and the booking route matches it. [Person] will approve the preview.
That message gives the person doing the work a way to finish and check the edit. It doesn't require you to explain how the site is built.
Include the Details the Edit Needs
A sentence on one page and a phone number used across the site are different jobs. Tell the developer whether you mean one location or every appearance of the business detail. They can then identify the shared source and the places that need checking.
If a screenshot helps, mark the relevant area and remove private information. Include the URL as well; the screenshot may not show which version or page you were looking at.
For copy, label the approved replacement clearly. If you want a draft, say so and supply the facts it must reflect. Several versions attached to one email are hard to act on unless someone names the one that is approved.
For a photo or download, provide the original file through the agreed upload method. Explain where it belongs, which file it replaces and any credit or usage restriction. A screenshot of an image in an email may leave the website team without a suitable source file.
For a button change, include the destination and the action the visitor should take there. A calendar change can also affect the surrounding explanation and confirmation text. That is why a short reason for the edit helps the person implementing it.
Keep passwords and customer records out of the request. Arrange necessary access through the normal secure route.
Keep the Request as Short as the Job Allows
For a one-line correction, a URL and an approved replacement may be enough. For a more involved change, use these labels:
- Page and section.
- Current content and approved replacement, or a drafting brief.
- Supporting files and destination links.
- Reason and any real deadline.
- What should work when it's finished, and who approves it.
Ask for a preview when the edit affects an important customer step. After publication, check the public page against the request. If you are sending a change to us, put the URL first and describe what the customer should see or be able to do afterward. That is a useful starting point for the work.
Related Guides
Drafted with AI assistance.
