How should I compare engineering proposals?

Compare engineering proposals by normalizing the scope before comparing fees. Put each response beside the same questions: which disciplines and project phases are included, what drawings or calculations will be delivered, who performs and reviews the work, how existing conditions will be verified, what coordination and comment responses are included, and which assumptions or exclusions could change the work. Also compare the provider's communication path, revision rules, schedule dependencies, and jurisdictional authorization. A proposal that omits field evidence, coordination, or professional review may appear less expensive while leaving material risk with the owner. The AHJ decides completeness and acceptance; no proposal can responsibly guarantee that decision.

The correct application of comparing engineering 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