- Explain assessment
- Review evidence
- Protect inquiry
Make the company’s role clear before the offer
A visitor should understand the business behind the website and its role in a project. Sales, design, installation and ongoing support may involve different organizations. Use the arrangement the company verifies rather than implying every task is performed by one team for visual simplicity.
Organize the main navigation around actual services. Residential work, commercial projects and other confirmed offerings may require different explanations and inquiry routes. Do not populate a service grid with products the company does not currently provide.
Use verified credentials and partner references. A manufacturer logo or certification badge can create a strong impression, so the company should confirm both the fact and permission to display it. The design should remain complete and useful without invented proof elements.
Keep contact and service-area information easy to find. An owner should know how to reach the company and whether the project is within its confirmed scope. Do not use maps or addresses to imply staffed locations that have not been established.
Explain the assessment journey in concrete stages
Show what happens after an initial request using the company's actual process. A conversation, information review and property-specific proposal are different stages. Avoid a simplified graphic that makes a form submission look like a guaranteed approval or final project price.
Describe what the company needs at the first step and what is collected later. A basic inquiry may not require detailed utility or financial documents. The team should decide where sensitive information belongs and how owners are directed to the approved route.
Make the next action clear on each page. A service overview may invite a conversation, while an existing-customer page may provide a support contact. Using the same vague button everywhere can obscure those differences and send requests to the wrong team.
Write confirmations as part of the journey. The message should acknowledge the event that occurred and explain only the next step the company can support. It should not imply financing approval, incentive eligibility, project acceptance or a reserved installation date.
Give assumptions and qualifications a usable place
Solar evaluation depends on the property and proposed project. The Department of Energy's homeowner material identifies relevant variables, but a general guide does not establish a particular owner's result. The website should make the company's verified assessment process understandable rather than promising a universal outcome.
If the design includes an estimate or calculator, define exactly what it does. The company needs to approve its inputs, method, output and limitations. Do not make an illustration appear to be a current quote or a dependable savings forecast merely because it is interactive.
Place essential context where people encounter the associated claim. A prominent number should not rely on an obscure footer to explain that it is only an example. Review the complete layout, including mobile order and image text, with the appropriate technical and offer reviewers.
Keep incentive, tax, financing and utility-policy statements out until their exact current applicability has been verified. Official general pages can contain older examples. The design should accommodate reviewed information without assuming that every visitor qualifies for the same financial arrangement.
Use project evidence honestly
Build galleries from approved material and identify the company's actual role in each project. A photograph can show an installation without proving a specific production or financial result. Avoid adding numbers or success claims unless the company supplies support and approves their context.
Distinguish completed projects, illustrative renderings and stock imagery. A visitor should not mistake a concept for evidence of work already performed. Clear captions can preserve the value of a visual while preventing the design from implying more than the source establishes.
Review permission and private details before publishing. Project images may reveal addresses, people or other information the owner did not agree to share. Use only the material authorized for the intended public purpose and keep any restrictions attached to the asset.
Give testimonials a similar review. Permission to quote a customer does not establish that every implied savings or performance claim is supportable. The company should assess the overall impression, especially when a short quotation is placed beside a dramatic numerical graphic.
Build forms and interactions around a limited task
Choose fields from the agreed first-contact purpose. A project type, service location and contact preference may help route an inquiry. Avoid requesting account numbers, credit information or extensive documents simply because a form template includes those options.
Use clear labels and useful error messages. Test mobile entry and keyboard navigation, including correction of invalid information. A person should understand what is being requested and why without needing to call the sales team to decode a field.
Verify external destinations and any proposed technical connection. A redesign does not automatically integrate a proposal, finance or installation-management platform. Keep approved links accurate and assess new capabilities separately before making them part of the promised user experience.
Test failed delivery and incomplete requests. Do not show a completed assessment or booked consultation when the system only received a message or failed to send it. Provide the company's approved alternative contact route where appropriate and keep the confirmation truthful.
Make maintenance part of the finished design
Assign owners for service descriptions, project examples, offer terms and contact routes. Different kinds of information may require different reviewers. The website should have a practical update process that does not depend on one person remembering every place a claim appears.
Prepare a method for revising date-sensitive material. If the company changes an offer, review associated graphics, downloads and metadata as well as the main page. An outdated image can keep a misleading promise visible after the surrounding text is corrected.
Measure the site's actual role. Relevant inquiry delivery and clearer routing can be useful indicators, while assessments, agreements and completed installations require separate evidence. Do not present traffic or form volume as proof of customer savings or project revenue.
Dappr can scope the work remotely from its staffed St. George office using the verified offering, current systems and approved visual assets. A useful handoff gives the company reviewed pages, tested paths and clear remaining dependencies, so publication can be assessed on the complete experience.
Questions before you begin
Should a solar website include a savings calculator?
Only when its purpose, method, assumptions and limitations can be verified and approved. An interactive illustration should not be presented as a personalized quote or guarantee.
Can project images prove financial results?
A photograph alone does not establish production or savings. Use supported facts, permission and clear context for any result claim.
What should the first form collect?
Collect information appropriate to routing the initial inquiry. Review any sensitive utility, financial or document collection separately through the company’s approved process.
Can tax incentives be added from a general guide?
Verify the exact current program and applicability before publishing a claim. Even official broad resources may contain older examples.
What makes the website ready for review?
Provide accurate service roles, reviewed claims, tested forms and links, and update ownership. Identify unresolved technical and specialist questions before a publication decision.