8 Questions Before a Free Solar Assessment Campaign

“Free solar assessment” can describe anything from a two-minute phone qualification to a reviewed site and usage screen. Advertising the phrase before defining the deliverable creates a gap that copy, automation, and sales staff fill differently. The visitor expects analysis; the team may expect only a lead.

Resolve that gap before buying traffic. A responsible campaign states what is assessed, from which evidence, by whom, for which decision, and with which limitations. It delivers useful value even when the visitor does not buy.

The following eight questions form a launch review. A campaign that cannot answer one should pause that part of the promise rather than cover the gap with broader copy.

1. Define “assessment” for this campaign

Write the deliverable as a noun and a decision. Examples include a bill-readiness checklist, preliminary remote site screen, production-assumption review, quote-comparison intake, or consultation-preparation memo.

Avoid outputs whose names imply greater authority than the process. A remote roof view is not a site survey. An automated layout is not an engineering design. A calculator output is not a quote. A sales call is not a financial review.

Define the release status:

Put the definition on the advertisement, landing page, form, confirmation, and output. Do not let “assessment” become “analysis” in one channel and “quote” in another.

If no substantive artifact or decision support is delivered, call the offer a consultation. Clear naming may reduce clicks from people seeking instant results, but those clicks were based on a different service.

What must a free solar assessment deliver to the visitor?

A free solar assessment must deliver the decision support promised in the advertisement: a named artifact or scoped conversation, the evidence used, default status, findings the process can support, open conditions, correction path, and next action. It must remain useful without a purchase. “Free” describes price, not depth, so the page must define what has and has not been assessed.

Build the artifact before the advertisement. If the assessment is a remote site screen, create the actual property, source, imagery, preliminary-status, and open-condition sections. If it is a bill-readiness review, create the period, unit, meter, missing-record, and next-step sections. The deliverable controls the claim, form, staffing, and capacity plan.

Use a promise-to-delivery contract:

The assessment may end with “insufficient evidence for this output” when it explains why and gives a useful recovery. That is a valid deliverable. A fabricated report is not. A company that cannot produce a substantive artifact consistently should advertise a consultation and explain its preparation instead.

Connect public value to the free solar resource framework. Some visitors need a bill worksheet, site-readiness guide, or quote table before an assessment makes sense. Let them use that resource without forcing an application for a service they are not ready to receive.

Keep sales follow-up visible but separate. The page can say that the assessment is commercially provided and that the company will offer a related service. It should not make a hidden call, subscription, partner contact, or data transfer the price of an artifact described as free.

Test the standalone output. Give it to a target reader without the landing page and ask what was assessed, which evidence controlled it, what remains open, and what happens next. If they infer a final design, quote, savings guarantee, approval, or eligibility decision beyond the contract, revise the output before buying traffic.

2. Name the audience and decision it serves

A homeowner researching basic solar, a household comparing quotes, and a commercial facility preparing interval data need different assessments. Broad targeting forces a generic output or an excessive form.

Define property type, geography, project stage, decision role, and question. State excluded or separately routed cases. Do not infer qualification from neighborhood, surname, device, or purchased characteristics.

The Department of Energy homeowner solar guide spans site suitability, bids, financing, contracts, and installer selection. Choose one stage for the campaign and link to public education for others.

Write the job: “When ______, the visitor wants to ______, so they can ______.” Then remove questions and promises that do not serve it.

Set a respectful outside-scope path. Explain that the campaign does not cover the request, give a relevant official or educational source when available, and avoid retaining unnecessary data. Silence or an endless nurture sequence is not qualification.

3. Classify required, optional, and offline evidence

List each output claim and the evidence needed to support it. A site-specific screen may need a reliable location and usable remote source. A usage review needs dates, units, meter scope, and known load changes. A financial scenario needs far more than monthly bill cost.

Classify form inputs:

• Required now: without it, the named deliverable cannot be produced.
• Useful now: improves the output but can remain open with a visible limitation.
• Required later: needed before a later project release, not before this campaign output.
• Do not collect: unrelated to the promised assessment or unsafe to handle in this flow.

Let the visitor say “unknown” and change the output status. Do not fill missing project data with hidden defaults. If an illustrative default is pedagogically useful, label and expose it.

