Skip to content

Handbook 4Chapter 6 of 8

Pricing Narrative and Compliance Matrix Templates

Six copy-ready templates for the parts of a bid that decide whether you are compliant and whether your price makes sense: a compliance matrix, an RFP questions letter, a pricing narrative, a basis of estimate, an assumptions and exceptions list and a clarification response letter.

38 min readUpdated All levels

Key takeaways

  • Start the compliance matrix the day the RFP arrives and update it after every amendment and set of answers; it is your outline, your task list and your final check.
  • Ask questions in writing, through the channel the RFP names, before the deadline, and assume every competitor will read them.
  • A pricing narrative explains how you built the price; a basis of estimate shows the math for each task. Both must match the technical volume exactly.
  • Assumptions describe conditions your price depends on; exceptions reject a requirement. Exceptions can make a bid non-responsive, so use them rarely and precisely.
  • Answer clarification requests directly, by the deadline, and change nothing the buyer did not ask or allow you to change.

A proposal can lose before anyone reads your approach: a missed requirement, an exception buried in the price volume, or a number the evaluator cannot trace. This chapter gives you a compliance matrix template in structured plain text, plus copy-ready templates for the documents around it: a letter of questions to the issuer, a pricing narrative, a basis of estimate (BOE), an assumptions and exceptions list, and a clarification response letter. Each template has a fields list, and the guidance shows how to adapt it for construction, IT, professional services and nonprofit bids.

Where pricing and compliance documents fit in your bid

These six documents are not written in one sitting. Each one belongs to a stage of the bid, and they feed each other: your questions come out of building the compliance matrix, the answers change the matrix and your assumptions, and the assumptions shape the price. The timeline below shows when each one is drafted on a typical four-to-six-week response.

When each document is drafted
  1. Day 1 to 3

    Compliance matrix, first version

    Shred the instructions, evaluation criteria, scope and forms into rows. Every unclear requirement becomes a candidate question.

  2. Before the question deadline

    Questions to the issuer

    Send one consolidated, numbered letter through the channel the RFP names, ideally a few days before the deadline.

  3. When answers or amendments arrive

    Matrix update

    Add new requirements, close answered questions and acknowledge each amendment the way the RFP asks.

  4. Middle weeks

    Basis of estimate and pricing narrative

    Build the price from the same staffing plan and schedule as the technical volume.

  5. Final week

    Assumptions and exceptions list

    Finalize only the assumptions the price truly depends on, and any exceptions you have decided to take.

  6. After submission

    Clarification response

    If the buyer asks for clarification, answer exactly what was asked by the deadline.

Key terms
Compliance matrix

A table of every requirement in the solicitation, with its source, where your proposal answers it, who owns it and its status.

Cross-reference (response) matrix

A shorter version submitted with the proposal so evaluators can find where each requirement is answered.

Shred

Breaking the RFP into individual requirement statements, usually by finding every 'shall', 'must' and 'will'.

Basis of estimate (BOE)

The documented reasoning behind each cost element: the method, the data and the math that produced the hours, quantities and rates.

Loaded labor rate

A direct wage rate plus fringe benefits, overhead, general and administrative expense and profit.

Other direct costs (ODCs)

Non-labor costs charged directly to the contract, such as travel, materials, software licenses or equipment rental.

Assumption

A condition your approach and price are based on, stated so the buyer knows what happens if it changes.

Exception

A statement that you do not accept a requirement or term of the solicitation as written.

Clarification

A limited exchange after submission in which the buyer asks you to explain or confirm something, usually without letting you revise the proposal.

Discussions and BAFO

Broader negotiations with offerors still in contention, usually ending with a request for final proposal revisions or a best and final offer (BAFO).

Amendment or addendum

A formal change to the solicitation issued by the buyer. You usually must acknowledge each one.

Compliance matrix template (structured plain text)

A compliance matrix turns a 90-page RFP into a checklist you can manage. Internally, it is the backbone of the proposal: it drives the outline, assigns writers, flags questions and becomes the final check before submission. Externally, many RFPs ask you to submit a cross-reference or response matrix so evaluators can find each answer quickly. Others forbid extra pages, so check the instructions before you include one.

How to build a compliance matrix in seven steps
  1. Step 1: Collect every document

    The RFP, all attachments and exhibits, the price form, required forms and certifications, specifications or scope of work, the draft contract, and every amendment or addendum. Note the version date of each.

  2. Step 2: Shred the instructions

    Read the submission instructions line by line and create one row for each requirement: every 'shall', 'must', 'will', 'is required to', 'include', 'provide' and 'submit', plus page limits, fonts, file formats and delivery rules. Keep the RFP's wording and section reference.

    Tip: Search the PDF for those words, but still read every page. Requirements hide in tables, footnotes and attachments.
  3. Step 3: Add the evaluation criteria

    Map each evaluation factor to the instruction rows that answer it. If a criterion has no matching instruction, add a row anyway: evaluators score what the criteria say.

  4. Step 4: Add scope and specification requirements

    Each task, deliverable, service level or technical specification gets a row and a compliance position: comply, comply with an assumption, or exception.

  5. Step 5: Add forms, terms, insurance and bonds

    Signature pages, affidavits, amendment acknowledgments, insurance limits, bid security, diversity utilization plans and any registration or license proof the RFP requires.

  6. Step 6: Assign owners and locations

    Give every row an owner and a planned location in your outline (volume, section, page). Mark rows that need a question to the issuer.

  7. Step 7: Update, then verify

    Update the matrix after every amendment and set of answers. Before submission, have someone who did not write the proposal check every row against the final files.

Sample compliance matrix rows (illustrative)
Sample compliance matrix rows (illustrative)
IDRFP referenceRequirementProposal locationOwnerStatus
A-02Sec. 4.1, p. 18Technical proposal shall not exceed 25 pages, 11-point font, 1-inch marginsVolume I, allProposal managerComplete
B-04Sec. 4.3(c), p. 20; Criterion 2 (30 points)Describe the approach to transitioning services within 30 days of awardVol. I, Sec. 3.2, p. 9Operations leadIn progress
C-11SOW 3.6, p. 41Respond to emergency work orders within 2 hours, 24/7Vol. I, Sec. 3.4, p. 12; Assumption A-3Operations leadQuestion pending (Q-5)
D-03Attachment FSigned non-collusion affidavit, notarizedVolume III, Tab 4Contracts managerNot started
E-02Contract Art. 12Professional liability insurance of 2 million dollars per claimVol. III, Tab 6; Exception E-1Contracts managerComplete

