Construction manager recording metrics on tablet outdoors

Writing Past Performance Narratives That Actually Score

August 27, 2026

A winning past performance narrative proves five things in the first paragraph an evaluator reads: relevance, recency, magnitude, measurable outcomes, and a verified point of contact. Miss any one of those and your reference gets scored down before the evaluator finishes reading it, no matter how good the underlying project was.

Federal Acquisition Regulation Subpart 42.15 governs how contractor performance information gets collected and used in source selection, and evaluators trained on CPARS data are looking for specific fields, not a general impression of your company. Before you write another word of a proposal, run every reference against this checklist:

Contract number, agency or customer name, and total contract value
Current, verified point of contact (name, title, phone, email)
Period of performance, with dates that match your CPARS record
Your firm’s exact role and percentage of work performed
At least two quantified outcomes tied directly to solicitation requirements
A one or two sentence relevance statement connecting this project to the work being bid

Pro Tip: Build these six fields into a locked header row on every reference document you keep. When a proposal deadline lands in 72 hours, you should be copying and pasting, not hunting down a project manager who left the company two years ago.

TL;DR:

Prioritize relevance in your references, leading with projects that closely match the scope and trade mix of the current solicitation, regardless of size or recency.

Use a standardized four-block structure for references, including scope, measurable outcomes, relevance tie-back, and optional corrective actions, to ensure clarity and scoring consistency.

Focus on quantifiable metrics such as on-time completion, safety incidents, cost variance, and option-year exercises, supported by verifiable evidence like customer letters or CPARS data.

Regularly verify and update your CPARS and internal records quarterly to prevent discrepancies and respond within 14 days if evaluations are inaccurate.

Build a routine of capturing project data, POCs, and metrics every quarter to create an easily accessible reference library, improving proposal readiness and evaluation scores.

How Do Evaluators Score Past Performance Narratives?
What Belongs in a Scorable Past Performance Reference Template?
Which Metrics and Evidence Actually Move the Score?
Where Do Evaluators Verify Your CPARS and PPIRS Records?
No Direct Federal Past Performance? Here Is How to Build a Credible Record
What Are the Most Common Past Performance Mistakes, and How Do You Fix Them Before Submission?
Building a Quarterly Past Performance Workflow That Holds Up Under Deadline Pressure
What the Research Behind This Guide Actually Supports
Key Takeaways
Sources

How Do Evaluators Score Past Performance Narratives?

Section M evaluators typically score past performance against four or five dimensions: relevance, recency, magnitude, complexity, and management or business relations. Each one carries different weight depending on the solicitation, but relevance almost always outranks the others.

Diagram of past performance scoring dimensions and their weights

Relevance measures how closely your past project matches the scope of work being solicited, not how big the dollar figure was. A $2 million tenant improvement job for a federal agency can outscore an $8 million commercial build if the tenant improvement work matches the current solicitation’s trade mix, site conditions, and customer type. Evaluators are asking one question: could this contractor walk into our project on day one and perform without a learning curve?

Recency typically follows a three to five year lookback window, though the exact window is set in the solicitation itself and varies by agency. A highly relevant contract from four years ago frequently beats a marginally relevant one from last year. Practitioner guidance on scoring heuristics backs this up directly: evaluators weigh relevance ahead of raw recency when the two conflict, because a contract that matches the scope tells the evaluator more about your capability than a recent contract that does not.

Magnitude looks at contract dollar value and physical scale, square footage, crew size, or unit count, compared to the solicited work. Complexity covers factors like multi-phase scheduling, hazardous conditions, historic preservation requirements, or coordination across multiple subcontractors and trades. Management and business relations is where CPARS narrative comments and customer satisfaction language carry real weight; a rating of “Satisfactory” with a bland narrative scores lower than the same rating paired with specific customer praise.

Ordering your references for maximum score impact

Most solicitations let you submit three to five references, and the order you present them in signals your best evidence first.

Lead with your most relevant reference, even if it is not your largest or most recent contract.
Follow with your second most relevant, prioritizing recency as a tiebreaker.
Place your largest-magnitude contract third if it has not already appeared, to demonstrate capacity.
Reserve your most complex project for last if it requires more explanation to connect to the solicitation.

