Winning the vehicle is not winning the work
There’s a moment of relief when a small shop lands its first IDIQ or gets onto a GSA Schedule — the multi-year effort of getting qualified to bid is finally done. Then reality sets in: the vehicle itself carries no guaranteed dollars. An Indefinite-Delivery/Indefinite-Quantity contract, a GSA Multiple Award Schedule, a BPA — these are hunting licenses, not kills. The actual revenue arrives as a stream of task orders and delivery orders issued against the vehicle over its life, often across several years, frequently competed among the vehicle’s awardees. Win the vehicle and celebrate for an afternoon; then realize you now have a second, ongoing pipeline to run — the one that turns the license into money.
This is where a lot of small GovCon shops quietly leak revenue. They tracked the pursuit that won the vehicle with real discipline — capture, bid-no-bid, the proposal — and then treated the vehicle as a finish line. Task orders drop with short response windows, recompetes sneak up, and options quietly expire, all because the whole thing lived in someone’s head or a spreadsheet nobody refreshed. The fix is to model the vehicle-and-its-orders as the two-tier structure it actually is.
Model the vehicle as a parent, task orders as its children
The mental shift is to stop thinking of a contract vehicle as a single deal and start thinking of it as a container for many deals. The vehicle is the parent: the IDIQ or Schedule you hold, with its ceiling, its period of performance, its ordering rules, and its list of competing awardees. Each task order is a child pursuit inside it, with its own scope, its own response deadline, its own win-probability, and its own competition — sometimes all awardees, sometimes a small on-ramp subset.
In practice that means each active task-order opportunity moves through its own compact pipeline — something like Anticipated → RFQ Released → Bidding → Submitted → Won/Lost — while the vehicle sits above them as the account they all roll up to. Your pipeline reports then answer two different questions at once: "how much task-order revenue is in flight right now?" and "which vehicles are actually producing versus sitting idle?" A vehicle that’s issued zero orders in a year is a different problem than a vehicle you’re losing every order on, and only a two-tier model lets you tell them apart.
The task-order clock is faster and more merciless
A new-contract pursuit gives you the long GovCon runway — months of capture before anything is biddable. Task orders are the opposite: an RFQ against an existing vehicle can land with a response window of days, because the qualification work was supposed to be done up front when you won the vehicle. Miss the window and you don’t just lose the order — you signal to the ordering office that you’re not a reliable responder, which quietly shrinks your share of the next several orders too.
That compressed clock is exactly where a CRM earns its keep over a spreadsheet. The instant a task order is anticipated — often you’ll hear about it before the RFQ formally drops — it should become a pursuit with a task to watch for the solicitation, and the moment the RFQ lands, an automation can materialize the standard response checklist: confirm scope fit, check labor categories and rates, draft the quote, submit before the cutoff. This is speed-to-lead discipline applied to a stream of small, fast pursuits, and it’s the difference between a vehicle that pays for itself and one that becomes an expensive certificate on the wall.
Options and recompetes are the deadlines that hurt most
Two dates matter more than any single task order, and both are easy to sleepwalk past. The first is the option-year decision — most vehicles and the orders under them run in a base period plus option years, and each option is a moment where the customer chooses to continue or not. The second is the recompete: every vehicle eventually ends and gets re-competed, and if you learn about your incumbent recompete when the draft RFP drops, you’ve already lost the year of positioning you needed.
Both are just immovable dates — the same calendar discipline every GovCon pursuit lives on — and both should be tasks with enough lead time to act, not entries you hope someone remembers. A recompete task set to fire twelve to eighteen months before period-of-performance end turns "we got surprised by our own recompete" into "we started capture on our incumbent position a year out," which is precisely the advantage incumbency is supposed to give you. Feeding those outcomes back through win-loss analysis tells you, over time, which vehicles are worth chasing an on-ramp onto and which are dead weight.
Rates and labor categories are pursuit data, not afterthoughts
Task-order competitions on a vehicle are frequently won or lost on price within pre-negotiated labor categories, which means your rates and category mappings are recurring pursuit data you’ll reference on every order. Keeping which labor categories you hold, and at what ceiling rates, attached to the vehicle record — the same data-hygiene instinct that keeps contacts clean — means every task-order response starts from a known baseline instead of a scramble through old award documents. It also lets you spot the orders you’re structurally unable to win before you waste effort quoting them, which is bid-no-bid applied at task-order speed.
Run the whole two-tier game in one system
In Hitt CRM, a contract vehicle becomes the account that all its task orders roll up to, each order a pursuit on a pipeline with its own deadline and win-probability, and the contracting and ordering officers who run it captured as contacts on a shared timeline that outlives the multi-year vehicle. Tags and properties mark the vehicle type, the agency, and your labor categories so a segment can surface "every active RFQ we haven’t quoted" or "every vehicle with a recompete inside 18 months" in a click. Automations drop the response checklist the moment an RFQ posts and fire the option-year and recompete reminders on schedule, while reports show your true task-order win rate by vehicle — the number that tells you which hunting licenses are actually feeding you and which to let lapse. The vehicle is the license; the CRM is how you turn it into a stream of orders you never let slip.
The one-sentence version
An IDIQ or GSA Schedule is a hunting license, not revenue, so model the vehicle as a parent account with each task order as a fast-clock child pursuit under it, treat option-year and recompete dates as lead-time tasks an automation fires so your own incumbency never surprises you, keep your labor categories and rates as reusable pursuit data, and run the whole two-tier stream through one CRM so no order drops past you and no recompete sneaks up while you were busy celebrating the vehicle you already won.