Every firm that decides to pursue a GSA Schedule asks the same first question: how long does the application take. GSA’s own answer is one unhelpful sentence, several weeks to months, and the honest range depends on the offer. The better question is what GSA is checking before it awards, because the checks explain every document the solicitation demands, and they account for most of the offers that come back rejected.
Start with what the thing is. The Multiple Award Schedule runs on one big standing solicitation, 47QSMD20R0001, posted on SAM.gov and kept current through numbered refreshes. There is no application form in the sense that word usually carries. You are submitting an offer in response to a federal solicitation, and a GSA contracting officer evaluates it the way contracting officers evaluate offers: can this company perform, should the government accept these prices, and will this award hold up in a file read years from now. Getting on Schedule is winning a contract, not filling out a form, and each check below exists because someone at GSA has to sign a determination saying you passed it.
Six checks decide the outcome. Take them in the order the reviewer meets them.
What the corporate experience check is really asking
GSA’s stated prerequisites begin with time: at least two years in business. That is also the baseline we hold clients to, alongside a revenue floor, and the two years are not about age for its own sake. They are about the existence of a record. A company that has operated for two years has financial statements that describe something, projects that started and finished, customers who can be called and asked. The corporate experience narrative in your offer walks the reviewer through that record: what the company does, how it is organized, who runs it, and what resources it can put behind a federal order that arrives with a deadline attached.
There is an exception for younger companies, and it is narrower than the people selling it tend to mention. Startup Springboard lets a qualifying firm substitute the professional experience of its executives and key personnel for the corporate track record the company itself cannot show yet. GSA currently describes it as available only to offers in the Information Technology large category that are agency-sponsored and participating in a FASt-lane initiative. If that is not your firm, the two years stand, and the productive move is to spend them building the record the offer will eventually need rather than drafting around its absence.
Financial responsibility and the ability-to-perform review
The FAR bars award to anyone but a responsible prospective contractor. FAR 9.103 states the rule, and FAR 9.104-1 makes adequate financial resources, or the ability to obtain them, the first standard on the list. That is the authority behind the financial statements the solicitation asks for, and it is the frame the reviewer reads them in. The question is not whether the business looks impressive. The question is whether the company can carry payroll and payables through the gap between performing a federal order and being paid for it, and keep doing so for the life of a long contract.
Marginal financials do not automatically end the offer. They generate work: requests for explanation, interim statements, evidence of a credit line, sometimes a fuller responsibility review before anyone will sign. The fatal version is the unexplained anomaly. A losing year with a one-paragraph explanation attached is a data point. The same year sitting silent in the statements is a doubt, and a reviewer who has to resolve a doubt without your help resolves it defensively. Pass-through structures deserve the same treatment: an S corporation that distributes its profit every year can look threadbare on a balance sheet while the underlying business is healthy, and nobody but you is going to make that argument in the file.
Past performance against the SINs you offer
The past performance section is not a trophy shelf. It is evidence, and it gets read against a narrow question: do this company’s completed projects resemble the work sold under the Special Item Numbers it is offering. The solicitation asks for relevant experience narratives, project descriptions with enough detail to evaluate, and references who will actually respond when contacted. Federal customers are not required. Commercial work counts, provided the narrative describes it in terms a stranger can weigh: what was delivered, over what period, at what rough scale, for what kind of customer.
The common failure is writing for size instead of relevance. A project description inflated to sound large but detached from the scope of the SIN it supposedly supports reads, to a reviewer, like a project that does not fit. Two paragraphs of specific delivery under the right SIN beat two pages of adjectives, every time the file is read by someone whose job is matching evidence to scope. The references matter for the same reason. A named contact who confirms the narrative closes the question. A reference who never answers leaves it open, and open questions do not resolve in your favor at this stage.
The SIN fit is the offer’s load-bearing decision
Special Item Numbers are the shelf labels of the federal catalog. FAR 8.401 defines a SIN as a grouping of generically similar, but not identical, supplies or services, and everything downstream is organized by them: eBuy scopes every RFQ to specific SINs, buyers search by them, and your awarded SIN list determines which requirements you can even see. The central decision inside the offer is which shelves to claim.
Claiming shelves your record cannot support is the self-inflicted rejection. Reviewers map your projects and your pricing to each SIN offered, one at a time. A SIN with no experience behind it and no priced items that fit invites removal of that SIN, and enough of them invites rejection of the whole offer, because a catalog assembled from ambition rather than from record tells the reviewer something about everything else in the file. The discipline cuts the other way too. The awarded SIN list defines what you can sell through this contract for as long as you hold it, up to twenty years. Modifications exist to add SINs later, and they cost time and carry their own support package, a small offer inside your contract. Offer narrow and true, then widen from evidence.
“In my ordering years on the government side, I could tell within a page which catalogs had been built to win the Schedule and which had been built to win an order. The awarded SINs read like ambition, the labor categories did not map to the work in front of me, and the price had no room left to move. Those quotes were easy to set aside, and the vendor usually never learned why, because no Part 15 debriefing machinery exists at the order level to tell them.”
Pricing support that can survive a negotiation
Before award, GSA has to determine that your prices are fair and reasonable, and the solicitation has carried two instruments for getting there. The older track is the Commercial Sales Practices disclosure: you report the discounts you give commercial customers, GSA identifies the customer or category of customer whose deal anchors yours, and your Schedule price gets negotiated against that relationship. The newer track is Transactional Data Reporting, where the analysis leans on order-level sales data reported monthly instead of a disclosure of your commercial dealing. GSA now states that TDR is mandatory for all MAS SINs, so a new offeror should expect to price under that regime. The underlying demand is the same on either track: show your support.
Support means documents. Invoices at the rates you are proposing. A published price list, if one exists. Awarded contract rates, signed quote sheets, market data for the labor categories offered. The pricing narrative connects those documents to the proposed prices, and it has to survive contact with a negotiator whose job is to counter it. Narratives that cannot, die exactly there: a rate nobody has ever actually paid, a discount structure the invoices contradict, a price list created the week of submission. One constraint from the ordering side belongs in the spreadsheet from day one. The awarded price is a ceiling, and FAR 8.405-4 obliges ordering activities to seek a further reduction on orders above the simplified acquisition threshold. A ceiling negotiated at the floor of what your books can defend leaves nothing to give when that request arrives.
The compliance floor
None of the above gets read if the basics fail. Your SAM.gov registration has to be active, current, and consistent with the offer: same legal name, same UEI, representations and certifications complete and matching what the proposal claims about size and status. Reviewers check the public record against the file you submitted, and a mismatch is a return, not a conversation. If the registration itself is shaky, repair it before you draft anything; it is a distinct piece of work, and we treat SAM registration as its own engagement for that reason.
Products carry one more gate. Schedule contracts include the Trade Agreements clause at FAR 52.225-5, which limits the catalog to U.S.-made or designated country end products. A product line manufactured outside that list does not belong in the offer, and discovering the problem after submission is an expensive way to map your own supply chain.
Where offers die
Rejections cluster in four places, and none of them is exotic.
Unsupported pricing. The proposed rates have no invoices behind them, or the support contradicts the narrative built on top of it.
Thin experience under the chosen SINs. The projects are real, but they belong to different shelves than the ones claimed.
Financials that raise a question nobody pre-answered. The reviewer found the anomaly before you explained it, and the explanation now reads as damage control.
Inconsistency between the offer and the public record. The SAM registration, the website, the state filing, and the proposal describe four slightly different companies, and the reviewer is not obligated to guess which one is real.
The honest gate: who should not apply yet
The checks above are GSA’s gate. There is a second gate GSA will not run for you. An awarded Schedule is a hunting license, not a contract: it settles your prices, terms and clauses so buyers can reach you quickly, and it buys nothing by itself. We wrote a full companion piece on how orders actually flow under a Schedule, and its logic bears directly on the application decision. If you cannot name the offices that buy your category through the Schedule, passing every check in this article still leaves you holding a maintenance obligation: sales reporting, catalog upkeep, mass modifications, and a minimum sales requirement the contract can be lost for missing. The pipeline question deserves an answer before the paperwork question does.
The same honesty applies to the checks themselves. If your record cannot support the SINs you want, or your financials cannot stand a stranger’s reading, the fix is not better proposal writing. The fix is months of running the business in the direction of the record you need, and submitting before then spends real effort establishing the weakness in a government file.
When the record is there, the remaining work is assembly: a SIN map drawn from projects that support it, pricing tied to invoices that agree with it, the financial story told before anyone has to ask. That assembly, from eligibility review through SIN selection, pricing strategy, and negotiation with GSA, is what our GSA Schedule practice does. What GSA checks is knowable in advance. Offers fail when nobody read the solicitation the way a contracting officer will, and that is the cheapest problem in federal contracting to fix before it happens.