What is a task order?
A task order is an individual order for work placed against an existing IDIQ contract. The parent contract established terms, pricing, and eligibility. The task order is the work.
The equivalent term for supplies is a delivery order. The mechanics are the same, and public data uses both, which matters when you are counting a company’s order history.
Why this is the number that counts
Federal contracting produces two very different kinds of announcement, and they are routinely conflated.
The first is “company X has been awarded a place on a five-billion-dollar vehicle.” That means the company can now compete for orders under a contract whose ceiling, shared across all holders over its full life, is five billion.
The second is “company X received a forty-million-dollar task order.” That means the company has forty million dollars of actual work.
Only the second describes performance. The first describes eligibility. Any analysis of a federal contractor that does not keep these apart will produce numbers that are wrong by orders of magnitude — which is why this platform reports vehicle access separately from obligated dollars and never sums a ceiling into a company’s footprint.
Fair opportunity, and what competing actually looks like
On a multiple-award contract, each holder must be given a fair opportunity to be considered for orders above a small threshold, with defined exceptions — urgency, a logical follow-on to work already underway, a genuinely unique capability, or a need to satisfy the contract’s minimum.
In practice, competing for an order means responding to a solicitation with a technical approach, staffing, and pricing, on a compressed timeline, against the other holders. It is lighter than an open-market competition and it is not light. Companies that hold vehicles they cannot afford to bid on effectively do not hold them.
The protest limitation
Protests of individual orders are restricted, which is a deliberate design choice: the point of ordering against an existing vehicle is speed, and unlimited protest rights would defeat it.
The main available routes are a claim that the order exceeds the scope, period, or maximum value of the underlying contract, and a protest at the Government Accountability Office for orders above a dollar threshold that differs between defense and civilian agencies. Below those thresholds, and outside the scope argument, an unsuccessful offeror generally has no forum.
The practical consequence is that scope arguments carry disproportionate weight in order-level disputes, and agencies pay close attention to keeping orders inside the four corners of the vehicle.
Reading order history
Order-level data is public, and it is the most informative thing available about a federal contractor. Four things worth reading from it:
- Recency. Orders three years old describe a former customer.
- Agency concentration. One agency supplying nearly all order volume is a business with a single point of failure.
- Order size distribution. Many small orders and a few large ones describe very different businesses.
- Recompete exposure. Orders approaching the end of their period of performance are the ones a competitor is already preparing for.
One structural caveat applies to all of it: federal obligation reporting carries a standard lag of roughly ninety days, so a very recent award may not appear in any public dataset yet — including this one. That is a limit of the source, and it is better stated than glossed over.