- Organize services
- Clarify locations
- Test routing
Begin with what the current site no longer explains
A redesign is most useful when the problem is concrete. The service list may have changed, inquiries may reach the wrong person or customers may struggle to understand the next step. Identify those issues before choosing a new visual direction.
Davis County's economic-development resources include support for existing-business retention and expansion. That context is relevant to a company updating its public offer, but it does not establish what the website needs. Customer questions and staff experience should guide the brief.
List the main visitor tasks and the information required to complete them. A new buyer, an existing customer and a commercial prospect may need different routes. The design should make those routes understandable without exposing an internal organization chart.
Keep the regional service model precise
Explain where the business receives visitors, where it travels and what it provides remotely. A Davis County service statement should not imply branches in every community. If coverage differs by service, make that rule visible near the relevant action.
Local resources illustrate different contexts, from Kaysville business-support activity to Farmington station-area planning. Use those references only where they help explain a genuine operation. A city plan or program does not verify a company's address, availability or affiliation.
Dappr's delivery is remote from St. George. The same honesty should apply to client maps, photographs and location wording. Design should clarify the arrangement rather than create an impression the fine print later contradicts.
Create an approval process for changing content
Gather current service details, contact information, brand assets and approved photographs. Identify who confirms facts and who can resolve missing information. A visual approval does not establish that a claim or availability promise is true.
Write the core pages with real content before finalizing layouts. Long service names, important conditions and detailed explanations affect smaller screens. Placeholder copy can hide both design problems and unanswered business questions.
Use authentic evidence. A project example should represent real work and have permission. If the offer has changed, review older examples for relevance. Do not invent new results simply because the redesign includes a section intended for proof.
Route the request according to the service
The form should ask for enough information to direct the first conversation. A service choice may help routing, but unnecessary fields should not burden the visitor. Explain required information and what happens after submission.
W3C's form guidance supports clear labels, instructions and feedback. Apply those principles to field names, error states and confirmation. A person should understand how to correct a mistake and whether the request reached the business.
Test the receiving workflow with staff. If Dappr CRM is included, define assignments and stages in the scope. Do not call a requested appointment confirmed unless the system actually reserves it. The page and reply need to describe the same process.
Preserve useful access and prepare the handoff
Inventory important URLs before a redesign. Existing customers may use saved links, search results or messages shared by staff. Preserve useful addresses and document approved changes, then test the paths that depend on them.
Review responsive layouts, keyboard use, visible focus and the main customer actions with actual content. Keep essential information available without decorative effects, including a usable reduced-motion experience when animation is present.
Assign responsibility for updates after launch. Services, staff, hours and coverage can change again. A concise handoff should explain routine edits, approval contacts and how to report a broken feature. Dappr can build the site and the maintenance process around those needs so the redesign remains useful beyond its first review.
Keep a record of the approved service descriptions at handoff so later edits can be checked against the original operating decisions.
Questions before you begin
When is a redesign justified?
When the existing site no longer supports important customer tasks or accurately explains the business. Define that problem before selecting a visual direction.
How should we show expanded county coverage?
Explain the genuine territory and any service-specific limits. Do not imply additional offices unless they actually exist.
Can old project examples remain on the new site?
Yes, if they are accurate, approved and still relevant. Review them when services change rather than assuming every old example fits the current offer.
What should be tested in the inquiry process?
The interface, confirmation, actual delivery and staff routing. A form that looks correct may still fail operationally.
How do we keep the redesign current?
Assign owners for changing facts and implementation, with a clear update process and maintenance scope after launch.