What Gets Firms Knocked Off SF330 Shortlists?
Most firms that lose shortlists don't lose on technical qualifications. They lose on avoidable errors in how they present those qualifications. According to APMP benchmarks, proposal teams that follow a structured review process before submission improve their win rates by 25-40% — largely by catching the same mistakes that appear in this list.
The SF330 form has nine sections, each with specific evaluation weight. Errors in high-weight sections — particularly Section E (resumes), Section F (project experience), and Section H (additional information) — cost more points than errors in administrative sections. Here are the seven mistakes that show up most often.
1. Submitting Resumes That Don't Match the Solicitation's Evaluation Criteria
Section E is usually the highest-weighted section in SF330 evaluations. Each resume gets one page to prove that person belongs on this project. When the resume reads like a generic career summary instead of a targeted case for this specific contract, evaluators score it lower.
What this looks like:
- A structural engineer's resume lists 15 projects but none match the solicitation's scope (highway bridges when the pursuit is for building structural assessments)
- Certifications are listed but the PE registration is from a different state than where the work will be performed
- The "role on this project" field says "Senior Engineer" without specifying what that means for this contract
Why it costs points:
Evaluators score resumes against the criteria published in the solicitation. If the solicitation says "relevant bridge inspection experience within the past 10 years," and the resume leads with a wastewater treatment plant from 2018, that resume is working against you — even if the person has bridge experience buried on line 12.
How to fix it:
Read the evaluation criteria before you start any resume. Highlight the specific qualifications, project types, and experience thresholds the agency listed. Then build each resume to answer those criteria directly — relevant projects first, matching certifications prominent, role descriptions tied to the scope of work.
For firms managing 20+ staff across multiple simultaneous pursuits, this tailoring work is where managing multiple resume versions becomes the real bottleneck.
2. Using Generic Project Descriptions in Section F
Section F asks for example projects that demonstrate your team's relevant experience. The word "relevant" is doing all the work in that sentence. Firms that maintain a library of project descriptions and drop them into every submittal unchanged are leaving points on the table.
What this looks like:
- The same 200-word project description appears in submittals for a coastal resilience study and a highway interchange design
- Project descriptions emphasize your firm's overall scope instead of the disciplines and deliverables this solicitation is evaluating
- Projects are selected because they're impressive, not because they're relevant
Why it costs points:
Evaluators aren't reading Section F to learn what your firm has done. They're reading it to assess whether your team has done this type of work before. A $50M airport terminal project is not relevant experience for a $2M stormwater master plan — even though it sounds more impressive.
How to fix it:
For each pursuit, select project experience sheets based on the solicitation's scope, not your firm's greatest hits. Then rewrite each description to lead with the aspects that match the evaluation criteria. The same project can appear in multiple submittals with different emphasis — that's tailoring, not recycling.
3. Inconsistent Formatting Across the Submittal
When one team member's resume uses 11pt Calibri and another uses 10pt Times New Roman, or when the prime's project sheets have a header graphic and the subconsultant's don't, evaluators notice. Inconsistent formatting signals a disorganized team — and evaluators extrapolate from the proposal to the project.
What this looks like:
- Resumes from subconsultant firms use a completely different layout than the prime's resumes
- Section F project sheets have different column widths, fonts, or date formats
- Headers and footers change style between sections
- Some resumes have the firm logo, others don't
Why it costs points:
Evaluators review dozens of SF330s per solicitation. The submittals that look cohesive and polished create a subconscious impression of a well-managed team. Formatting inconsistency doesn't usually have its own scoring line, but it drags down scores for "quality of submittal" or "responsiveness" criteria that most solicitations include.
How to fix it:
Establish a single resume template and a single project sheet template for the prime firm, and require all subconsultants to use them. Send the templates early in the pursuit — not the day before the deadline. When subconsultants push back, remind them that consistent presentation is a scoreable factor.
Better yet, maintain structured staff and project data in a central system and generate formatted outputs from templates automatically. That's the core of what tools like RFPM.ai do — one data source, consistent formatting across every pursuit.
4. Missing or Incorrect Certifications and Registrations
Professional registrations matter in A/E procurement. When a solicitation requires a PE licensed in the state where the work will be performed, that's not a suggestion. Listing a PE from the wrong state, listing an expired certification, or omitting a required registration entirely can move your firm from "shortlisted" to "non-responsive."
What this looks like:
- A PE license listed without a state designation — evaluators can't verify it's valid for this contract
- A LEED AP credential that expired two years ago listed as current
- The solicitation requires a licensed surveyor and no one on the team has one listed
- Certification numbers are wrong or transposed
Why it costs points:
Some agencies treat missing required certifications as grounds for non-responsiveness — meaning your submittal doesn't get scored at all. Even when it's not disqualifying, incorrect credentials tell evaluators the firm doesn't manage its own staff data carefully. If you can't keep track of your team's licenses, how will you manage a $10M design contract?
How to fix it:
Maintain a centralized record of every staff member's certifications, license numbers, states of registration, and expiration dates. Review this data quarterly — not just before a submittal deadline. When preparing Section E, cross-reference the solicitation's requirements against your team's current credentials before you start writing resumes.
5. Exceeding Page Limits
This one should be obvious, but it happens constantly. If the solicitation says 50 pages, page 51 is either not read or your entire submittal is disqualified. Different agencies handle overages differently, but none of the outcomes are good.
What this looks like:
- The firm "rounds up" — interpreting a 50-page limit as a soft guideline
- Attachments, cover letters, or divider pages push the count over without anyone noticing
- Font sizes shrink to 8pt to fit more content per page, which technically meets page count but violates readability expectations
Why it costs points:
Many federal agencies have explicit instructions: submittals exceeding page limits will not be evaluated beyond the limit. That means your carefully written Section H narrative on page 51 simply won't be read. Some agencies disqualify the entire submittal. Either way, you did the work for nothing.
How to fix it:
Track page counts throughout the drafting process, not just at the end. Assign page budgets per section before writing starts — for example, if the limit is 50 pages: 1 page for Sections A-D, 10 pages for Section E (10 key personnel), 8 pages for Section F (8 projects), 1 page for Section G, and 30 pages for Section H. Adjust the budget based on what the solicitation weights most heavily.
Build in a 2-page buffer. If your budget totals 48 pages against a 50-page limit, you have room for minor overruns. If your budget totals 50, you don't.
6. Writing Section H Like a Brochure Instead of an Evaluation Response
Section H (Additional Information) is the only freeform section in the SF330. It's where you differentiate. Most firms treat it as a place to dump boilerplate — recycled management plans, generic quality control narratives, and firm history paragraphs that could apply to any project in any state.
What this looks like:
- Section H opens with two paragraphs about the firm's founding year and number of offices
- The technical approach could apply to any project of this type, anywhere, for any agency
- Evaluation criteria are addressed out of order or not addressed at all
- No mention of the specific project location, agency, or known challenges
Why it costs points:
Evaluators score Section H against the published evaluation criteria. If the solicitation lists five criteria in a specific order with specific weights, your Section H should address those five criteria in that order with proportional depth. A generic narrative that doesn't mirror the evaluation framework forces evaluators to hunt for relevant content — and they won't.
According to SMPS research, firms that structure Section H to directly mirror the solicitation's evaluation criteria score 15-20% higher on narrative sections than firms that use a standard template approach.
How to fix it:
Before writing a single word of Section H, create an outline that maps each evaluation criterion to a section heading. Weight your page allocation based on the point values. If "relevant experience" is worth 35 points and "management approach" is worth 15, don't give them equal space.
Then write to the agency, not to yourself. Reference the project by name. Reference the location. Reference specific challenges visible in the RFP scope, site conditions, or schedule. Show the evaluator you read the solicitation — not that you searched and replaced "[Project Name]" in a template.
7. Not Updating Part II Annually
SF330 Part II is the firm's general qualifications profile. Agencies expect it to be current. When a Part II lists a project manager who left two years ago, or shows revenue figures from 2023, or omits a discipline the firm added last year, it tells the agency the firm doesn't maintain its own records.
What this looks like:
- Part II lists staff who no longer work at the firm
- Revenue and project volume figures are two or more years old
- New office locations, certifications, or capability areas aren't reflected
- The "date prepared" field shows a date more than 12 months ago
Why it costs points:
Some agencies request Part II independently of any specific solicitation — it's part of prequalification or annual registration. When Part II is stale, agencies may not include your firm in solicitation distributions. Even when Part II is submitted with Part I, outdated information raises credibility questions about everything else in the submittal.
How to fix it:
Pick a month. Every year, during that month, update Part II. Treat it like a tax filing — it has a fixed annual cycle. Update staff counts, project lists, revenue figures, office locations, and certifications. Assign one person as the owner and put it on their calendar.
How to Catch These Mistakes Before Submission
The firms that consistently make shortlists aren't necessarily better qualified — they're better organized. They catch errors before the submittal goes out, not after they get the rejection letter.
A pre-submission review checklist should include:
- Compliance check — Does the submittal meet every requirement in the solicitation (page limits, format, required sections, certifications)?
- Relevance check — Does every resume and project sheet directly relate to this solicitation's evaluation criteria?
- Consistency check — Are fonts, headers, date formats, and layouts uniform across all sections and all team members?
- Currency check — Are all certifications current? Are all staff members still with the firm? Is Part II dated within the last 12 months?
- Criteria alignment check — Does Section H address every evaluation criterion in the order and proportion the solicitation specified?
Run this checklist with someone who didn't write the proposal. Fresh eyes catch what the writer's eyes skip.
Frequently Asked Questions
What is the most common reason firms get knocked off SF330 shortlists?
The most common reason firms lose SF330 shortlists is failing to tailor the submittal to the specific solicitation. Generic resumes, recycled project descriptions, and boilerplate Section H narratives signal that the firm didn't invest effort in this particular pursuit. Evaluators score tailored submittals higher because they demonstrate understanding of the project and commitment to the opportunity.
Can you get disqualified from an SF330 evaluation for formatting errors?
Yes. Exceeding page limits is the most common formatting-related cause of disqualification. Some agencies will stop reading at the page limit; others will reject the entire submittal. Font size minimums, required section ordering, and file format requirements can also be grounds for non-responsiveness if the solicitation specifies them.
How many projects should I include in SF330 Section F?
Most solicitations specify a range — typically 5 to 10 projects. If no number is specified, include enough to demonstrate breadth across the solicitation's scope areas without exceeding your page budget. Every project should be directly relevant. Five highly relevant projects beat ten loosely related ones.
How do I improve my SF330 evaluation score without changing my team?
Focus on presentation and tailoring. Rewrite resumes to lead with experience that matches evaluation criteria. Select and rewrite project descriptions for relevance. Structure Section H to mirror the solicitation's criteria exactly. Fix formatting inconsistencies. These changes cost zero additional staff but can move scores significantly.
How often should I update SF330 Part II?
Update Part II at least once per year. The best practice is to assign a fixed annual month — such as January or the start of your fiscal year — and treat it as a recurring task. Update sooner if your firm experiences significant changes: key hires or departures, new office locations, new certifications, or major completed projects.
RFPM.ai automates resume generation and project sheet assembly for engineering and construction firms. See how it works