What to Send a Developer for a Small Website Update
You know what needs changing on your website. The phone number is wrong, a button goes to the wrong place, or the new service still has not made it onto the page. Then you sit down to ask for help and wonder how much explanation a developer actually needs.
A useful website update request does not require technical vocabulary. It needs enough information to identify the page, understand the desired result, and agree on the work. You can leave the diagnosis to me.
Here is what I would like to see when you send a small website change brief, along with a checklist you can copy at the end.
Start with the exact page address
Send the URL of the page where the change belongs. If the problem appears in a menu, footer, or other shared section, tell me whether you have seen it on several pages.
“The staff page needs updating” is a starting point. “On this page, replace Alex’s bio with the attached copy and remove the old headshot” gives me something concrete to review.
A shared component can turn one visible change into a sitewide change. That may be exactly what you want, but it is useful to know before editing the template behind it. If you only want one page changed, include that detail too.
Describe what happens now and what should happen instead
For a content update, describe the replacement. For a problem, describe the behavior you can observe. “The contact form shows a success message, but our office does not receive the email” is much more helpful than guessing which plugin is responsible.
A good request might say: “On my phone, opening the menu covers the Request an Appointment button. I need visitors to be able to use that button after closing the menu.” That explains both the symptom and the business purpose.
If the problem comes and goes, say when you last saw it and what you were doing. Being logged in, using a saved browser tab, or visiting a different version of the domain can change what someone sees. You do not have to test every possibility before asking.
Include screenshots and the device you used
A screenshot helps with spacing, overlapping content, missing images, and awkward mobile layouts. A short screen recording can be better for a menu that opens and closes unexpectedly or a sequence of steps that leads to a problem.
Include the browser and device if you know them. “Safari on my iPhone” is enough to start. If you know the browser version or the approximate screen width, include it, but do not delay the request to find those details.
Keep unrelated personal information out of screenshots. A cropped view of the affected website section is usually more useful than an image of your whole desktop and inbox.
Send the final copy and the right files
If a paragraph needs replacing, send the exact approved wording. If a new team member needs adding, send the name, title, bio, photo, and where they should appear. Mention whether an existing page is a suitable layout reference.
For images, the original file is generally a better starting point than a screenshot of an image inside a document. Tell me what it shows and any important cropping instructions. If the image needs selecting or creating, make that part of the request.
Missing copy and unclear approvals can hold up a straightforward edit. It is fine if some pieces are still being prepared; just identify which parts are ready and who will approve the rest.
Explain the deadline and the priority
A new phone number that starts receiving calls Monday has a different deadline from a team photo you would like refreshed sometime soon. Tell me the date and what depends on it so I can assess availability and scope.
If you have several requests, put them in order. A broken inquiry form usually deserves attention before a decorative adjustment. We can also identify the smallest useful change when a larger project cannot fit the available window.
Sending a request does not automatically reserve a slot. I will review the work and confirm the next step with you before billable work begins.
Arrange access after we understand the task
Keep passwords out of your initial message or the footer contact form. Once we know what needs doing, we can arrange appropriate accounts, invitations, or another secure way to provide the required access.
A page edit may only need website access. A theme change or hosting problem may require something different. You do not need to send every account you have in case one turns out to be useful.
It also helps to name the person who manages hosting, the domain, or any third-party form integration. Knowing who can approve access avoids a search through old accounts halfway through the job.
Agree on the work and the decision points
My standard rate is $120/hour USD, billed in 15-minute increments. Before starting, we discuss the scope, estimate, and any assumptions about the existing website.
An unfamiliar problem may need an agreed investigation budget before I can estimate the repair. If the first task reveals additional work, that should lead to a conversation about the next step.
For more detail on budgeting, read what affects the cost of small website updates. This request checklist is about helping us understand the job, rather than promising a particular repair time.
A website update request you can copy
- Page URL: where the change or problem appears.
- Current situation: what the page says or does now.
- Desired result: what you want visitors to see or be able to do.
- Supporting material: approved copy, images, screenshots, or a recording.
- Device and browser: especially for a layout or behavior problem.
- Deadline and priority: when it is needed and what depends on it.
- Approval contact: who can answer questions and review the finished work.
You can use this for a single edit or a short to-do list. If you are unsure what is causing the issue, describe the result you need and we can work from there.
I handle small website updates and repairs for businesses and agencies. Tell me what needs changing, and include whatever details you already have.