Past Performance

Past performance is the single most predictive factor of future success in government procurement. Your contract history, performance ratings, and client references demonstrate your track record and build confidence in your capabilities. In Canadian government RFPs, past performance typically accounts for 20-40% of total evaluation points.

Why Past Performance Matters

Evaluation Weight

Most government RFPs include past performance as a major evaluation criterion:

Typical Evaluation Breakdown:

• Technical Approach: 35-45%
• Past Performance: 20-30%
• Management Approach: 15-20%
• Cost/Price: 20-30%

Past Performance Sub-Criteria:

• Relevance: How similar are your past projects to this opportunity? (40%)
• Recency: How recent is your experience? (20%)
• Performance Quality: What were your performance ratings? (25%)
• Scale: Have you handled projects of similar size/complexity? (15%)

AI Capability Matching

Cothon's AI uses past performance to validate and strengthen capability statements:

Capability Statement + Past Performance = High Confidence

Example:

Capability Statement: "We provide cybersecurity risk assessment services using NIST 800-53 framework."

Supporting Past Performance:

• "Security Risk Assessment - Public Safety Canada" ($450K, 2024)
• "NIST 800-53 Implementation - Transport Canada" ($320K, 2023)
• "ATO Package Development - Justice Canada" ($680K, 2023)

AI Assessment: 95% confidence match when RFP requires "NIST 800-53 security assessment"

Capability Statement Without Past Performance = Low Confidence

Same capability statement, but zero past performance contracts listed.

AI Assessment: 45% confidence match (claim lacks evidence)

Proposal Content Generation

The AI generates past performance narratives for proposals by pulling from your contract library:

Auto-Generated Content Example:

Your Past Performance Entry:

Project: Cloud Infrastructure Migration
Client: Innovation, Science and Economic Development Canada (ISED)
Value: $2.4M
Duration: 18 months (Jan 2023 - Jun 2024)
Scope: Migrated 450 applications and 1,200 servers from on-premise data centers
to AWS GovCloud, including application refactoring, data migration, security
hardening, and staff training.
Performance: Completed on time and 3% under budget. Zero security incidents.
Client satisfaction: 4.8/5.0.
Reference: John Smith, Director of IT Services, john.smith@ised-isde.gc.ca,
(613) 555-1234

AI-Generated Proposal Section:

Relevant Project Example: Cloud Infrastructure Migration for Innovation, Science and Economic Development Canada (ISED)

From January 2023 to June 2024, we successfully delivered a comprehensive cloud infrastructure migration for ISED, migrating 450 applications and 1,200 servers from on-premise data centers to AWS GovCloud. This $2.4M engagement is directly relevant to the current requirement as it involved similar scope, scale, and security requirements.

Our approach included application refactoring to cloud-native architectures, comprehensive data migration with zero data loss, implementation of ITSG-33 security controls, and extensive training for client IT staff. The project was completed on time and 3% under budget with zero security incidents during or after migration.

Client satisfaction was rated 4.8/5.0, with particular recognition for our proactive risk management and seamless cutover execution. The Director of IT Services, John Smith, is available as a reference (john.smith@ised-isde.gc.ca, 613-555-1234) to discuss our performance and outcomes.

Result: Rich, credible past performance narratives automatically generated from your structured data.

Contract Information to Capture

Basic Contract Details

