A solicitation can look like a strong fit until the attachments say otherwise. A 20-page statement of work, a 90-page technical package, two past-performance questionnaires, pricing worksheets, and a Monday deadline can turn a promising opportunity into a bad use of your team’s week. Knowing how to assess proposal capacity means measuring the real work required to submit a compliant offer, not just deciding whether your company can perform the contract.
Federal contractors rarely lose capacity because they found too many opportunities. They lose it because they commit proposal resources before checking the conditions hidden in the solicitation package. The result is rushed reviews, weak pricing, missed amendments, and bids that should have been declined on day one.
Proposal capacity is more than available people
Proposal capacity is the amount of qualified work your team can complete to the standard the agency requires before the deadline. It includes writers and estimators, but it also includes executive reviewers, technical subject-matter experts, subcontractor coordination, pricing approvals, document production, and final submission coverage.
A proposal manager with an open calendar does not create capacity if the estimator is finishing two major bids or the operations lead is unavailable to validate staffing assumptions. Likewise, five employees who can edit a narrative do not solve a requirement for a certified cost estimate, manufacturer authorization, bonding, security clearances, or past-performance verification.
Start by separating two questions:
- Can we perform this contract if we win?
- Can we produce a compliant, competitive proposal by this deadline?
The first is a delivery question. The second is a proposal-capacity question. Both must be true. A qualified contractor can still make a poor bid/no-bid decision when the response window is too short or the proposal load is already full.
Read the solicitation before assigning the work
SAM.gov tells you a contract exists. The attachment package tells you what it will cost to pursue.
Before you schedule a kickoff meeting, identify the documents that control the response: the solicitation, statement of work or performance work statement, amendments, pricing schedule, instructions to offerors, evaluation criteria, and every required form or certification. A notice description may say “janitorial services” or “IT support.” The attachments may require 24/7 dispatch, base-access processing, named key personnel, wage determinations, transition plans, site visits, or a pricing workbook with hundreds of line items.
This initial read should answer four operational questions:
- What must be submitted, in what format, and through which portal or email address?
- Which requirements are mandatory and disqualifying?
- What information must come from people outside the proposal team?
- How many business days remain after you account for internal review and submission contingency?
Do not treat the posted response date as your team’s actual deadline. Set an internal submission target at least one business day earlier, and more for complex packages or portals your team does not use regularly. The last day is for resolving upload errors, confirming attachments, and handling changes - not writing the executive summary.
Build a realistic effort estimate
The fastest way to overcommit is to label every opportunity “small,” “medium,” or “large” based on contract value. Proposal effort does not track neatly with value. A modest supply order with a detailed pricing sheet and manufacturer letters may consume more capacity than a larger follow-on services proposal where your team already has the content, labor categories, and performance history ready.
Estimate effort by workstream instead. For each proposal, assign a rough number of hours and identify the owner for technical response, pricing, compliance, past performance, resumes, subcontractor inputs, management review, production, and final submission. Include time to read the package. Teams often omit it, then discover that the first meaningful review takes several hours because the requirements are scattered across amendments and appendices.
A simple capacity view can track four items for every live pursuit:
- Remaining proposal hours by workstream
- Named owner and backup for each deliverable
- Internal review dates and approval dependencies
- External dependencies, including subcontractors, vendors, customers, and bonding agents
Use ranges when the requirement is unclear. If a site visit is mandatory but the agency has not released access instructions, the uncertainty itself is a capacity risk. If a subcontractor must supply pricing within 48 hours, do not count that work as complete because someone said they were interested.
Check the calendar for collision risk
Capacity is a calendar problem before it becomes a staffing problem. Two proposals due the same week may draw on the same estimator, technical lead, executive signer, or past-performance contact. One might be manageable alone. Together, they can force shortcuts at exactly the point where compliance matters most.
Map key milestones, not just final due dates. Look for collisions around kickoff, questions to the government, site visits, subcontractor quote deadlines, pink-team reviews, pricing approvals, and submission. A proposal due Friday can still disrupt a proposal due Tuesday if both need the same operations leader to approve labor assumptions on Monday.
This is where experienced teams distinguish between nominal and usable capacity. Nominal capacity is the total hours someone has on paper. Usable capacity accounts for meetings, customer delivery work, travel, PTO, approval lag, and the concentration required to review a long solicitation carefully. A key person with 20 open hours is not truly available for 20 hours of high-stakes proposal work.
Score complexity, not just fit
A strong NAICS match or set-aside match puts an opportunity on the board. It does not make it a good pursuit. Add a capacity score that reflects the work required to bid well.
Consider the following factors together: response time, attachment volume, pricing complexity, number of required volumes, new teaming relationships, site-access requirements, security or credentialing conditions, and the availability of relevant past performance. A solicitation with a short response window and five unknown dependencies should score as high effort even if the scope is familiar.
It depends on your team’s maturity. A contractor with reusable technical content, a dedicated capture lead, and established suppliers can absorb work that would overload a newer firm. But reuse has limits. Boilerplate does not satisfy agency-specific instructions, and recycled narratives can miss changed evaluation language or a new amendment.
Make bid/no-bid decisions early enough to matter
A bid/no-bid meeting held two days before submission is often a formality. By then, the team has already spent time reading, talking to partners, and building pricing assumptions. The decision should happen after a disciplined qualification review but before the work expands.
A practical decision standard is simple: pursue only when you can identify a credible path to compliance, competitiveness, and on-time submission. If any of those paths depends on an unconfirmed assumption, record the assumption, owner, and decision date. Then decide whether the issue can be resolved before the proposal crosses its point of no return.
Declining a proposal is not lost pipeline if it protects a better-qualified pursuit. The real cost of chasing every relevant notice is not only wasted hours. It is the erosion of quality across proposals you could have won.
Keep capacity current as the solicitation changes
Capacity assessment is not a one-time intake exercise. Amendments can add forms, revise wage determinations, change a site-visit date, extend the deadline, or replace the entire pricing schedule. A deadline extension may create capacity, but it can also signal a materially changed requirement that needs another technical and pricing review.
Build a change check into your pursuit workflow. When an amendment arrives, ask what changed, which owner must review it, and whether the proposal plan still holds. Do not assume an extension is good news until you compare the new documents with the old ones.
InstantSam can help teams get to this decision faster by reading solicitation attachments and organizing scope, mandatory requirements, evaluation criteria, timelines, and risks into a usable briefing. That reduces the time spent hunting through PDFs. It does not replace your judgment about whether your estimator, technical lead, and reviewers can actually carry the work.
Protect the team’s best work
The goal is not to keep everyone busy. It is to preserve enough room for careful reading, informed pricing, compliance checks, and meaningful review on the opportunities where your company has a legitimate advantage.
When a new notice appears, resist the urge to assign it immediately. Read the source documents, expose the dependencies, map the calendar, and decide what this pursuit would displace. The bid you decline early may be what allows your team to submit the next one with the time and precision it deserves.