Explain safe collection. Do not instruct a homeowner to climb a roof or approach electrical equipment. Offer qualified site review for evidence that cannot be gathered safely or reliably online.

4. Specify what the visitor receives and when

Show a sample with invented-project labeling and no attractive outcome claim. List sections, delivery channel, review status, source date, and the event that starts delivery. If a person reviews the submission, name the role and scope.

Set timing from measured capacity. An automatic acknowledgment can be immediate, while a reviewed output depends on queue, operating hours, data quality, and exception handling. Do not advertise “instant” when a human review is material, or “same day” without retained evidence across the stated scope.

Define failed-delivery behavior. An unreadable upload, unsupported property, missing bill period, or conflicting address should produce an evidence request or alternate resource, not a fabricated report.

The output should remain useful without a sales call. If explanation genuinely requires a conversation, say the deliverable is the scoped consultation and provide preparation material beforehand.

Carry the exact input summary into the receiving record. The visitor should not repeat the form while the representative improvises a different assessment.

5. Set the campaign’s substantiated claim boundary

Review the complete impression: ad, keyword, imagery, badges, form labels, calculator, result, CTA, email, call script, and retargeting. A small disclaimer does not correct a headline that promises savings or approval.

The FTC advertising guidance provides U.S. principles on truthful, non-misleading, supported claims. Apply relevant rules in every market with qualified review.

Bind every number, date, percentage, price, timeline, performance statement, and regulatory claim to current evidence or validated code. Do not claim a universal response speed, accuracy, conversion result, approval rate, or customer outcome without retained support.

Separate design layers. A layout does not prove production. Production does not prove bill savings. A financial scenario does not prove suitability. None proves engineering, authority, lender, insurer, or utility approval.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

The FTC consumer solar article encourages scrutiny of claims, payment arrangements, contracts, and installer identity. Make those checks easier rather than using “free” to accelerate past them.

6. Design data, consent, and communication handling

Map every field from collection through vendors, analytics, storage, review, CRM, messaging, retention, correction, deletion, and incidents. Addresses, utility records, property images, financial information, and operating data can be sensitive.

The NIST Privacy Framework can structure privacy-risk management. It does not certify the campaign or replace jurisdiction-specific analysis.

Separate states for delivering the requested assessment, human response, appointment reminders, promotional email, calls, texts, and partner contact. The FCC telemarketing and robocalls page provides official U.S. context for calls and texts. Requirements vary, so review the actual channel and market.

Do not preselect permission or require an upload when a checklist can serve the decision. Keep sensitive values out of advertising pixels, URLs, subject lines, and session replay. Let visitors review the record before submission and provide a correction path.

State the commercial purpose plainly. “Free” should mean no fee for the defined assessment, not absence of a sales motive. Tell the visitor what follow-up follows and let them decline unrelated promotion.

7. Assign routing, review, and exception owners

Name the operational owner for each campaign path. A marketer owns the ad, but a design question, document conflict, privacy request, complaint, safety mention, or existing-customer issue needs a different role.

Create a routing table with trigger, owner, evidence, response boundary, and escalation. Do not let one lead score override exception rules.

Set capacity before traffic. Estimate from measured handling time and current staffing using validated planning tools, then clamp spend when the queue exceeds the promised service. Do not publish an unsupported capacity number.

Reviewers need the exact campaign output, source record, defaults, open conditions, and consent state. A CRM note saying “free assessment lead” is not enough.

Test handoffs with submissions that are incomplete, contradictory, outside territory, duplicated, opted out, or already customers. Confirm that the correct sequence stops and the responsible person receives the case.

Use the production-estimate answer guide for modeled-output questions and solar lead response automation for deeper routing design. The campaign brief should not try to answer every downstream issue.

When the promised assessment includes a financial scenario, document where the generation and financial analysis workflow ends and where project-specific validation begins.

8. Define the outcome that justifies continuation

Define the campaign’s task and harm measures before launch. Form count and cost per lead can reward broad promises and unready submissions.

Track:

Segment by ad, audience, assessment type, geography, device, and output status where lawful and useful. A broad educational campaign should not share a booking benchmark with a proposal-review campaign.

Set pause rules for unsupported claims, delivery failure, queue breach, bad routing, consent defects, source expiry, or elevated complaints. Marketing spend should not continue while the promised assessment is unavailable.