Template

Compliance matrix (structured plain text)

A complete five-part compliance matrix you can paste into a document or spreadsheet: submission rules, content mapped to evaluation criteria, scope requirements, forms, and contract terms, with a status key and a final verification line.

When to use it

Every bid, from a 10-page quote to a multi-volume proposal. Keep it internal, or trim it to the location columns if the RFP asks you to submit a cross-reference matrix. Paste the rows into a spreadsheet if you prefer one column per field.

COMPLIANCE MATRIX
Solicitation: [SOLICITATION_NUMBER], [SOLICITATION_TITLE]
Issuer: [ISSUING_AGENCY]
Proposal due: [DUE_DATE] at [DUE_TIME] [TIME_ZONE]  |  Questions due: [QUESTIONS_DUE_DATE]
Amendments incorporated: [AMENDMENT_NUMBERS_AND_DATES_OR_NONE]
Matrix owner: [PROPOSAL_MANAGER]  |  Last updated: [LAST_UPDATED_DATE]

STATUS KEY: C = complete and verified | IP = in progress | NS = not started | Q = question pending with issuer | NA = not applicable (explain in notes)

PART A. SUBMISSION AND FORMAT REQUIREMENTS
ID | RFP reference | Requirement | Proposal location | Owner | Status | Notes
A-01 | [SECTION_PAGE] | Deliver [NUMBER_OF_COPIES_OR_FILES] in [FORMAT] by [DELIVERY_METHOD] no later than [DUE_DATE_TIME] | Transmittal | [OWNER] | [STATUS] | [NOTES]
A-02 | [SECTION_PAGE] | Page limit of [PAGE_LIMIT] for [VOLUME_NAME]; font [FONT_SIZE]; margins [MARGINS] | All volumes | [OWNER] | [STATUS] | [NOTES]
A-03 | [SECTION_PAGE] | File naming and labeling: [NAMING_RULE] | All files | [OWNER] | [STATUS] | [NOTES]
A-04 | [SECTION_PAGE] | Price submitted separately from technical proposal: [YES_NO_AND_RULE] | Volume [X] | [OWNER] | [STATUS] | [NOTES]

PART B. PROPOSAL CONTENT MAPPED TO EVALUATION CRITERIA
ID | RFP reference | Requirement | Evaluation criterion and weight | Proposal location | Owner | Status
B-01 | [SECTION_PAGE] | Describe [TOPIC] | [CRITERION_NAME], [POINTS_OR_WEIGHT] | Vol. [X], Sec. [X.X], p. [PAGE] | [OWNER] | [STATUS]
B-02 | [SECTION_PAGE] | Provide [NUMBER] past performance references on the agency's form | [CRITERION_NAME], [POINTS_OR_WEIGHT] | Vol. [X], Sec. [X.X] | [OWNER] | [STATUS]
B-03 | [SECTION_PAGE] | Provide resumes for [KEY_POSITIONS], maximum [PAGES] pages each | [CRITERION_NAME], [POINTS_OR_WEIGHT] | Vol. [X], App. [X] | [OWNER] | [STATUS]
B-04 | [SECTION_PAGE] | [REQUIREMENT] | [CRITERION_NAME], [POINTS_OR_WEIGHT] | [LOCATION] | [OWNER] | [STATUS]

PART C. SCOPE OF WORK AND SPECIFICATION REQUIREMENTS
ID | SOW or spec reference | Requirement | Compliance position | Proposal location | Status
C-01 | [SOW_PARAGRAPH] | [REQUIREMENT] | Comply | [LOCATION] | [STATUS]
C-02 | [SOW_PARAGRAPH] | [REQUIREMENT] | Comply with assumption [A-NUMBER] | [LOCATION] | [STATUS]
C-03 | [SOW_PARAGRAPH] | [REQUIREMENT] | Exception [E-NUMBER] (approved by [APPROVER]) | [LOCATION] | [STATUS]

PART D. FORMS, CERTIFICATIONS AND ATTACHMENTS
ID | Form or attachment | What it requires | Signer | Notarized | Location | Status
D-01 | [FORM_NAME_OR_NUMBER] | [WHAT_IT_REQUIRES] | [SIGNER] | [YES_NO] | [TAB_OR_APPENDIX] | [STATUS]
D-02 | Amendment acknowledgments | Sign and return each amendment, or list them in the transmittal letter if the RFP allows | [SIGNER] | No | [LOCATION] | [STATUS]
D-03 | [DIVERSITY_OR_UTILIZATION_PLAN_IF_REQUIRED] | [GOAL_AND_FORM] | [SIGNER] | [YES_NO] | [LOCATION] | [STATUS]

PART E. CONTRACT TERMS, INSURANCE AND BONDS
ID | RFP reference | Requirement | Our position | Location | Status
E-01 | [CLAUSE] | Insurance: [COVERAGE_TYPES_AND_LIMITS] | [ACCEPT / ACCEPT WITH ASSUMPTION / EXCEPTION E-NUMBER] | [LOCATION] | [STATUS]
E-02 | [CLAUSE] | Bid security: [AMOUNT_OR_PERCENT_AND_FORM] | [ACCEPT] | [LOCATION] | [STATUS]
E-03 | [CLAUSE] | [OTHER_KEY_TERM, for example liquidated damages, payment terms, indemnification] | [POSITION] | [LOCATION] | [STATUS]

OPEN ITEMS
[ROW_ID]: [ISSUE] | Action: [ACTION_NEEDED] | Owner: [OWNER] | Due: [DATE]

FINAL VERIFICATION
Checked against the final submission files by [REVIEWER_NAME] on [VERIFICATION_DATE].
Every row is marked C, or NA with an explanation: [YES_NO]
Every amendment is acknowledged: [YES_NO]

