The real problem: proposal teams are asked to remember a contract
Most small contractors do not lose past-performance points because they did bad work. They lose them because the proposal team cannot prove the work cleanly when the RFP lands. The contract ran for 18 months. The customer accepted the deliverables. The team solved staffing problems, hit schedule, handled surge work, and probably saved the government money somewhere. Then, six months later, someone opens the past-performance volume and asks the PM, "What happened on that task order again?"
That is a broken operating model. A $10M Defense contractor usually has enough contract history to look credible, but not enough overhead to employ a dedicated proposal operations staff. The fix is not another proposal tool. It is a monthly closeout habit that captures evidence while the work is still fresh.
Think of this as a lightweight capture system for your own performance. If you spend 30 minutes per active contract each month, you can avoid 20 to 40 hours of scramble during a live bid. More important, you stop writing vague past-performance language like "successfully supported mission-critical requirements" and start writing with facts.
What a source-selection team actually needs from your record
A useful past-performance record answers six questions quickly:
- Relevance. Was the work similar in scope, customer, labor mix, security posture, and complexity?
- Scale. What was the contract value, annual revenue, number of FTEs, sites, CLINs, deliverables, or users supported?
- Recency. Did the work happen inside the solicitation's look-back window, often three to five years?
- Quality. Were deliverables accepted, options exercised, issues closed, and customer expectations met?
- Management control. Did you manage cost, schedule, staffing, subcontractors, CDRLs, risks, and changes?
- Validation. Can a government or prime point of contact confirm the story?
That list is also your archive structure. If your monthly record does not support those six answers, it will not help much in a proposal. If it does, your past-performance section starts to write itself.
The monthly closeout ritual
Run the ritual during the first week of each month for every active contract worth using later. Do not wait for contract closeout. By closeout, people have moved, details are stale, and the PM is already worried about the next thing.
The meeting can be simple: 30 minutes, one owner, one template, one archive location. The PM brings the facts. Contracts brings modifications, funding, and customer correspondence if needed. Finance brings invoice or burn-rate notes. Capture or proposal operations owns the final record.
For a $10M shop with three to six active contracts, this is not a bureaucracy problem. It is two or three hours a month. That is cheap compared with paying a proposal consultant to reverse-engineer your history under a five-day deadline.
Use a fixed agenda:
- Scope delivered this month. What work was completed, accepted, or advanced?
- Metrics worth keeping. Hours delivered, positions filled, tickets closed, reports submitted, systems supported, sites visited, users served, or deliverables accepted.
- Customer signal. Positive feedback, corrective feedback, meeting notes, acceptance emails, exercised options, new requests, or issue closure.
- Performance risk. Staffing gaps, clearance delays, late government inputs, ODC pressure, subcontractor problems, and what you did about them.
- Proposal-useful artifact. One or two files that prove the story: an accepted CDRL, an IMS extract, a burn chart, a staffing roster, a training record, or a customer email.
The evidence file: what to capture every month
Do not turn the archive into a dumping ground. A good monthly packet is small enough that someone will maintain it and complete enough that a proposal writer can trust it.
1. Contract snapshot
Keep a one-page summary current: customer, prime or subcontract role, contract number, period of performance, total value, funded value, NAICS, contract type, place of performance, clearance level, major deliverables, and points of contact. If you are a subcontractor, capture your actual workshare instead of borrowing the prime's numbers. Inflating scope is how a past-performance reference becomes a credibility problem.
2. Monthly performance note
Write 150 to 250 words in plain English: what changed, what was delivered, what mattered, what risk was controlled. This note is not marketing copy. It is raw material. Proposal language can be polished later, but the facts need to be captured now.
3. Quantitative proof
Every contract has numbers if you look. For services work, capture FTE count, labor categories, fill rate, turnover, deliverable count, on-time percentage, help-desk tickets, inspection results, training completions, or response times. For software or data work, capture release cadence, defect closure, uptime, data volume, user count, automation savings, or backlog burn-down. Use ranges when precision is not appropriate, but do not settle for adjectives.
4. Customer and prime signal
Save acceptance emails, meeting minutes, action-item closures, CPARS drafts, award-fee notes, exercised options, letters of appreciation, and prime feedback. A two-sentence email from a COR confirming a deliverable was accepted on time can carry more weight than a generic testimonial written after the fact.
5. Artifacts that show management discipline
Past performance is not just whether the customer liked you. It is whether you controlled the work. Archive selected status reports, risk registers, staffing plans, CDRL trackers, financial burn charts, and schedule updates. If the solicitation asks how you managed similar complexity, those artifacts become proof instead of memory.
Build the B.5 skeleton before the RFP exists
Most solicitations ask for variations on the same past-performance material: contract name, customer, value, dates, role, relevance, scope, performance quality, and point of contact. You can pre-build 70 percent of that now.
Create a two-page narrative for each strong reference. Page one is structured data: the facts that rarely change. Page two is the relevance narrative: the work you performed, why it resembles future opportunities, and what proof exists. Keep the narrative modular. A logistics proposal may need staffing and surge emphasis. A software proposal may need agile cadence, cybersecurity, and user support. The same underlying record should support multiple angles without rewriting from scratch.
At $10M scale, the target is five to eight ready references. Fewer than three leaves you thin. More than ten usually means nobody is maintaining them well. Prioritize recent work, direct government relationships, similar NAICS and contract type, and work where the customer will actually answer the phone.
This is the same discipline behind small-team color reviews: do the thinking before the calendar is on fire. The proposal deadline should test your judgment, not your filing system.
The roles: who owns what in a small shop
Do not make this everyone's job. Everyone's job becomes nobody's job. Assign one owner for the archive and make the monthly input mandatory for PMs.
- Program manager. Supplies monthly facts, performance notes, risks, customer signal, and artifacts.
- Contracts or finance. Confirms value, funding, modifications, invoice status, contract type, and official dates.
- Capture/proposal owner. Maintains the archive, turns raw notes into reference narratives, and flags gaps before a live bid.
- Executive sponsor. Enforces the habit when PMs are busy and decides which references are strategically important.
If you are still founder-led, the founder may be the executive sponsor and capture owner. Fine. Just write it down. A simple RACI beats heroic memory every time.
Numbers to track because evaluators believe specifics
Past-performance writing dies when every sentence sounds like a capability statement. Specifics fix that. You do not need classified detail or proprietary customer data. You need enough defensible numbers to show scale and control.
Useful numbers include:
- Contract value, funded value, and annual run rate.
- FTE count by labor category and clearance level.
- Number of deliverables submitted and accepted on time.
- Schedule variance or milestone performance when tracked.
- Staffing fill rate, time-to-fill, and turnover on key roles.
- Help-desk tickets closed, systems supported, users served, or releases shipped.
- ODC or travel volume if it demonstrates operational complexity.
- Options exercised, scope added, or follow-on work awarded.
Keep the ranges honest. If the work was a $750K subcontract supporting 4 FTEs, say that. Do not dress it up as a $12M program because the prime held the larger vehicle. Evaluators have seen that move, and it smells desperate.
Storage: boring beats clever
The archive should live somewhere your team already uses: SharePoint, Google Drive, Box, or a controlled folder in your proposal operations workspace. The rules matter more than the tool.
Use a consistent folder pattern:
- 00_contract_snapshot for the current one-page factsheet.
- 01_monthly_notes for monthly closeout entries.
- 02_customer_signal for feedback, acceptance, and correspondence.
- 03_performance_metrics for charts, invoices, staffing, and schedule evidence.
- 04_proposal_narratives for the polished two-page B.5-ready reference.
Lock permissions tighter than normal proposal drafts. Past-performance files can contain customer names, contract numbers, pricing, proprietary prime data, and sometimes CUI-adjacent material. Treat the archive like sensitive capture data, not marketing collateral. If your work includes controlled information, keep it inside the same controlled environment you use for contract execution and link from the narrative rather than copying restricted material into a broad proposal folder.
The monthly scorecard
A simple scorecard keeps the system from becoming another abandoned folder. Once a month, rate each reference green, yellow, or red:
- Green. Snapshot current, monthly note complete, at least one artifact saved, POC confirmed, narrative updated in the last 90 days.
- Yellow. Missing one element: stale POC, weak metric, no customer signal this month, or narrative older than 90 days.
- Red. No current record, uncertain scope/value, no validating contact, unresolved performance issue, or workshare cannot be defended.
Red is not failure. Red is a warning that the reference should not be the backbone of your next bid without executive attention. Sometimes the right answer is to retire the reference, especially if the customer relationship cooled or the work no longer matches where the company is going.
This scorecard also supports bid/no-bid discipline. If an RFP requires three highly relevant references and you only have one green and two yellow, that is not just a proposal problem. That is a capture-positioning problem. Your go/no-go call should know that before anyone opens the compliance matrix.
Need a hand?
If your team is rebuilding past performance from email archaeology every time an RFP drops, we can help tighten the operating rhythm. Bring one contract, one recent proposal, and whatever evidence you have. We'll tear down the current record, show you the gaps, and give you a monthly archive pattern your PMs can actually maintain.
FAQ
How much past-performance detail should a small contractor keep?
Keep enough to prove scope, scale, complexity, schedule, cost control, and customer satisfaction without rebuilding the file later. For most contracts, that means a one-page monthly evidence note, current staffing and deliverable snapshots, key customer emails, invoice or funding summaries, and two or three proof artifacts per month. The goal is not a museum. The goal is a defensible record you can mine in two hours when the RFP asks for recent, relevant work.
Can we use prime-contractor work as past performance?
Yes, if the solicitation allows subcontractor past performance and you can clearly show the work your company actually performed. Do not over-claim the prime's scope, dollar value, or customer relationship. Capture the subcontract number, period of performance, your workshare, your deliverables, and the prime or government point of contact who can validate the work.
What if the customer will not give us a quote?
Do not wait for a polished testimonial. Capture objective facts instead: on-time deliverables, accepted data items, exercised options, added scope, issue closure, award fees, or clean invoice acceptance. A short customer email that says “accepted” or “thanks, this addresses the issue” can be more useful than a quote you never receive.
Who should own the past-performance archive?
One person should own the system, but the program manager has to feed it. In a $10M shop, the owner is usually the capture lead, contracts manager, operations lead, or a founder wearing one of those hats. The PM supplies monthly facts; the owner keeps the archive clean and proposal-ready.
How often should we update records?
Monthly is the right cadence for active contracts. Quarterly is usually too slow because details disappear, employees move, and customer context gets fuzzy. A 30-minute monthly closeout is enough if the template is tight and the archive location is obvious.