Treat self-selection as a possible success. A visitor may learn that a different resource, later timing, or another provider fits. Evaluate visitor task completion alongside sales progression.

Run a prelaunch simulation

Create test cases for ideal evidence, missing bills, wrong address, stale imagery, planned roof work, commercial property, unsupported location, contradictory documents, no upload consent, accessibility needs, opt-out, and a possible service or safety issue.

Walk each case through ad, page, form, result, email, CRM, review, and follow-up. Confirm labels and qualifications survive mobile layouts and downloads. The W3C forms tutorial supports accessible labels, grouping, errors, and feedback.

Recalculate displayed numbers in code. Extract Class A claims independently and bind them. Check every external source and internal route. Inspect analytics for sensitive data.

Ask a target reader what they think “free assessment” means after seeing the ad and result. If their answer exceeds the defined output, change the campaign before launch.

Build the sample deliverable before writing the advertisements

Campaign teams often approve the headline while the assessment output is still an idea. Reverse that order. Produce a complete sample for a clearly labeled fictional project, run it through review, and use its actual contents to write the promise.

The sample should include:

• the assessment purpose and status;
• input inventory with supplied, inferred, default, and missing states;
• source names and observation dates;
• the narrow findings the process can support;
• open questions and their consequence;
• the next review, including who owns it;
• commercial disclosure, privacy context, and correction route.

Remove any section that cannot be delivered consistently at campaign scale. If the sample includes an annotated roof but the operational team cannot review imagery for every eligible submission, either limit volume, change the service, or remove that promise. Do not call a generic automatic screenshot a reviewed annotation.

Create two failure samples as well. One should show a submission that lacks a controlling input. The other should show an outside-scope case. Both need a useful response and honest next path. These examples stop the product team from treating only successful generation as a valid campaign outcome.

Check the sample on a phone, in an email, as a downloaded file, and inside the sales view. Source labels and limitations should survive each format. If a channel cannot preserve them, narrow the claim used there.

Give the sample to a responder without background. They should be able to state what was assessed, what remains open, and what to ask next. If they interpret the report as a final design or quote, the deliverable needs revision before traffic.

Plan budget and capacity around completed assessments

Media planning commonly starts from cost per form submission. A free assessment has delivery work after the form, so the useful unit is a completed, quality-checked assessment of the promised type.

Map the operational stages: intake validation, source retrieval, automated processing, exception triage, human review where promised, artifact delivery, correction, and follow-up. Measure handling time and failure rate from a pilot. Use code to model capacity from those measured inputs rather than publishing a number calculated from memory.

Reserve capacity for exceptions. Averages conceal the submissions that need manual correction, language support, accessibility assistance, privacy handling, or technical routing. If the team fills every hour with ideal cases, the campaign will miss its own promise when ordinary variation appears.

Tie media controls to queue status. Reduce or pause spend when the oldest eligible submission approaches the disclosed boundary, when reviewer availability changes, or when a required source or service fails. Keep ads from sending people into an unavailable offer.

Do not lower review quality to protect acquisition metrics. If the campaign becomes viable only by removing the review described to visitors, change the promise and obtain fresh approval before resuming.

Budget for correction and maintenance too. A model source, form logic, output template, policy, or routing rule can change after launch. The campaign owner needs resources to retest it, not only to buy more traffic.

How should a team set capacity before funding a free solar assessment campaign?

A team should set capacity from handling stages, eligible-case mix, reviewer availability, correction work, and the delivery boundary promised to visitors. Pilot the complete service first, measure it with tools, and use retained inputs in a capacity model. Tie media spend to queue health. Do not publish a response-time or volume promise derived from memory, ideal cases, or vendor benchmarks.

Map every piece of work after submission. Intake validation, source retrieval, automated processing, exception triage, human review, artifact delivery, correction, privacy or accessibility support, and first response may involve different owners. A campaign can generate forms faster than it can complete assessments.

Use this planning process:

1. Define one eligible assessment type and the exact completion state.
2. Run labelled pilot cases through ordinary and exception paths.
3. Measure handling and waiting through the organization’s approved method, preserving the case type and owner.
4. Identify bottlenecks, unavailable roles, source dependencies, and rework causes.
5. Build the capacity calculation in code with declared units and measured inputs.
6. Reserve room for correction, privacy requests, accessibility support, and source or system failure.
7. Set internal media clamps from queue state and the disclosed service boundary.
8. Recalculate after material changes to offer, traffic mix, staffing, model, or review depth.