Fields to fill in

[AMENDMENT_NUMBERS_AND_DATES_OR_NONE]
Update this line every time the buyer issues a change. It tells reviewers which version of the RFP the matrix reflects.
[Row IDs (A-01, B-01 and so on)]
Letter by part, number by order. Use the same IDs in your question letter and assumptions list so everything cross-references.
[SECTION_PAGE]
The exact RFP section and page, for example 'Sec. 4.3(c), p. 20'. Evaluators and reviewers both need it.
[Requirement]
Copy the RFP's wording for anything mandatory. Paraphrase only for long descriptive passages, and never soften a 'shall'.
[CRITERION_NAME], [POINTS_OR_WEIGHT]
From the evaluation section. Weight tells writers where to spend their pages.
[Compliance position]
Comply, comply with assumption (give its number), or exception (give its number and who approved it).
[OWNER]
One named person per row, not a department.
[STATUS]
Use the status key. 'Q' rows must be closed or converted to assumptions before submission.
[Final verification]
Done by someone who did not write the proposal, against the final PDF or printed copies, not the drafts.
Internal compliance matrix versus a submitted cross-reference matrix
Internal compliance matrix versus a submitted cross-reference matrix
Internal compliance matrixSubmitted cross-reference matrix
PurposePlan, assign and verify the whole responseHelp evaluators find each answer
ColumnsReference, requirement, location, owner, status, notes, open itemsReference, short requirement, proposal section and page
Who sees itYour team onlyThe evaluators
When requiredAlways (best practice)When the RFP asks, or when it allows extra pages and the response is long
Watch out forLetting it go stale after amendmentsPage limits: check whether the matrix counts against them

RFP questions letter: how do you write questions to the issuer?

Most RFPs set a question period with a firm deadline and name one person or portal for all communication. Questions are your chance to fix ambiguities, correct errors, and ask for changes to requirements that would limit competition or add needless cost. They are also public: buyers usually publish every question and answer to all prospective bidders, often as an amendment or addendum, so write as if your competitors will read every word.

In federal procurements, once a solicitation is released the contracting officer is the focal point for all exchanges, and information given to one potential offeror that bidders need to prepare proposals must be made available to everyone. State and local buyers follow similar rules, and many go further.

What to ask, and what to keep to yourself

Good questions

  • Do: Conflicts between sections, for example a page limit of 20 in one place and 25 in another
  • Do: Missing information you need to price, such as workload data, site square footage or the number of users
  • Do: Requirements that seem to favor one product or vendor, with a request to accept equivalents
  • Do: Unclear evaluation or submission rules, such as whether the price form counts toward the page limit
  • Do: A deadline extension, with a short reason, when the RFP is complex or a key attachment was late

Avoid

  • Don't: Questions that reveal your solution, your pricing approach or your partners
  • Don't: Questions already answered in the RFP (they signal you did not read it)
  • Don't: Several questions packed into one paragraph
  • Don't: Argumentative or sales-pitch questions
  • Don't: Phone calls or emails to anyone other than the designated contact
Weak exampleWeak question

Can you tell us more about the help desk requirements and what the county is looking for? We have a lot of experience with help desks and want to make sure our innovative tiered model fits.

Vague, reveals your approach, and gives the buyer nothing specific to answer.

Strong exampleStrong question

Reference: SOW 3.2, page 14, and Attachment C. Background: SOW 3.2 requires support for 'all county users', but Attachment C lists ticket volumes for 2,100 users while Section 1.1 states the county has 3,400 employees. Question: For pricing purposes, should offerors assume 2,100 or 3,400 supported users? Suggested resolution: please confirm the number, or provide 12 months of ticket volume for the full user base.

Cites the exact sections, explains the conflict in one sentence, asks one answerable question and offers a fix.

Template

Questions to the issuer letter

A consolidated, numbered letter of questions that cites each RFP reference, explains the issue in one sentence and asks one specific question, with an optional suggested resolution.

When to use it

During the question period, sent to the designated contact through the exact email address or portal the RFP names. If the RFP supplies a question form, put the same content into that form.

[COMPANY_NAME]
[COMPANY_ADDRESS]

[DATE]

To: [DESIGNATED_CONTACT_NAME], [DESIGNATED_CONTACT_TITLE]
[ISSUING_AGENCY]
Submitted via: [EMAIL_ADDRESS_OR_PORTAL_EXACTLY_AS_STATED_IN_RFP]

Re: Questions regarding [SOLICITATION_NUMBER], [SOLICITATION_TITLE]

Dear [DESIGNATED_CONTACT_NAME]:

[COMPANY_NAME] respectfully submits the following questions about the solicitation referenced above, in accordance with Section [QUESTIONS_SECTION] of the solicitation and before the question deadline of [QUESTION_DEADLINE]. Where the solicitation provides a question form, the same questions are entered on that form and attached.

Question 1
Reference: Section [SECTION], page [PAGE]
Background: [ONE_SENTENCE_QUOTING_OR_SUMMARIZING_THE_LANGUAGE_AT_ISSUE]
Question: [ONE_SPECIFIC_QUESTION]
Suggested resolution: [WHAT_THE_ISSUER_COULD_DO, for example confirm a figure, provide data, accept an equivalent, extend a date]

Question 2
Reference: Section [SECTION], page [PAGE]
Background: [BACKGROUND]
Question: [ONE_SPECIFIC_QUESTION]

Question 3
Reference: Attachment [ATTACHMENT_ID], [FORM_OR_TABLE_NAME]
Background: [BACKGROUND]
Question: [ONE_SPECIFIC_QUESTION]

Question 4 (schedule)
Reference: Section [SECTION], Schedule of Events
Background: [REASON_AN_EXTENSION_WOULD_HELP_THE_BUYER, for example time to incorporate answers to these questions]
Question: Would [ISSUER_SHORT_NAME] consider extending the proposal due date to [REQUESTED_DATE]?

We understand that questions and answers may be shared with all prospective proposers. Please let us know if you need these questions in a different format.

Thank you for your time and for the opportunity to propose.

