CRM
What to ask in a landfill gas monitoring proposal form
Build a first-contact landfill gas monitoring RFP form around service type, site jurisdiction, existing program and responsible follow-up.
The job of a first-contact form is qualification
Landfill gas monitoring projects are not consumer appointments. A form should help the contractor identify the required service and whether the buyer has a defined monitoring program. It cannot determine regulatory obligations, certify safety or issue a valid quote by itself.
The buyer may be a municipal authority, a landfill owner, a consulting engineer, a remediation contractor or a procurement agent. Some have an established sampling plan; others need an exploratory conversation. Design for both. Do not reject the second group for failing to provide data they do not yet have.
A useful first screen for buyers
Use the headline Request a landfill gas monitoring proposal with one explanatory line: “Tell us your location and monitoring objective. Our team will review your requirements before confirming scope, schedule or price.”
Collect a named work contact, organization, work email and optional phone. Identify the broad site region or jurisdiction. This helps confirm operating area and relevant regulatory context without requesting a detailed site address prematurely.
Include a contact-preference field if the company's normal sales process can honor it.
Service selection that reflects real scopes
Use a simple choice of: perimeter or subsurface monitoring; surface emissions survey; gas collection or wellfield monitoring; sampling and laboratory coordination; program review; or Not sure.
Do not treat these as equivalent fixed-price products. A surface emissions request may require a different method, operating condition and field plan from a perimeter monitoring program. If the firm doesn't offer a listed service, it should not appear in the form.
Allow multiple selections only where team routing can handle mixed-scope projects. A free-text objective is often more useful than an excessively long checklist.
The context fields worth collecting early
Jurisdiction and program stage
Ask which state, province or country the site is in, and whether the task concerns a new program, continuing scheduled monitoring, follow-up of existing results, or procurement planning. Permit status can be “known,” “unknown,” or “to discuss.” The form should not interpret that answer as legal advice.
Broad site characteristics
Ask whether the property is an operating landfill, a closed facility, a development site influenced by landfill gas, or another setting. Distinguish the project category, not the entire operational layout.
A rough site-size band may be appropriate if the technical team uses it for scoping. If not, omit it. Don't invent a mandatory number of sampling locations or visits.
Existing program and materials
Ask whether a monitoring plan or relevant scope document exists, with Yes / No / Unsure. Do not require immediate public upload of permits, monitoring results or property records. The technical team can identify an approved channel for necessary documents during follow-up.
Timing and procurement
Request a desired start period, proposal submission deadline and expected contract model (one-time event or ongoing service), where known. The web form should not imply guaranteed availability, a fixed monitoring cycle or regulatory sign-off.
An intake example: four very different buyers
An existing landfill operator asks for recurring surface surveys. The enquiry should reach the person who handles periodic field programs. A consultant asks for subsurface monitoring to support a site assessment; this may need a different specialist. A facility owner has no approved plan and requests help understanding scope; this needs a discussion, not an instant quote. A buyer asks for both monitoring and control-system maintenance; distinguish the monitoring portion from mechanical services.
A sensible form produces enough information to recognize the difference. It does not ask each buyer to guess the exact compliance subpart or sampling protocol.
Privacy, security and governance
Do not include public free-text prompts such as “upload all facility operating documents.” Do not put customer site context into analytics URLs, marketing event names or public page content. Explain who will review the request and provide the applicable privacy notice.
After submission, use a human-reviewed handoff. Classify by scope, assign an owner, request missing information through the firm's approved process, and provide a qualified proposal only once requirements and assumptions are agreed.
If a message describes a potentially urgent environmental condition, use the organization's established escalation procedure. A normal marketing form is not an emergency-reporting service.
Test the form before it goes live
Submit one example with no monitoring plan, another with a defined annual scope and one with an out-of-area site. Verify labels, mobile controls, readable errors and email delivery to the appropriate staff. Check that a submitted form creates no false promise about testing frequency, reporting outcome or attendance date.
The OneStudio implementation boundary
OneStudio's published features describe customer-facing website and client-record modules. A project-specific complex RFQ form, secure documentation exchange or workflow automation must be validated against the actual OneStudio setup before being promised.
Use the website to collect an introductory business enquiry, then let qualified environmental professionals define the monitoring plan. See OneStudio solutions and pricing when designing that public front office.