CRM
Smoke control special inspection RFQ: ask the right project questions
Plan smoke-control inspection RFQ forms with project, jurisdiction, scope and deadline fields without promising code approval or an immediate booking.
Why a generic “name, email, message” form falls short
A quote for smoke-control testing depends on far more than a square-foot estimate. An existing hospital needs a different coordination plan from a new atrium tower. The stage of construction, adopted code, available plans, access requirements and unresolved interface issues can radically alter the procurement conversation. A website does not have to estimate that technical effort automatically. It should help the project manager start the conversation with enough context for an expert to respond intelligently.
The first form should be short and safe. Heavy documentation belongs in a subsequent controlled exchange. Structure the submission as a request for scope review, not a test order.
Fields worth asking on the first contact
Buyer and decision-maker
Collect name, work email, company, callback method and role: owner, construction manager, general contractor, MEP subcontractor, design professional or facilities lead. Role is more useful than a personal title because it tells the reviewer who can provide design documents and access.
Site and jurisdiction
Ask for city, state/province, building type and relevant authority having jurisdiction, if known. The AHJ field must be optional. Never assume that a visitor knows the adopted code edition; ask which construction documents or inspection statement govern the project in the follow-up.
Requested engagement
Let the visitor select one or more categories: special inspection, commissioning support, integrated systems coordination, existing-system retesting, documentation review or not sure. Only present services the firm actually supplies. A catch-all “full certification” option risks implying authority the firm may not have.
Project milestone
Offer design / procurement, installation underway, pre-occupancy, existing occupied building, or remediation/retest. Include a date range, not a promise to meet that date. If a shutdown or evacuation drill may be involved, use a yes/no flag for later coordination, not a public field for sensitive operating plans.
Known system context
Provide optional choices such as stair pressurization, atrium, exhaust/supply fans, dampers, fire-alarm interfaces, controls sequences and unknown. Avoid technical calculations, threshold defaults or upload requirements. They should be interpreted by the actual design and testing professionals.
Route the enquiries without pretending to dispatch crews
A CRM can keep ordinary lead statuses such as new enquiry, needs technical review, scope call arranged, proposal sent and not a fit. Store detailed plans and formal inspection reports in approved technical systems instead of general client notes.
| First-contact signal | Appropriate next step | What not to promise |
|---|---|---|
| Pre-occupancy, designs available | Technical scope call and document request | A guaranteed occupancy approval |
| Existing building, recent failure | Clarify the failure category and contracted investigation | Root cause or remedial cost from a web form |
| Time-sensitive project, unknown AHJ | Human scheduling and jurisdiction review | Automatic 24-hour test attendance |
| Requests “fire alarm inspection only” | Confirm whether the company offers that discipline | A smoke-control inspection as a substitute |
| No design team identified | Ask who owns the approved sequence and test plan | Independent design approval by the website |
Example of clear post-submit copy
“Thank you. Your smoke-control project enquiry has been received. Our team will review the location, scope and schedule before confirming whether we can quote or arrange a site visit. Submission does not book an inspection or confirm compliance.” This reduces an expensive category of misunderstanding without sounding alarmist.
Build a useful page around the form
The form should sit beside a concise checklist: approximate building size, system category, procurement deadline, previous inspection stage, and design-team contact if applicable. Beneath it, answer what happens next. The strongest link from a technical service page is a request form that does less, but asks better questions.
A site built with OneStudio's website tools may combine this public information with the appropriate client follow-up workflow. Do not claim built-in engineer assignment, inspection certification or technical file portals without verifying an actual integration. The OneStudio solutions page explains the website-first model.
CTA: replace vague enquiries with scoped conversations
Publish a clear request-first path, test it on a phone, and make a named employee responsible for follow-up. Review OneStudio features to plan the web and customer side while keeping specialist inspection work under professional control.
Questions businesses ask
Should the form require approved plans?
No. Ask whether plans exist, then agree on a secure professional exchange. Requiring uploads can exclude early-stage enquiries and can unnecessarily expose sensitive life-safety designs.
Can an enquiry become an appointment?
Yes, after the firm defines a meeting or assessment service, availability and the limits of what is being booked. An inspection date should be confirmed by a qualified person after project readiness is checked.