Sincerely,

[YOUR_NAME]
[YOUR_TITLE], [COMPANY_NAME]
[YOUR_EMAIL] | [YOUR_PHONE]

Fields to fill in

[DESIGNATED_CONTACT_NAME], [EMAIL_ADDRESS_OR_PORTAL_EXACTLY_AS_STATED_IN_RFP]
Copy from the solicitation's communications section. Questions sent anywhere else may be ignored or, in some jurisdictions, recorded as improper contact.
[QUESTIONS_SECTION], [QUESTION_DEADLINE]
Cite the section that invites questions. Send a day or two early; deadlines are firm and late questions often go unanswered.
[Reference line]
Section, page and amendment number if relevant. The buyer should find the issue in seconds.
[Background]
One sentence. Quote the conflicting or unclear language rather than describing it.
[Question]
One question per number, answerable with a fact, a yes or no, or a document.
[Suggested resolution]
Optional, but it makes a 'yes' easy. Frame it around the buyer's benefit, such as more competition or more accurate pricing.
[Question 4 (schedule)]
Delete if you do not need more time. Ask once, with a reason, early in the question period.

Pricing narrative and basis of estimate templates

The price form tells the buyer what you will charge. The pricing narrative tells them why the number is right: how you built it, what it includes, what it assumes, and how it ties to your technical approach. The basis of estimate goes one level deeper and shows the method, data and math behind each task. Federal negotiated procurements, cost-reimbursement contracts, many state and city service RFPs, and most grant-funded nonprofit budgets ask for some version of both, under names like cost proposal narrative, price volume, budget justification or budget narrative.

Two cautions before you write. First, some solicitations, especially sealed bids and invitations for bid, want the price form and nothing else; extra narrative can be ignored or, worse, read as a qualification of your price. Second, many RFPs require price to be submitted separately from the technical proposal, so keep dollar figures out of the technical volume unless the instructions say otherwise. See Types of Solicitations: RFP, RFQ, IFB and RFI for how each type evaluates price.

Estimating methods and how to document each one
Estimating methods and how to document each one
MethodHow it worksBest whenWhat to document
Analogous (historical)Start from actual hours or costs on a similar past job and adjust for differencesYou have reliable actuals from comparable workThe reference contract, its actuals, and each adjustment with a reason
ParametricMultiply a workload driver by a productivity rate (hours per ticket, cost per square foot)The work is repetitive and you have measured ratesThe driver quantity and its source, the rate and its source, any adjustment
Bottom-up (engineering)Estimate each task or work package and add them upThe scope is new or detailed enough to break downThe task list tied to the scope, hours per task, and who estimated them
Vendor or subcontractor quoteUse a written quote for materials, equipment or subcontracted workNon-labor items and specialty tradesThe quote, its date, its validity period and what it excludes
Expert judgmentAn experienced estimator's documented reasoningData is scarce and the approach is novelWho made the judgment, their experience, and the reasoning; never just 'based on experience'
Strong exampleWorked example: a basis of estimate for help desk staffing (illustrative numbers)

Driver. The RFP's Attachment C shows an average of 2,400 tickets a month. Our current contract with a 3,100-user agency shows 85 percent of tickets resolved at Tier 1 and 15 percent escalated to Tier 2.

Productivity. Over the last 12 months on that contract, Tier 1 tickets averaged 22 minutes including documentation, and Tier 2 tickets averaged 75 minutes.

Math. Tier 1: 2,040 tickets x 22 minutes / 60 = 748 hours a month. Tier 2: 360 tickets x 75 minutes / 60 = 450 hours a month. Each full-time employee provides about 140 productive hours a month (2,080 paid hours a year, less leave, holidays and training, is about 1,680 hours, divided by 12).

Staffing. Tier 1: 748 / 140 = 5.3, rounded up to 6 FTEs because the county's data shows Monday volume about 30 percent above average. Tier 2: 450 / 140 = 3.2, staffed with 3 FTEs plus the team lead covering overflow.

Every number has a source, the math is visible, and the rounding decisions are explained. An evaluator can disagree with an input, but cannot call the estimate unsupported.

Template

Pricing narrative (price volume introduction)

A seven-part narrative that summarizes the price, explains how it was built, covers labor and non-labor costs, states inclusions and exclusions, and confirms consistency with the technical proposal.

When to use it

When the RFP asks for a cost or price narrative, budget justification or price volume, or allows supporting explanation with the price form. Skip it when the RFP limits the price submission to the form alone.

PRICE PROPOSAL NARRATIVE
[COMPANY_NAME]  |  [SOLICITATION_NUMBER], [SOLICITATION_TITLE]  |  [DATE]

1. PRICE SUMMARY
[COMPANY_NAME] proposes a total price of [TOTAL_PRICE] for the base period and [OPTION_TOTAL] for [NUMBER_OF_OPTIONS] option periods, as entered on [PRICE_FORM_NAME]. Our pricing is [PRICING_TYPE, for example firm fixed price, fixed unit prices, or fixed hourly rates] and remains valid for [VALIDITY_PERIOD].

Period | Dates | Price
Base period | [BASE_DATES] | [BASE_PRICE]
Option period 1 | [OPTION_1_DATES] | [OPTION_1_PRICE]
Option period 2 | [OPTION_2_DATES] | [OPTION_2_PRICE]
Total | | [GRAND_TOTAL]

2. HOW WE BUILT THIS PRICE
Our price is built from the same staffing plan, schedule and approach described in our technical proposal, Section [TECHNICAL_SECTION]. We estimated labor using [LABOR_ESTIMATING_METHOD, for example actual productivity data from comparable contracts] and non-labor costs using [NON_LABOR_METHOD, for example written vendor quotes]. The basis of estimate for each task is provided in [BOE_LOCATION].

