CRM
A private utility locating quote form that gets the scope right
Build a useful utility locating RFQ form with site, scope, timing and access fields while avoiding unsafe instant-clearance promises.
A quote form is not a clearance certificate
An enquiry form should give an estimator enough context to decide how to respond, not certify that a location is safe to dig. It should never mark a property as cleared or dispatch-ready automatically. Even well-described sites may contain incomplete utility records, untraceable lines or access constraints that require a different plan.
Ask only what changes the next decision
Stage one: project fit
Collect a contact name, organization (if relevant), email or callback number, site city/ZIP, general project type and requested timing. Ask a short free-text question: What work will happen after locating? Excavation, directional drilling, saw cutting, landscaping and industrial maintenance imply different hazards and coordination needs.
A two-step layout is often better than fourteen visible fields. The first step confirms the business actually serves the project. If the location is outside the service radius, the form should not imply an automatic booking.
Stage two: scope for the estimator
Depending on the service, useful fields are approximate work footprint, surface type, expected utilities, whether records or marked drawings are available, whether the site is occupied and whether access requires an escort or permit. For commercial work, record bid/field dates separately. A quote due tomorrow and field access next month are different priorities.
811 information with careful wording
Ask Has an 811 locate request been made for this excavation? with Yes / No / Not sure, but do not treat the answer as a legal clearance check. A private locate can complement the public process; it does not waive the statutory responsibilities of excavators or facility owners.
A compact field specification
Never request confidential infrastructure plans, employee credentials or detailed security layouts in a generic website form. If those are needed, use a separately approved exchange after qualification.
| Field | Why it matters | Required at first contact? |
|---|---|---|
| Contact and safe callback | Return an answer | Yes |
| City and ZIP | Service-area screening | Yes |
| Project category | Route to suitable reviewer | Yes |
| Work to follow | Evaluate survey purpose | Yes |
| Requested field date | Detect urgency | Yes, approximate |
| Property type | Residential versus industrial requirements | Useful |
| Survey footprint | Start assessing time/scope | Useful |
| Existing records | Identify later information needs | Optional |
| Access/security | Avoid unsuitable assumptions | Optional |
| 811 status | Prompt a separate legal/safety check | Optional |
Example: two enquiries that must not be treated alike
Enquiry A: A homeowner wants to place fence posts near a private irrigation line next month. Staff can verify service-area coverage, explain 811 obligations and request a short site description.
Enquiry B: A hospital contractor needs a subsurface survey before emergency excavation near clinical buildings. Staff must identify urgent safety and access coordination, verify the actual contractor's emergency process and avoid promising same-day coverage unless it is operationally guaranteed.
These requests may use the same public form but must not share the same downstream assumptions. If urgent incidents exist, display a separately staffed telephone route and specify that an online request is not monitored continuously.
Lead stages you can implement without fake automation
Use plain stages such as New enquiry, Scope review, Awaiting information, Quote in preparation, Quote delivered, Accepted and Closed. Assign human ownership. Record a reason when an enquiry is rejected, for example outside territory or scope requiring another specialist. Keep technical survey records in the contractor's established field system.
OneStudio publicly describes contact enquiries and client records. Confirm any exact form configuration, integrations or attachment handling inside the customer's actual site before claiming them in public copy.
Mobile and privacy acceptance tests
Submit a test enquiry with a short message, then with a long message; intentionally leave required fields blank; try a non-service-area ZIP; confirm no fabricated booking confirmation is returned. Ensure that the form does not email full sensitive site plans to a general inbox. Set a realistic privacy statement about who handles enquiries, without inventing a data-retention policy.
CTA: make the first response more valuable
A quote form works when it shortens the distance to a meaningful human review. Build a professional public intake experience with OneStudio, and review the available business features before connecting specialist locating tools.