Federal solar solicitations arrive in three formats, and it's worth naming them clearly before we discuss response strategy:

• Sealed bid IFB (Invitation for Bids) - Award goes to the lowest responsive, responsible bidder. Filed on Standard Form 33 (Solicitation, Offer and Award). Awards on price alone; technical passes are pass/fail. Common for straightforward retrofits with fully spec'd equipment.
• Negotiated RFP (Request for Proposals) - Award goes to the best-value offeror. Uses FAR Part 15 procedures. Technical, past-performance, and price are separately scored and traded off. Common for design-build solar, complex EPCs, and ambiguous scope.
• RFQ against a Schedule (Request for Quotations) - For agencies buying against Schedule holders. FAR Part 8.4 procedures - simpler, faster, but still evaluated on the RFQ's stated basis. Common for maintenance, small installs, and equipment purchases.

Each of the three has different pages, different evaluation criteria, and different forms. But the underlying questions the government is asking are the same in all three: Can you do the work? Have you done work like this before? Are you a responsible contractor? What will it cost? Do your products satisfy the domestic-content and trade-agreements requirements?

This guide is organized by those underlying questions, not by solicitation type. The templates flex to fit IFB, RFP, and RFQ formats.

Even though SF-33 (Solicitation, Offer and Award) is a fill-in-the-blank cover form, it is the #1 place small contractors bounce out of federal solicitations on technicalities. The evaluator sees this form first - a sloppy SF-33 sets the tone.

Pro tip: Save a pre-populated SF-33 in the shared drive with all the standard blocks (offeror name, address, UEI, CAGE, phone, email, authorized signer) filled in, so you're only editing the solicitation-specific blocks each time. This single template alone saves 15–30 minutes on every submission.

Every negotiated federal solar RFP asks the same five underlying technical questions, in different words. Structure your technical volume around them and score higher every time.

1. Do you understand the scope of work?

The government wants to see that you read the SOW, PWS, or SOO. Restate the scope in your own words, itemize the deliverables, note the assumptions the RFP left ambiguous, and identify the constraints (site access, existing infrastructure, environmental restrictions). Weak proposals paraphrase; strong proposals reveal insight - flagging a code interpretation issue or noting a schedule dependency the government hadn't articulated.

2. What's your technical approach?

Describe how you'll design, procure, install, commission, and warranty the system. Cover: modeling approach and software (PVsyst, SAM, Aurora), electrical single-line design principles, string sizing methodology, inverter selection rationale, racking selection rationale, grounding and bonding approach, monitoring and communication architecture, and code compliance methodology (NEC 690, 705, 706 as applicable; local jurisdiction). For solar+storage, add battery sizing methodology and UL 9540 / NFPA 855 compliance.

3. What's your management approach?

Show the project schedule (Gantt or milestone list), the org chart (with roles for each named team member), the quality management plan, the safety plan (SDS handling, LOTO, fall protection, arc flash), the environmental plan (spill response, waste management, MS4/SWPPP compliance), and the risk register with mitigations. Federal evaluators look for evidence that a small business is capable of running the project, not just doing the work.

4. Who is your team?

Resumes for key personnel: project manager, PE (with license number and state), superintendent, safety officer, commissioning agent. Each resume should include education, relevant certifications (NABCEP, NECA, IBEW journeyman, EPA 608 if refrigerant work is involved), specific past-project experience, and years in role. For small businesses without a full bench, name your subcontractor teammates and include their resumes too.

5. What are you going to buy, and where does it come from?

This is the section that opens the door to distributor documentation. List the major equipment: modules, inverters, racking, wire, combiner boxes, disconnects, monitoring, and (for solar+storage) batteries. For each line, name the manufacturer and model, cite the datasheet as an appendix, and note country of origin and compliance status (BABA-declared, TAA-designated country, Buy American compliant). This is where PES's per-SKU documentation pack shines - you can attach OEM declarations and country-of-origin certifications directly.

Weakness in any one of these five sections drops your score. Weakness in section 5 (equipment provenance) increasingly disqualifies proposals outright - federal evaluators have been trained to identify BABA and TAA compliance failures at the equipment-list level.

Past performance is scored separately from technical on most federal RFPs. It carries roughly equal weight - sometimes more. Per federal capability-statement guidance from GovProcure, a strong past-performance table lists 3–5 relevant contracts with: agency name, contract number, brief description, dollar value, and period of performance.

The past-performance template PES provides to contractors:

Per supplierdiversity.com's federal capability statement guidance, "credible past performance" reads like this: "USDA Forest Service, Contract GS-35F-0123X, 2022–2024, $1.4M - deployed and managed network monitoring infrastructure across 14 field offices in three regions." Vague past performance reads like "installed solar system at a school." Federal evaluators reward specificity.