3. LABOR
Labor categories: [NUMBER] categories, defined in [LABOR_CATEGORY_REFERENCE] and mapped to the positions in our staffing plan.
Direct rates: based on [RATE_BASIS, for example current payroll, a named salary survey, or the applicable wage determination or prevailing wage schedule].
Loaded rates: include fringe benefits, overhead, general and administrative expense and profit, built up as shown in [RATE_BUILDUP_REFERENCE].
Escalation: option period rates increase by [ESCALATION_PERCENT]% a year, based on [ESCALATION_SOURCE].
Wage compliance: [STATEMENT_ON_PREVAILING_WAGE_LIVING_WAGE_OR_LABOR_AGREEMENT_COMPLIANCE_OR_NOT_APPLICABLE].

4. NON-LABOR COSTS
Materials and equipment: [BASIS_AND_AMOUNT, with quotes attached as [ATTACHMENT_ID]]
Subcontracts: [SUBCONTRACTOR_NAME], [SCOPE], [VALUE], supported by [QUOTE_OR_BOE]
Travel and other direct costs: [BASIS_AND_AMOUNT]
Bonds and insurance: [INCLUDED_IN_RATES_OR_SEPARATE_LINE, with basis]

5. WHAT THE PRICE INCLUDES AND EXCLUDES
Included: [KEY_INCLUSIONS, for example transition, all supplies, after-hours emergency response]
Excluded: [EXCLUSIONS, each tied to the solicitation language or answer that supports it]
Assumptions affecting price: see our Assumptions and Exceptions List, items [ASSUMPTION_NUMBERS].

6. VALUE AND COST CONTROL
[TWO_TO_THREE_SENTENCES on why the price is realistic and how the approach controls cost risk for the buyer, for example no mobilization fee, local staff already in place, fixed monthly price tied to service levels.]
Small business or diversity participation (if applicable): [PARTICIPATION_PERCENT]% of contract value, detailed in [UTILIZATION_PLAN_REFERENCE].

7. CONSISTENCY STATEMENT
The staffing levels, hours, schedule and assumptions in this price proposal match those in our technical proposal. Where the price form required a different structure, the crosswalk is shown in [CROSSWALK_REFERENCE].

Authorized signature: ______________________
[SIGNER_NAME], [SIGNER_TITLE]  |  [DATE]

Fields to fill in

[TOTAL_PRICE], [OPTION_TOTAL], [GRAND_TOTAL]
Must match the price form to the cent. Check them last, after every other change.
[PRICING_TYPE]
Use the solicitation's own term for the contract type so there is no doubt about what you are offering.
[VALIDITY_PERIOD]
The offer validity period the RFP requires, for example 90, 120 or 180 days from the due date.
[RATE_BASIS]
Name the source. If prevailing wage, a service contract wage determination or a labor agreement applies, say so and confirm your rates meet it.
[RATE_BUILDUP_REFERENCE]
Some buyers want each indirect rate shown; others only want loaded rates. Give what the RFP asks for and no more.
[ESCALATION_PERCENT], [ESCALATION_SOURCE]
Tie escalation to a published index or your labor agreement, not a round guess.
[EXCLUSIONS]
Each exclusion should trace to the RFP or an answer. An exclusion that contradicts a requirement is really an exception and belongs in the exceptions list.
[PARTICIPATION_PERCENT]
Only if the RFP sets goals (for example MWBE or SDVOB goals on New York State contracts). Must match the utilization plan exactly.

Template

Basis of estimate (one task or work package)

A one-page BOE for a single task: identification, description, method, visible calculation, labor mix, non-labor items, assumptions and a cross-check.

When to use it

For each major task or cost element when the RFP asks for a basis of estimate, cost build-up or budget justification, and as internal backup for every price even when the buyer does not ask to see it.

BASIS OF ESTIMATE
Solicitation: [SOLICITATION_NUMBER]  |  Offeror: [COMPANY_NAME]
BOE number: [BOE_NUMBER]  |  Prepared by: [ESTIMATOR_NAME]  |  Reviewed by: [REVIEWER_NAME]  |  Date: [DATE]

1. TASK IDENTIFICATION
Task or work package: [TASK_NUMBER_AND_NAME]
Scope reference: [SOW_OR_SPEC_PARAGRAPHS]
Period covered: [PERIODS]
Deliverables or outputs: [DELIVERABLES_AND_QUANTITIES]

2. TASK DESCRIPTION
[TWO_TO_FOUR_SENTENCES describing the work, consistent with technical proposal Section [TECHNICAL_SECTION].]

