The FY26 federal year-end readiness checklist

The Opportunities tab matches open federal solicitations against your company’s own federal award history and labels why each one matched. Two of those match reasons are exactly this discipline: an Existing customer chip when the notice comes from a sub-agency that has awarded to you before, and an Existing office chip when it comes from the specific contracting office that has. Each chip carries your own award count and dollars with that buyer, so it is evidence rather than an assertion.

The office-level match is derived from the contract numbers in your own award history rather than a lookup table, which is why it can name a specific issuing office instead of stopping at the department. On a free account the same matches, with the same reason text, arrive in the weekly digest described under item 4 rather than on the tab.

The Contracts tab keeps a lifecycle monitor over your active portfolio, sorted by expiration urgency, with counts of what expires inside thirty and ninety days. The timeline reads the period of performance from the award record itself, including the potential end date when the record carries one. The Home page groups the same awards by end date, thirty days or less, thirty-one to ninety, ninety-one to a year, and beyond, per awarding agency, so the customers to call this month are visible before you open the tab.

Where the underlying award data does not state a potential end date, the timeline says so rather than estimating an option year. A guessed date is worse than a blank one when you are deciding which customer to call.

The Opportunity Requirements Package workflow takes a single SAM.gov notice and builds the requirement documents a response is assembled from. It pulls the notice’s published attachments, ranks them by what they are likely to contain rather than the order they happen to be listed in, reads what fits the budget, and states plainly which files it read and which it skipped.

It also adapts to what the notice actually is. A sources sought notice or a request for information gets a market research package rather than a compliance matrix it has no requirements to fill, and when such a notice carries no readable attachment the run says the requirement lives in the notice description it cannot fetch and asks for it, rather than guessing at a scope.

The weekly digest email leads with the opportunities matched to your company, in the same order the dashboard ranks them and with the same reason text on each, alongside the regulatory changes you are watching and, for a small business, the DoW SBIR/STTR topics that fit. It exists so the weekly check happens even in the week you do not log in.

It is strictly opt-in. Nothing is sent unless you turn it on in account settings, and a week with nothing to report sends nothing at all.

The Contract Mix card on the Contracts tab reads your portfolio for the two senses of contract type that matter, the pricing arrangement that drives FAR Part 31 and Part 42 exposure and the award vehicle, and reports the share of your work that is flexibly priced. The figures are reported over the share of contracts that actually state the field rather than assuming the rest match, so a sparse field reads as missing data and never as a portfolio without cost-type work.

Ledger Scan screens an uploaded general ledger against a FAR 31.205 unallowable term catalog that is generated from the regulation text and checked against it, and returns the transactions worth a second look with the matched term and its criteria attached to each one. Uploading and previewing a ledger and browsing the term catalog are on every account; the screen itself, and the analysis and workpapers drafted from what it finds, are Pro and Max.

It is deliberately modest about what it claims. A keyword screen surfaces candidates for review and says so on its own upload screen, and nothing it flags is a determination.

For each of your top matched notices, the Market Intelligence view builds a lane: who has won work under that NAICS and product or service code from that buyer, drawn live from federal spending data over a stated window, with your own position in the lane stated at the foot of the table and the incumbent named when the notice’s award record names one. Where the notice is a set-aside, the lane limits the winners to companies that have won under that set-aside when the data allows it. When it cannot, the panel labels the list as unrestricted rather than presenting every past winner as an eligible competitor.

It states its limit on the page rather than in a footnote. A lane reports who has won that work, which is an inference about likely competition, never a list of bidders on any open solicitation.