Why do engineering proposals list assumptions and exclusions?

Assumptions and exclusions keep an engineering price tied to a known scope. They may address the quality of existing drawings, access to concealed conditions, owner-furnished equipment, survey or geotechnical information, agency forms, construction services, and changes after authorization. They are not a way to avoid professional responsibility: the engineer must disclose material limitations and perform the agreed work competently. The AHJ may still request work outside the initial assumptions.

The correct application of engineering proposal assumptions and exclusions 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