Skip to content
BidPulsar
BidPulsar™FBP Product Division
Built by Federal Bid Partners • team has written hundreds of proposals
RP-Led CMMC
Need proposal or grant support? Talk with our capture and CMMC team.
GSA7 min readUpdated June 7, 2026

Proposed EPA Mechanism Guide: Supporting GSA Escalation and Price Movement

A guide to the proposed economic price adjustment mechanism upload, including escalation logic, support, and how it should connect to the pricing story.

Built for
GSA MAS offer teams building an eOffer upload package from the Refresh 32 checklist
By the end
Know what the Proposed EPA file proves and how to prepare it without creating review friction.
Field guide

Proposed EPA review checks

Check 1
Choosing an escalation percentage without support makes future price movement look arbitrary.
Signal
Escalation method is named clearly.
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
Support explains why the method fits the offer.
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 mechanism does not contradict the price file.
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 EPA mechanism explains how proposed prices may move after award and why that approach is reasonable.

It belongs in the pricing and contract-maintenance lane with pricing support and the price file.

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.

  • Escalation method is named clearly.
  • Support explains why the method fits the offer.
  • The mechanism does not contradict the price file.
Part 3

What to watch before upload

Choosing an escalation percentage without support makes future price movement look arbitrary.

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 Proposed EPA upload helps

A labor-heavy contractor explains its annual rate movement with market compensation context, then ties that to labor category rates and pricing support.

Frequently asked questions

Is Proposed EPA 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 Proposed EPA fit in the offer package?

It belongs in the pricing and contract-maintenance lane with pricing support and the price file.

What is the safest review habit?

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