This scene plays out at government contractors constantly, and it quietly sinks proposals that are technically strong everywhere else. Past performance often carries 20-30% of a best-value score, yet it's frequently the last section pulled together instead of the first one planned.
This guide breaks down what Section L and Section M actually require, how evaluators score past performance under FAR 15.305, and how to build a repeatable process instead of a last-minute scramble. Manual reference-hunting across CRMs, CPARS printouts, and old proposals is exactly the kind of repetitive revenue-process work platforms like Intellectible are built to eliminate.
Key Takeaways
- Past performance typically drives 20-30% of best-value scoring — reference selection is a scoring decision, not paperwork
- Section L governs what to submit; Section M governs how it's judged; confusing the two creates avoidable risk
- Evaluators weigh recency, relevance, source, and context more heavily than raw contract dollar value
- A "neutral" past performance rating protects newer contractors under FAR 15.305(a)(2)(iv): it does not disqualify them
- Centralizing past performance data and mapping it to Section M criteria cuts proposal-prep time and reduces last-minute reference scrambles
What Section L and Section M Actually Tell Offerors
FAR 15.204-1 splits the solicitation into distinct instructions. Section L (Instructions, Conditions, and Notices to Offerors) specifies:
- Number of past performance references required
- Page limits and formatting rules
- Required forms, such as Past Performance Questionnaires (PPQs)
- Submission deadlines and delivery method
Section M (Evaluation Factors for Award) specifies how the government scores what you submit, including factor weighting and adjectival or qualitative standards.
Here's the confusion that trips up capture teams: Section L is about compliance. Section M is about scoring. Treat them interchangeably and you'll either miss a submission requirement or write references that check the box without earning points.
A Quick Example
Say Section M states the government will evaluate "demonstrated experience managing IT modernization contracts of similar scope and complexity." That single phrase should determine:
- Which references you pick (must show IT modernization, not just any IT work)
- How you frame the narrative (scope and complexity, explicitly)
- What data points you lead with (contract value, systems migrated, users affected)
Experience and past performance are also legally distinct evaluation factors: what you've done versus how well you did it. Some solicitations score both separately, so read Section M carefully before assuming they're combined.
How Past Performance Is Actually Evaluated
Evaluators do not rank past performance by contract size or brand name. They apply a defined FAR framework, then score the evidence you put in front of them.
The FAR 15.305(a)(2) Standard
Per FAR 15.305, evaluators must weigh four dimensions:
- Recency: how current is the work?
- Relevance: does it resemble this requirement?
- Source: who's vouching for the performance?
- Context: what circumstances shaped the outcome?
Contract dollar value isn't on that list. A $2 million contract executed flawlessly can outscore a $50 million contract with mediocre reviews.
CPARS: The Government's Scoring Backbone
CPARS evaluates six dimensions: quality, schedule, cost control, management, regulatory compliance, and small business subcontracting. Ratings run from Exceptional down to Unsatisfactory.
| Rating | What It Means |
|---|---|
| Exceptional | Exceeds requirements, benefits the government |
| Very Good | Exceeds some requirements |
| Satisfactory | Meets contractual requirements |
| Marginal | Fails to meet some requirements |
| Unsatisfactory | Fails most requirements |
A bare rating without narrative gives evaluators little to quote in a source selection report. Ratings alone don't win points; the story behind them does.
Some solicitations accept PPQs instead of or alongside CPARS. Submitting both for the same contract creates unnecessary compliance risk and confuses evaluators about which document is authoritative. Check Section L carefully for which is required, and don't hedge by submitting extra paperwork nobody asked for.
Rules Contractors Often Misread
Past performance qualification is the FAR-defined standard evaluators use to judge currency, relevance, and quality of prior work. If you're a newer contractor without federal history, FAR 15.305(a)(2)(iv) requires a neutral rating, not a penalty. You stay in the competition; you simply can't be scored favorably or unfavorably on that factor.
Contractors also do not file annual CPARS reports. FAR 42.15 places the CPARS preparation obligation on the government, not the contractor. Assessing officials prepare evaluations, and contractors get up to 14 days to comment or rebut. Still document performance throughout the period of performance (quantified outcomes, resolved issues, delivery metrics) so material is ready when the government's evaluation drops.
Selecting and Writing References That Map to Section M
Three tightly scoped, recent references usually outscore five loosely relevant ones. Evaluators score what they can quote directly from your narrative, not what they have to infer.
Five Elements of a Strong Reference Write-Up
- Contract identification: agency, contract number, period of performance
- Scope and role: what you actually did, prime or sub
- Quantified outcomes: numbers, not adjectives
- Problem resolution: a challenge you solved and how
- Relevance bridge: an explicit tie to the named Section M criterion
Weak vs. Strong Outcome Statements
- ❌ "Successfully delivered IT support services to the client."
- ✅ "Reduced average ticket resolution time from 48 hours to 6 hours across a 12,000-user network, while maintaining a 98.7% SLA compliance rate."
Dollar figures, percentages, and delivery rates anchor the narrative. Adjectives don't.
Those outcome statements only help if the underlying contracts qualify. Commercial work and joint ventures often do.
Commercial Work and Joint Ventures Count
FAR 15.305(a)(2)(ii) explicitly allows commercial contracts as past performance evidence. The agency decides relevance, not whether the contract was federal or commercial.
For joint ventures:
- Evaluators consider the JV's own track record first
- If that record is thin, individual members' past performance can count too
- Newer entrants teaming for early federal awards can lean on member history when the JV itself is light
The Rule of Two and When Past Performance Isn't the Deciding Factor
The Rule of Two requires contracting officers to set aside acquisitions for small businesses whenever there's a reasonable expectation that at least two responsible small businesses will submit competitive offers at fair market prices.
Why does this matter for past performance strategy? Set-aside pools skew toward newer small businesses, which changes how past performance is weighed:
- Neutral ratings show up more often in these pools — and evaluators expect that
- Commercial experience carries more relative weight
- The competitive bar for "recent, relevant" work is often lower than in full-and-open competitions
Where Past Performance Evaluation Gets Relaxed
- Simplified acquisitions (at or below the $350,000 SAT): COs may rely on their own knowledge, customer surveys, or CPARS instead of full Part 15 procedures
- Micro-purchases (under $15,000): formal past performance evaluation is rarely required
- Sealed bidding: price and price-related factors outweigh past performance narratives
Pursuit teams building a track record should target these lower-friction opportunities first. The CPARS entries that follow become evidence you can cite on larger competitive pursuits.
Automating Past Performance and Section M Response with AI
The core problem isn't unique to any one contractor: past performance data lives scattered across CRMs, SharePoint folders, and the institutional memory of whoever wrote the last proposal. That's fine until an RFP drops with a two-week turnaround and nobody can find the right reference fast enough. Intellectible's GovCon Engine addresses this by comparing new opportunities against historical award data: contract timing, agency patterns, value ranges, and scope similarity, using a vector database built for semantic matching. When an RFP comes in, the platform extracts requirements, Section M evaluation factors, and submission obligations. It then builds compliance matrices that map each factor to proposal sections and keeps the source evidence behind every match. That means:
- Extract and organize Section M factors and related requirements automatically
- Cross-reference historical awards by scope similarity, not keyword search alone
- Draft past performance language from approved work and prior proposal content
- Map evidence to evaluation criteria so Section M responses stay traceable This is the same underlying engine that helped Oceus review more than double the qualified opportunities per week. It also helped HHS cut what their team called "tedious, monotonous hours of RFP efforts," so staff could focus on analysis and selling instead of hunting for documents. Across Intellectible's Revenue Discovery workflows, clients see 95%+ time saved on opportunity search and Go/No-Go decisions, and a 150%+ increase in actionable pipeline opportunities, without adding headcount. That gain doesn't stop with capture. It carries through to pricing and proposal teams who need the same historical data organized when the deadline clock starts ticking.
Frequently Asked Questions
What information do Sections L and M provide to prospective contractors in a government solicitation?
Section L tells offerors what to submit and how (page limits, forms, deadlines). Section M tells them how the government will evaluate it. Treating these as interchangeable creates both compliance flags and weaker scores.
What is past performance qualification in government contracting?
Past performance qualification is the FAR 15.305(a)(2) standard evaluators use to judge recency, relevance, source credibility, and performance trend of prior work, not contract dollar value.
How does Section M weighting change which citations you submit?
Read the evaluation factors before selecting references. Where Section M weights recency and relevance heavily, a smaller recent contract in the same scope outscores a larger older one; where it emphasises magnitude, the calculus reverses. Submitting a standard citation set regardless of how the solicitation scores past performance leaves points on the table.
Are contractors required to prepare an annual past performance evaluation?
No. FAR 42.15 makes CPARS evaluation an agency responsibility, prepared by government assessing officials. Contractors get a 14-day comment window but should document performance continuously throughout the contract.
How many past performance references does a typical proposal require?
It varies by solicitation, but three tightly relevant, recently completed references usually beat five loosely related ones. Evaluators score what they can quote directly.
Can a company with no federal contracts still win a government contract?
Yes. FAR 15.305(a)(2)(iv) requires a neutral rating for offerors without relevant history, so you cannot be scored unfavorably for lacking it. Relevant commercial experience can also be submitted and evaluated.