What to do if you don't have federal past performance: use relevant commercial past performance, but flag it honestly. State clearly: "This is a commercial reference. Contract terms and evaluation standards differ from federal contracting; however, the technical scope closely parallels the current solicitation's requirements."

What to do about weak past performance on a specific contract: address it head-on in a "Past Performance Issue Discussion" subsection. Own the issue, describe the resolution, cite the corrective actions. Evaluators respect candor; they punish spin.

1. 1

   Day 1 - Read the entire solicitation twice

   First read: high-level scope, evaluation criteria, due date, and page limits. Second read: every FAR clause, every mandatory form, every submittal requirement. Highlight every deadline. Never rely on someone else's summary.

2. 2

   Day 2 - Bid/no-bid decision

   Score the opportunity against your bid/no-bid criteria: strategic fit, past-performance match, socioeconomic set-aside eligibility, team capacity, competitive landscape, and expected margin. If you can't score it above a documented threshold, walk away. Bidding weak opportunities wastes 200-hour proposal cycles.

3. 3

   Day 3 - Assemble the team and set the schedule

   Name a proposal manager. Identify who will write each section. Set internal review dates (Pink Team at 60% draft, Red Team at 90% draft). Book the Pink and Red Team reviewers now - they get busy.

4. 4

   Days 4–5 - Submit RFIs

   Every solicitation has an RFI window. Use it. Ask the questions where the solicitation is ambiguous: scope boundaries, evaluation criteria interpretation, whether specific products are acceptable, whether specific certifications count. RFIs unanswered are ambiguities that hurt you later.

5. 5

   Days 6–10 - Draft the technical volume

   Follow the RFP's exact section outline. Match section numbering. Match the evaluation factors in your section headings. Don't invent your own outline; the evaluator has a scoring sheet keyed to the RFP outline, not yours.

6. 6

   Days 8–12 - Draft the past-performance volume

   Parallel work with technical volume drafting. Contact each past-performance reference personally and ask permission. Send them a brief background on the current solicitation so they can respond intelligently to any survey.

7. 7

   Days 10–14 - Draft the pricing volume

   Pricing is separate. Build the price from a documented cost basis: labor rates with burden, material costs with PES quotes, subcontract quotes with executed teaming agreements, other direct costs, and margin. Include the pricing narrative explaining the buildup.

8. 8

   Day 15 - Pink Team review at 60% draft

   Small internal review team reads the proposal top-to-bottom without contributing. Their job: identify what's missing, what's confusing, and what evaluators will misread. Fix the top 10 issues before Red Team.

