Federal fiscal year end: getting IT ordered before September 30

Why September is the busiest month in federal IT

Most of the money that buys end-user hardware in a federal agency is one-year money. Operations and maintenance appropriations are available for obligation during a single fiscal year, and whatever is still unobligated at midnight on September 30 stops being available for new work. That single fact drives the entire fourth-quarter pattern: a requirement that sat unfunded in March suddenly has cover in August, and a program office that has been patient all year becomes very impatient in the space of about six weeks.

This is not waste and it is not a loophole. It is what happens when an agency finally knows what is left after the year's real emergencies have been paid for. But it does compress a normal procurement into a short window, and compressed procurements fail in predictable, avoidable ways.

Two rules are worth naming so you can talk to your contracting officer in their own language. Funds must be obligated within their period of availability, and the bona fide needs rule generally requires that a fiscal year's appropriation be used for a need arising in that fiscal year. How those apply to a specific order — particularly one that will not be delivered until the next fiscal year — is a determination for your contracting and finance offices, not for a vendor. Ask the question early and get the answer in writing.

Work backward from September 30, not forward from today

The single most useful thing you can do in July is build the calendar in reverse. Every year-end program that lands on time has roughly this shape:

• Through the end of July — lock the requirement. Model, memory, storage, operating system image, dock, warranty term, accessories. Not "about forty laptops." An exact configuration with quantities. A requirement that is still moving in August will not be quoted, approved and obligated in September.
• Late July into early August — get quotes in hand. Real quotes, with part numbers, current lead times, and a stated validity period. If the quote expires before your approval chain finishes, you will be re-quoting in the worst week of the year.
• August — route approvals and certify funds. This is where the calendar is actually consumed. Security review, funding certification, contracting review, and any approval your agency layers on top. Assume every step takes longer than it did in February, because everyone else is doing the same thing.
• First half of September — obligate. Award the order, accept the quote, run the card. The order should exist as a binding obligation with two weeks of margin, not two days.
• Mid-September onward — stock only. By this point the honest options are configurations sitting in distribution today. Anything build-to-order is a gamble.

If your refresh is larger than a single order, the sequencing advice in our federal PC refresh playbook applies here too — pilot the configuration early so you are not validating a dock behavior in the last week of the fiscal year.

Obligation and delivery are different things

A great deal of year-end confusion comes from conflating the moment funds are obligated with the moment hardware arrives on the loading dock. For appropriations purposes what matters is a valid, binding obligation recorded within the period of availability. Delivery in October does not by itself make a September obligation improper — but whether a particular buy is consistent with the bona fide needs rule is a determination your contracting officer makes, and the answer depends on the facts of the requirement.

What that means practically: do not let a program manager assume "we have to have it by the 30th" when the real requirement is "we have to be obligated by the 30th." Those two statements produce completely different shopping lists. The first one eliminates every configuration with a lead time. The second one keeps your options open. Settle which one is true before you start pricing.

What actually blocks a year-end order

In our experience the order that dies in September is almost never blocked by price. It is blocked by one of these:

• An unconfirmed configuration. Somebody still has not decided on the memory tier or the dock, so the quote keeps changing and the approval package cannot be finalized.
• Compliance confirmed too late. TAA status and Section 889 representations are configuration- and order-specific, not brand-level facts. If your requirement carries those clauses, they belong in the first quote request, not in a frantic email on September 24. We confirm country of origin and applicable representations per line at quote time, and we will flag any line that cannot meet a stated requirement rather than substituting quietly.
• Stock and allocation. Fourth quarter is when everyone in the federal market wants the same popular configurations. Availability moves daily, and a quote priced against stock on Monday can be a build-to-order line by Thursday.
• Administrative gaps. Expired SAM registration, a remit-to address that does not match, a WAWF (PIEE) setup nobody has tested, a card with a single-purchase limit below the order value. Each of these is trivial in June and fatal in late September.
• A quote that expired. Pricing and lead-time validity are finite. Ask for the validity window in writing and re-confirm before the approval package goes out.

Structuring a fast, defensible small buy

For most end-user hardware, the fastest legitimate paths at year end are a purchase-card micro-purchase or a simplified acquisition under FAR Part 13. Both are designed for speed, and both are perfectly defensible when documented properly.

A few points worth getting right. The micro-purchase threshold and the simplified acquisition threshold are both defined in FAR 2.101 and are periodically adjusted for inflation — do not plan around a figure you memorized, confirm the current numbers in the FAR before you scope the buy. Splitting a requirement into multiple actions to stay under a threshold is prohibited (see FAR 13.003(c)), and it is exactly the sort of thing that surfaces in a year-end review. FAR 13.104 asks you to promote competition to the maximum extent practicable, which in practice usually means obtaining and documenting quotes from more than one source.

Your file should end up holding the requirement, the quotes you obtained, a price-reasonableness determination, and the compliance confirmations that attach to the buy. That package is what makes a fast order survive scrutiny in November.

Uniqcli holds no contract vehicles. What we can transact today is the Government Purchase Card, simplified acquisition and standard FAR purchase orders, quote responses on GSA eBuy, and WAWF invoicing through PIEE. The GSA MAS application is underway. If your agency requires a vehicle we are not on, tell us early and we will tell you plainly rather than burning your September. The federal buying page lays out exactly how each of those paths works on our side.

What we can and cannot promise on lead time

We can tell you what a configuration's lead time looks like the day we quote it, and we can tell you which lines are sitting in distribution now versus built to order. We cannot guarantee a delivery date, and any reseller who does at the end of Q4 is telling you something they do not control. Freight, allocation and factory schedules all move.

The way to manage that honestly is to prefer stock-configured models for anything that must land quickly, keep a second acceptable configuration approved as an alternate, and re-confirm availability the day before you obligate rather than relying on a quote from three weeks earlier.

A September checklist

• Requirement frozen as an exact bill of materials with quantities
• Confirmed whether the deadline is obligation or delivery, in writing
• Compliance clauses named in the quote request from day one
• At least two quotes obtained and documented, with validity dates
• Card limits, SAM registration and WAWF setup verified this month
• An approved alternate configuration on file in case of allocation
• Availability re-confirmed within 24 hours of placing the order

Build the configuration once and reuse it — our BOM builder is the fastest way to turn a rough list into a fixed, quotable bill of materials with the dock, warranty and accessories attached.

If you are working a year-end requirement now, send us the configuration, the quantities and your target obligation date. We will come back with current pricing, honest lead times and per-line compliance confirmation, and we will tell you if the date is not achievable rather than letting you find out on September 29. Start a year-end quote.