How should I write an engineering request for proposals?

Write an engineering request for proposals by describing the project location, existing and proposed use, known site or building conditions, design stage, disciplines under consideration, desired deliverables, available records, coordination parties, and the authority or permit question already known. Ask each respondent to state its scope, exclusions, assumptions, required owner inputs, review approach, proposed responsible professional, and treatment of revisions. Do not prescribe a seal or approval outcome as the service; the professional must decide whether the work is within competence and authorized for the jurisdiction. The AHJ controls its checklist and interpretation, so the RFP should request confirmation of requirements rather than promise a particular result.

The correct application of engineering requests for proposals 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