3. ESTIMATING METHOD
Method: [ANALOGOUS / PARAMETRIC / BOTTOM-UP / VENDOR QUOTE / EXPERT JUDGMENT, or a combination]
Data source: [SOURCE, for example actual hours on contract [REFERENCE_CONTRACT] for [DATE_RANGE], the solicitation's workload data in [ATTACHMENT_ID], or a quote from [VENDOR] dated [QUOTE_DATE]]
Why this method fits: [ONE_SENTENCE_RATIONALE]

4. CALCULATION
Workload driver: [DRIVER, for example tickets, square feet, participants, drawings, inspections]
Quantity: [QUANTITY] per [TIME_UNIT]
Productivity or unit rate: [RATE] per [UNIT], based on [RATE_SOURCE]
Adjustment: [ADJUSTMENT_PERCENT]% for [REASON, for example larger site, new system learning curve, peak periods]
Result: [QUANTITY] x [RATE] x (1 + [ADJUSTMENT_PERCENT]%) = [TOTAL_HOURS_OR_UNITS] per [TIME_UNIT]

5. LABOR MIX
Labor category | Hours | Share | Why this category
[LABOR_CATEGORY_1] | [HOURS_1] | [SHARE_1]% | [REASON_1]
[LABOR_CATEGORY_2] | [HOURS_2] | [SHARE_2]% | [REASON_2]
Total | [TOTAL_HOURS] | 100% |

6. NON-LABOR ITEMS FOR THIS TASK
[ITEM]: [QUANTITY] x [UNIT_COST] = [ITEM_TOTAL]; source: [QUOTE_CATALOG_OR_HISTORICAL]

7. ASSUMPTIONS AND RISKS
Assumption: [ASSUMPTION], listed as item [ASSUMPTION_NUMBER] in our Assumptions and Exceptions List
Risk: [RISK] and how the estimate accounts for it: [TREATMENT]

8. CROSS-CHECK
Compared with [BENCHMARK, for example actual hours on a similar contract or an independent estimate]: [RESULT, for example within 6% after adjusting for scope]

Fields to fill in

[BOE_NUMBER]
Match your work breakdown or price form line numbers so evaluators can move between documents.
[SOW_OR_SPEC_PARAGRAPHS]
Every hour should trace to a scope paragraph. Hours with no scope reference look like padding.
[Data source]
Specific and checkable: contract, period, data set or quote. 'Industry standard' is not a source.
[Calculation]
Show the formula with real numbers. Evaluators trust math they can redo.
[ADJUSTMENT_PERCENT], [REASON]
Explain every adjustment. Unexplained round-number padding is a red flag.
[Labor mix]
Categories must match your price form and staffing plan. Do not assign senior rates to routine work without a reason.
[Cross-check]
A second method or benchmark that lands close to your estimate is strong evidence it is realistic.

Assumptions and exceptions list template

An assumption states a condition your approach and price rely on, such as site access hours, the number of users, or the buyer providing a test environment. A clarification states how you read ambiguous language. An exception says you do not accept a requirement or term as written. They carry very different risk. Clear assumptions protect you and help the buyer compare offers. Exceptions can make a proposal non-responsive: some state agencies treat any exception to their terms as grounds for rejection, others weigh exceptions in the evaluation, and some require you to list each one on a form by clause and page, or write 'none'.

How to decide what goes on the list
  1. Step 1: Try a question first

    Most assumptions start as questions. If the issuer answers during the question period, you may not need the assumption at all, and the answer applies to every bidder.

  2. Step 2: Keep only price-relevant assumptions

    List assumptions that would change your scope, schedule or price if they proved wrong. Drop boilerplate; a long list reads as a hedge.

  3. Step 3: Never assume away a requirement

    'We assume the 2-hour emergency response does not apply on weekends' is an exception in disguise when the RFP says 24/7. Treat it as an exception or comply.

  4. Step 4: Take exceptions only to terms you truly cannot accept

    Typical candidates are unlimited liability, insurance limits you cannot obtain, or intellectual property terms that conflict with licensed software. Get approval from an officer of the company.

  5. Step 5: Propose specific replacement language

    Quote the clause, offer exact alternative wording, give a business reason and state the price effect if it is not accepted. Buyers can accept a precise proposal; they cannot accept 'to be negotiated'.

Assumptions that protect you versus wording that creates risk

Clear and safe

  • Do: 'Pricing assumes work at the 14 sites listed in Attachment B; added sites would be priced at the unit rates on the price form.'
  • Do: 'We assume the county provides a test environment by week 4, as stated in the answer to Question 12.'
  • Do: 'Night work, if required, will be performed between 10 p.m. and 6 a.m. as described in SOW 2.4.'

Risky or non-responsive

  • Don't: 'Our price is subject to change after a site visit.' (qualifies a firm price)
  • Don't: 'We take exception to the payment terms.' (no clause, no alternative, no reason)
  • Don't: 'We assume insurance requirements will be negotiated after award.' (an exception disguised as an assumption)

Template

Assumptions, clarifications and exceptions list

A three-part list that separates assumptions (with basis and effect), clarifications of ambiguous language, and exceptions (with quoted clause, proposed language, reason and price effect).

When to use it

With the price or administrative volume whenever you have assumptions or exceptions, or when the RFP requires an exceptions form. If the RFP supplies its own form, transfer the content into it.

ASSUMPTIONS, CLARIFICATIONS AND EXCEPTIONS
[COMPANY_NAME]  |  [SOLICITATION_NUMBER], [SOLICITATION_TITLE]  |  [DATE]

Except as listed below, [COMPANY_NAME] takes no exception to the terms, conditions, specifications and requirements of the solicitation, including amendments [AMENDMENT_NUMBERS]. Nothing below changes our acceptance of the solicitation's mandatory requirements.

PART 1. ASSUMPTIONS
Our technical approach and price are based on the conditions below. If a condition does not hold, we will work with [ISSUER_SHORT_NAME] to agree on any adjustment through the contract's change process.

A-1
Solicitation reference: [SECTION_OR_SOW_PARAGRAPH]
Assumption: [WHAT_WE_ASSUMED, stated as a fact about the work]
Basis: [WHY_IT_IS_REASONABLE, for example the solicitation's workload data, the site visit on [DATE], or the answer to Question [NUMBER]]
Effect if it changes: [EFFECT_ON_SCOPE_SCHEDULE_OR_PRICE, for example additional sites priced at the unit rates on the price form]

A-2
Solicitation reference: [REFERENCE]
Assumption: [ASSUMPTION]
Basis: [BASIS]
Effect if it changes: [EFFECT]

PART 2. CLARIFICATIONS
These state how we have read language that could be interpreted more than one way. They do not take exception to any requirement.

CL-1
Solicitation reference: [REFERENCE]
Our interpretation: [INTERPRETATION]

PART 3. EXCEPTIONS
(If there are none, replace this part with: None. [COMPANY_NAME] takes no exceptions to the solicitation.)

E-1
Solicitation reference: [CLAUSE_NUMBER_AND_TITLE], page [PAGE]
Current language: "[QUOTED_LANGUAGE]"
Proposed language: "[PROPOSED_REPLACEMENT_LANGUAGE]"
Reason: [BUSINESS_REASON, for example the required limit is not commercially available to firms of our size at a reasonable cost]
Effect on price if not accepted: [PRICE_EFFECT_OR_NONE]
Alternatives we would accept: [ALTERNATIVE, for example a lower limit with an umbrella policy]

Approved by: [OFFICER_NAME], [OFFICER_TITLE]
Authorized signature: ______________________   Date: [DATE]

Fields to fill in

[AMENDMENT_NUMBERS]
List every amendment you acknowledge, so the buyer knows which version of the terms you accepted.
[Assumption]
State it as a fact about the work, not a condition on your offer. Avoid 'subject to'.
[Basis]
Point to the RFP, an attachment, the site visit or a published answer. An assumption with a basis looks reasonable; one without looks like a hedge.
[Effect if it changes]
Tell the buyer how a change would be handled, ideally by existing unit prices or the change clause.
[Clarifications]
Use sparingly, for genuine ambiguity the question period did not resolve.
[QUOTED_LANGUAGE], [PROPOSED_REPLACEMENT_LANGUAGE]
Quote exactly and propose exact wording. Vague exceptions are the ones most likely to be rejected.
[PRICE_EFFECT_OR_NONE]
Some buyers evaluate the cost of exceptions. Saying 'none' when true makes the exception easier to accept.
[Approved by]
Exceptions are business decisions. Have an officer with authority to bind the company approve each one.

How to respond to a clarification request

After submission, a buyer may send questions about your proposal. In federal negotiated procurements, clarifications are limited exchanges used when the agency plans to award without discussions; they can cover things like the relevance of your past performance, adverse past performance information you have not had a chance to address, or minor clerical errors. Discussions are broader negotiations with the offerors still in contention and usually end with a request for final proposal revisions. State and local buyers use similar steps under names like requests for clarification, interviews, oral presentations and best and final offers.

The rule for a clarification response is discipline. Answer exactly what was asked, in the order asked, by the deadline, with a pointer to where the answer already sits in your proposal. Do not revise your price, approach or staffing unless the buyer has asked or allowed you to; an unrequested change can turn a clarification into something the buyer cannot accept, or be ignored entirely.

Clarification response workflow
  1. Stage 1: Log the request

    Note the deadline, the format and who sent it.

  2. Stage 2: Classify each item

    Explanation, confirmation, clerical correction, or a revision the buyer invited.

  3. Stage 3: Draft direct answers

    One to three sentences each, with proposal references.

  4. Stage 4: Check consistency

    Against the price form, technical volume and assumptions list.

  5. Stage 5: Sign and send

    From an authorized signer, through the channel the buyer named, before the deadline.

Template

Clarification response letter

A formal reply to a buyer's request for clarification: each request quoted, a direct answer, a proposal reference, and a closing statement that the proposal is otherwise unchanged.

When to use it

When a buyer sends questions about your submitted proposal. If the buyer instead opens discussions or requests final proposal revisions, follow those instructions; this letter is for clarifications.

[COMPANY_LETTERHEAD]

[DATE]

[DESIGNATED_CONTACT_NAME]
[DESIGNATED_CONTACT_TITLE]
[ISSUING_AGENCY]
Submitted via: [EMAIL_ADDRESS_OR_PORTAL_NAMED_IN_REQUEST]

Re: Response to request for clarification dated [REQUEST_DATE]
Solicitation: [SOLICITATION_NUMBER], [SOLICITATION_TITLE]
Offeror: [COMPANY_NAME] ([VENDOR_ID])

Dear [DESIGNATED_CONTACT_NAME]:

Thank you for your [EMAIL_LETTER_OR_PORTAL_MESSAGE] of [REQUEST_DATE] requesting clarification of the proposal [COMPANY_NAME] submitted on [SUBMISSION_DATE]. Our responses follow in the order of your requests, and are provided by the requested deadline of [RESPONSE_DEADLINE].

Item 1
Your request: "[QUOTED_REQUEST_1]"
Our response: [DIRECT_ANSWER_1, in one to three sentences]
Proposal reference: [VOLUME_SECTION_PAGE]. No change to the proposal.

Item 2
Your request: "[QUOTED_REQUEST_2]"
Our response: [DIRECT_ANSWER_2]
Proposal reference: [VOLUME_SECTION_PAGE]. No change to the proposal.

Item 3 (clerical correction)
Your request: "[QUOTED_REQUEST_3]"
Our response: [EXPLANATION_OF_THE_ERROR_AND_THE_CORRECT_FIGURE_OR_TEXT]. This correction does not change [OUR_TOTAL_PRICE_OR_TECHNICAL_APPROACH].
Proposal reference: [VOLUME_SECTION_PAGE]. Corrected page attached only because you requested it.

Except as stated above, our proposal is unchanged, and our offer remains valid through [OFFER_VALIDITY_DATE].

Our point of contact for this procurement remains [CONTACT_NAME], [CONTACT_TITLE], [CONTACT_PHONE], [CONTACT_EMAIL].

Sincerely,

[SIGNER_NAME]
[SIGNER_TITLE], authorized to bind [COMPANY_NAME]

Attachments: [ATTACHMENT_LIST_OR_NONE]

Fields to fill in

[EMAIL_ADDRESS_OR_PORTAL_NAMED_IN_REQUEST]
Reply through the channel the buyer used or named, even if you know other people at the agency.
[VENDOR_ID]
Whatever identifier the buyer uses for you: Unique Entity ID (UEI) on federal bids, or the state or city vendor number.
[QUOTED_REQUEST_1]
Quote each request exactly so there is no dispute about what you answered.
[DIRECT_ANSWER_1]
Lead with the answer ('Yes, the project manager is full time'), then one sentence of support. No marketing.
[No change to the proposal]
Keep this line unless the buyer asked or permitted a revision. It signals discipline.
[Item 3 (clerical correction)]
Use only for obvious errors such as a transposed number or a missing page reference. Show the correct figure and its effect.
[OFFER_VALIDITY_DATE]
Confirm the offer is still open. If the buyer asked you to extend validity, state the new date.
[SIGNER_NAME], [SIGNER_TITLE]
Someone authorized to bind the company, ideally the same person who signed the proposal.

How to adapt these templates for construction, IT, professional services and nonprofits

The structure of each template holds across sectors; what changes is how price is expressed and which compliance items carry the most risk. Use this table to tune each template before you start.

Pricing and compliance by industry
Pricing and compliance by industry
IndustryPricing narrative and BOECompliance items to watchTypical assumptions and exceptions
Construction and facilitiesLump sum or unit prices, allowances, alternates, schedule of values, bond premiums, escalation on long schedules, prevailing wage ratesBid form, bid security, addenda acknowledgments, non-collusion affidavit, licenses, insurance certificates, MWBE or SDVOB utilization plans, apprenticeship rulesSite access hours, existing conditions, hazardous materials excluded unless specified, permit fees; exceptions to liquidated damages or indemnity terms
IT and softwareOne-time implementation versus recurring subscription, support tiers, hosting, licenses, service level credits, option-year escalationSecurity and privacy questionnaires, accessibility requirements, data location, cyber insurance, software license termsNumber of integrations, data quality for migration, client-provided environments; exceptions to liability caps, intellectual property and source code terms
Professional services and consultingLabor categories, hourly rates, hours by task, deliverable-based milestones, travelKey personnel qualifications, labor category definitions, conflict of interest disclosures, rate validityNumber of meetings and review cycles, stakeholder availability, turnaround time on client comments; exceptions to unlimited revisions or payment terms
Nonprofits and human servicesLine-item budget with a budget narrative: staff positions and FTEs, fringe, indirect costs, participant costs, cost per participant, any matchBoard approval, audited financial statements, insurance, program forms, the funder's budget templateReferral volumes, space or equipment provided by the funder, start date; indirect cost rate rules

Construction bidders should pay special attention to wage and bonding rules. Public works in New York, New Jersey and Connecticut generally carry state prevailing wage requirements (coverage and dollar thresholds vary by state), much federal and federally funded construction follows Davis-Bacon wage rates, and many federal service contracts carry Service Contract Act wage determinations; your rate basis must say which applies. Bonds and certifications are covered in Bonding, Insurance and Compliance Requirements and Small Business and Diversity Certifications.

Nonprofits should follow the funder's budget template exactly and explain every line in the narrative. If the solicitation is for a federal grant or a subaward of federal funds, the budget generally follows the federal Uniform Guidance, which as of 2026 lets an organization without a negotiated indirect cost rate claim a de minimis rate of up to 15 percent of modified total direct costs. City and state contracts often set their own indirect rate rules, and some federal agencies apply different limits, so follow the RFP and confirm with the program officer or your accountant.

Pricing and compliance mistakes to avoid

Do and don't

Do

  • Do: Rebuild the compliance matrix after every amendment and acknowledge each amendment as instructed
  • Do: Use the buyer's price form exactly, with every line filled (write 0 or 'included' rather than leaving blanks, if the RFP allows)
  • Do: Show your math in the basis of estimate and name every data source
  • Do: Keep staffing, hours and schedule identical across the technical and price volumes
  • Do: Send questions early, in one numbered letter, to the designated contact only
  • Do: Have an officer approve every exception before submission

Don't

  • Don't: Put dollar figures in the technical volume when the RFP requires a separate price submission
  • Don't: Qualify a firm price with phrases like 'subject to change' or 'estimate only'
  • Don't: Bury exceptions in a cover letter, assumptions list or footnote
  • Don't: Justify hours with 'based on our experience' and no data
  • Don't: Change prices or approach in a clarification response nobody asked you to revise
  • Don't: Call agency staff during a restricted or no-contact period
Final pricing and compliance check before you submit0 of 10 done

For the full submission-day routine, including file naming, delivery and receipts, pair this checklist with the templates in Bid Management Templates and Checklists and the review process in Reviews, Submission and Debriefs.

Frequently asked questions

What columns should a compliance matrix template include?

At minimum: a requirement ID, the RFP reference (section and page), the requirement in the solicitation's own words, where your proposal answers it, the owner and the status. Add the evaluation criterion and its weight for content requirements, and a notes column for questions and assumptions. Group rows by type, such as submission and format rules, proposal content, forms and contract terms, so nothing gets lost. If the RFP asks for a cross-reference matrix, submit a shorter version with just the requirement and where you answer it.

Do I have to submit the compliance matrix with my proposal?

Only if the solicitation asks for one or clearly allows it. Many RFPs require a cross-reference matrix; others impose strict page limits or forbid extra materials, and a matrix may count against those limits. Read the submission instructions. Either way, keep a full internal compliance matrix for every bid, because it is your best protection against missing a requirement.

What is a basis of estimate?

A basis of estimate (BOE) is the written explanation of how you arrived at each cost in your proposal: the task it covers, the estimating method (historical, parametric, bottom-up, vendor quote or expert judgment), the data source, the calculation and the assumptions. A good BOE lets an evaluator retrace your math and see that the hours and costs match the work described in your technical proposal. Federal cost proposals often require one; for other bids, keep it as internal backup.

What is the difference between an assumption and an exception in a proposal?

An assumption states a condition your price and approach are based on, such as the number of sites or users, without rejecting any requirement. An exception says you do not accept a requirement or term as written. Assumptions are normal and helpful when they are reasonable and tied to the RFP. Exceptions are riskier: depending on the buyer's rules they can lower your score or make your proposal non-responsive, so take them rarely, list them where the RFP says, and propose exact alternative language.

Will other bidders see the questions I ask?

Usually, yes. Public buyers typically publish every question and its answer to all prospective bidders, often in an amendment or addendum, and they often (but not always) remove the name of the company that asked. Federal rules require information given to one potential offeror that is needed to prepare proposals to be made available to all. Write questions that do not reveal your solution, pricing or partners.

What should I do if I miss the question deadline?

Check the solicitation first: some buyers accept late questions at their discretion, but most are not obliged to answer them. If the issue is a genuine conflict or error, you can still submit the question to the designated contact and explain why it matters, but plan to proceed without an answer. Resolve the issue in your proposal with a clear, reasonable assumption rather than an exception, and do not contact anyone other than the designated contact.

What is the difference between clarifications and discussions?

In federal negotiated procurements, clarifications are limited exchanges, used when the agency intends to award without discussions, that let an offeror explain things like past performance relevance or correct minor clerical errors. They generally do not allow you to revise your proposal. Discussions are broader negotiations with every offeror still in contention, in which weaknesses can be raised and proposals revised, usually ending with final proposal revisions. State and local buyers use similar steps, sometimes called best and final offers.

Complete handbook

Download the complete handbook (PDF)

All 8 chapters, templates and checklists, ready to print or share.

Put it into practice

Search open RFPs from federal, state, local, education, private and non-profit issuers, each with the RFP Detector Score.

Find RFPs

Free handbooks

Keep learning

All guides and templates