Three different dates that look the same. What can be compressed, what can't, and how to make yourself a real partner in the schedule.
"We need it by Friday" isn't an acquisition timeline. It might be true. It might be a preference. It might be a funding panic wearing a mission hat. The acquisition team has to know which one it is before anyone can build a schedule.
One framing change before we start: you are part of the acquisition team. Once a requirement leaves your office, the schedule is something you build with contracting. The customers who get the best timelines show up as partners with their part of the work already done. Shouting doesn't make the calendar move faster.
This lesson teaches you how to explain the need date, reverse-plan the acquisition, spot what can actually compress, recognize when the schedule genuinely flexes, and track your contracts so the next one doesn't become a bridge.
Most schedule fights start because everyone says "need date" but means something different. Separate the dates before the package hits contracting.
The date the office wants the thing in hand. It may be real, but by itself it doesn't explain the mission consequence.
The date tied to the mission event, inspection, outage, deployment, school start, funding law, or operational consequence.
The date the CO must award the contract or order so the vendor has enough time to deliver, mobilize, transition, or perform.
The acquisition usually has to award before the need date. Sometimes far before it. If you need a contractor fully performing on 1 October, the award may need to happen in August so the contractor can hire, clear people, transition, order materials, or stand up systems.
Customers often see the timeline as "send package, get contract." Contracting sees a chain of decisions that each require facts. The CO has to choose a path, make sure the package supports it, solicit the market, answer questions, evaluate responses, document the decision, and award a contract that can survive review.
That process is how the Government avoids buying the wrong thing, excluding the wrong vendors, using the wrong funds, skipping required approvals, or awarding something nobody can administer. The schedule pays for defensibility.
The CO asks for time because every shortcut has a file consequence. Some shortcuts are legal and smart. Some are protest bait. Some create an unauthorized commitment. The timeline conversation is how you tell the difference.
Every acquisition is different, but most customer packages move through the same basic phases.
The customer doesn't own all of those steps, but the customer can slow almost all of them down by sending a vague requirement, missing POCs, fuzzy funding, or a fake need date. The good news: the customer can also speed almost all of them up. We'll get to that in section 06.
Start with the date the mission actually needs performance, then work backward. Don't start with the day you remembered to send the package.
| Question | What to ask | Why it matters |
|---|---|---|
| Mission date | What event or consequence makes this date real? | If the date isn't tied to a mission consequence, it's probably a preference, not a need. |
| Performance start | Does the contractor have to be fully performing by that date, or just awarded by then? | Award isn't the same as readiness. Services often need transition time. |
| Vendor lead time | How long does industry need for production, shipping, onboarding, hiring, clearance, or mobilization? | The Government can't compress lead time the vendor physically needs. |
| Government lead time | What approvals, security reviews, IT reviews, legal reviews, or funding actions happen before award? | Hidden reviews are where schedules go to disappear. |
| Solicitation time | How long does industry need to respond well? | If you give vendors a rushed response window, you may get fewer quotes, worse pricing, or weak technical submissions. |
| Evaluation time | Who evaluates, how complex is the review, and when are those people available? | Customer evaluators can become the bottleneck if they aren't reserved early. |
Once those answers exist, the PALT Builder can turn them into a rough milestone schedule. The tool is useful because it makes the trade visible: every late input pushes a downstream date unless something else gets compressed.
Some parts of an acquisition timeline can move. Some can't. Knowing which is which keeps you from asking the CO to do something that won't actually save time.
Fast meetings, dedicated reviewers, same-day answers, leadership priority, and clean customer availability can reduce churn.
Short deadlines can work for simple buys or known markets, but they weaken competition when the requirement is complex.
Manufacturing, shipping, hiring, clearance, badging, network approval, and transition usually take the time they take.
Urgency can change the strategy when facts support it. The next section covers what real emergencies look like and what tools the system has for them.
Late planning isn't automatically urgent and compelling. A real emergency may justify faster or restricted action. A normal requirement that sat in the inbox for two months usually doesn't.
Funding expiration isn't the same as mission urgency. Expiring funds create pressure, but they don't erase competition, documentation, or bona fide need concerns.
Compressing the timeline isn't just contracting's job. Most of the levers that actually move the schedule sit on the customer side. Here's what helps.
You can't shorten vendor lead time or skip required approvals. But you control the time before, around, and after each contracting step. That time adds up to weeks. Sometimes months.
Real emergencies happen. An oil spill on the flight line. A building fire. A flood. A hurricane. A pandemic. A cyber incident that takes a system down. These are true urgent and compelling situations, and the system has paths for them.
When the situation is real, the acquisition team has tools:
What separates a real emergency from a procrastination crisis is the facts in the file. A genuine emergency has timestamps, witness statements, photos, mission impact analysis, and a clear story of what happened. A procrastination crisis has stress.
Call your CO immediately. Don't wait for the package to be perfect. Bring whatever facts you have and let contracting shape the response in real time. The earlier they know what's happening, the more options they have. Waiting until you've drafted a clean package is exactly the wrong move when something is on fire.
You are part of the acquisition team. That means tracking what you've already bought.
Most customer offices know they have contracts. Few of them can answer, on the spot:
Your contracting office tries to track this for every contract on the facility. They're also writing new contracts, processing modifications, doing market research, training CORs, and putting out the day's fires. They can't be the only people watching your contracts. They will miss things. Not because they're bad at their jobs — because the volume is too much for one office to be the sole source of truth on every action.
When you track your own portfolio, you can:
A spreadsheet works. Columns: contract number, vendor, ceiling value, current obligated value, period of performance start and end, option exercise dates, COR name and training status, last file review date, notes. Update quarterly. Send your CO a copy when something changes. They will love you, and the next acquisition will start three months earlier than it would have otherwise.
These are the phrases that should make the customer pause before sending the package as "ready."
A schedule-ready package doesn't just list a date. It explains the date.
Send the date and the story behind the date. "Need by 30 September" is weak. "Need contractor fully performing by 30 September because the current contract expires that day and the help desk supports 1,200 users with no organic backup" gives the CO something real to plan around.
If you have a real need date, run the schedule through the PALT Builder and see what has to happen before award. If the timeline is already tight, run the package through Preflight so the missing pieces show up before contracting has to find them the hard way. If you're staring at a portfolio of contracts and don't have a tracker yet, build one this week. Quarter-hour now saves a quarter later.