An agency letter of support is a written, signed statement from an authorized federal ordering official demonstrating a genuine, specific need for your company on the GSA Schedule. Under recent MAS solicitation refreshes, more Springboard and FASt Lane applicants are being asked to produce one. It cannot come from you, it cannot be boilerplate, and you cannot generate it on short notice — so the request has to start early.
I spent eighteen years in federal acquisition as a Contracting Specialist and Contracting Officer at GSA, IRS, DoD, and DOI, with a FAC-C Level III and a Harvard M.S. Across our 70+ proven GSA Schedule awards, I have read a lot of agency justifications from the reviewing side of the desk. The ones that worked were specific and true. The generic ones got spotted immediately. Here is how to get a letter that holds up.
What is an agency letter of support and who has to sign it?
It is a letter, written and signed by an authorized federal agency ordering official, that shows GSA a real requirement exists and that your company is tied to it. It cannot be written by you or signed by you. GSA is not looking for a general endorsement or a "we like working with them" note — it wants evidence of a specific, current government need.
This requirement grew out of the recent refreshes that tightened the young-company on-ramp — the same changes covered in our breakdown of how Refresh 31 and 32 reshaped the Springboard path. What used to be an informal courtesy is now, in certain circumstances, a documented prerequisite.
What must the letter actually say?
The letter must connect a specific agency requirement to your specific company, with enough detail that a GSA reviewer can verify it is real. Four elements make or break it: the requirement, the reason it is you, the timeline, and a signature from someone with the authority to make the ask.
- The requirement: a specific IT requirement or program the agency has, ideally referencing the relevant SIN(s).
- Why you specifically: prior performance, specialized capability, an existing working relationship, or being the intended source for an upcoming opportunity.
- The timeline or urgency: the operational, mission, or statutory driver behind the request.
- Authority and contact: official letterhead, signed by an authorized agency official, with their contact information included.
| A strong letter… | A weak letter… |
|---|---|
| Names a specific requirement and SIN | Speaks generally about "IT services" |
| Explains why this company is the intended source | Offers a vague endorsement of the company |
| States a real timeline or deadline | Omits any sense of urgency |
| Is signed by an authorized official on letterhead | Comes from someone without ordering authority |
When I was reviewing these as a Contracting Specialist, vague or boilerplate language undermined credibility instantly. The justification has to be true and specific to your situation. GSA has seen enough of these to recognize a generic ask on sight.
What is the fastest way to get an agency to write it?
Do not ask a busy agency contact to draft a letter cold. Most have never written one and will not know the format GSA expects. The approach that works: send a short note explaining what is needed and why, with a draft letter they can edit, put on letterhead, and sign. You are asking them to review and approve — not to author a legal document.
- Explain the ask in two sentences — what the letter does and why it helps the agency get you in place faster.
- Attach a ready-to-edit draft so the lift on their end is minutes, not hours.
- Offer a call for anyone who would rather talk it through than edit a document.
- Follow up on their timeline, not yours — this is a favor that depends on the relationship.
What does a sample outreach email look like?
Keep it short, make the ask concrete, and hand them the draft. Here is a template you can adapt.
Subject: Request for FASt Lane Sponsorship Letter — [Client Company Name]
Hi [Agency Contact Name],
Following up on our discussion regarding [project/requirement name], I wanted to check on the possibility of using GSA's FASt Lane program to help us move faster on getting this in place under our GSA Schedule.
FASt Lane requires a short written request from your office confirming a compelling need for [Client Company Name] specifically to support this requirement — this lets GSA expedite our [new offer / modification] instead of going through the standard timeline. To make this easy on your end, I've drafted a short letter below that you're welcome to edit, put on your office's letterhead, and sign — or rework however works best for you.
Happy to jump on a call if that's easier. Thanks for the support. — [Client Name], [Title, Company], [Phone / Email]
What does a sample draft letter look like?
Give the agency a fill-in-the-blanks draft that already contains every element GSA looks for. Every bracketed detail must reflect something actually true.
[Agency Name / Office] — [Address] — [Date]
To: General Services Administration, [IT Large Category Contracting Officer / FASt Lane review team]
Subject: Request for FASt Lane Sponsorship — [Client Company Name], GSA Contract No. [XXX, if applicable]
[Agency Name] has an ongoing/upcoming requirement for [brief description of the IT requirement — e.g., cloud services, cybersecurity support], specifically under SIN [SIN number(s)].
[Client Company Name] has been identified to support this requirement based on [reason — e.g., prior successful performance, specialized capability, sole viable source, existing task order relationship]. Given [the operational timeline / mission-critical nature / statutory deadline] associated with this requirement, [Agency Name] requests that GSA consider [Client Company Name]'s [new offer / modification] for expedited processing under the FASt Lane program.
Please contact [Agency POC Name, Title, Email, Phone] with any questions. Sincerely, [Agency Official Name], [Title], [Agency Name].
What two things must you get right before sending it?
First, every bracketed detail must be true — do not write "sole viable source" if that is not accurate, because GSA reviewers are specifically evaluating whether the justification is genuine. Second, have your GSA Contracting Officer or Contract Specialist glance at the final version before it goes out.
Requirements around this letter have shifted with each recent refresh. A quick check with your CO or CS confirms the letter still matches what reviewers currently expect — before you spend your one shot at the agency relationship on a version that is already out of date. You can read the current MAS solicitation language on SAM.gov and the FASt Lane program details on gsa.gov.
Why is the relationship the real bottleneck, not the letter?
The letter itself is simple once you have the relationship. The hard part is having an agency contact willing to put their name on it. That willingness is built through prior performance, market research calls, and capability briefings — not manufactured under a submission deadline.
From the CO seat, the single best predictor of whether a company could produce a credible letter was whether it had a genuine working relationship before it needed one. If you are pursuing FASt Lane or a Springboard path that may require this, start the agency conversation now — well before a deadline forces it. The same relationship-first logic drives our guidance for small businesses and JVs in what GSA's shifting rules mean for mentor-protégé teams.
What Should You Do Now?
- Confirm you actually need the letter — it applies to certain Springboard and FASt Lane situations, not every application. Check with your CO or CS.
- Identify the right signer — an authorized agency ordering official with real knowledge of the requirement.
- Send a draft, not a blank request — hand them a ready-to-edit letter and outreach note.
- Verify every bracketed claim is true before it goes out; a false "sole source" statement is worse than no letter.
- Have your CO or CS review the final version against current refresh requirements before you send.
- Build the relationship early — the letter is easy; the willingness behind it is not.
Frequently Asked Questions
Can I write my own agency letter of support?
No. The letter must be written and signed by an authorized federal agency ordering official. You can, and should, provide a ready-to-edit draft to make it easy — but the agency has to review, approve, and sign it on official letterhead.
What makes a letter of support credible to GSA?
Specificity. Name the requirement and SIN, explain why your company is the intended source, state a real timeline, and have it signed by someone with ordering authority. Vague or boilerplate language undermines credibility, and reviewers are trained to spot a generic ask.
Do all Springboard and FASt Lane applicants need this letter?
No. It applies in certain circumstances, generally when your application is tied to a specific upcoming agency opportunity. Because you cannot produce one quickly, confirm whether it applies with your Contracting Officer early rather than assuming it does not.
How early should I start the letter conversation?
Well before any submission deadline. The letter depends on an agency contact willing to sign it, and that willingness rests on an existing relationship. Cold-asking under deadline pressure is the slowest and weakest path.
Should my Contracting Officer review the letter before it is sent?
Yes. Requirements have shifted with each recent refresh, so a quick review by your CO or Contract Specialist confirms the letter still matches current expectations before you spend your one shot at the agency relationship.
What if the agency relationship does not exist yet?
Then that is the real work — build it through market research calls, capability briefings, industry days, or existing past performance. A letter of support is only as strong as the relationship it comes from, and no template substitutes for that.
If you need help deciding whether a letter applies to your offer and drafting one that survives GSA review, that is exactly what we do — start at our GSA Schedule services page.