Website planning
Who will update your website after launch?
Choose who will make website edits, agree on support, and use a simple checklist to keep changes clear after launch.
Decide who will update your website before it launches. The right arrangement depends on what changes, how often it changes, and who has time to keep it accurate. You might make routine edits yourself, send changes to your designer, or share the work.
Start by naming a person who will notice when information is out of date. Even with ongoing website support, someone inside the business needs to confirm a new price, approve a photo, or say when an event has ended.
Start with the changes you expect
Write down three changes you are likely to need in the next few months. Be specific: replacing holiday hours, adding a completed project, or opening registration for an event. That gives your designer something concrete to plan around.
Then ask how each change would happen. Who supplies the wording? Who puts it on the site? Who checks it afterward? How much notice does that person need? A handoff demonstration using one of your own examples is more useful than a general promise that the website will be easy to edit.
Choose an arrangement your team can maintain
Making your own edits can work well when information changes regularly and someone on your team is comfortable using the editing tools. Ask to try the actual task during handoff. Find out which areas you can change, how to preview an edit, and how to get help if something looks wrong.
Designer support may fit better when changes are occasional or you would rather send over the details and have someone handle them. Agree on how requests are submitted, expected timing, and what the support covers. A deadline that matters to your business needs to be discussed before the change is needed.
A shared arrangement can also make sense. Your team might update event dates and photos through an editor, while your designer handles new page layouts or features. Write down that division so everyone knows where a request belongs.
For the Grafton Education Foundation website, the redesign included dynamic content for recurring updates, alongside organized areas for grants, events, sponsors, and donations. That is a useful example of planning the editing setup around information the organization expects to change.
Clarify what ongoing support includes
Updating a sentence, adding a new page, and keeping the technical side running are different tasks. Before choosing a support plan, ask which are included and which need a separate quote. Use examples from your own website so terms such as “minor content updates” have a shared meaning.
G. Fritch Design offers optional managed hosting that includes hosting, security, technical maintenance, and minor content updates. The editing and handoff approach depends on the project setup. Discuss the work you expect to handle yourself and the support you want before the scope is agreed.
Your handoff notes should also identify who manages the domain and hosting, who handles renewals, and how your organization can obtain the access it needs. Keep those details available to the people responsible for the website, especially when staff or volunteers change.
Make an update request easy to act on
A useful request gives the person making the edit the final information and a clear place to put it. Include:
- The page URL and the section that needs to change.
- The exact replacement wording, including dates, prices, and contact details.
- The approved image and a short explanation of what it shows, if needed.
- When the change should go live and when it should be removed or replaced.
- The person who can confirm the finished update is accurate.
For example, imagine a nonprofit moving a fundraising event from one Saturday to another. In this hypothetical situation, the date appears on the homepage and event page, and the registration button opens a separate signup page. The request should name all three places and provide the new date, time, and registration link.
If the new details are still being decided, say so. The person editing the site should know whether the wording is final or awaiting approval.
Check the finished update as a visitor
After the change goes live, open the page on your phone. Read the new wording, check the image, and follow the relevant button or link. For the event example, confirm that the signup page agrees with the date shown on the website.
If a form was changed, include its success and error messages in the check. W3C accessibility guidance explains that people need clear feedback about whether a submission succeeded and how to correct a problem.
Before launch, you should be able to name who supplies changes, who publishes them, and who checks the result. Bring your likely updates to the project conversation so the website and handoff can support that routine.