Past Performance and Experience Guide: Writing GSA Project Narratives That Prove Fit

A guide to past performance and experience documents in a GSA offer, including project selection, scope fit, customer proof, and narrative clarity.

Built for

GSA MAS offer teams building an eOffer upload package from the Refresh 32 checklist

By the end

Know what the Past Performance file proves and how to prepare it without creating review friction.

Field guide

Past Performance review checks

Check 1

Listing impressive projects that do not match the offered scope can weaken the proof story.

Signal

Projects match the offered scope or SIN.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Check 2

Do not let this upload contradict pricing, SAM data, or narrative responses.

Signal

Dates, role, value, and customer are clear.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Check 3

Do not let this upload contradict pricing, SAM data, or narrative responses.

Signal

Narrative explains outcomes, not just tasks.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Part 1

What this upload proves

Past performance and experience evidence proves the company has delivered comparable work and understands the proposed scope.

It belongs in the technical proposal and performance lane.

Part 2

How to prepare it cleanly

Start by naming the proof role, file owner, source system, date pulled or signed, and whether the file is required, conditional, or optional for the selected offer.

Then compare the file against the pricing workbook, SAM record, eOffer narrative, and category/SIN instructions so the package tells one story.

Projects match the offered scope or SIN.
Dates, role, value, and customer are clear.
Narrative explains outcomes, not just tasks.

Part 3

What to watch before upload

Listing impressive projects that do not match the offered scope can weaken the proof story.

Use filenames that help the reviewer understand the document before opening it. A clear file name with document type, company, SIN or category when relevant, and date is usually better than an internal shorthand.

The upload goal is calm review: current file, clear purpose, no contradictions.

Examples

What this looks like in practice

Real-world exampleHow a clean Past Performance upload helps

A company offering facilities services chooses projects that show multi-site maintenance, response time, quality control, and customer coordination instead of unrelated general management work.

Frequently asked questions

Is Past Performance always required?

Treat it as required for planning purposes, then confirm the live requirement against the solicitation, eOffer prompts, and selected SIN/category instructions.

Where does Past Performance fit in the offer package?

It belongs in the technical proposal and performance lane.

What is the safest review habit?

Check the document against the pricing file, SAM record, narrative responses, and source instructions before uploading it.