What Is Proposal Management?
Proposal management is the process of planning, coordinating, writing, and submitting proposals in response to RFPs, RFQs, and SOQs. In architecture, engineering, and construction (AEC) firms, it specifically involves assembling staff resumes, project experience sheets, technical approaches, and compliance documents into a submittal that demonstrates the firm's qualifications to a client or agency evaluation committee.
Unlike industries where sales happen through demos and cold calls, most AEC firms win projects through formal selection processes. Your proposal is often your first — and sometimes only — chance to make an impression. According to the Society for Marketing Professional Services (SMPS), proposal-related activities consume 3-8% of a typical AEC firm's revenue.
How Proposal Management Works in AEC
The AEC proposal process follows a different path than general business proposals. Most pursuits involve qualification-based documents — SF330s, SOQs, or RFP responses — rather than sales decks or pricing quotes.
Here's the typical sequence:
- An agency issues a solicitation. This could be an RFQ (asking for qualifications), an RFP (asking for a full proposal), or sometimes an RFI (gauging interest).
- Firms decide whether to pursue it. This is the go/no-go decision — evaluating whether the opportunity aligns with the firm's strengths, capacity, and strategic goals.
- The proposal team assembles materials. Staff resumes, project sheets, team structure, technical approach, certifications, and compliance documents.
- Materials are tailored to the solicitation. Generic content doesn't win. Every resume, project description, and narrative section should connect to the specific evaluation criteria in the solicitation.
- The package is reviewed, assembled, and submitted. On time, in the required format, with all mandatory elements included.
- The agency evaluates and selects. Depending on the procurement method — qualifications-based selection (QBS), best value, or low-bid — the firm either wins the contract, makes the shortlist, or gets a debrief.
What Makes AEC Proposals Different
AEC proposal management has unique characteristics that don't apply to most other industries.
| AEC Proposals | General Business Proposals |
|---|---|
| Selection often based on qualifications, not price (Brooks Act for federal A/E) | Price is usually a primary factor |
| Standardized forms required (SF330, agency-specific templates) | Freeform format is common |
| Staff resumes are evaluated individually (key personnel) | Team credentials rarely scrutinized at the individual level |
| Project experience sheets must demonstrate relevant past work | Case studies are optional nice-to-haves |
| Subconsultant and teaming arrangements are part of the submittal | Subcontracting is usually handled after award |
| DBE/MBE/SBE/WBE participation goals may apply | Diversity requirements are less formalized |
| Page limits are strictly enforced | Length constraints are rare |
The biggest operational difference: AEC proposals are built from reusable components (resumes, project sheets, firm descriptions) that must be tailored for every pursuit. The content is largely the same — but the formatting, emphasis, and selection of which experience to highlight changes every time.
The Proposal Management Bottleneck
Most firms don't struggle with the writing. They struggle with the assembly.
A typical SOQ or SF330 submittal requires 8-15 staff resumes and 5-10 project experience sheets, each tailored to the solicitation. For a mid-size firm responding to 30-50 solicitations per year, that's hundreds of resume-formatting and project-sheet-tailoring tasks annually.
The common breakdown:
| Task | Time Per Submittal | Annual Cost (40 submittals/year) |
|---|---|---|
| Tailoring staff resumes (10 avg) | 5-10 hours | 200-400 hours |
| Tailoring project sheets (7 avg) | 3-7 hours | 120-280 hours |
| Writing/adapting technical narrative | 4-12 hours | 160-480 hours |
| Assembly, formatting, QC | 3-6 hours | 120-240 hours |
| Total per submittal | 15-35 hours | 600-1,400 hours/year |
The resume and project sheet work — roughly half the effort — is mostly reformatting. The underlying information (education, certifications, project history) doesn't change between pursuits. What changes is which experience to highlight and how to format it for this particular client or agency.
The Five Functions of Proposal Management
Effective proposal management in AEC covers five distinct functions. Most firms handle all five, whether they name them or not.
1. Pursuit Strategy (Go/No-Go)
Deciding which opportunities to chase. This involves evaluating:
- Do we have relevant experience for this project type and geography?
- Are key personnel available and qualified?
- Do we have a relationship with the client or agency?
- Can we meet the deadline without compromising quality?
- Is the contract value worth the pursuit effort?
Firms that chase everything win less. According to APMP (Association of Proposal Management Professionals), firms with a disciplined go/no-go process report win rates 15-25% higher than firms that respond to every solicitation they find.
2. Content Management
Maintaining the reusable building blocks — staff qualifications, project descriptions, firm boilerplate, certifications, and reference contacts. This is the operational backbone of proposal management.
The core question: where does your firm's proposal content live, and how current is it?
- If it lives in scattered Word documents on a shared drive, you'll spend hours finding and reformatting it for every pursuit.
- If it lives in one person's head, you have a key-person risk that breaks the moment they leave.
- If it lives in a structured system with consistent formatting, tailoring becomes selection and generation rather than manual reformatting.
3. Proposal Production
The actual work of building each submittal — selecting the right content, tailoring it to the solicitation, writing new narrative sections, assembling the package, and formatting it to meet the client's requirements.
This is where most of the labor goes. It's also where most of the errors happen. Common production failures:
- Outdated certifications on a resume (PE expired, wrong license state)
- Project sheets that don't match the solicitation's evaluation criteria
- Inconsistent formatting across team members' resumes
- Section H narrative that reads like it was written for a different project (because it was)
4. Quality Control
Reviewing the final package before submission. A good QC check covers:
- Are all evaluation criteria addressed?
- Do all names, titles, and firm names match throughout the document?
- Are certifications and dates accurate?
- Does the submittal comply with page limits and format requirements?
- Has someone who didn't write it read the entire package?
5. Knowledge Capture
After each pursuit — win or lose — capturing what worked and what didn't. This includes:
- Requesting a debrief from the agency if you weren't selected
- Noting which resumes, project sheets, and narratives were effective
- Updating staff profiles and project descriptions with new information
- Tracking win rates by client, project type, and team composition
How to Improve Your Firm's Proposal Process
These are the changes that make the biggest difference, in order of impact.
-
Start the resume and project sheet work immediately. The number one reason for poor-quality submittals is starting too late. Begin assembling staff resumes and project sheets as soon as the solicitation drops — don't wait until the narrative is drafted.
-
Create a single source of truth for staff qualifications. Every person's education, certifications (with expiration dates), project history, and specializations should live in one place. Not five versions in five folders. How to manage resume versions covers the full range of approaches.
-
Tailor everything to the evaluation criteria. Read the solicitation's evaluation criteria before you start writing. Reorder your project highlights to match. Emphasize the experience that scores points — not the experience you're most proud of.
-
Track your win rate and learn from losses. Measure proposals submitted vs. proposals won. Request debriefs on losses. Over time, this data tells you which types of pursuits your firm wins and which to stop chasing.
-
Standardize your templates. Every resume should follow the same layout. Every project sheet should use the same structure. Consistency signals professionalism to evaluators who are reviewing 15 submittals in a week.
-
Assign ownership. Someone — a proposal manager, marketing coordinator, or principal — must own the process. Without clear ownership, proposal work defaults to "everyone's second priority," which means last-minute scrambles and avoidable errors.
Frequently Asked Questions
What's the difference between proposal management and business development?
Business development focuses on identifying opportunities, building client relationships, and positioning the firm to be invited to pursue work. Proposal management focuses on execution — turning an opportunity into a winning submittal once the decision to pursue has been made. In larger firms, these are separate roles. In smaller firms, the same person often handles both, which is why pursuit volume matters — you can't build relationships and produce quality proposals if you're doing 50 submittals a year with a one-person marketing team.
How long does it take to respond to an RFP?
It depends on the solicitation type. A straightforward SOQ with no technical narrative might take 3-5 days of focused work. A federal SF330 with a detailed Section H takes 2-3 weeks. A full RFP with technical approach, staffing plan, and fee proposal can take 3-4 weeks. The variable isn't the writing — it's the resume and project sheet preparation time, which scales with team size.
Do small firms need a formal proposal management process?
Yes. A 10-person firm submitting 15 SOQs per year benefits as much from organized resumes and project sheets as a 200-person firm. The difference between winning and losing a shortlist is often presentation quality — not firm size. Small firms that present their qualifications clearly and consistently outperform larger firms that submit disorganized packages.
What software do engineering firms use for proposals?
Most firms use a combination of Microsoft Word (for document production), shared cloud storage (for file management), and Excel (for tracking pursuits and deadlines). Some use dedicated proposal management software. Tools like RFPM.ai focus specifically on the AEC bottleneck — keeping staff qualifications structured so resumes and project sheets generate automatically, tailored to each pursuit, in whatever format the client requires.
How do I measure proposal management success?
Three metrics matter most. Win rate (proposals won / proposals submitted) — most AEC firms average 25-40%. Capture rate (contracts won / opportunities identified) — this measures your go/no-go discipline. Hours per submittal — track this over time. If your process is improving, this number should decrease while quality stays the same or improves. A fourth metric worth watching: how many submittals are completed without a last-minute scramble. If the answer is "none," your process needs work.