Do not publish the calculation in the article or campaign unless it has current first-party evidence and appropriate review. The public statement may simply describe the response sequence and say that timing is confirmed after intake. Internally, the team needs enough detail to reduce spend before the promise becomes unavailable.

Illustrative workflow example, not a customer result: A pilot reveals that ordinary bill-readiness cases move through the planned steps, while files with unclear periods require a separate correction loop. The campaign team keeps both paths in the capacity model and makes the deliverable promise conditional on usable evidence. When the correction queue reaches its internal clamp, media pauses. The team does not report a public turnaround statistic or hide the exception work to protect acquisition metrics.

Capacity controls belong in campaign operations, not only a dashboard. The media owner needs a stop signal, the assessment owner needs queue visibility, and responders need an honest message when the service cannot meet its normal path. Never lower the promised review quality silently to keep ads running.

Review ad-to-output continuity across every channel

Create a promise matrix with rows for search ads, social ads, organic posts, partner placements, landing-page headlines, form labels, confirmation messages, outputs, call scripts, and retargeting. Record the exact assessment claim and qualification in each.

Look for gradual inflation. “Preliminary site screen” may become “solar assessment” in the landing page, “custom design” in email, and “your savings plan” in the call script. No one line created the full overclaim, but the visitor experiences the sequence as one service.

Check imagery. A completed customer project beside an automated assessment can imply that the visitor’s result has passed later stages. Use an accurately labeled interface or illustrative process image instead. Do not use authority, utility, certification, or partner marks without current permission and evidence.

Partners need the same controlled copy, target rules, disclosures, and stop signals. Prohibit them from adding unsupported incentives, deadlines, results, or “government program” language. Audit live placements rather than assuming the approved file was used.

Retargeting deserves special attention. A person who opened a checklist but did not submit may receive an ad that says “your design is ready.” That message invents state. Retarget only from observable actions and keep the claim within what actually occurred.

Operate a claim and source expiry calendar

Every campaign claim needs a ledger entry with exact wording, source, authority tier, jurisdiction, observation date, effective date, expiry, asset locations, and owner. Product capabilities should bind to the current product source of truth. Operational claims need measured first-party records. External rules and incentives need current primary authority.

Use event triggers as well as dates. A utility filing, regulatory change, finance-program update, product release, service-area change, reviewer-capacity change, or vendor outage can make a claim false before its scheduled review.

When a claim expires, identify every dependent asset and stop it. Updating the landing page while the old wording continues in partner ads and automated email is not a complete correction. Keep a distribution inventory and require owners to confirm removal.

Record the replacement evidence and what changed. Do not overwrite the old record, because existing leads may have received the earlier assessment. Their project history should retain the version and source set that produced it.

Treat “free” as a claim too. Confirm that the defined assessment has no fee and identify any later paid service without baiting the visitor. If a credit card, refundable deposit, purchase, membership, or another condition exists, the headline and offer terms must reflect it.

Audit the first live cohort before increasing spend

Review every assessment in a small initial cohort or use a risk-based sample appropriate to volume. Compare the ad promise, input record, output, review decision, delivery time, correction, consent, and first response.

Interview the receiving team. Ask which submissions were actionable, which evidence was repeatedly missing, where routing failed, and which output wording customers misunderstood. Interview willing participants about what they expected before submitting and what they believed the assessment proved.

Do not scale on conversion rate alone. Require a clean claim audit, acceptable delivery completion, functioning correction and opt-out paths, controlled queue, and no unresolved privacy or accessibility defect. Name the thresholds internally from the pilot and business risk rather than borrowing generic benchmarks.

If the cohort reveals a promise gap, pause, correct the artifacts, and decide whether earlier recipients need clarification. A campaign is not validated merely because the form acquired inexpensive contacts.

When should a free solar assessment campaign be paused?

A solar assessment campaign should pause when the advertised deliverable is unavailable, queue capacity exceeds its control boundary, evidence or model sources expire, routing fails, consent or privacy behavior breaks, accessibility defects block the task, claims become unsupported, or visitors receive a stronger impression than the output earns. Stop acquisition first, then repair the origin and review recipients and derivatives.