A general contractor bidding a $4 million VA clinic renovation, for example, should lead with a prior VA or GSA healthcare renovation of similar size, even if a larger private hospital job exists in the portfolio. The private job goes second or third, framed around transferable systems work, not led with as the headline reference.

What Belongs in a Scorable Past Performance Reference Template?

Every reference should follow the same four to six block structure so evaluators can score it quickly and consistently across your entire proposal. Inconsistent formatting between references is one of the fastest ways to signal a rushed submission.

Start with a header table. Practitioner templates consistently recommend a one-row header table followed by 150 to 300 words of narrative, and that word count range is not arbitrary. It is long enough to include real evidence and short enough that evaluators reading dozens of proposals actually read the whole thing.

Below the header table, structure the narrative itself in four blocks:

Scope summary (2 to 3 sentences): what the project involved, in plain terms that mirror the language used in the current solicitation. If the solicitation says “design-build renovation,” your narrative should say “design-build renovation,” not “remodel.”
Measurable outcomes (2 to 4 sentences): the metrics that prove performance, covered in detail in the next section.
Relevance tie-back (1 to 2 sentences): an explicit sentence connecting this project’s scope, size, or complexity to the solicitation you are currently bidding. Do not make the evaluator infer this connection themselves.
Corrective action note (optional, 1 to 2 sentences): if any part of the contract had a documented issue, a brief, factual statement of what happened and what corrected it. Silence on a known problem the evaluator can find in CPARS reads worse than a short, honest explanation.

Pro Tip: Mirror the solicitation’s own vocabulary in your scope summary. If the RFP uses “critical path scheduling” and your narrative says “we kept things on track,” you have written a narrative that reads as generic. Evaluators are often scoring against a checklist derived from the RFP’s own language, and matching that language directly makes the connection easy to find.

Formatting matters as much as content here. Keep the header table visually separated from the narrative text, use consistent font and spacing across every reference in the proposal, and never let a reference run longer than one page. A reference that requires the evaluator to hunt for the point is a reference that scores lower regardless of the quality of the underlying work.

Which Metrics and Evidence Actually Move the Score?

Vague outcome statements are the single most common weakness in construction past performance narratives, and they are entirely avoidable. Evaluators are trained to look for numbers, not adjectives.

The metrics that consistently score well include:

On-time completion percentage or number of days ahead of or behind the original schedule
SLA or milestone compliance rate, particularly on multi-phase or task-order contracts
Safety incident rate (OSHA recordable incidents per hours worked), especially for anyone citing Cal/OSHA or federal safety compliance history
Cost variance, expressed as a percentage under or at the original contract ceiling
Option-year exercises, meaning the customer chose to extend or expand the contract
Customer satisfaction scores or documented written commendations
Individual CPARS element ratings (quality, schedule, cost control, management, small business utilization)

Option-year exercises deserve special attention because they are a signal evaluators trust more than almost anything a contractor can write themselves. When a customer voluntarily extends or expands a contract, that decision is documented in government records the contractor cannot manufacture or exaggerate. If you have one, state it plainly: “The customer exercised multiple option years and added additional scope during the contract.”

The strongest past performance narratives read like a status report a project manager would hand to a client, not like marketing copy. A line such as “completed most milestones on or ahead of schedule, maintained a strong safety record, and had an option year exercised at customer request” does more work than three paragraphs of praise.

Document your evidence honestly. Cherry-picking your single best metric while ignoring a documented schedule slip elsewhere in the same contract is a real risk once an evaluator pulls the CPARS record and finds a mismatch. Where you have supporting letters, customer emails, or performance evaluations beyond CPARS, reference them by name and date rather than describing them vaguely. “Per written correspondence from the COR dated June 2024” reads as verifiable. “The client was very happy with our work” does not.

Tracking these metrics as you go, rather than reconstructing them under deadline pressure, is where most contractors fall behind. A KPI tracking approach built into your project close-out process turns this into a five-minute lookup instead of a week of digging through old emails.

Foreman tracking project metrics on clipboard at site

Where Do Evaluators Verify Your CPARS and PPIRS Records?

Evaluators do not just read what you submit. They cross-reference it against government systems, and any gap between your narrative and the official record works against you.

