Engineering Proposal: How to Scope Technical Projects, Present Fees, and Win Contracts

What to include in an engineering proposal

Begin with a project understanding section that demonstrates you have studied the site, reviewed available documents, and grasped the client's objectives and constraints. This section is where you differentiate yourself from firms that send generic proposals. Follow with the scope of services, broken into task areas or project phases. Each task should describe the engineering work to be performed, the deliverables produced, and any submittals or regulatory filings included. Address the applicable codes and standards. Specify your assumptions about site conditions, geotechnical data, survey information, and permitting requirements. End with your fee, schedule, and terms of engagement.

• Project understanding reflecting site-specific knowledge
• Scope of services broken into tasks or phases with deliverables
• Applicable codes, standards, and regulatory requirements
• Assumptions about site conditions, existing data, and client-provided information
• Coordination requirements with other disciplines or consultants
• Fee structure with billing basis and reimbursable expenses
• Project schedule with design milestones and submittal dates

Common mistakes in engineering proposals

The most consequential mistake is vague scope language. "Provide structural engineering services" does not tell the client whether you are covering schematic design only or carrying the project through construction administration. If the scope boundary is unclear, you will either perform unpaid work or have a dispute when the client expects services you did not intend to include. Another common error is omitting coordination assumptions. Most engineering projects involve multiple disciplines: architecture, mechanical, electrical, geotechnical, environmental. If your proposal does not specify how many coordination meetings, drawing reviews, or response cycles are included, the effort creeps beyond what you priced. Engineers also frequently understate the regulatory component. Permitting, agency reviews, and code compliance responses consume significant hours, and leaving them out of the scope creates budget pressure mid-project.

Fee structures for engineering services

Engineering fees are typically structured as lump sum, hourly with a not-to-exceed cap, or a percentage of construction cost. Lump sum fees are appropriate when the scope is well-defined and the project conditions are known. Hourly billing with a cap gives flexibility for projects with uncertain scope while still providing the client with budget predictability. Percentage-of-construction fees are common in building design but less transparent and harder to justify if the construction budget changes. Whichever structure you use, break the fee down by task or phase so the client sees what each component costs. Include a section on reimbursable expenses: printing, travel, subconsultant fees, permitting costs. These are often overlooked in proposals and become points of contention during billing.

• Lump sum for well-defined scope with known conditions
• Hourly with a not-to-exceed cap for uncertain scope
• Percentage of construction cost for building design (less common now)
• Break fees down by task or phase for transparency
• List reimbursable expenses separately: travel, printing, subconsultants, permits

Regulatory and permitting considerations

Engineering projects are governed by building codes, environmental regulations, zoning ordinances, and agency-specific requirements that vary by jurisdiction. Your proposal should identify which regulations apply and what your scope includes in terms of compliance. Will you prepare the permit application? Attend review meetings with the building department? Respond to plan check comments? Each of these activities takes time, and clients assume they are included unless you state otherwise. For projects in regulated industries like water treatment, energy, or transportation, the regulatory burden is even heavier. Outline the approvals required, the agencies involved, and the expected review timelines. Regulatory delays are the most common source of schedule slippage in engineering projects, and your proposal should acknowledge this with realistic scheduling.

Construction-phase services and project closeout

Many engineering proposals stop at the design phase, leaving construction administration as an afterthought. This is a mistake. Construction-phase services, including submittal reviews, RFI responses, site observations, and punch list support, are a significant part of the engineering effort and should be scoped and priced in the proposal. Define the number of site visits included, the expected volume of submittals and RFIs, and what constitutes a substantial completion milestone. If you offer construction-phase services as an optional add-on, present them as a separate line item with their own fee. Clients who skip this often return mid-construction asking for help, and without prior agreement, the terms are harder to negotiate.