Special Inspection and CMT RFQ Form: Fields That Matter

Overview

A useful RFQ should help the testing firm answer who is requesting the work, where the project is, what is being built, which inspections or tests appear to be in scope, when coverage starts, whether drawings/specifications are available, and which technical manager should review the opportunity.

Field 1: Company and contact

Collect company, contact name, role, work email and phone.

Field 2: Buyer role

Useful options include owner/developer, general contractor, subcontractor, architect/engineer, construction manager, public agency and other.

This helps clarify who controls scope, scheduling and proposal approval.

Field 3: Project name and address

Collect project name, street/city/state and jurisdiction if known.

Location can affect mobilization, code context and agency requirements.

Field 4: Project type

Use broad categories such as commercial, multifamily, healthcare, education, industrial, infrastructure, public works, renovation and other.

Field 5: Requested special inspections

Allow multiple selections where offered: reinforced concrete, rebar, structural steel, bolting, welding, masonry, fireproofing, anchors, other and not sure / see plans.

Do not list a discipline the firm is not qualified to perform.

Field 6: Requested construction materials testing

Useful categories can include concrete, soils/compaction, asphalt, masonry/grout, aggregate, laboratory testing, field density, other and not sure.

Field 7: Project phase

Use bidding/preconstruction, mobilizing, foundations, structure, active construction, closeout and not sure.

Field 8: Schedule / start date

Collect expected first service date, project duration at a high level, one-time test versus recurring coverage, and normal shift versus off-hours if relevant.

The technical/operations team should confirm the actual schedule later.

Field 9: Project documents

Ask whether the buyer can provide a statement of special inspections, structural drawings, project specifications, bid scope or testing schedule.

Use optional upload/handoff rather than making documents mandatory for first contact.

Field 10: Jurisdiction / agency requirements

At a high level, ask whether the work is under a local building department, DOT/public agency, federal/state project, private project or unknown.

Do not use the form to determine code compliance automatically.

Field 11: Accreditation / qualification requirement

Ask whether the project specifically requires an AASHTO-accredited lab, ISO/IEC 17025, agency-approved lab, certified inspectors/technicians, project-specific qualification or not sure.

Only display options relevant to the firm's real market.

Field 12: Proposal deadline

Collect proposal due date, bid date, project start or urgent/already under construction.

Field 13: Notes

Prompt: Tell us what the project is, which inspection/testing scope you expect and anything in the bid documents that will affect staffing or laboratory work.

What the public RFQ should not decide

Do not let the public form determine final inspection frequency, specific test method, technician certification requirement, sample plan, compliance determination, reporting format or deficiency disposition.

Those belong to professional review.

Confirmation message

Use: Thanks. We received your project RFQ. Our team will review the location, requested inspections/testing, schedule and available project documents and contact you about scope and proposal next steps.

Avoid saying that the inspection program is approved.

Collect enough to route the RFQ to a technical reviewer

A strong form reduces commercial back-and-forth while keeping detailed inspection, testing and reporting in the specialist system.

Explore OneStudio features, compare plans, or browse solutions.

Questions businesses ask