CPARS (Contractor Performance Assessment Reporting System) is the primary portal where past performance evaluations get recorded, and PPIRS pulls that data into the broader past performance database evaluators access during source selection. FAR Subpart 42.15 sets the framework for how this information gets collected, and it applies to contracts above the simplified acquisition threshold, meaning most construction contracts of meaningful size have a CPARS record whether the contractor remembers filing one or not.

Before you submit any proposal citing a federal reference, work through this sequence:

Log into CPARS and pull every evaluation tied to your firm’s CAGE code, not just the contracts you remember well.
Download the full assessment, including narrative comments, not just the star or adjectival rating summary.
Cross-check dates, dollar values, and role descriptions against your own internal records for every contract you plan to cite.
Flag any discrepancy immediately. A rating that dropped from “Satisfactory” to “Marginal” without your knowledge, or a dollar value that does not match your invoices, needs a documented response before it surfaces in an evaluator’s review.

Pro Tip: You have 14 days from notification to submit a contractor response in CPARS when you disagree with an assessment. Missing that window means the rating stands as written, with no contractor rebuttal attached, for the life of the record. Set a calendar reminder the day you receive any CPARS notification.

If a mismatch surfaces after the response window has closed, you are not without options. Document the discrepancy in writing to the contracting officer, keep a timeline of your own performance records, and be prepared to address it proactively in your proposal narrative rather than hoping the evaluator does not notice. A brief, factual note acknowledging a rating and explaining the corrective action taken afterward is far more credible than silence.

No Direct Federal Past Performance? Here Is How to Build a Credible Record

Plenty of qualified construction firms have never held a federal prime contract, and FAR does not require one. What it does require is that you present relevant, verifiable evidence, wherever it comes from.

FAR allows evaluators to consider subcontractor performance, key personnel experience carried over from a previous employer, predecessor company history, and commercial work, provided you document it honestly. The tactics that work best include:

Secure prime contractor reference letters for every subcontract you have performed, specifying your exact scope and percentage of the total contract value.
Use GSA schedule task orders and small awards as legitimate federal references, even when the total value is modest. A $180,000 GSA task order performed flawlessly is a real, citable federal reference.
Document key personnel experience separately from firm-level past performance. If your proposed project manager ran a comparable federal job at a previous company, that experience belongs in the personnel section and reinforces your firm’s capability even if the firm itself was not the prime.
Cite state, local, and commercial work that mirrors federal requirements, framing it explicitly: “This state DOT bridge rehabilitation followed AASHTO and OSHA standards comparable to those required under this solicitation.”
Cross-reference SBIR Phase I awards or public technical work where applicable, since these carry federal credibility even outside traditional construction contracting.

Building this into a routine matters more than any single tactic. Create a reference library organized by NAICS code and contract type, verify every point of contact on a quarterly cadence so nothing goes stale, and write a one-paragraph summary for each project the moment it closes out, while the details are still fresh.

Pro Tip: A single well-documented commercial project with hard metrics, an on-time completion rate, a cost variance, a customer letter, will consistently outscore a vague federal reference with no numbers attached. Evaluators reward evidence, not the mere presence of a federal contract number.

What Are the Most Common Past Performance Mistakes, and How Do You Fix Them Before Submission?

The failures that sink otherwise strong proposals are almost always fixable in the final weeks, if you know where to look.

Vague outcome language. “Successfully completed the project” tells an evaluator nothing. Fix it by pulling actual schedule and cost data from your project close-out records and rewriting every outcome sentence with a number attached.
Stale points of contact. A COR who left the agency two years ago is a dead end when the evaluator tries to verify your reference. Fix it by calling every listed POC before submission, confirming their title and reachability, and having a backup contact ready.
Size or scope mismatch. Citing a $50,000 punch-list job against a $5 million solicitation signals poor judgment about relevance. Fix it by being honest about which references genuinely match and pairing a smaller, highly relevant job with a note explaining why its scope still applies.
Overclaiming. Describing your firm as the “lead” on a project where you were a second-tier subcontractor is a credibility risk once an evaluator checks CPARS or calls the prime. Fix it by stating your exact role and percentage performed, every time, without exception.
Missing or unreviewed CPARS entries. Submitting a reference without ever having checked whether the CPARS record matches your narrative is a preventable error. Fix it by pulling the record first, always.

