A care or home-support website redesign brief should explain what needs to improve before it describes the new appearance. Visitors may struggle to understand the services, check coverage or work out how to enquire. Your team may find the site difficult to maintain. Those are different problems, and the proposal should address the ones that matter to your business.
A useful brief helps you compare suppliers, approve a realistic scope and understand what your team must provide. ARKIELLO’s website and SEO service for care and home-support businesses connects those decisions with content, local discovery and the enquiry journey.
Describe the business and the problem
Start with your website address, platform, main services and actual operating areas. Explain who usually enquires: the person seeking support, a family member or another contact. Describe the decisions those visitors need to make without assuming everyone arrives with the same knowledge.
Then name the concern. For example, service descriptions may be unclear, the mobile form may be awkward or important updates may require developer help. Use available enquiry feedback and reliable data to support the brief. Separate what you know from what you suspect.
Consider a focused improvement before a rebuild
A new website is not automatically the answer to weak enquiries. If the platform works and the main issue is one confusing service page, a targeted content or form improvement may be enough. Explain what is working as well as what needs attention.
A broader redesign becomes easier to justify when structural, editing or usability problems affect several parts of the site. Our website redesign service starts with that distinction. Ask a supplier to explain why its proposed scope fits your problem.
Inventory the content you already have
List the pages, articles, images, downloads, forms and external tools the current site uses. Identify material to keep, improve, combine or retire. Record existing URLs so useful pages do not disappear accidentally during the build.
Clarify who will write new copy and who can approve service facts, credentials, imagery and testimonials. The website team should not guess the boundaries of your service. Obtain the appropriate approval for material before it is published, particularly when it identifies a client or family.
Define the questions each page should answer
Agree a page list before comparing visual concepts. Core pages may need to explain services, coverage, the organisation and how an enquiry works. Each should have a distinct purpose and a next step that suits the visitor’s decision.
Use our home-support website enquiry questions to identify information gaps. For coverage, the service-area page planning guide explains when a separate area page is useful. Do not turn a list of towns into an automatic requirement for dozens of similar pages.
Specify the enquiry journey and its owner
Document the form fields, destination inbox, confirmation message and any booking or enquiry tools. Decide who receives requests, how they are assigned and what visitors should expect next. Do not promise immediate availability or an instant booking unless the process actually supports it.
Keep the initial enquiry focused on the information needed to start a conversation. If a separate intake process is required, distinguish it from the public marketing form. Agree how the finished form will be tested, including an authorized test of delivery and the visitor’s confirmation screen.
Plan search continuity and measurement
Ask how existing URLs, page information and internal links will be handled. Keep useful addresses where practical. Where an address changes, agree an appropriate destination and a tested redirect rather than sending every removed page to the homepage.
List existing Analytics and Search Console arrangements, if any. Agree what the project will measure and who will verify it. A contact-button click is different from a completed enquiry, and an enquiry is different from a new client. Reports should make those distinctions clear rather than presenting every interaction as a business result.
Agree access, ownership and handover
Record who controls the domain, hosting, platform, accounts and paid integrations. Arrange appropriate access for the work without including passwords in the brief. Clarify who retains ownership and who can edit routine content after launch.
Ask what handover includes: editing guidance, documentation, technical support and any ongoing maintenance. A website delivered on a new platform may change your team’s responsibilities. Compare those responsibilities before choosing a platform, rather than assuming a move is necessary for every redesign.
Make launch criteria part of the proposal
A useful scope explains review stages, responsibilities and what must pass before publication. Include checks for:
- Approved service facts, coverage and imagery.
- Readable mobile layouts and usable navigation.
- Working links, images, forms and confirmation pages.
- Planned redirects and appropriate search settings.
- Agreed measurement and editing access.
- A named person responsible for final approval.
Ask about exclusions, changes of scope and support after launch. Our website redesign quote guide helps compare deliverables before comparing totals. Timing depends on access, content and approvals as well as production work.
Review relevant work before deciding
The Avelora Life project involved a Wix revamp, ten Alberta location pages and Google Business Profile, Maps, Analytics and Search Console work for an international client in Canada. It is an example of project scope, not evidence that every care business needs the same platform, page count or services. No particular ranking or enquiry result is implied.
Start with a clear brief
Send your website URL, services, actual coverage and main concern. Include any real deadline and what your team can supply. We can discuss priorities and a suitable scope before preparing a proposal. Discuss your care-business website.