How should I vet an engineering subconsultant?

Vet an engineering subconsultant by identifying the specialty scope, project jurisdiction, interfaces with the prime consultant, expected deliverables, and professional who will accept responsibility for that work. Verify the proposed professional's board status and authorization, review relevant experience, and ask how calculations, models, drawings, field information, and revisions will pass between teams. The prime agreement should state who selects, directs, pays, reviews, and replaces the subconsultant, while the technical documents should identify boundaries rather than imply that one seal covers every discipline. Each professional remains responsible only for the work properly undertaken and authorized. The AHJ may impose its own identification and submittal rules, so its requirements must be confirmed directly.

The correct application of vetting engineering subconsultants starts with the actual project, not a generic promise. Confirm the jurisdiction, adopted code, design scope, existing conditions, required deliverables, and professional responsibility before relying on a conclusion. A responsible engineer documents assumptions and identifies information that still needs verification.

Project type, occupancy, existing construction, site conditions, code edition, agency requirements, and changes made after the original design can change the work. A concise answer is useful for orientation, but the signed or sealed project record must reflect the current scope and the authority's process.

• Confirm the authority having jurisdiction and current checklist
• Use current drawings, calculations, field evidence, and equipment information
• Separate engineering decisions from owner, architect, contractor, utility, and agency decisions
• Record assumptions, limitations, and questions requiring direct AHJ confirmation