Contract Title: Descriptive project name (use client's official project name if available)

Client Organization: Full official name (e.g., "Public Services and Procurement Canada" not "PSPC")

Client Department/Branch: Specific division or branch (e.g., "Real Property Branch")

Contract Number: Official contract/agreement number (if not confidential)

Contract Value: Total contract value in CAD

• Exact amount if single contract (e.g., "$1,245,000")
• Range if sensitive (e.g., "$1M-$2M")
• Include amendments/modifications in total

Contract Duration:

• Start Date: YYYY-MM-DD
• End Date: YYYY-MM-DD (or "Ongoing" for active contracts)
• Total Duration: (automatically calculated, e.g., "18 months")

Contract Type:

• Firm Fixed Price (FFP)
• Time and Materials (T&M)
• Cost Plus Fixed Fee (CPFF)
• Indefinite Delivery Indefinite Quantity (IDIQ)
• Task Order/Call-up
• Standing Offer Agreement (SOA)

Prime or Subcontractor:

• Prime Contractor (you directly contracted with client)
• Subcontractor (you worked under prime contractor)
  • If subcontractor, list prime contractor name

Project Scope and Deliverables

Scope Summary: 2-3 paragraph description of project scope, objectives, and context

Key Deliverables: Bullet list of major deliverables

• Reports, studies, assessments
• Designs, drawings, specifications
• Software applications, systems, platforms
• Physical construction, installations
• Training, documentation, support

Services Provided: Specific services you delivered (aligns with your capability statements)

Technical Approach: Brief description of methodology, technologies, frameworks used

Team Size: Number of personnel deployed (FTEs and total team)

Example - Project Scope Entry:

Contract: "Enterprise Resource Planning (ERP) System Implementation"

Scope Summary:

"Implemented SAP S/4HANA ERP system for the Department of Fisheries and Oceans (DFO), replacing legacy financial and procurement systems across 26 regional offices serving 12,000 employees. The project included business process re-engineering, data migration from three legacy systems (JD Edwards, Oracle Financials, custom procurement database), system configuration, integration with GCPay and GCHire platforms, comprehensive testing, and national user training."

Key Deliverables:

• Current State Assessment and Business Process Documentation
• Future State Process Design and Configuration Blueprints
• Data Migration Strategy and Migration Tools
• Configured SAP S/4HANA System with 15 Custom Extensions
• Integration with GCPay and GCHire (RESTful APIs)
• Test Plans, Test Cases, and Test Results Documentation
• Training Materials (user guides, quick reference cards, e-learning modules)
• Post-Go-Live Support (6 months hypercare)

Services Provided:

• ERP consulting and business process re-engineering
• SAP S/4HANA configuration and customization
• Data migration and cleansing
• System integration (APIs, middleware)
• Training development and delivery
• Change management and organizational readiness

Technical Approach:

"SAP Activate methodology with Agile delivery model. Configured SAP Finance (FI), Controlling (CO), Materials Management (MM), and custom procurement modules. Developed 15 custom ABAP extensions for Canadian government-specific requirements (bilingual interfaces, GC security controls). Integrated via RESTful APIs with GCPay (payment processing) and GCHire (HR system). Data migration using SAP Data Services with custom ETL scripts for legacy system extraction."

Performance Metrics and Outcomes

Schedule Performance:

• On-Time Delivery: Yes/No
• Schedule Variance: (e.g., "Delivered 2 weeks early" or "3% ahead of schedule")
• Milestones Met: X of Y milestones delivered on time

Budget Performance:

• On-Budget Delivery: Yes/No
• Cost Variance: (e.g., "Delivered 2% under budget" or "within 1% of budget")
• No Cost Overruns: Confirmed

Quality Performance:

• Defect Rate: (e.g., "0.02 defects per 1000 lines of code")
• Rework Required: (e.g., "Zero design rework required")
• Acceptance: (e.g., "All deliverables accepted on first submission")

Client Satisfaction:

• Overall Rating: X/5.0 or percentage
• Specific Ratings: Communication, quality, timeliness, professionalism

Business Outcomes:

• Cost Savings: (e.g., "Enabled $2.3M annual operating cost reduction")
• Efficiency Gains: (e.g., "Reduced process time from 45 days to 18 days")
• Revenue Impact: (e.g., "Enabled $5M additional program delivery capacity")
• User Adoption: (e.g., "95% user adoption within 3 months")

Safety and Security:

• Safety Incidents: (e.g., "Zero lost-time injuries")
• Security Incidents: (e.g., "Zero security breaches or data loss")
• Compliance: (e.g., "100% compliance with ITSG-33 controls")

Example - Performance Metrics:

Contract: "Highway 401 Bridge Rehabilitation Design"

Schedule Performance:

• On-Time Delivery: Yes
• Schedule Variance: Delivered 3 weeks early (12% ahead of schedule)
• All 5 major milestones delivered early or on-time

Budget Performance:

• On-Budget: Yes
• Cost Variance: 1.5% under budget ($45K savings on $3M contract)

Quality Performance:

• Ministry of Transportation design review: Zero deficiencies identified
• All drawings accepted on first submission
• Peer review by external P.Eng.: No issues found

Client Satisfaction:

• Overall Rating: 4.9/5.0
• Communication: 5.0/5.0
• Technical Quality: 4.8/5.0
• Responsiveness: 5.0/5.0

Business Outcomes:

• Rehabilitation design extended bridge life from 25 to 50 years (100% improvement)
• Value engineering recommendations saved $1.2M in construction costs (18% savings)
• Phased construction approach maintained traffic flow (zero full closures required)

Safety:

• Zero safety incidents during design phase site visits
• Construction safety analysis identified and mitigated 8 high-risk activities

Client Reference Information

Reference Contact Name: Full name and title

Reference Contact Title: Position/role

Reference Contact Email: Direct email address

Reference Contact Phone: Direct phone number (include extension)

Relationship: How this person knows your work (e.g., "Project Manager overseeing our contract", "Client representative receiving deliverables")

Reference Consent: Confirmed Yes/No (always obtain permission before listing as reference)

Reference Quality:

• Excellent (will provide strong positive reference)
• Good (will provide positive reference with minor caveats)
• Fair (may provide mixed feedback)
• Do Not Use (issues occurred, negative feedback likely)

Example - Reference Entry:

Reference Contact: Jennifer Chen, Director of IT Modernization

Organization: Shared Services Canada

Email: jennifer.chen@ssc-spc.gc.ca

Phone: (613) 555-7890 ext. 245

Relationship: Jennifer was the Client Project Manager overseeing our $4.2M cloud migration contract. She directly managed our Statement of Work, reviewed all deliverables, and conducted our performance evaluations.

Reference Consent: Yes (confirmed via email 2024-03-15)

Reference Quality: Excellent (Jennifer rated our performance 4.9/5.0 and has expressed willingness to serve as reference for similar opportunities)

Key Points Jennifer Can Speak To:

• Our technical approach to AWS migration and security implementation
• Our proactive communication and risk management throughout the project
• Our ability to deliver on time despite scope changes mid-project
• Quality of our deliverables and documentation
• Professionalism of our team and collaboration with SSC staff

Organizing Past Performance

Relevance-Based Organization

Organize contracts by relevance to your core capabilities:

Tier 1 - Flagship Projects (5-10 contracts):

• Your absolute best, most relevant, most impressive contracts
• Large scale, excellent performance, strong references
• Recent (last 3 years)
• Directly align with core capabilities

Tier 2 - Supporting Projects (15-25 contracts):

• Solid performance, good relevance
• Mix of sizes and recency
• Demonstrate breadth and consistency
• Support core and secondary capabilities

Tier 3 - Additional Experience (25-50+ contracts):

• Older projects (3-7 years)
• Smaller projects
• Adjacent capabilities
• Demonstrates depth of experience and track record

Capability-Aligned Organization

Tag contracts by capability area:

Example - IT Consulting Firm:

Capability: Cloud Migration

• 12 contracts tagged
• Total value: $28M
• Average project size: $2.3M

Capability: Cybersecurity Assessment

• 18 contracts tagged
• Total value: $15M
• Average project size: $830K

Capability: Custom Application Development

• 22 contracts tagged
• Total value: $42M
• Average project size: $1.9M

AI Usage: When RFP requires "cloud migration expertise," the AI pulls from the 12 cloud migration-tagged contracts for relevant past performance examples.

Client-Type Organization

Group by client type to demonstrate sector experience:

Federal Government:

• 45 contracts, $85M total value
• Departments: ISED, SSC, PSPC, DND, Transport Canada, etc.

Provincial Government:

• 28 contracts, $38M total value
• Provinces: Ontario, BC, Alberta, Quebec

Municipal Government:

• 15 contracts, $12M total value
• Cities: Toronto, Vancouver, Calgary, Montreal

Crown Corporations:

• 8 contracts, $15M total value
• Organizations: Canada Post, VIA Rail, CBC, etc.

Private Sector (if relevant):

• 12 contracts, $22M total value

Recency-Based Organization

Highlight recent performance:

Last 12 Months: 8 contracts, $12M Last 24 Months: 18 contracts, $28M Last 36 Months: 32 contracts, $52M

Why It Matters: Many RFPs specify "provide 3 relevant contracts from last 3 years." Organizing by recency enables quick filtering.

Writing Effective Past Performance Narratives

Storytelling Structure

Use storytelling to make past performance memorable:

Challenge → Approach → Results

Example:

Challenge:

"The Department of National Defence (DND) needed to migrate 2,500 legacy applications from aging on-premise data centers to cloud infrastructure within 18 months. The challenge was significant: applications ranged from 25-year-old COBOL mainframe systems to modern web applications, with complex interdependencies and strict security requirements (Protected B classification). The existing data centers were scheduled for decommissioning, creating a hard deadline with severe consequences for mission-critical operations if missed."

Approach:

"We developed a risk-prioritized migration strategy, assessing all 2,500 applications across 6 dimensions (technical complexity, business criticality, security classification, interdependencies, data volume, stakeholder readiness). This assessment created a migration sequence optimizing for risk reduction—mission-critical low-complexity applications migrated first to build confidence and refine processes.

Our technical approach included:

• Application portfolio rationalization (eliminated 400 redundant applications, saving $3M in migration costs)
• Containerization of 600 applications using Docker and Kubernetes for cloud portability
• Lift-and-shift migration of 1,200 applications with minimal refactoring
• Re-platforming of 300 applications to cloud-native services (AWS Lambda, RDS, S3)
• Data migration using AWS Database Migration Service with zero downtime cutover
• Security hardening implementing ITSG-33 controls and PBMM (Protected B, Medium Integrity, Medium Availability) compliance

We deployed a 45-person team including 20 AWS-certified cloud engineers, 15 application migration specialists, 5 security specialists, and 5 project managers. Work was organized in 6 parallel migration streams with weekly synchronization and risk review."

Results:

"The migration was completed 2 weeks ahead of the 18-month deadline, 4% under budget ($320K savings on $8M contract), with zero mission-critical application downtime. Post-migration outcomes included:

• 42% reduction in infrastructure operating costs ($4.5M annual savings)
• 99.95% application availability (improvement from 98.2% on-premise)
• 60% reduction in provisioning time for new application resources (2 days vs. 5 days)
• 85% faster deployment cycles through CI/CD automation
• Zero security incidents during or after migration

Client satisfaction was rated 4.8/5.0, with the DND CIO stating: 'This was the most complex IT transformation DND has undertaken, and [Company] delivered with professionalism, technical excellence, and unwavering commitment to success.' The CIO and the Director of Cloud Services are available as references."

Quantify Everything

Use specific numbers, not adjectives:

❌ Vague: "We delivered high-quality results on time and under budget with excellent client satisfaction."

✅ Quantified: "We delivered all 8 project milestones on time, completed the project 5% under budget ($125K savings on $2.5M contract), achieved zero defects in final deliverables, and received 4.7/5.0 client satisfaction rating."

❌ Vague: "We successfully managed a large, complex project with a significant team."

✅ Quantified: "We managed a $12M, 24-month program deploying a 65-person multidisciplinary team across 8 regional offices, coordinating 15 subcontractors and delivering 45 major milestones with 96% on-time completion rate."

Highlight Challenges Overcome

Procurement evaluators value problem-solving and resilience:

Examples:

Challenge: Scope Changes

"Mid-project, the client identified an additional 200 applications requiring migration (20% scope increase). We absorbed this scope change with only 6-week timeline extension (10% increase) and no cost overrun by optimizing our migration factory processes and redeploying resources from completed streams."

Challenge: Technical Complexity

"Three mainframe applications were initially deemed 'unmigrateable' to cloud. We developed custom modernization approaches including COBOL-to-Java refactoring for two applications and mainframe-as-a-service containerization for the third, successfully migrating all three without functionality loss."

Challenge: Tight Timeline

"The project deadline was accelerated by 4 months due to lease expiration of the existing data center. We increased team size from 30 to 45 FTEs, implemented 24/5 operations (weekday night shifts for testing and cutover), and delivered on the accelerated timeline without quality compromise."

Challenge: Stakeholder Resistance

"Initial user adoption was slow (35% after month 1) due to change resistance. We implemented an enhanced change management program including executive champions, peer advocates, and intensive hands-on training, achieving 92% adoption by month 3 and 98% by month 6."

Use Client Quotes

Direct client testimonials add powerful credibility:

Examples:

"[Company Name] delivered exceptional results on our most complex IT modernization project. Their technical expertise, proactive communication, and unwavering commitment to success exceeded our expectations." — Jane Smith, CIO, Innovation, Science and Economic Development Canada

"The quality of engineering design was outstanding—zero deficiencies in MTO review, all drawings accepted on first submission. This is rare in our experience with consultants." — Robert Chen, P.Eng., Chief Engineer, Ministry of Transportation Ontario

"Their change management approach was the difference between project success and failure. User adoption exceeded our targets, and staff feedback was overwhelmingly positive." — Marie Dubois, Director of Business Transformation, Revenu Québec

How to Obtain Quotes:

1. Request testimonial at project closeout (when satisfaction is highest)
2. Provide suggested text or questions to guide client
3. Get written permission to use quote in proposals
4. Attribute fully (name, title, organization)

Link to Capability Statements

Explicitly connect past performance to your capability statements:

Example:

Capability Statement:

"We provide bridge inspection and rehabilitation design services using non-destructive evaluation techniques and CSA S6 standards."

Supporting Past Performance Narrative:

"This capability is demonstrated by our recent contract for the City of Vancouver, 'Knight Street Bridge Structural Assessment and Rehabilitation Design' ($2.8M, 2023-2024). We conducted comprehensive structural inspection using ground-penetrating radar, ultrasonic testing, and visual inspection per CSA S6-19 standards. Our rehabilitation design extended bridge life 30 years and was delivered on time with zero MTO review deficiencies. This project exemplifies our bridge engineering expertise and aligns directly with the current RFP requirements."

AI Impact: When generating proposals, the AI sees the explicit linkage and uses this past performance example for the relevant RFP requirements.

Past Performance Metrics and Analytics

Aggregate Performance Statistics

Calculate aggregate metrics across your portfolio:

Overall Performance Statistics:

• Total Contracts Completed: 150
• Total Contract Value: $285M
• Average Contract Value: $1.9M
• On-Time Delivery Rate: 96% (144 of 150 contracts)
• On-Budget Delivery Rate: 94% (141 of 150 contracts)
• Average Client Satisfaction: 4.6/5.0
• Average Cost Variance: -2.3% (under budget)
• Average Schedule Variance: -1.5% (ahead of schedule)

By Contract Size:

• Small (<$500K): 65 contracts, 98% on-time, 4.7/5.0 satisfaction
• Medium ($500K-$2M): 55 contracts, 95% on-time, 4.6/5.0 satisfaction
• Large ($2M-$5M): 22 contracts, 95% on-time, 4.5/5.0 satisfaction
• Major (>$5M): 8 contracts, 88% on-time, 4.5/5.0 satisfaction

By Client Type:

• Federal Government: 58 contracts, $145M, 4.7/5.0 satisfaction
• Provincial Government: 45 contracts, $82M, 4.6/5.0 satisfaction
• Municipal Government: 35 contracts, $38M, 4.5/5.0 satisfaction
• Crown Corporations: 12 contracts, $20M, 4.6/5.0 satisfaction

By Service Area:

• Cloud Migration: 25 contracts, $68M, 97% on-time, 4.8/5.0 satisfaction
• Cybersecurity: 35 contracts, $42M, 94% on-time, 4.6/5.0 satisfaction
• Application Development: 40 contracts, $95M, 96% on-time, 4.5/5.0 satisfaction
• Project Management: 30 contracts, $52M, 98% on-time, 4.7/5.0 satisfaction

Performance Trends

Track performance trends over time:

Year-over-Year:

• 2024: 32 contracts, $58M, 98% on-time, 4.8/5.0 satisfaction (improving trend)
• 2023: 28 contracts, $52M, 95% on-time, 4.6/5.0 satisfaction
• 2022: 25 contracts, $45M, 94% on-time, 4.5/5.0 satisfaction
• 2021: 22 contracts, $38M, 93% on-time, 4.4/5.0 satisfaction

Insight: Performance improving year-over-year demonstrates process maturity and continuous improvement.

Benchmarking

Compare your performance against industry benchmarks:

Use in Proposals: "Our on-time delivery rate of 96% exceeds the industry average of 78% by 18 percentage points, demonstrating our commitment to schedule performance."

Common Past Performance Mistakes

Mistake 1: Listing Contracts Without Context

Problem:

- Cloud Migration Project, Government of Canada, $2M, 2023
- Security Assessment, Department X, $500K, 2022
- Application Development, Agency Y, $1.5M, 2021

Why It Fails:

• No detail on scope or deliverables
• No performance metrics
• No outcomes or results
• Impossible for AI to match against requirements
• Evaluators can't assess relevance

Fix: Write full narratives with scope, approach, results, and references for each contract.

Mistake 2: Only Listing Successful Projects

Problem: Only including "perfect" projects with no challenges

Why It's Suspicious:

• Evaluators know every project has challenges
• Absence of challenges suggests dishonesty or inexperience
• Misses opportunity to showcase problem-solving skills

Fix: Include realistic challenges and how you overcame them. Authenticity builds credibility.

Mistake 3: Outdated Past Performance

Problem: All past performance from 5-10 years ago

Why It Fails:

• Many RFPs require "last 3 years" past performance
• Old projects suggest you're no longer active or capability has degraded
• Technology evolves—10-year-old IT project is obsolete

Fix: Maintain current project pipeline. If you lack recent projects in a capability area, mark that capability as "Emerging" or remove it.

Mistake 4: No Client References

Problem: Past performance listed but "References available upon request"

Why It Fails:

• Evaluators assume you lack permission or had poor performance
• Delays evaluation process
• Reduces credibility

Fix: Include full reference contact information with permission for every major contract.

Mistake 5: Exaggerating Role or Results

Problem: "We delivered a $50M ERP implementation" (reality: you were a $2M subcontractor on a $50M prime contract)

Why It's Fraud:

• Misrepresents your actual role and scope
• Verification reveals discrepancy
• Can result in disqualification and debarment

Fix: Be accurate about your role (prime vs. sub), your scope (if sub, what % or what specific deliverables), and your contract value (your subcontract, not total prime).

Mistake 6: Generic Performance Claims

Problem: "All projects delivered successfully with high client satisfaction"

Why It Fails:

• No specific metrics
• Unverifiable claims
• Sounds like marketing fluff

Fix: Provide exact metrics: "96% on-time delivery rate (144 of 150 contracts), average client satisfaction 4.6/5.0 across 150 projects."

Building Your Past Performance Library

Start with Recent Major Contracts

Begin by documenting your top 10-15 most recent, most significant contracts:

Selection Criteria:

• Completed within last 3 years (recent)
• Contract value >$500K (significant)
• Excellent performance (4.5/5.0+ satisfaction)
• Strong reference available (client will speak positively)
• Relevant to core capabilities (aligns with your focus areas)

Expand to Supporting Contracts

After documenting flagship projects, expand to 20-30 supporting contracts:

• Mix of sizes (include smaller contracts demonstrating consistency)
• Range of clients (show breadth—federal, provincial, municipal)
• Various capability areas (support all core and secondary capabilities)
• Recent and slightly older (last 5 years)

Maintenance and Updates

Add New Contracts Immediately:

• As soon as a contract is completed and closed out
• Capture data while fresh (details, metrics, client feedback)
• Request reference permission before relationship cools

Update Ongoing Contracts Quarterly:

• Active contracts: update status, milestones achieved
• Performance metrics: update as data becomes available

Annual Review:

• Archive contracts >7 years old (move to "Historical Experience")
• Update aggregate statistics
• Refresh client references (confirm contacts still valid)
• Request updated testimonials for key contracts

Past Performance in AI Proposal Generation

How the AI Uses Past Performance

When generating proposals, Cothon's AI:

1. Relevance Matching:

• Compares RFP requirements against past performance scope and tags
• Ranks past performance by relevance score (0-100%)

2. Selects Examples:

• Top 3-5 most relevant contracts become detailed case studies
• Next 10-15 become corporate experience summary
• Remaining contracts contribute to aggregate statistics

3. Generates Narratives:

• Pulls scope, approach, results from your past performance data
• Emphasizes aspects most relevant to current RFP
• Incorporates client testimonials where available

4. Creates Compliance Matrices:

• Maps past performance to specific RFP evaluation criteria
• Generates compliance statements: "Demonstrated by our contract with [Client]..."

Optimizing for AI Generation

Tag Thoroughly:

• Tag each contract with all relevant capability areas
• Tag with technologies, methodologies, standards used
• Tag with client type, sector, geography

Write Detailed Scopes:

• AI generates better content from detailed source material
• 300-500 words per contract for flagship projects

Include Specific Outcomes:

• AI emphasizes quantified outcomes in proposal narratives
• "40% cost reduction" is better than "cost effective"

Provide Client Quotes:

• AI incorporates direct quotes when available
• Strengthens credibility of generated content

Link to Capabilities:

• Explicitly state which capability statements this past performance supports
• AI recognizes linkages and uses aligned examples

Next Steps

Once your past performance library is built:

FAQ

Q: How many past performance contracts should I include in my profile?

A: Minimum 10-15 for meaningful AI matching and proposal generation. Ideal range: 20-40 contracts covering your core capabilities. Beyond 50 contracts, prioritize recent and relevant over comprehensive historical listing.

Q: Should I include contracts where performance was less than perfect?

A: Include contracts where overall performance was good (4.0/5.0+) even if there were challenges. Exclude contracts with serious performance issues (<3.5/5.0 satisfaction) unless you can frame them as lessons learned with corrective actions implemented.

Q: How detailed should past performance narratives be?

A: Flagship projects (top 10-15): 400-600 words with full Challenge→Approach→Results narrative. Supporting projects: 200-300 words focusing on scope and key outcomes. Additional projects: 100-150 words with basic scope and metrics.

Q: Can I include contracts where I was a subcontractor?

A: Yes, absolutely. Clearly state your role as subcontractor, identify the prime contractor, and describe YOUR specific scope and deliverables (not the overall prime contract). Use your subcontract value, not the prime contract value.

Q: What if my client won't provide a reference?

A: Not every contract needs a reference. Prioritize references for your flagship 10-15 contracts. For others, note "Reference available upon request" or "Reference: [Name], [Title] (permission pending)." Never list someone as reference without permission.

Q: Should I include very old contracts (10+ years)?

A: Generally no for detailed past performance narratives. However, include them in aggregate statistics ("170 total contracts over 15 years") to demonstrate longevity and depth of experience. Some RFPs require "Demonstrate 10 years continuous operation in this domain"—aggregate data addresses this.

Q: How do I handle confidential or classified contracts?

A: Provide general scope description without classified details: "Cybersecurity assessment for federal law enforcement agency (Protected B classification), $800K, 2023. Scope included vulnerability assessment, penetration testing, and security architecture review. Due to classification, detailed scope and reference not available. Available for discussion under NDA."

Q: Can I use past performance from previous employers or merged companies?

A: Generally no—past performance should be YOUR company's experience. Exception: if your company acquired another company or underwent merger/name change, you can include prior company's contracts with explanation: "Project completed by [Previous Company Name] prior to merger with [Current Company] in [Year]."

Q: What if I'm a new company with limited past performance?

A: Focus on what you have: pilot projects, pro bono work, founding team's prior experience (with appropriate disclosure), and teaming arrangements. Mark capabilities as "Emerging" and pursue smaller contracts to build past performance library.

Q: Should past performance include price/cost information?

A: Include contract value (demonstrates scale) but not detailed pricing or rate information. "Contract value: $2.4M" is appropriate. "Hourly rates: $150-$200/hour" is not (pricing is typically confidential).

Q: How does the AI weight past performance vs. capability statements?

A: Both are critical. Capability statements describe what you CAN do. Past performance proves you HAVE done it. The AI achieves highest confidence (90%+) when strong capability statements are backed by relevant past performance. Capability without past performance: 50-60% confidence. Past performance without capability statement: 60-70% confidence. Both together: 90%+ confidence.

---

Your past performance library is the proof of your capabilities—the evidence that transforms claims into credibility. Invest the time to build a comprehensive, detailed, accurate past performance repository, and you'll see dramatic improvements in opportunity matching, proposal quality, and win rates.