Websites
Radon Mitigation Estimate Form: What to Ask Before a Contractor Reviews the Property
Build a practical radon mitigation estimate form that collects property, testing and timing context without asking for unnecessary medical information or promising a final price.
Overview
A radon mitigation estimate form should collect property information, not panic.
The visitor may already have a test result. They may be in the middle of a home purchase. They may have an older mitigation system. Or they may simply want to understand whether the contractor serves their area and what happens next.
A good form gives the company enough context to review the request while keeping three boundaries clear:
- an enquiry is not a final system design;
- a submitted number is not a medical diagnosis;
- an online estimate request is not automatically a guaranteed price or appointment.
Start with the decision the contractor needs to make
Before adding fields, define the first internal decision.
For many radon contractors it is something like:
“Is this property in our service area, is the request within our services, and what information do we need before we can estimate or schedule the next step?”
If that is the decision, the form should collect information that supports it and avoid unrelated detail.
Contact fields
Name
Ask for the homeowner, buyer, seller, agent or other contact responsible for the enquiry.
Email is useful for confirming the request and sending next-step information.
Phone
Phone can be valuable for time-sensitive real-estate work. Make it required only if the company actually uses phone contact during the first review.
Relationship to the property
This optional field can help distinguish homeowner, buyer, seller, landlord, property manager or real-estate professional. Do not ask for unnecessary legal details.
Property fields
Property address or service location
A contractor usually needs enough location information to confirm service area and understand the property context.
If the first step only needs a ZIP code or city, asking for a full address may be unnecessary. Match the field to the business process.
Property type
Useful options may include:
Only include categories the contractor actually serves.
- single-family home;
- townhouse;
- multifamily property;
- commercial property;
- other.
Foundation / lower-level context
Depending on the company’s process, an optional field can ask whether the property has a basement, crawlspace, slab or mixed foundation.
The visitor may not know the right answer, so always allow “not sure.”
Approximate size or levels
Some contractors use home size or number of foundation areas as early estimate context. Ask only if it is genuinely useful before site review.
Existing radon information
Has the property been tested?
Use a simple yes / no / not sure choice.
This is often more useful than immediately forcing the visitor to provide a number.
Most recent result, if known
If the contractor wants the measurement as context, make it optional and label the unit clearly.
Do not have the website diagnose the result. The form is collecting a customer-supplied value, not validating the test method or providing health advice.
Test date
An optional test date can help the contractor understand how recent the information is.
Who performed the test?
Ask this only if it changes the contractor’s workflow. In many cases the report itself can be discussed later.
Existing system fields
Is a mitigation system already installed?
This separates new installation enquiries from repair, replacement or evaluation requests.
What is the issue?
If the company services existing systems, useful options may include:
Do not offer these choices if the company does not provide those services.
- fan not running;
- noise or vibration;
- system inspection;
- fan replacement;
- post-mitigation concern;
- other.
Timing fields
Is this connected to a real-estate transaction?
A yes/no field can help identify genuine deadlines.
Important date
If there is an inspection, contingency, closing or move-in deadline, allow the visitor to provide it.
Make clear that entering a date does not guarantee availability.
Preferred timing
Ask for general preference rather than presenting live appointment slots unless the business actually supports and wants direct scheduling for this service.
Short project description
A free-text field lets the visitor add details that do not fit the structured questions.
Keep the prompt focused on property and service context, for example:
“Tell us anything that may help us understand the property or the service you are requesting.”
Do not invite the visitor to submit medical histories, symptoms or unrelated personal information.
What not to ask
A public radon estimate form usually does not need:
The contractor is estimating a property service. Collect the minimum information needed for that service conversation.
- medical diagnoses;
- smoking history;
- family health history;
- symptoms;
- Social Security numbers;
- financial account information;
- passwords or access credentials;
- unrelated demographic information.
Should the form ask for the radon report?
That depends on the company’s real document workflow.
A report can be useful, but a public form does not need to become the permanent record system for environmental documents. If the business has an approved way to receive reports after initial contact, explain that the team may request the report during follow-up.
OneStudio’s current public pages document contact forms and enquiries. They do not document a specialized environmental-testing document repository. Keep the initial enquiry aligned with the documented product scope. See OneStudio pricing.
A lean estimate form example
For many contractors, a first-stage form can be compact.
Contact
- Name
- Phone, optional or required according to the real workflow
Property
- Service address or ZIP code
- Property type
- Foundation type, optional
Radon context
- Tested? Yes / No / Not sure
- Most recent result, optional
- Test date, optional
- Existing mitigation system? Yes / No / Not sure
Timing
- Real-estate transaction? Yes / No
- Important date, optional
Request
That is enough to begin many conversations without pretending to produce a final engineering decision online.
- Service needed
- Short description
A repair-focused version
If the contractor also services existing mitigation systems, the form can branch conceptually around a different question:
Existing system
Do not ask for technical values the homeowner cannot reasonably know.
- Approximate system age, if known
- Fan running? Yes / No / Not sure
- Visible issue
- Last known test result, optional
- Preferred contact timing
Explain the next step beside the form
People are more comfortable submitting when the page explains what happens next.
A plain-language note can say that the team will review the property and test context, confirm whether the address is in the service area, and then contact the visitor about the appropriate estimate or scheduling step.
If an on-site evaluation is required before final pricing, say so.
If the company can provide pricing from supplied information, say what information is required.
Do not promise “instant quote” unless the quote is genuinely generated and binding according to the business’s process.
Keep estimate language separate from booking language
Some services can be booked directly. Variable-scope mitigation work may need review first.
If the company cannot confirm scope, price or availability until a person reviews the property, label the CTA “Request an estimate” or “Request a consultation” rather than “Book installation.”
This keeps the website aligned with the real operation.
How client records can help after the enquiry
Once an enquiry becomes a real client relationship, keeping contact information and interaction history together can reduce scattered notes. OneStudio’s Business plan currently includes CRM/client base functionality, while Site includes contact forms and enquiries. Review OneStudio features and OneStudio pricing for the current plan boundaries.
Do not describe that CRM as environmental compliance, test-result management, field-service dispatch or a specialist radon record system.
Privacy and trust checklist
Before publishing the form, confirm:
- every required field is needed for the first decision;
- health information is not requested;
- test-result language is neutral and non-diagnostic;
- the page does not guarantee a specific mitigation outcome;
- the page does not imply a final price before review when one is not possible;
- service-area information is accurate;
- the company’s phone and email are current;
- form submissions reach the right person;
- the confirmation message explains the next step;
- the mobile version is easy to complete.
Make the form a calm first step
The best radon estimate form does not dramatize the situation. It gathers the facts the contractor needs, protects the visitor from unnecessary data collection and makes the next step clear.
For an owned website and enquiry path, review OneStudio features and OneStudio pricing for the capabilities currently documented by OneStudio.
Questions businesses ask
Should the estimate form require the latest radon reading?
Not always. A result can be useful context, but some visitors will not have one or may not know whether an old test is relevant. Allow the contractor’s real process to determine whether the field is required.
Should the form ask whether someone in the home has health problems?
A normal mitigation estimate generally needs property and service information, not medical history. Keep health questions out of the public estimate form unless a legitimate, reviewed process specifically requires them.
Can the website give a final mitigation price automatically?
Only if the business truly has a verified pricing model that can do so from the information collected. Otherwise, present the form as an estimate request and explain that final scope and price follow review.