Pause is a service-control state, not a marketing embarrassment. Keeping traffic live while the promised reviewer, model, source, upload path, or output is unavailable creates a larger correction problem. The campaign can sometimes step down to a public resource or narrower consultation, but that change needs new approved copy and a complete continuity test.

Use a pause record:

CAMPAIGN, OFFER, AND VERSION:
AUDIENCE AND ASSESSMENT TYPE:
TRIGGER OBSERVED:
PROMISE OR OUTPUT AFFECTED:
NEW ACQUISITION STOPPED AT:
LIVE ADS, PARTNER PLACEMENTS, AND AUTOMATIONS:
ASSESSMENTS ALREADY IN QUEUE:
RECIPIENTS REQUIRING CLARIFICATION:
SOURCE, MODEL, ROUTING, PRIVACY, OR ACCESSIBILITY DEFECT:
OWNER AND QUALIFIED REVIEWER:
EVIDENCE REQUIRED TO RESUME:
RETEST CASES:
REVISED CAPACITY OR CLAIM BOUNDARY:
RESUME / NARROW / RETIRE DECISION:

Pause claims independently when possible. An expired incentive source may require removing the financial part of an otherwise useful site-readiness assessment. A broken upload can permit a no-upload checklist while document review is suspended. Keep the current page explicit about what remains available.

Inspect every acquisition surface. Search ads, social variants, partner placements, retargeting, landing pages, email, sales scripts, and saved templates can keep the old promise alive after the main campaign is paused. Require owners to confirm removal or correction instead of assuming a central copy change propagates.

Review queued cases under the promise they actually saw. Do not run earlier recipients through a narrowed process without telling them. Preserve their campaign version, consent, output status, and evidence. If the defect could have changed a material conclusion or communication choice, qualified reviewers must decide the correction.

Resume only after the source or service is restored, affected paths pass the controlled tests, queue capacity supports the stated boundary, and every channel carries the same revised claim. A cheaper lead or improving submission rate is not evidence that the campaign defect was fixed.

Write the launch contract

Summarize the audience, decision, deliverable, input gates, source set, model status, limitations, communication states, routing, capacity clamp, metrics, pause conditions, and content owner in one document. Version it.

Give ad buyers approved claims and prohibited variants. Give responders a decision brief and role boundary. Give reviewers access to sources. Give privacy, legal, accessibility, and technical owners a release check.

When a source, model, form, output, or routing rule changes, update the contract and retest affected paths. A campaign is a maintained service, not only a set of advertisements.

Frequently Asked Questions

What should a free solar assessment include?

The campaign should name the actual deliverable, such as an educational checklist, preliminary site screen, document review, or scoped consultation. State the inputs, reviewer, turnaround basis, limitations, and next step. Do not use “assessment” to imply a site survey, final design, savings guarantee, price, engineering judgment, approval, or eligibility decision that the process does not provide.

Can an assessment be free if it leads to a sales call?

Yes, when no assessment fee is charged and the commercial purpose and follow-up are clear before submission. Deliver the promised value and identify the publisher’s relationship. Do not disguise a qualification call as a technical assessment, invent a high-value report, or make continued promotional contact an undisclosed condition of receiving the stated output.

Which information should a solar assessment form collect?

Collect the minimum information needed for the named assessment and response. This may include the decision, site, evidence availability, known constraints, and preferred next step. Bills, interval data, photographs, financial details, and identity require a defined purpose and protected handling. Let visitors continue with a checklist when sensitive uploads are unnecessary.

How should a campaign describe preliminary solar results?

Label the output beside every result and identify supplied inputs, inferred data, defaults, source dates, model version, and open conditions. Separate layout, production, bill impact, financial scenarios, and approval. Use validated calculations for displayed results and keep the qualification attached in PDFs, email, mobile layouts, ads, and salesperson follow-up.

How should a company measure a free assessment campaign?

Measure completion of the promised assessment, usable evidence, correct routing, kept scoped reviews, progression to the defined next stage, corrections, unwanted contact, and complaints. Segment by audience and acquisition source. Form volume or cost per lead alone can reward vague promises, weak qualification, and follow-up that the visitor did not expect.