When a reference is borderline, honesty beats omission. If your most relevant project is also among your smaller contracts, say so directly and explain why its scope and site conditions closely match the current requirement. Evaluators respect a contractor who understands the limits of their own evidence more than one who oversells a weak match.

Pro Tip: Read every draft narrative out loud before submission. If a sentence sounds like marketing copy rather than a status report, an evaluator will notice the same thing and score it accordingly.

Building a Quarterly Past Performance Workflow That Holds Up Under Deadline Pressure

Rowena Tulacz has spent more than three decades advising construction firms on the operational and business development side of federal contracting, and the pattern that shows up most often is the same: contractors treat past performance documentation as a proposal-season scramble instead of an ongoing operational habit.

The fix is a quarterly maintenance cycle, not a once-a-year fire drill. Build it around four recurring tasks:

Quarterly Task	What It Prevents
Verify every POC’s contact information and current title	Stale contacts discovered during a live proposal deadline
Capture and log fresh metrics from closed-out projects	Scrambling to reconstruct cost and schedule data from memory
Confirm CPARS entries match internal contract records	Discrepancies surfacing after the 14-day response window closes
Refresh backup documentation (letters, emails, screenshots)	Missing evidence when a reference needs updating mid-cycle

For each reference, maintain a standardized folder with the contract number, a metadata sheet, supporting evidence, a verified POC file, and a CPARS screenshot dated to the quarter it was pulled. A consistent naming convention across every project folder means anyone on your proposal team can find what they need without asking the one person who set up the system three years ago.

Store documentation in a shared, backed-up location, not on one estimator’s laptop.
Write a one-paragraph summary for every closed-out project within 30 days of completion, while the numbers are still fresh.
Assign one person ownership of the quarterly review, even in a small firm.

This is precisely the operational gap R Construction Solutions LLC works with construction contracting firms to close. Converting scattered project files, emails, and closeout reports into evaluator-ready narratives is a core part of the firm’s federal procurement consulting work, alongside broader support on bid preparation and estimating accuracy.

Pro Tip: If your firm has never won a federal award, start the reference library now anyway. The habit of tracking metrics and POCs pays off on your first bid and every one after it, whether the reference that ends up scoring best is federal, state, or commercial.

If your team is heading into a proposal deadline without this system in place, R Construction Solutions LLC works directly with construction contractors to build the quarterly workflow, reference library, and narrative templates described here, tailored to your firm’s actual contract history. Contact Rowena Tulacz to walk through where your past performance documentation stands today and what it would take to make it evaluator-ready before your next bid closes.

What the Research Behind This Guide Actually Supports

Rowena Tulacz’s editorial perspective on writing past performance narratives:

Most guidance on this topic treats past performance as a writing problem. It is not. It is a records problem wearing a writing problem’s clothes. Contractors who struggle to score well on past performance almost never lack good projects; they lack a system for capturing what happened on those projects while it was still fresh and verifiable.

The conventional advice tells contractors to “quantify outcomes,” which is true and useless without a habit behind it. You cannot quantify a schedule variance from eighteen months ago if nobody wrote it down. Prioritize the quarterly capture habit before you touch a single template. A contractor with a mediocre narrative template and disciplined records will consistently outscore one with a polished template and no evidence behind it.

— Rowena Tulacz

Key Takeaways

A past performance narrative scores well when it proves relevance to the solicitation, falls within the evaluator’s recency window, and backs every claimed outcome with a verified, checkable number.

Point	Details
Lead with relevance, not size	Order references by relevance to the solicitation first, then by recency and dollar magnitude.
Use the four-block structure	Pair a header data table with a 150 to 300 word narrative covering scope, outcomes, and relevance tie-back.
Quantify every outcome	Cite on-time percentages, cost variance, safety rates, and option-year exercises instead of general praise.
Verify CPARS before you submit	Pull your CPARS record, check it against your own files, and respond within the 14-day window if it is wrong.
Maintain records quarterly	Verify POCs and capture metrics every quarter so proposal season never starts with a records scramble.

Sources

These are the primary references worth bookmarking, not just citing once and forgetting.