9. 9

   Day 18 - Red Team review at 90% draft

   External senior reviewers (or independent internal reviewers who weren't in the writing) read as if they were the evaluator. Score against the evaluation factors. Every score below 'Good' becomes a red-line.

10. 10

    Day 20 - Production, final review, and formatting

    Compile all volumes, check every page against page-limit rules, verify every attachment, sign every form. Reserve a full day just for production - federal proposals need signed cover pages, table of contents matching pagination, cross-reference matrices, and clean PDF outputs.

11. 11

    Day 21 - Submit early

    Submit at least 4 hours before the due time. Federal submission systems (SAM.gov, PIEE, agency-specific portals) freeze up in the final hour. Late submission is late - no exceptions. Print the submission receipt.

Every federal solar RFP now includes country-of-origin, domestic-content, and Trade Agreements Act certifications. Per FAR Part 25 (Foreign Acquisition), the specific certification clauses vary by contract type, but most solicitations include one or more of:

• FAR 52.225-2 - Buy American Certificate (for Buy American Act coverage)
• FAR 52.225-4 - Buy American - Free Trade Agreements - Israeli Trade Act Certificate
• FAR 52.225-6 - Trade Agreements Certificate
• FAR 52.225-24 - Notice of Required Use of American Iron, Steel, and Manufactured Goods - Buy American Statute - Construction Materials Under Trade Agreements
• Agency-specific BABA certification clauses (2 CFR 184 flowdown)

The certifications are unforgiving. Certifying compliance and then delivering non-compliant materials is a False Claims Act exposure. The certification templates below have to match your actual sourcing plan.

Template A - Buy American Certificate (adapted from FAR 52.225-2)

"The offeror certifies that each end product, except those listed in paragraph (b) of the certification, is a domestic end product as defined by FAR 52.225-1. The offeror shall list as foreign end products those end products that are not domestic end products. Country of origin is stated for each foreign end product listed."

Attach: a table listing every equipment line, its manufacturer, model number, country of origin, and its status (domestic end product, qualifying country end product, foreign end product). PES provides this table pre-populated for every stocked SKU.

Template B - BABA Domestic Content Declaration

"The offeror certifies that all iron and steel products, manufactured products, and construction materials incorporated into the project shall be produced in the United States as required by the Build America, Buy America Act (Section 70914 of the Infrastructure Investment and Jobs Act, Pub. L. No. 117-58) and OMB Guidance at 2 CFR Part 184. For manufactured products, the offeror certifies that the domestic content ratio exceeds 55% of the total cost of components, calculated per 2 CFR 184.5."

Attach: for each manufactured product, the OEM's BABA declaration by SKU. For iron and steel products, the mill test report showing melt through coatings in the U.S. For construction materials, the manufacturer's certificate of origin.

Template C - TAA Certification (for Schedule-based procurements)

"The offeror certifies that each end product to be delivered under this contract is a U.S.-made or designated country end product, as defined in the Trade Agreements clause of this contract."

Attach: country-of-origin table with an added TAA-status column (U.S.-made, designated country, or non-designated country).

Why the three certifications are not interchangeable: Buy American Act uses the 60/65/75% component test on federal direct procurement. BABA uses the 55% test on federally assisted infrastructure. TAA is a country-of-origin test - country either qualifies or doesn't, no cost fraction. A single equipment line on a federal solar bid can trigger all three. Per CBH's analysis of the domestic-content escalator, tracking the specific vintage of Buy American Act thresholds matters for accurate certification.

Federal RFPs increasingly require a pricing narrative - a written explanation of how you arrived at your price. Even when not explicitly required, a strong narrative influences best-value trade-off evaluations. Structure it like this:

Contractors who submit a "we're offering $842,300 as a lump sum" price with no narrative get pushed toward the lower tail of the price distribution during best-value evaluations. Contractors who submit a fully justified buildup with vendor quotes attached defend the number and often win the trade-off.

PES is a stocking distributor. Our role on your federal solar bid is to deliver the documentation and quotes you need on the RFP calendar. Registered contractors on the Axis portal get:

• Solicitation-specific quote - pull a firm-price quote for every equipment line, valid through the RFP proposal validity period (typically 90–180 days), with freight to site included
• Country-of-origin documentation - per-SKU country-of-origin certificate, TAA status, BABA declaration where applicable, ready to attach to your Buy American / TAA / BABA certifications
• Datasheet package - PDF datasheets for every proposed product, formatted for easy inclusion as RFP appendices
• Warranty statements - manufacturer warranty terms attached as RFP appendices where required
• Environmental attribute pack - Energy Star, FEMP, EPEAT, ozone-non-depleting certifications required by many federal RFPs
• Lead-time commitment - a documented lead-time commitment per SKU, tied to the RFP schedule
• Freight and logistics plan - pallet freight quotes to the project site with LTL, TL, or drop-trailer options

Contractors who use the Axis portal's Solicitation Support workflow cut their equipment-side proposal-prep time by 50–70%. Instead of chasing OEM datasheets, country-of-origin certifications, and freight quotes across 10–15 vendors, they pull a bundled documentation pack in one export.

Sections L (Instructions to Offerors) and M (Evaluation Factors for Award) are where federal solicitations tell you exactly what to do and how you'll be graded. Contractors lose points on the same handful of traps, over and over:

• Page-limit violations. If Section L says the technical volume is 40 pages max, page 41 does not get read. Evaluators are instructed to stop. Font, margins, and figure treatment are usually specified too - miss the 11-point Times New Roman with 1" margins and your compact 40 pages become 55 pages when reformatted, and you lose the last third.
• Section-numbering mismatches. Section L usually specifies an outline. Match it exactly - including sub-numbering. Evaluators score against a scoring sheet keyed to the required outline. Non-matching outlines cause evaluators to hunt for content, and hunting turns into 'not found' during pass-throughs.
• Cross-referencing to appendices instead of writing in-line. Many solicitations say the evaluator won't count material in appendices toward the page count - which contractors take as license to shove content out of the technical volume. But Section M says evaluators score the technical volume, not the appendix. Appendices are supporting evidence, not narrative substitute.
• Missing 'shall' statements. RFP Sections C, L, and M use 'shall' when something is mandatory. Search your proposal for every 'shall' in the RFP and make sure you answered each one. A single missed 'shall' can trigger a 'material deficiency' finding.
• Silence on evaluation subfactors. Section M often lists subfactors under each main factor. If Section M lists three subfactors under 'Technical Approach' and you only address two, you get zero on the third - not a partial score.
• Ignoring the Small Business Subcontracting Plan. For solicitations expected to exceed $750,000 ($1.5M for construction), a Small Business Subcontracting Plan is often required from other-than-small primes. Missing plan = non-responsive. Small businesses are exempt but should still describe their supplier plan.

The remedy for all six is a compliance matrix - a two-column table where the left column lists every requirement from Section L and Section M and the right column names the section of your proposal that addresses it. Build the matrix before you start writing. Update it as you go. Attach it to the proposal (usually not counted against page limits when explicitly labeled a compliance matrix).