Past Performance Evaluation Order Form Guide: PPQ Workflow and Customer Feedback

A guide to the past performance evaluation order form and PPQ workflow in a GSA offer, including what the form is trying to collect and how to avoid vague references.

Built for

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

By the end

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

Field guide

Past Performance Order review checks

Check 1

Choosing a weak or unprepared reference can make a strong project look average.

Signal

Customer contact information is current.

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

Project dates, value, and scope are accurate.

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

The evaluator understands the response deadline and context.

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

The form starts or supports the process for collecting customer feedback about prior performance.

It belongs in the experience and performance lane with past performance narratives and project examples.

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.

Customer contact information is current.
Project dates, value, and scope are accurate.
The evaluator understands the response deadline and context.

Part 3

What to watch before upload

Choosing a weak or unprepared reference can make a strong project look average.

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 Order upload helps

Before sending a PPQ request, the offer team confirms the customer remembers the project, has the right contact details, and understands the GSA context.

Frequently asked questions

Is Past Performance Order 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 Order fit in the offer package?

It belongs in the experience and performance lane with past performance narratives and project examples.

What is the safest review habit?

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